linux-kernel - Re: [PATCHSET] block: per-queue policy activation, take#2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F91B433.2070209@kernel.dk>
Date:	Fri, 20 Apr 2012 21:08:35 +0200
From:	Jens Axboe <axboe@...nel.dk>
To:	Tejun Heo <tj@...nel.org>
CC:	vgoyal@...hat.com, ctalbott@...gle.com, rni@...gle.com,
	linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
	containers@...ts.linux-foundation.org
Subject: Re: [PATCHSET] block: per-queue policy activation, take#2

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/