linux-kernel - Re: 2.6.32 regression, hard lock

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: <s5hocm9som6.wl%tiwai@suse.de>
Date:	Tue, 08 Dec 2009 12:15:45 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Richard Zidlicky <rz@...ux-m68k.org>, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: 2.6.32 regression, hard lock

At Mon, 7 Dec 2009 16:48:26 -0800,
Andrew Morton wrote:
> 
> On Tue, 8 Dec 2009 01:23:53 +0100
> Richard Zidlicky <rz@...ux-m68k.org> wrote:
> 
> > 
> > > > first visible symptom is that ppp over UMTS connection "stops working", connection
> > > > did not die. Trying to restart the connection fails and the related processes hang.
> > > > 
> > > > After that one after another everything stops working, "telinit 6" does not do its
> > > > job and SysRQ sync-umount-reboot is logged in messages but has no visible effect.
> > > > 
> > > > Attaching messages and .config.
> > > > 
> > > 
> > > I uploaded your dmesg output to
> > > http://userweb.kernel.org/~akpm/stuff/messages.txt
> > 
> > > 
> > > I'm looking at those traces and am not able to develop a theory to
> > > explain it :(
> > 
> > thanks for looking at it. 
> > 
> > I did revert to 2.31.5 and to my big surprise found a similar thing happened
> > so it is not a regression, at least not from 2.6.31.
> 
> This trace is different.  It's a lock ranking warning and is surely
> unrelated to the IRQs-off lockup which you earlier experienced.
> 
(snip)
> And fortunately I know who to cc on this one ;)

Oh, it's a pity to me that you know that ;)

It's a known issue for several kernel releases.  (There are a few
subsystems that have the similar lockdep pattern involving with
mm->mmap_sem, too.)

But, as Andrew pointed, this should be irrelevant with the IRQ
lockup.  At most it could be a dead-locking of PA and other
sound-related processes, but I've never heard the real issue.


thanks,

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