linux-kernel - Re: 3.9+ tty lockdep trace.

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: <20130507150423.GA13062@redhat.com>
Date:	Tue, 7 May 2013 11:04:23 -0400
From:	Dave Jones <davej@...hat.com>
To:	Peter Hurley <peter@...leysoftware.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Jiri Slaby <jslaby@...e.cz>
Subject: Re: 3.9+ tty lockdep trace.

On Tue, May 07, 2013 at 10:14:09AM -0400, Peter Hurley wrote:

 > >> Just hit this again, by switching tty's during bootup.
 > >> The previous time was switching from X to console iirc, so that seems to be
 > >> the key to triggering this.
 > >
 > > Sorry for not getting back to this sooner, merge window fun...
 > >
 > > Anyway, Peter, could this be something that your ldisc patches are
 > > triggering?
 > 
 > Yes, although early analysis also suggests the lockdep splat is possible
 > regardless, just much less likely.
 > 
 > I looked at this over the weekend, but I wasn't able to determine (in
 > the limited time I had available) if the splat was valid; ie., if the
 > cpu states could actually be concurrent and result in deadlock.
 > 
 > I need to study the VT_DISALLOCATE ioctl in more detail which I plan
 > to do this week.

I don't know if it proves/disproves anything, but shortly before the dump
gets printed, everything is kind of locked up. I can switch tty's, but
the gettys on them are dead to the world until after the dump.

ISTR a pause for a while when I hit this switching from X too.

	Dave

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