[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m11webz8dx.fsf@ebiederm.dsl.xmission.com>
Date: Fri, 10 Aug 2007 10:01:14 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, "Ingo Molnar" <mingo@...e.hu>,
"Nick Piggin" <nickpiggin@...oo.com.au>
Subject: Re: 2.6.23-rc2-mm2
"Michal Piotrowski" <michal.k.k.piotrowski@...il.com> writes:
> Ah, it is intended.
> sysctl-error-on-bad-sysctl-tables.patch
Yes. I'm trying to flush out the bad sysctl table entries and prevent
us from adding new ones.
>> [ 25.120741] sysctl_check_dir: failed: /kernel ref: /kernel .1
>> [ 25.127102] sysctl table check failed: /kernel Writable sysctl directory
>> [ 25.134157] sysctl table check failed: /kernel Inconsistent directory names
>> [ 25.141477] sysctl table check failed: /kernel/sched_domain Writable sysctl
> directory
>> [ 25.149755] sysctl table check failed: /kernel/sched_domain/cpu0 Writable
> sysctl directory
>> [ 25.158529] sysctl table check failed: /kernel/sched_domain/cpu0/domain0
> Writable sysctl directory
>> [ 25.168102] sysctl table check failed: /kernel/sched_domain/cpu1 Writable
> sysctl directory
>> [ 25.176862] sysctl table check failed: /kernel/sched_domain/cpu1/domain0
> Writable sysctl directory
>>
>> Eric?
Yes. For the sched debug case I sent Ingo and friends but apparently
other changes in Ingos tree kept it from applying and Andrew dropped
it. So instead the code now screams at you and refuses to register
Ingo sysctl table.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists