From: WANG Cong <xiyou.wangcong@gmail.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: WANG Cong <xiyou.wangcong@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Eric Youngdale <ericy@cais.com>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: [Patch] fs/binfmt_elf.c: fix a wrong free
Date: Sat, 3 May 2008 22:39:43 +0800 [thread overview]
Message-ID: <20080503143942.GE3986@hack> (raw)
In-Reply-To: <Pine.LNX.4.64.0805031625150.20470@sbz-30.cs.Helsinki.FI>
On Sat, May 03, 2008 at 04:26:11PM +0300, Pekka J Enberg wrote:
>On Sat, 3 May 2008, WANG Cong wrote:
>> Fix a wrong free in fs/binfmt_elf.c::elf_core_dump().
>>
>> Signed-off-by: WANG Cong <wangcong@zeuux.org>
>> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
>> Cc: Eric Youngdale <ericy@cais.com>
>>
>> ---
>> fs/binfmt_elf.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
>> index b25707f..43254e3 100644
>> --- a/fs/binfmt_elf.c
>> +++ b/fs/binfmt_elf.c
>> @@ -2032,10 +2032,10 @@ static int elf_core_dump(long signr, struct pt_regs *regs, struct file *file, un
>>
>> end_coredump:
>> set_fs(fs);
>> + free_note_info(&info);
>>
>> cleanup:
>> kfree(elf);
>> - free_note_info(&info);
>> return has_dumped;
>> }
>
>Looks like fill_note_info() requires that you call free_note_info() if it
>fails; otherwise we'll leak memory. So perhaps something like the
>following totally untested patch?
>
Hi, Pekka!
Thanks for your comments. Yes, it seems that fill_note_info() is ugly.
:-) How about the below one?
Signed-off-by: WANG Cong <wangcong@zeuux.org>
---
diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
index f6d5a9d..357b503 100644
--- a/fs/binfmt_elf.c
+++ b/fs/binfmt_elf.c
@@ -1900,7 +1900,7 @@ static int elf_core_dump(long signr, struct pt_regs *regs, struct file *file, un
/* alloc memory for large data structures: too large to be on stack */
elf = kmalloc(sizeof(*elf), GFP_KERNEL);
if (!elf)
- goto cleanup;
+ goto ret;
segs = current->mm->map_count;
#ifdef ELF_CORE_EXTRA_PHDRS
@@ -2034,8 +2034,9 @@ end_coredump:
set_fs(fs);
cleanup:
- kfree(elf);
free_note_info(&info);
+ kfree(elf);
+ret:
return has_dumped;
}
next prev parent reply other threads:[~2008-05-03 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 12:46 [Patch] fs/binfmt_elf.c: fix a wrong free WANG Cong
2008-05-03 13:26 ` Pekka J Enberg
2008-05-03 14:39 ` WANG Cong [this message]
2008-05-04 10:39 ` Pekka Enberg
2008-05-04 14:30 ` WANG Cong
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=20080503143942.GE3986@hack \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@osdl.org \
--cc=ericy@cais.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=viro@zeniv.linux.org.uk \
/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).