From: Jens Axboe <jaxboe@fusionio.com>
To: Tejun Heo <tj@kernel.org>
Cc: Sasha Levin <levinsasha928@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH block/for-3.3/core] block: remove WARN_ON_ONCE() in exit_io_context()
Date: Tue, 27 Dec 2011 18:53:08 +0100 [thread overview]
Message-ID: <4EFA0604.1030607@fusionio.com> (raw)
In-Reply-To: <20111227173559.GD17712@google.com>
On 2011-12-27 18:35, Tejun Heo wrote:
> 6e736be7 "block: make ioc get/put interface more conventional and fix
> race on alloction" added WARN_ON_ONCE() in exit_io_context() which
> triggers if !PF_EXITING. All tasks hitting exit_io_context() from
> task exit should have PF_EXITING set but task struct tearing down
> after fork failure calls into the function without PF_EXITING,
> triggering the condition.
>
> WARNING: at block/blk-ioc.c:234 exit_io_context+0x40/0x92()
> Pid: 17090, comm: trinity Not tainted 3.2.0-rc6-next-20111222-sasha-dirty #77
> Call Trace:
> [<ffffffff810b69a3>] warn_slowpath_common+0x8f/0xb2
> [<ffffffff810b6a77>] warn_slowpath_null+0x18/0x1a
> [<ffffffff8181a7a2>] exit_io_context+0x40/0x92
> [<ffffffff810b58c9>] copy_process+0x126f/0x1453
> [<ffffffff810b5c1b>] do_fork+0x120/0x3e9
> [<ffffffff8106242f>] sys_clone+0x26/0x28
> [<ffffffff82425803>] stub_clone+0x13/0x20
> ---[ end trace a2e4eb670b375238 ]---
>
> Reported-by: Sasha Levin <levinsasha928@gmail.com>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> ---
> Heh, sorry about that. Forgot about fork failure path. Just removing
> the WARN_ON_ONCE() should be enough. Thanks for reporting the problem.
Thanks, applied.
--
Jens Axboe
prev parent reply other threads:[~2011-12-27 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 9:46 WARNING: at block/blk-ioc.c:234 exit_io_context+0x40/0x92() Sasha Levin
2011-12-27 17:35 ` [PATCH block/for-3.3/core] block: remove WARN_ON_ONCE() in exit_io_context() Tejun Heo
2011-12-27 17:53 ` Jens Axboe [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=4EFA0604.1030607@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=levinsasha928@gmail.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 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.