From: Dave Jones <davej@redhat.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: 3.4+ tty lockdep trace
Date: Tue, 22 May 2012 21:17:01 -0400 [thread overview]
Message-ID: <20120523011701.GA15255@redhat.com> (raw)
In-Reply-To: <CACVXFVMz_GKHXpzbqt24yY=fHJ6uYZPOcSnKNFHrvbdpWxc7tw@mail.gmail.com>
On Wed, May 23, 2012 at 09:06:22AM +0800, Ming Lei wrote:
> > [ 43.375802] stack backtrace:
> > [ 43.375841] Pid: 639, comm: sshd Not tainted 3.4.0+ #24
> > [ 43.375882] Call Trace:
> > [ 43.377572] [<ffffffff810b4604>] __lock_acquire+0x1584/0x1aa0
> > [ 43.379286] [<ffffffff810b51e2>] lock_acquire+0x92/0x1f0
> > [ 43.380995] [<ffffffff81656d57>] ? tty_lock+0x37/0x80
> > [ 43.382700] [<ffffffff816534f1>] mutex_lock_nested+0x71/0x3b0
> > [ 43.384403] [<ffffffff81656d57>] ? tty_lock+0x37/0x80
> > [ 43.386094] [<ffffffff81085521>] ? get_parent_ip+0x11/0x50
> > [ 43.387794] [<ffffffff81656d57>] ? tty_lock+0x37/0x80
> > [ 43.389480] [<ffffffff8165a68d>] ? sub_preempt_count+0x6d/0xd0
> > [ 43.391176] [<ffffffff813b0243>] ? tty_release+0x1c3/0x5d0
> > [ 43.393003] [<ffffffff81656d57>] tty_lock+0x37/0x80
> > [ 43.394867] [<ffffffff81656dc3>] tty_lock_pair+0x23/0x5c
> > [ 43.396671] [<ffffffff813b024e>] tty_release+0x1ce/0x5d0
> > [ 43.398462] [<ffffffff811a765c>] fput+0x12c/0x300
> > [ 43.400292] [<ffffffff811a23a9>] filp_close+0x69/0xa0
> > [ 43.402084] [<ffffffff811a2f2d>] sys_close+0xad/0x1a0
> > [ 43.403871] [<ffffffff8165e652>] system_call_fastpath+0x16/0x1b
>
> We have one patch to address the problem, could you test it from the link below?
>
> http://marc.info/?l=linux-kernel&m=133765211309247&w=2
Yes, that seems to fix it. Thanks.
Dave
next prev parent reply other threads:[~2012-05-23 1:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 0:26 3.4+ tty lockdep trace Dave Jones
2012-05-23 1:06 ` Ming Lei
2012-05-23 1:17 ` Dave Jones [this message]
2012-05-23 2:02 ` Dave Jones
2012-05-23 2:44 ` Ming Lei
2012-05-23 23:05 ` Alan Cox
2012-05-24 6:13 ` Sasha Levin
2012-05-24 11:10 ` Alan Cox
2012-05-24 11:20 ` Sasha Levin
2012-05-24 11:21 ` Sasha Levin
2012-05-24 11:24 ` Sasha Levin
2012-05-24 14:54 ` Alan Cox
2012-05-25 2:32 ` Steven Rostedt
2012-05-25 8:07 ` Sasha Levin
2012-05-25 8:30 ` Ming Lei
2012-05-25 10:24 ` Sasha Levin
2012-05-25 11:02 ` Alan Cox
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=20120523011701.GA15255@redhat.com \
--to=davej@redhat.com \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.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