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
| ||
|
Date: Fri, 15 Apr 2011 08:13:22 +0200 From: Jens Axboe <jaxboe@...ionio.com> To: Christoph Hellwig <hch@...radead.org> CC: Linus Torvalds <torvalds@...ux-foundation.org>, Michael Guntsche <mike@...loops.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: 2.6.39 Block layer regression was [Bug] Boot hangs with 2.6.39-rc[123]] On 2011-04-15 06:22, Christoph Hellwig wrote: > On Thu, Apr 14, 2011 at 08:25:33PM -0700, Linus Torvalds wrote: >> What's the thinking there? It looks very confused to me. > > It is. I sent a patch a couple of days ago to fix it. Yeah thanks for that, I agree it looks a bit confusing as-is. I'll queue it up. >> Now, clearly RAID seems to be involved in the problem? The main thing >> with that would be that the execution of the requests would tend to >> generate new requests, that go back on the plug queue. Yes? And the >> loop in flush_plug_list() means that they all should get flushed out, >> I assume. But something clearly isn't working, and it does seem to be >> about the RAID kind of setup. So either they didn't get put on the >> plug queue, or the task got a new plug (which _wasn't_ flushed). >> >> Because we're clearly waiting for some request that hasn't completed. >> Where in the plug queues would it be hiding? > > There's a thread where Neil explains what the problem with MD is - it > needs a callback on unplug time to generate e.g. the write intent bitmap > or as large as possible writes for RAID5. Jens and Neil have been > looking into it. I think we are done, Neil just needs to rebase around the current for-linus and then we should expedite things in. -- 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/
Powered by blists - more mailing lists