| 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: Tue, 11 Mar 2008 11:09:04 +0100 From: Pavel Machek <pavel@....cz> To: Paul Clements <paul.clements@...eleye.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, nbd-general@...ts.sourceforge.net, Laurent Vivier <Laurent.Vivier@...l.net> Subject: Re: [PATCH 1/1] NBD: allow nbd to be used locally On Mon 2008-03-10 13:26:34, Paul Clements wrote: > Pavel Machek wrote: > >>> This patch allows a Network Block Device to be mounted locally >>> (nbd-client to nbd-server over 127.0.0.1). >>> >>> It creates a kthread to avoid the deadlock described in NBD tools >>> documentation. So, if nbd-client hangs waiting for pages, the kblockd >>> thread can continue its work and free pages. >> >> What happens if your new kthread blocks on memory allocation? > > Well, we expect that. The reason for the new thread is so that it hangs, > rather than kblockd hanging (which on a UP system brings all I/O to a > halt). As long as kblockd can continue making progress, we eventually free > up memory and then NBD can finish its requests, too. ...unless all the memory is in dirty buffers for nbd, and nbd server is swapped out or something? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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