From: David Vernet <void@manifault.com>
To: Tom Rix <trix@redhat.com>
Cc: Joe Lawrence <joe.lawrence@redhat.com>,
jpoimboe@redhat.com, jikos@kernel.org, mbenes@suse.cz,
pmladek@suse.com, nathan@kernel.org, ndesaulniers@google.com,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v2] livepatch: Reorder to use before freeing a pointer
Date: Tue, 22 Mar 2022 23:21:27 -0400 [thread overview]
Message-ID: <20220323032127.3frjsh4iiclv4cys@user-VirtualBox> (raw)
In-Reply-To: <b4b347ea-5b12-223a-86f5-c13aee714f08@redhat.com>
> > On 3/19/22 9:51 PM, trix@redhat.com wrote:
> > > From: Tom Rix <trix@redhat.com>
> > >
> > > Clang static analysis reports this issue
> > > livepatch-shadow-fix1.c:113:2: warning: Use of
> > > memory after it is freed
> > > pr_info("%s: dummy @ %p, prevented leak @ %p\n",
> > > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > >
> > > The pointer is freed in the previous statement.
> > > Reorder the pr_info to report before the free.
> > >
> > > Similar issue in livepatch-shadow-fix2.c
> > >
> > > Signed-off-by: Tom Rix <trix@redhat.com>
> > > ---
> > > v2: Fix similar issue in livepatch-shadow-fix2.c
> > >
> > > samples/livepatch/livepatch-shadow-fix1.c | 2 +-
> > > samples/livepatch/livepatch-shadow-fix2.c | 2 +-
> > > 2 files changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/samples/livepatch/livepatch-shadow-fix1.c b/samples/livepatch/livepatch-shadow-fix1.c
> > > index 918ce17b43fda..6701641bf12d4 100644
> > > --- a/samples/livepatch/livepatch-shadow-fix1.c
> > > +++ b/samples/livepatch/livepatch-shadow-fix1.c
> > > @@ -109,9 +109,9 @@ static void livepatch_fix1_dummy_leak_dtor(void *obj, void *shadow_data)
> > > void *d = obj;
> > > int **shadow_leak = shadow_data;
> > > - kfree(*shadow_leak);
> > > pr_info("%s: dummy @ %p, prevented leak @ %p\n",
> > > __func__, d, *shadow_leak);
> > > + kfree(*shadow_leak);
> > > }
> > > static void livepatch_fix1_dummy_free(struct dummy *d)
> > > diff --git a/samples/livepatch/livepatch-shadow-fix2.c b/samples/livepatch/livepatch-shadow-fix2.c
> > > index 29fe5cd420472..361046a4f10cf 100644
> > > --- a/samples/livepatch/livepatch-shadow-fix2.c
> > > +++ b/samples/livepatch/livepatch-shadow-fix2.c
> > > @@ -61,9 +61,9 @@ static void livepatch_fix2_dummy_leak_dtor(void *obj, void *shadow_data)
> > > void *d = obj;
> > > int **shadow_leak = shadow_data;
> > > - kfree(*shadow_leak);
> > > pr_info("%s: dummy @ %p, prevented leak @ %p\n",
> > > __func__, d, *shadow_leak);
> > > + kfree(*shadow_leak);
> > > }
> > > static void livepatch_fix2_dummy_free(struct dummy *d)
Acked-by: David Vernet <void@manifault.com>
next prev parent reply other threads:[~2022-03-23 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 1:51 trix
2022-03-21 13:24 ` Petr Mladek
2022-03-21 13:39 ` Joe Lawrence
2022-03-21 14:05 ` Tom Rix
2022-03-23 3:21 ` David Vernet [this message]
2022-03-23 15:53 ` Petr Mladek
2022-03-23 16:17 ` Tom Rix
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=20220323032127.3frjsh4iiclv4cys@user-VirtualBox \
--to=void@manifault.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mbenes@suse.cz \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=pmladek@suse.com \
--cc=trix@redhat.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
all inboxes | Powered by JetHome®