From: Sasha Levin <levinsasha928@gmail.com>
To: Tejun Heo <tj@kernel.org>, Jens Axboe <jaxboe@fusionio.com>
Cc: Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: WARNING: at include/linux/iocontext.h:140 copy_io+0xb9/0x130()
Date: Tue, 01 May 2012 14:05:36 +0200 [thread overview]
Message-ID: <1335873936.16988.148.camel@lappy> (raw)
Hi all,
I've stumbled on the warning at the bottom with today's linux-next within a KVM guest doing syscall fuzzing using trinity.
I haven't encountered this warning before, and it looks like it's not easy to reproduce it within the guest. Looking at the code in that area I guess it's some sorts of a rare race condition.
The only recent commits in that area are the work done on blk cgroup. It is enabled in the test kernel.
[ 418.101833] WARNING: at include/linux/iocontext.h:140 copy_io+0xb9/0x130()
[ 418.108177] Pid: 29267, comm: trinity Tainted: G W 3.4.0-rc5-next-20120501-sasha #104
[ 418.108180] Call Trace:
[ 418.108186] [<ffffffff810b6c67>] warn_slowpath_common+0x87/0xb0
[ 418.108189] [<ffffffff810b6ca5>] warn_slowpath_null+0x15/0x20
[ 418.108192] [<ffffffff810b44d9>] copy_io+0xb9/0x130
[ 418.108196] [<ffffffff810b5ae4>] copy_process+0x884/0xf90
[ 418.108200] [<ffffffff810f17c5>] ? sched_clock_local+0x25/0x90
[ 418.108203] [<ffffffff810b65b7>] do_fork+0x137/0x240
[ 418.108208] [<ffffffff810e808e>] ? sub_preempt_count+0xae/0xf0
[ 418.108212] [<ffffffff82d92cf9>] ? _raw_spin_unlock_irq+0x59/0x80
[ 418.108216] [<ffffffff82d93be5>] ? sysret_check+0x22/0x5d
[ 418.108219] [<ffffffff81057b13>] sys_clone+0x23/0x30
[ 418.108222] [<ffffffff82d93f43>] stub_clone+0x13/0x20
[ 418.108225] [<ffffffff82d93bb9>] ? system_call_fastpath+0x16/0x1b
[ 418.108228] ---[ end trace 8f6ca168297608bb ]---
next reply other threads:[~2012-05-01 12:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 12:05 Sasha Levin [this message]
2012-05-01 16:17 ` [PATCH v3.4-rc5] block: iocontext->nr_tasks should be initialized to one Tejun Heo
2012-05-01 18:02 ` Jens Axboe
2012-05-01 18:09 ` Tejun Heo
2012-05-01 18:18 ` Jens Axboe
2012-05-01 18:31 ` Jeff Moyer
2012-05-01 18:36 ` Vivek Goyal
2012-05-01 18:48 ` Jeff Moyer
2012-05-01 18:59 ` Vivek Goyal
2012-05-01 19:04 ` Jeff Moyer
2012-05-01 19:08 ` Vivek Goyal
2012-05-01 18:37 ` Jens Axboe
2012-05-01 18:50 ` Jeff Moyer
2012-05-01 19:03 ` Jens Axboe
2012-05-01 18:04 ` Jens Axboe
2012-05-01 18:06 ` Tejun Heo
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=1335873936.16988.148.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=davej@redhat.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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