linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Ian Kent <raven@themaw.net>, autofs@linux.kernel.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: autofs4 hang in 2.6.37-rc1
Date: Sun, 14 Nov 2010 14:55:07 +0200	[thread overview]
Message-ID: <4CDFDC2B.6040205@redhat.com> (raw)

A 2.6.37-rc1 (f6614b7bb405a) setup hangs in autofs4:

INFO: task automount:10399 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
automount     D 0000000000000000     0 10399      1 0x00000000
  ffff88012a059da8 0000000000000082 0000000000000000 0000000000000000
  ffff88012a058010 ffff88012a059fd8 0000000000011800 ffff8801290f2c40
  ffff8801290f2fb0 ffff8801290f2fa8 0000000000011800 0000000000011800
Call Trace:
  [<ffffffff813a3c3c>] __mutex_lock_common+0x126/0x18b
  [<ffffffff813a3cb5>] __mutex_lock_slowpath+0x14/0x16
  [<ffffffff813a3dbc>] mutex_lock+0x31/0x4b
  [<ffffffff811b17f7>] autofs4_root_ioctl+0x28/0x53
  [<ffffffff810f5e5c>] do_vfs_ioctl+0x557/0x5bb
  [<ffffffff810eca65>] ? sys_newlstat+0x2d/0x38
  [<ffffffff810f5f02>] sys_ioctl+0x42/0x65
  [<ffffffff81002b42>] system_call_fastpath+0x16/0x1b

This is a simple /home automount.  More info on request.

-- 
error compiling committee.c: too many arguments to function


             reply	other threads:[~2010-11-14 12:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14 12:55 Avi Kivity [this message]
2010-11-14 13:51 ` autofs4 hang in 2.6.37-rc1 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

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=4CDFDC2B.6040205@redhat.com \
    --to=avi@redhat.com \
    --cc=autofs@linux.kernel.org \
    --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).