linux-kernel - Re: BUG: scheduling while atomic

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] [day] [month] [year] [list]

Message-Id: <23E5FE2E-C893-4606-A2B7-07ACF0A7A0BE@it-loops.com>
Date:	Mon, 6 Jul 2009 20:37:56 +0200
From:	Michael Guntsche <mike@...loops.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Herbert Xu <herbert@...dor.apana.org.au>,
	linux-kernel@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: BUG: scheduling while atomic


On Jul 6, 2009, at 20:18, Alan Cox wrote:

> On Mon, 6 Jul 2009 20:07:34 +0200
> Michael Guntsche <mike@...loops.com> wrote:
>
>>
>> On Jul 6, 2009, at 19:17, Alan Cox wrote:
>>
>>> This is the more drastic way of doing it. I had hoped to put this
>>> off but
>>> in fact it cleans stuff up enormously. This has had only basic  
>>> testing
>>> but the underlying idea is to simply remove all the pty special  
>>> casing
>>> that causes messes in the first place.
>> <snip>
>>
>> Hi Alan,
>>
>> Must commit a6540f731d506d9e82444cf0020e716613d4c46c still be  
>> reverted
>> with your patch or can it stay in?
>
> Herbert is (as usual ;)) correct that it should be reverted.

No crashes with the reverted commit and Alan's patch on my hardware  
here.
A Load Test that would trigger it after some seconds is now running  
for several minutes without any problems.

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