linux-kernel - Re: BUG: scheduling while atomic: ip/23212/0x00000102

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: <200808050040.09726.rjw@sisk.pl>
Date:	Tue, 5 Aug 2008 00:40:08 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	David Miller <davem@...emloft.net>
Cc:	arekm@...en.pl, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: BUG: scheduling while atomic: ip/23212/0x00000102

On Tuesday, 5 of August 2008, Rafael J. Wysocki wrote:
> On Monday, 4 of August 2008, David Miller wrote:
> > From: Arkadiusz Miskiewicz <arekm@...en.pl>
> > Date: Mon, 4 Aug 2008 18:45:10 +0200
> > 
> > > 
> > > git kernel, pulled around  Sat Aug 2 13:32:05 CEST,
> > > i686, thinkpad z60m notebook
> > 
> > Obviously the tg3 PCI power-management changes were totally untested.
> 
> If you mean the commit below, actually they were tested.
> 
> I run this code on a regular basis on my production box and I have never seen
> this stack trace.  How exactly can I make it appear?

OK, I see.  I must have overlooked it. :-/  Sorry again.

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