From: ebiederm@xmission.com (Eric W. Biederman)
To: NeilBrown <neilb@suse.de>
Cc: qing gu <qing.gu@oracle.com>,
neilb@cse.unsw.edu.au, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH]: md: Initialize ctl_name field of table raid_root_table/raid_dir_table to avoid dump_trace info in debug kernel
Date: Tue, 13 Mar 2012 19:14:05 -0700 [thread overview]
Message-ID: <m14ntsc4k2.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20120314125720.1bb87546@notabene.brown> (NeilBrown's message of "Wed, 14 Mar 2012 12:57:20 +1100")
NeilBrown <neilb@suse.de> writes:
> On Mon, 12 Mar 2012 11:58:53 +0800 qing gu <qing.gu@oracle.com> wrote:
>
>> This patch is used to dispense trace info when system boots with debug
>> kernel. I have verified it on RHEL6.2 & SLES11.2. Both work fine.
>> In the failure case, system logs that:
>>
>> /Feb 21 19:33:55 nsgbj-216-137 kernel: sysctl_check_dir: failed: /dev ref: /dev .7
>> Feb 21 19:33:55 nsgbj-216-137 kernel: sysctl table check failed: /dev Inconsistent directory names
>> Feb 21 19:33:55 nsgbj-216-137 kernel: Pid: 1, comm: swapper Not tainted 2.6.32-220.el6.x86_64.debug #1
>> Feb 21 19:33:55 nsgbj-216-137 kernel: Call Trace:
>> Feb 21 19:33:55 nsgbj-216-137 kernel: [<ffffffff810a2029>] ? set_fail+0x59/0x60
>> Feb 21 19:33:55 nsgbj-216-137 kernel: [<ffffffff810a23d4>] ? sysctl_check_table+0x3a4/0x680
>> ...
>> /
>>
>> As you can see, system failed with mismatch
>> /sysctl_check_dir: failed: /dev ref: /dev .7/
>>
>> Signed-off-by: Neil Gu <qing.gu@oracle.com>
>>
>> -----------------------------------------------------------
>
> (please put patches inline in your email - it makes them easier to reply to)
>
>
> scripts/kconfig/Makefile | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index ce88755..9630ad3 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -129,6 +129,7 @@ static ctl_table raid_table[] = {
>
> static ctl_table raid_dir_table[] = {
> {
> + .ctl_name = DEV_RAID,
> .procname = "raid",
> .maxlen = 0,
> .mode = S_IRUGO|S_IXUGO,
> @@ -139,6 +140,7 @@ static ctl_table raid_dir_table[] = {
>
> static ctl_table raid_root_table[] = {
> {
> + .ctl_name = CTL_DEV,
> .procname = "dev",
> .maxlen = 0,
> .mode = 0555,
>
> These lines were removed in November 2009 by Eric Biederman in
> commit 894d2491153a9f8270dbed21175d06fde4eba6c7
>
> So I'm not keen on adding them back without understanding the history.
>
> Eric: Do we need these after all?
For the main trunk no. The .ctl_name field no longer exists.
kernel/binary_sysctl.c is used to provide backwards compatibility with
the old binary names.
There might be a point for doing something in -stable or someone's
enterprise kernel if some messed up set of backports were merged.
Eric
next parent reply other threads:[~2012-03-14 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F5D747D.9060508@oracle.com>
[not found] ` <20120314125720.1bb87546@notabene.brown>
2012-03-14 2:14 ` Eric W. Biederman [this message]
2012-03-14 2:35 ` [PATCH]: md: Initialize ctl_name field of table raid_root_table/raid_dir_table to avoid dump_trace info in debug kernel NeilBrown
2012-03-19 3:26 ` qing gu
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=m14ntsc4k2.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=neilb@suse.de \
--cc=qing.gu@oracle.com \
--cc=trivial@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