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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <464B2C0B.20500@redhat.com>
Date:	Wed, 16 May 2007 12:06:35 -0400
From:	Chuck Ebbert <cebbert@...hat.com>
To:	Tejun Heo <htejun@...il.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	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

Tejun Heo wrote:
>>>  The safest approach I can think of is making
>>> dentries for attributes unreclaimable but those are made reclaimable for
>>> good reasons.  :-(
>> Yeah, that was the google workaround.  It's OK unless you happen to have
>> thousands of disks on an ia32 box.
> 
> 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.
> 

Realistically, how can disabling the reclamation be worse than what's
there now?

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