From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: Avi Kivity <avi@redhat.com>
Cc: Ian Kent <raven@themaw.net>, Arnd Bergmann <arnd@arndb.de>,
autofs@linux.kernel.org,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: autofs4 hang in 2.6.37-rc1
Date: Mon, 22 Nov 2010 01:42:07 -0700 [thread overview]
Message-ID: <201011220142.08110.thomas@fjellstrom.ca> (raw)
In-Reply-To: <4CE0F713.8090503@redhat.com>
On November 15, 2010, Avi Kivity wrote:
> On 11/15/2010 03:31 AM, Ian Kent wrote:
> > > If the ioctl can sleep for multiple seconds, the mutex should
> > > indeed be dropped, and that would be safe because we used to
> > > do the same with the BKL.
> > >
> > > The question is why this would sleep for more than 120 seconds.
> >
> > umount against a server that isn't responding can easily take more than
> > 2 minutes.
>
> Well, in my setup, the server should be responding.
Same as in mine. Server's up, but automount is locking up solid. trying to
access the share, or links pointing to anything on it also lock up and can't
be killed.
[ 5520.863130] INFO: task automount:1491 blocked for more than 120 seconds.
[ 5520.863139] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 5520.863145] automount D 0000000000000001 0 1491 1 0x00000000
[ 5520.863157] ffff880137f5fdc8 0000000000000086 ffff880137f5fd48
0000000000000086
[ 5520.863172] ffff8800379efd78 ffff880137f5e000 ffff880137f5e000 ffff88013f1c06a0
[ 5520.863184] ffff880137f5e010 ffff88013f1c0960 ffff880137f5ffd8 ffff880137f5ffd8
[ 5520.863197] Call Trace:
[ 5520.863214] [<ffffffff81038541>] ? get_parent_ip+0x11/0x50
[ 5520.863232] [<ffffffff813914ea>] __mutex_lock_slowpath+0x11a/0x1e0
[ 5520.863242] [<ffffffff813962fd>] ? sub_preempt_count+0x9d/0xd0
[ 5520.863251] [<ffffffff8139106e>] mutex_lock+0x1e/0x40
[ 5520.863264] [<ffffffffa03390a8>] autofs4_root_ioctl+0x38/0x70 [autofs4]
[ 5520.863274] [<ffffffff8112d4e7>] do_vfs_ioctl+0x97/0x530
[ 5520.863283] [<ffffffff8104af2c>] ? sys_wait4+0xac/0xf0
[ 5520.863291] [<ffffffff8112d9ca>] sys_ioctl+0x4a/0x80
[ 5520.863302] [<ffffffff81002feb>] system_call_fastpath+0x16/0x1b
Got about 8+ of those in my dmesg right now. Another machine running .36 right
now, is playing music off the same share, and this machine doesn't lock up at
all when running .36 as well. Tried 2.6.37-rc1 and now -rc3.
--
Thomas Fjellstrom
thomas@fjellstrom.ca
prev parent reply other threads:[~2010-11-22 8:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 12:55 autofs4 hang in 2.6.37-rc1 Avi Kivity
2010-11-14 13:51 ` Avi Kivity
2010-11-14 15:15 ` Arnd Bergmann
2010-11-14 15:34 ` Avi Kivity
2010-11-15 1:45 ` Ian Kent
2010-11-15 8:54 ` Arnd Bergmann
2010-11-15 13:22 ` Ian Kent
2010-11-15 13:27 ` Avi Kivity
2010-11-15 13:38 ` Ian Kent
2010-11-15 13:42 ` Ian Kent
2010-11-18 3:54 ` Ian Kent
2010-11-25 13:17 ` Arnd Bergmann
2010-11-15 1:31 ` Ian Kent
2010-11-15 9:02 ` Avi Kivity
2010-11-22 8:42 ` Thomas Fjellstrom [this message]
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=201011220142.08110.thomas@fjellstrom.ca \
--to=thomas@fjellstrom.ca \
--cc=arnd@arndb.de \
--cc=autofs@linux.kernel.org \
--cc=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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).