From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ekaterina Esina <eesina@astralinux.ru>
Cc: Rob Springer <rspringer@google.com>,
Todd Poynor <toddpoynor@google.com>,
Ben Chan <benchan@chromium.org>, Richard Yeh <rcy@google.com>,
John Joseph <jnjoseph@google.com>, Simon Que <sque@chromium.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH 5.10] staging: gasket: interrupt: Clean interrupt_data after free
Date: Tue, 16 May 2023 13:02:15 +0200 [thread overview]
Message-ID: <2023051640-trustless-gluten-a7b8@gregkh> (raw)
In-Reply-To: <ba0ad96d-6515-66e3-e140-cd7c3999577e@astralinux.ru>
On Tue, May 16, 2023 at 01:44:06PM +0300, Ekaterina Esina wrote:
>
>
> On 15.05.2023 16:02, Greg Kroah-Hartman wrote:
> > On Mon, May 15, 2023 at 03:29:50PM +0300, Esina Ekaterina wrote:
> > > Add interrupt_data = NULL after kfree(interrupt_data) in
> > > gasket_interrupt_init. It is needed to avoid double free
> > > in gasket_interrupt_cleanup, there is a check for NULL
> > > before kfree(interrupt_data).
> > >
> > > Found by Astra Linux on behalf of Linux Verification Center
> > > (linuxtesting.org) with SVACE.
> > >
> > > Fixes: 9a69f5087ccc ("drivers/staging: Gasket driver framework + Apex driver")
> > > Signed-off-by: Esina Ekaterina <eesina@astralinux.ru>
> > > ---
> > > drivers/staging/gasket/gasket_interrupt.c | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/drivers/staging/gasket/gasket_interrupt.c b/drivers/staging/gasket/gasket_interrupt.c
> > > index 864342acfd86..48b664b9134a 100644
> > > --- a/drivers/staging/gasket/gasket_interrupt.c
> > > +++ b/drivers/staging/gasket/gasket_interrupt.c
> > > @@ -337,6 +337,7 @@ int gasket_interrupt_init(struct gasket_dev *gasket_dev)
> > > sizeof(*interrupt_data->eventfd_ctxs), GFP_KERNEL);
> > > if (!interrupt_data->eventfd_ctxs) {
> > > kfree(interrupt_data);
> > > + interrupt_data = NULL;
> > > return -ENOMEM;
> > > }
> > > @@ -346,6 +347,7 @@ int gasket_interrupt_init(struct gasket_dev *gasket_dev)
> > > if (!interrupt_data->interrupt_counts) {
> > > kfree(interrupt_data->eventfd_ctxs);
> > > kfree(interrupt_data);
> > > + interrupt_data = NULL;
> > > return -ENOMEM;
> > > }
> > > --
> > > 2.40.1
> >
> > Also, your tool is wrong, this is not a correct fix at all.
> >
> > How did you test it? Why is your tool spitting out incorrect code? Why
> > are you not verifying it's output before asking others to do so?
> >
> > Please don't do this anymore, it's wasteful on our side, right? Please
> > take the time to review existing changes for problems, that would be
> > more useful overall to everyone.
> >
> > thanks,
> >
> > greg k-h
>
> I apologize, there is a mistake. It should've been
> gasket_dev->interrupt_data = NULL istead of interrupt_data = NULL
Which implies that your tools are broken, right? Please do better
testing before sending anymore patches.
greg k-h
prev parent reply other threads:[~2023-05-16 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 12:29 [PATCH 5.10] staging: gasket: interrupt: Clean interrupt_data after free Esina Ekaterina
2023-05-15 12:33 ` Greg KH
2023-05-15 13:02 ` Greg Kroah-Hartman
2023-05-16 10:44 ` Ekaterina Esina
2023-05-16 11:02 ` Greg Kroah-Hartman [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=2023051640-trustless-gluten-a7b8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=benchan@chromium.org \
--cc=eesina@astralinux.ru \
--cc=jnjoseph@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lvc-project@linuxtesting.org \
--cc=rcy@google.com \
--cc=rspringer@google.com \
--cc=sque@chromium.org \
--cc=toddpoynor@google.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