From: Sasha Levin <levinsasha928@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: Dave Jones <davej@redhat.com>
Subject: vfs: chmod: Hung task after calling chmod()
Date: Wed, 14 Mar 2012 17:00:44 -0400 [thread overview]
Message-ID: <1331758844.3723.3.camel@lappy> (raw)
Hi all,
I've found the following backtrace after running the trinity fuzzer in a KVM guest using the latest linux-next. Unfortunately I don't have full logs for this, so I can't tell exactly which parameters were passed to chmod().
[ 241.469508] INFO: task trinity:3058 blocked for more than 120 seconds.
[ 241.471949] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 241.476626] trinity D 0000000000000000 4544 3058 1 0x00000000
[ 241.480595] ffff880035f29d98 0000000000000082 ffff880035f29d28 ffff880035f29fd8
[ 241.483212] 00000000001d4340 ffff880035f28000 00000000001d4340 00000000001d4340
[ 241.487158] 00000000001d4340 00000000001d4340 ffff880035f29fd8 00000000001d4340
[ 241.490875] Call Trace:
[ 241.492186] [<ffffffff826edfc4>] schedule+0x24/0x70
[ 241.493132] [<ffffffff826ee023>] schedule_preempt_disabled+0x13/0x20
[ 241.493878] [<ffffffff826ec79f>] __mutex_lock_common+0x1ff/0x5a0
[ 241.494683] [<ffffffff811dbe4a>] ? chmod_common+0x5a/0xc0
[ 241.495357] [<ffffffff811ea22e>] ? putname+0x2e/0x40
[ 241.495946] [<ffffffff811dbe4a>] ? chmod_common+0x5a/0xc0
[ 241.496669] [<ffffffff826ecb80>] mutex_lock_nested+0x40/0x50
[ 241.497388] [<ffffffff811dbe4a>] chmod_common+0x5a/0xc0
[ 241.498033] [<ffffffff811e079c>] ? __fput+0x1cc/0x300
[ 241.498656] [<ffffffff826f0da9>] ? sysret_check+0x22/0x5d
[ 241.499480] [<ffffffff811dc964>] sys_fchmodat+0x34/0x50
[ 241.500350] [<ffffffff811dc994>] sys_chmod+0x14/0x20
[ 241.500952] [<ffffffff826f0d7d>] system_call_fastpath+0x1a/0x1f
[ 241.501671] 1 lock held by trinity/3058:
[ 241.502142] #0: (&type->i_mutex_dir_key){+.+.+.}, at: [<ffffffff811dbe4a>] chmod_common+0x5a/0xc0
[ 241.503314] Kernel panic - not syncing: hung_task: blocked tasks
--
Sasha.
reply other threads:[~2012-03-14 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1331758844.3723.3.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=davej@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.