linux-kernel - Re: [stable] Soft lockups since stable kernel upgrade to 2.6.23.8

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: <20071120203919.GB10008@elte.hu>
Date:	Tue, 20 Nov 2007 21:39:19 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Greg KH <greg@...ah.com>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>, Greg KH <gregkh@...e.de>,
	David <david@...olicited.net>,
	Javier Kohen <jkohen@...rs.sourceforge.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [stable] Soft lockups since stable kernel upgrade to 2.6.23.8


* Greg KH <greg@...ah.com> wrote:

> > but we only have cpu_clock() from v2.6.23 onwards - so we should not 
> > apply the original patch to v2.6.22. (we should not have applied 
> > your patch that started the mess to begin with - but that's another 
> > matter.)
> 
> Well, I can easily back that one out, if that is easier than adding 2 
> more patches to try to fix up the mess here.
> 
> Let me know if you feel that would be best.

i'd leave it alone - doing that we have in essence the softlockup 
detector turned off. Reverting to the older version might trigger false 
positives that need the new stuff.

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