linux-kernel - Re: [Bug #10815] 2.6.26-rc4: RIP find_pid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19f34abd0806160653w2e92e43o4fb20e198bcb4615@mail.gmail.com>
Date:	Mon, 16 Jun 2008 15:53:43 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Alexey Dobriyan" <adobriyan@...il.com>
Cc:	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	"Oleg Nesterov" <oleg@...sign.ru>, "Adrian Bunk" <bunk@...nel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [Bug #10815] 2.6.26-rc4: RIP find_pid_ns+0x6b/0xa0

On Mon, Jun 16, 2008 at 5:01 AM, Alexey Dobriyan <adobriyan@...il.com> wrote:
> On Sun, Jun 15, 2008 at 04:38:24PM -0700, Linus Torvalds wrote:
>> On Sun, 15 Jun 2008, Paul E. McKenney wrote:
>> >
>> > If that is the right thing to do.  I would feel better about it if I
>> > could reproduce the failure.
>>
>> Is there some configuration thing that might make it happen for Alexey but
>> not for you? The only obvious one is the normal PREEMPT thing, but
>> PREEMPT_RCU obviously depends on that, so there must be something else.
>>
>> CONFIG_SMP? CONFIG_NO_HZ? CONFIG_[RT|FAIR]_GROUP_SCHED? There's a number
>> of config options that change scheduling details..
>
> The only way I can "fix" rcutorture here is SMP=n (not maxcpus=1!).
>
> Among things tried and do not matter are NO_HZ, HIGH_RES_TIMERS, turning off
> debugging options (one by one and in bulk), DEBUG_PER_CPU_MAPS, HZ tweaks,
> SCHED_MC.
>
> All of this doesn't help, but SMP=n does.

Maybe this is a stupid suggestion, but SLUB _is_ involved here (in
poisoning the object when it is freed). Do you have SLUB_DEBUG_ON=y or
did you check whether it matters if you have these options on or off?


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/