linux-kernel - Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2

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]

Date:	Thu, 17 May 2007 13:54:17 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Tejun Heo <htejun@...il.com>,
	Clemens Schwaighofer <cs@...uila.co.jp>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Maneesh Soni <maneesh@...ibm.com>,
	Dipankar Sarma <dipankar@...ibm.com>, Greg KH <greg@...ah.com>
Subject: Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2

Andrew Morton wrote:
> On Wed, 16 May 2007 17:40:53 +0200 Tejun Heo <htejun@...il.com> wrote:
> 
>> I see.  I thought there was different approach on fixing the problem.
>> I'll try to backport the synchronization fix but am afraid it can be too
>> risky for -stable.  If it seems too risky, I'll send a patch to disable
>> reclamation.
> 
> OK.  Sad.  Maybe we add /proc/sys/fs/i-have-lots-of-disks-and-dont-mind-if-it-oopses
> to enable the old behaviour.

Out of curiosity, is there a decent reproducer for this problem, or is 
it just a few lucky individuals? :)

-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/