From: David Marchand <david.marchand@redhat.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>,
"Kearney, Tadhg" <tadhg.kearney@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Hunt, David" <david.hunt@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"Macnamara, Chris" <chris.macnamara@intel.com>
Subject: Re: [PATCH] power: fix double free of opened files
Date: Mon, 14 Nov 2022 11:00:39 +0100 [thread overview]
Message-ID: <CAJFAV8yZk4n2PP1_thCr_jb2HPjqr4kG+QCnx=1EtRM4TVJF8w@mail.gmail.com> (raw)
In-Reply-To: <BYAPR11MB33660E2C66F64ADA9C875C8AFF3C9@BYAPR11MB3366.namprd11.prod.outlook.com>
On Mon, Nov 7, 2022 at 10:18 AM Pattan, Reshma <reshma.pattan@intel.com> wrote:
> > Fix double free of f_min and f_max by reverting the flcose() for f_min and
> > f_max. As f_min and f_max are stored for further use and closed in uncore
> > deinitialization.
> >
> > Fixes: b127e74 ("power: fix open file descriptors leak")
Please, use 12 chars format for commit hash, as documented.
git config alias.fixline "log -1 --abbrev=12 --format='Fixes: %h
(\"%s\")%nCc: %ae'"
> >
> > Signed-off-by: Tadhg Kearney <tadhg.kearney@intel.com>
> > ---
>
> Acked-by: Reshma Pattan <reshma.pattan@intel.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2022-11-14 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 8:29 [PATCH] power: fix resource leak by open file pointers Tadhg Kearney
2022-10-17 8:37 ` Pattan, Reshma
2022-10-26 21:30 ` Thomas Monjalon
2022-11-04 16:23 ` [PATCH] power: fix double free of opened files Tadhg Kearney
2022-11-07 9:17 ` Pattan, Reshma
2022-11-14 10:00 ` David Marchand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJFAV8yZk4n2PP1_thCr_jb2HPjqr4kG+QCnx=1EtRM4TVJF8w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=chris.macnamara@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=reshma.pattan@intel.com \
--cc=tadhg.kearney@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).