From: Peter Hurley <peter@hurleysoftware.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Greg KH <greg@kroah.com>,
jslaby@suse.cz, Dave Jones <davej@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: tty: hang on ldisc_sem
Date: Thu, 27 Mar 2014 12:30:05 -0400 [thread overview]
Message-ID: <5334520D.8060602@hurleysoftware.com> (raw)
In-Reply-To: <53344CE4.4070609@oracle.com>
Hi Sasha,
On 03/27/2014 12:08 PM, Sasha Levin wrote:
>
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next
> kernel, I've encountered a lockup on ldisc_sem.
Can you send me the whole system log, preferably with the sysrq
show-task-states and held locks output in it (attachment is fine)?
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-03-27 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 16:08 tty: hang on ldisc_sem Sasha Levin
2014-03-27 16:30 ` Peter Hurley [this message]
[not found] ` <53377259.3050205@oracle.com>
2014-04-01 3:40 ` Sasha Levin
2014-04-01 10:32 ` Peter Hurley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5334520D.8060602@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox