linux-kernel - Re: tty ldisc lockups in linux-next

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: <506171DA.9070102@suse.cz>
Date:	Tue, 25 Sep 2012 10:56:58 +0200
From:	Jiri Slaby <jslaby@...e.cz>
To:	Sasha Levin <levinsasha928@...il.com>
CC:	Sasha Levin <sasha.levin@...cle.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Dave Jones <davej@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: tty ldisc lockups in linux-next

On 09/25/2012 10:55 AM, Sasha Levin wrote:
> On 09/25/2012 10:52 AM, Jiri Slaby wrote:
>>> Hi all,
>>>>
>>>> While fuzzing with trinity in a KVM tools guest running linux-next kernel, I keep hitting the following lockup:
>> Hi, I'm confused here. Is this different to what you reported a couple
>> days ago? Doesn't reverting aa3c8af86382 help in the end?
> 
> I was just about to send a reply to that mail saying that while reverting aa3c8af86382 reduces the odds for seeing it, it still
> happens. You were faster than me :)
> 
> But yes, it still happens even if I revert aa3c8af86382 or try applying your patch in that thread.

The patch won't help, it's kind of certain.

Instead I still wonder what process sits on the terminal. Could you
investigate?

-- 
js
suse labs
--
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/