From: Sasha Levin <levinsasha928@gmail.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Jiri Slaby <jirislaby@gmail.com>,
gregkh@linuxfoundation.org, alan@linux.intel.com,
linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>
Subject: Re: [PATCH 21/21] TTY: move tty buffers to tty_port
Date: Wed, 31 Oct 2012 16:10:11 -0400 [thread overview]
Message-ID: <509185A3.1020105@gmail.com> (raw)
In-Reply-To: <5091448D.3@suse.cz>
On 10/31/2012 11:32 AM, Jiri Slaby wrote:
> On 10/31/2012 04:30 PM, Sasha Levin wrote:
>> On Wed, Oct 31, 2012 at 8:53 AM, Jiri Slaby <jslaby@suse.cz> wrote:
>>> On 10/25/2012 08:02 PM, Sasha Levin wrote:
>>>> Fuzzing with trinity inside a KVM tools (lkvm) guest with -next kernel
>>>> uncovered the following warning:
>>>
>>> I cannot reproduce that :(. Do you still see it?
>>
>> Yes, it reproduces pretty easily while fuzzing.
>
> What is your exact setup? I tried trinity with 100 000 syscalls inside
> KVM with an LDEP-enabled kernel. How many serial ports do you have in
> the guest? Any USB serials in there?
btw, I'm also seeing the following lockups, don't know if it's related:
[ 2283.070569] INFO: task trinity-child20:9161 blocked for more than 120 seconds.
[ 2283.071775] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2283.074673] trinity-child20 D ffff8800276cb000 5424 9161 6364 0x00000000
[ 2283.076018] ffff880059d9da58 0000000000000002 0000000000000002 0000000000000000
[ 2283.077393] ffff880059d7b000 ffff880059d9dfd8 ffff880059d9dfd8 ffff880059d9dfd8
[ 2283.078763] ffff8800276cb000 ffff880059d7b000 ffff880059d9da78 ffff88001a095180
[ 2283.084144] Call Trace:
[ 2283.085039] [<ffffffff83a98bd5>] schedule+0x55/0x60
[ 2283.086748] [<ffffffff83a98bf3>] schedule_preempt_disabled+0x13/0x20
[ 2283.089000] [<ffffffff83a9735d>] __mutex_lock_common+0x36d/0x5a0
[ 2283.090658] [<ffffffff83a9afb3>] ? tty_lock_nested+0x73/0x80
[ 2283.091691] [<ffffffff83a9afb3>] ? tty_lock_nested+0x73/0x80
[ 2283.092779] [<ffffffff83a975cf>] mutex_lock_nested+0x3f/0x50
[ 2283.093875] [<ffffffff83a9afb3>] tty_lock_nested+0x73/0x80
[ 2283.094872] [<ffffffff83a9afcb>] tty_lock+0xb/0x10
[ 2283.095443] [<ffffffff81bae880>] tty_open+0x270/0x5f0
[ 2283.096181] [<ffffffff8127cda8>] chrdev_open+0xf8/0x1d0
[ 2283.097054] [<ffffffff8127693c>] do_dentry_open+0x1fc/0x310
[ 2283.098015] [<ffffffff8127ccb0>] ? cdev_put+0x20/0x20
[ 2283.098943] [<ffffffff8127777a>] finish_open+0x4a/0x60
[ 2283.099935] [<ffffffff81286947>] do_last+0xb87/0xe70
[ 2283.100910] [<ffffffff812844b0>] ? link_path_walk+0x70/0x900
[ 2283.101553] [<ffffffff81286cf2>] path_openat+0xc2/0x500
[ 2283.102282] [<ffffffff83a9a314>] ? _raw_spin_unlock_irqrestore+0x84/0xb0
[ 2283.103506] [<ffffffff8128716c>] do_filp_open+0x3c/0xa0
[ 2283.104282] [<ffffffff81296c11>] ? __alloc_fd+0x1e1/0x200
[ 2283.105278] [<ffffffff81277c0c>] do_sys_open+0x11c/0x1c0
[ 2283.106519] [<ffffffff81277ccc>] sys_open+0x1c/0x20
[ 2283.107241] [<ffffffff81277d01>] sys_creat+0x11/0x20
[ 2283.107975] [<ffffffff83a9be18>] tracesys+0xe1/0xe6
next prev parent reply other threads:[~2012-10-31 20:10 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 20:26 [PATCH 00/21] TTY buffer in tty_port and other stuff Jiri Slaby
2012-10-18 20:26 ` [PATCH 01/21] TTY: devpts, don't care about TTY in devpts_get_tty Jiri Slaby
2012-10-18 20:26 ` [PATCH 02/21] TTY: devpts, return created inode from devpts_pty_new Jiri Slaby
2012-10-18 20:26 ` [PATCH 03/21] TTY: devpts, do not set driver_data Jiri Slaby
2012-10-18 20:26 ` [PATCH 04/21] TTY: devpts, document devpts inode operations Jiri Slaby
2012-10-18 20:26 ` [PATCH 05/21] TTY: move devpts kill to pty Jiri Slaby
2012-10-18 20:26 ` [PATCH 06/21] TTY: vt, fix paste_selection ldisc handling Jiri Slaby
2012-10-18 20:26 ` [PATCH 07/21] TTY: ldisc, wait for idle ldisc in release Jiri Slaby
2012-10-18 20:26 ` [PATCH 08/21] TTY: hci_ldisc, remove invalid check in open Jiri Slaby
2012-10-18 20:47 ` Marcel Holtmann
2012-10-18 20:26 ` [PATCH 09/21] TTY: n_tty, simplify read_buf+echo_buf allocation Jiri Slaby
2012-10-18 20:26 ` [PATCH 10/21] TTY: n_tty, remove bogus checks Jiri Slaby
2012-10-18 20:26 ` [PATCH 11/21] TTY: audit, stop accessing tty->icount Jiri Slaby
2012-10-18 20:26 ` [PATCH 12/21] TTY: n_tty, add ldisc data to n_tty Jiri Slaby
2012-10-18 20:26 ` [PATCH 13/21] TTY: move ldisc data from tty_struct: simple members Jiri Slaby
2012-10-18 20:26 ` [PATCH 14/21] TTY: move ldisc data from tty_struct: bitmaps Jiri Slaby
2012-10-18 20:26 ` [PATCH 15/21] TTY: move ldisc data from tty_struct: read_* and echo_* and canon_* stuff Jiri Slaby
2012-10-18 20:26 ` [PATCH 16/21] TTY: move ldisc data from tty_struct: locks Jiri Slaby
2012-10-18 20:26 ` [PATCH 17/21] TTY: n_tty, propagate n_tty_data Jiri Slaby
2012-10-18 20:26 ` [PATCH 18/21] TTY: move TTY_FLUSH* flags to tty_port Jiri Slaby
2012-10-18 20:26 ` [PATCH 19/21] TTY: tty_buffer, cache pointer to tty->buf Jiri Slaby
2012-10-18 20:26 ` [PATCH 20/21] TTY: add port -> tty link Jiri Slaby
2012-10-18 20:26 ` [PATCH 21/21] TTY: move tty buffers to tty_port Jiri Slaby
2012-10-25 18:02 ` Sasha Levin
2012-10-25 18:08 ` Greg KH
2012-10-31 12:53 ` Jiri Slaby
2012-10-31 15:30 ` Sasha Levin
2012-10-31 15:32 ` Jiri Slaby
2012-10-31 15:59 ` Sasha Levin
2012-11-02 15:51 ` Jiri Slaby
2012-11-02 16:07 ` Sasha Levin
2012-11-02 16:18 ` Jiri Slaby
2012-11-02 16:23 ` Sasha Levin
2012-11-03 2:03 ` Sasha Levin
2012-11-03 15:55 ` Jiri Slaby
2012-11-03 23:06 ` Sasha Levin
2012-11-04 0:53 ` Sasha Levin
2012-11-27 19:57 ` Peter Hurley
2012-11-30 23:52 ` Sasha Levin
2012-12-01 14:59 ` flush_to_ldisc accesses tty after free (was: [PATCH 21/21] TTY: move tty buffers to tty_port) Peter Hurley
2012-12-01 20:06 ` Peter Hurley
2012-12-02 19:57 ` Peter Hurley
2012-12-04 19:21 ` Ilya Zykov
2012-10-31 20:10 ` Sasha Levin [this message]
2012-10-18 21:12 ` [PATCH 00/21] TTY buffer in tty_port and other stuff Greg KH
2012-10-22 14:57 ` Alan Cox
2012-10-22 23:59 ` Greg KH
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=509185A3.1020105@gmail.com \
--to=levinsasha928@gmail.com \
--cc=alan@linux.intel.com \
--cc=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).