All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Jianglei Nie <niejianglei2021@163.com>,
	vgoyal@redhat.com, dyoung@redhat.com, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3] proc/vmcore: fix potential memory leak in vmcore_init()
Date: Tue, 12 Jul 2022 09:06:30 +0800	[thread overview]
Message-ID: <YszJFi+deSIXK3ns@MiWiFi-R3L-srv> (raw)
In-Reply-To: <YswVHNQX+OGz6IaQ@casper.infradead.org>

On 07/11/22 at 01:18pm, Matthew Wilcox wrote:
> On Mon, Jul 11, 2022 at 03:49:51PM +0800, Baoquan He wrote:
> > On 07/11/22 at 03:34pm, Jianglei Nie wrote:
> > > elfcorehdr_alloc() allocates a memory chunk for elfcorehdr_addr with
> > > kzalloc(). If is_vmcore_usable() returns false, elfcorehdr_addr is a
> > > predefined value. If parse_crash_elf_headers() occurs some error and
> > > returns a negetive value, the elfcorehdr_addr should be released with
> > > elfcorehdr_free().
> > > 
> > > We can fix by calling elfcorehdr_free() when parse_crash_elf_headers()
> > > fails.
> > > 
> > > Signed-off-by: Jianglei Nie <niejianglei2021@163.com>
> > > ---
> > >  fs/proc/vmcore.c | 5 ++++-
> > >  1 file changed, 4 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/fs/proc/vmcore.c b/fs/proc/vmcore.c
> > > index 4eaeb645e759..125efe63f281 100644
> > > --- a/fs/proc/vmcore.c
> > > +++ b/fs/proc/vmcore.c
> > > @@ -1569,7 +1569,7 @@ static int __init vmcore_init(void)
> > >  	rc = parse_crash_elf_headers();
> > >  	if (rc) {
> > >  		pr_warn("Kdump: vmcore not initialized\n");
> > > -		return rc;
> > > +		goto fail;
> > 
> > Sigh. Why don't you copy my suggested code directly?
> 
> I think at this point, you should just submit your own patch
> and credit this person with Reported-by:

Thanks for telling. I will consider doing this in the future.


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Jianglei Nie <niejianglei2021@163.com>,
	vgoyal@redhat.com, dyoung@redhat.com, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3] proc/vmcore: fix potential memory leak in vmcore_init()
Date: Tue, 12 Jul 2022 09:06:30 +0800	[thread overview]
Message-ID: <YszJFi+deSIXK3ns@MiWiFi-R3L-srv> (raw)
In-Reply-To: <YswVHNQX+OGz6IaQ@casper.infradead.org>

On 07/11/22 at 01:18pm, Matthew Wilcox wrote:
> On Mon, Jul 11, 2022 at 03:49:51PM +0800, Baoquan He wrote:
> > On 07/11/22 at 03:34pm, Jianglei Nie wrote:
> > > elfcorehdr_alloc() allocates a memory chunk for elfcorehdr_addr with
> > > kzalloc(). If is_vmcore_usable() returns false, elfcorehdr_addr is a
> > > predefined value. If parse_crash_elf_headers() occurs some error and
> > > returns a negetive value, the elfcorehdr_addr should be released with
> > > elfcorehdr_free().
> > > 
> > > We can fix by calling elfcorehdr_free() when parse_crash_elf_headers()
> > > fails.
> > > 
> > > Signed-off-by: Jianglei Nie <niejianglei2021@163.com>
> > > ---
> > >  fs/proc/vmcore.c | 5 ++++-
> > >  1 file changed, 4 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/fs/proc/vmcore.c b/fs/proc/vmcore.c
> > > index 4eaeb645e759..125efe63f281 100644
> > > --- a/fs/proc/vmcore.c
> > > +++ b/fs/proc/vmcore.c
> > > @@ -1569,7 +1569,7 @@ static int __init vmcore_init(void)
> > >  	rc = parse_crash_elf_headers();
> > >  	if (rc) {
> > >  		pr_warn("Kdump: vmcore not initialized\n");
> > > -		return rc;
> > > +		goto fail;
> > 
> > Sigh. Why don't you copy my suggested code directly?
> 
> I think at this point, you should just submit your own patch
> and credit this person with Reported-by:

Thanks for telling. I will consider doing this in the future.


  reply	other threads:[~2022-07-12  1:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  7:34 [PATCH v3] proc/vmcore: fix potential memory leak in vmcore_init() Jianglei Nie
2022-07-11  7:34 ` Jianglei Nie
2022-07-11  7:49 ` Baoquan He
2022-07-11  7:49   ` Baoquan He
2022-07-11 12:18   ` Matthew Wilcox
2022-07-11 12:18     ` Matthew Wilcox
2022-07-12  1:06     ` Baoquan He [this message]
2022-07-12  1:06       ` Baoquan He

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=YszJFi+deSIXK3ns@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niejianglei2021@163.com \
    --cc=vgoyal@redhat.com \
    --cc=willy@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.