| 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
| ||
|
Message-ID: <20060829115044.GA26794@infradead.org> Date: Tue, 29 Aug 2006 12:50:44 +0100 From: Christoph Hellwig <hch@...radead.org> To: Cedric Le Goater <clg@...ibm.com> Cc: Christoph Hellwig <hch@...radead.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Neil Brown <neilb@...e.de>, nfs@...ts.sourceforge.net Subject: Re: [NFS] kthread: update lockd to use kthread On Fri, Aug 25, 2006 at 07:07:59PM +0200, Cedric Le Goater wrote: > This kernel thread is a sub thread of the lockd thread. It's a bit more > simple and does not require as much modification. It still depends on the > way its parent is killed and it will require some more work when the sunrpc > thread are fixed. Yes, the whole sunrpc/nfs thread situation is rather difficult. > The SIGKILL used to terminate the threads is a challenge ... it propagates > to sub threads. Some other stuff that bother me in using the kthread api in > sunrpc : nfs_callback_down() uses a wait on a completion with a timeout. > This is not possible with the kthread but might not be really useful. dunno. The usage look buggy to me because we can't guarantee thread exit. But I really don't even understand the requirements for those threads yet, I wish someone could write up a coherent description. - 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