From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Hu Tao <hutao@cn.fujitsu.com>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Tejun Heo" <tj@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH] Update num_symtab, symtab and strtab right after setup of core_num_syms, core_symtab and core_strtab.
Date: Mon, 27 Sep 2010 16:54:25 +0800 [thread overview]
Message-ID: <20100927085425.GE5785@cr0.nay.redhat.com> (raw)
In-Reply-To: <20100927082247.GA2463@localhost.localdomain>
On Mon, Sep 27, 2010 at 04:22:47PM +0800, Hu Tao wrote:
>On Mon, Sep 27, 2010 at 04:09:54PM +0800, Américo Wang wrote:
>> On Mon, Sep 27, 2010 at 03:30:28PM +0800, Hu Tao wrote:
>> >Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
>>
>>
>> Changelog is empty.
>> What bug did you observe?
>
>symtab and strtab will point to vfreed memory after free_copy(&info)
>near end of load_module().
>
I think you must mean the error path in load_module(), yeah, probably.
But you need to check if this patch misses other thing, like
the other functions which are called after add_kallsyms() inside load_module().
According to my eyes, this seems fine (at least on x86), so
Reviewed-by: WANG Cong <xiyou.wangcong@gmail.com>
>>
>>
>> This patch is not correct, symbols that are not core symbols will be
>> dropped right after this piece of code. So NACK.
>
>There is the reason why we should update num_symtab, symtab and strtab
>before non-core-symbols are dropped.
init section is dropped *after* these value are update, which is correct.
Again, you need to describe what you are trying to fix in your changelog.
Please resend it with a proper changelog.
Thanks.
next prev parent reply other threads:[~2010-09-27 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 7:30 Hu Tao
2010-09-27 8:09 ` Américo Wang
2010-09-27 8:22 ` Hu Tao
2010-09-27 8:54 ` Américo Wang [this message]
2010-09-28 0:55 ` Hu Tao
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=20100927085425.GE5785@cr0.nay.redhat.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hutao@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tj@kernel.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 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®