From: Jens Axboe <axboe@kernel.dk>
To: Tejun Heo <tj@kernel.org>
Cc: vgoyal@redhat.com, ctalbott@google.com, rni@google.com,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
containers@lists.linux-foundation.org
Subject: Re: [PATCHSET] block: per-queue policy activation, take#2
Date: Fri, 20 Apr 2012 21:08:35 +0200 [thread overview]
Message-ID: <4F91B433.2070209@kernel.dk> (raw)
In-Reply-To: <20120420171742.GC32324@google.com>
On 2012-04-20 19:17, Tejun Heo wrote:
> Hello, Jens.
>
> On Fri, Apr 20, 2012 at 02:02:05PM +0200, Jens Axboe wrote:
>> Tejun, everything merged in cleanly. A boot test didn't not go so well,
>> I'm afraid. It complains about stuck RCU. Even with extra RCU
>> debugging/info turned on, it doesn't give my any extra info.
>>
>> Config is attached. I can try and debug this on Monday, for now I've
>> pulled it out of for-next again.
>
> Hmmm... it works fine with the same config here (qemu w/ 4 cpus
> configured). Doesn't stuck RCU usually come from unbalanced RCU
> lock/unlocking? That should trigger context or RCU warnings before
> anything else, weird. Anyways, it would be great if you can provide
> more info on how to reproduce the problem.
The machine just sat there. I'll get some more info out of it and run a
bisect too.
--
Jens Axboe
next prev parent reply other threads:[~2012-04-20 19:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 20:11 [PATCHSET] block: per-queue policy activation, take#2 Tejun Heo
2012-04-13 20:11 ` [PATCH 01/11] cfq: fix build breakage & warnings Tejun Heo
2012-04-13 20:11 ` [PATCH 02/11] blkcg: kill blkio_list and replace blkio_list_lock with a mutex Tejun Heo
2012-04-13 20:11 ` [PATCH 03/11] blkcg: use @pol instead of @plid in update_root_blkg_pd() and blkcg_print_blkgs() Tejun Heo
2012-04-13 20:11 ` [PATCH 04/11] blkcg: remove static policy ID enums Tejun Heo
2012-04-13 20:11 ` [PATCH 05/11] blkcg: make blkg_conf_prep() take @pol and return with queue lock held Tejun Heo
2012-04-13 20:11 ` [PATCH 06/11] blkcg: make sure blkg_lookup() returns %NULL if @q is bypassing Tejun Heo
2012-04-13 21:50 ` [PATCH UPDATED " Tejun Heo
2012-04-13 20:11 ` [PATCH 07/11] blkcg: make request_queue bypassing on allocation Tejun Heo
2012-04-13 20:32 ` Vivek Goyal
2012-04-13 20:37 ` Tejun Heo
2012-04-13 20:44 ` Vivek Goyal
2012-04-13 20:47 ` Tejun Heo
2012-04-13 20:55 ` Vivek Goyal
2012-04-13 21:05 ` Tejun Heo
2012-04-13 21:16 ` Tejun Heo
2012-04-13 21:31 ` Tejun Heo
2012-04-17 12:04 ` James Bottomley
2012-04-18 21:42 ` Tejun Heo
2012-04-13 21:33 ` Vivek Goyal
2012-04-13 21:38 ` Tejun Heo
2012-04-16 12:39 ` Vivek Goyal
2012-04-13 20:37 ` Vivek Goyal
2012-04-13 20:11 ` [PATCH 08/11] blkcg: add request_queue->root_blkg Tejun Heo
2012-04-13 20:11 ` [PATCH 09/11] blkcg: implement per-queue policy activation Tejun Heo
2012-04-13 20:11 ` [PATCH 10/11] blkcg: drop stuff unused after per-queue policy activation update Tejun Heo
2012-04-13 20:11 ` [PATCH 11/11] blkcg: shoot down blkgs if all policies are deactivated Tejun Heo
2012-04-20 8:09 ` [PATCHSET] block: per-queue policy activation, take#2 Jens Axboe
2012-04-20 12:02 ` Jens Axboe
2012-04-20 17:17 ` Tejun Heo
2012-04-20 19:08 ` Jens Axboe [this message]
2012-04-25 18:19 ` 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=4F91B433.2070209@kernel.dk \
--to=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=ctalbott@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rni@google.com \
--cc=tj@kernel.org \
--cc=vgoyal@redhat.com \
/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