| 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: <20130103220814.GB2753@mtj.dyndns.org> Date: Thu, 3 Jan 2013 17:08:14 -0500 From: Tejun Heo <tj@...nel.org> To: "J. Bruce Fields" <bfields@...ldses.org> Cc: "Adamson, Dros" <Weston.Adamson@...app.com>, "Myklebust, Trond" <Trond.Myklebust@...app.com>, Dave Jones <davej@...hat.com>, Linux Kernel <linux-kernel@...r.kernel.org>, "linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org> Subject: Re: nfsd oops on Linus' current tree. Hello, On Thu, Jan 03, 2013 at 03:11:20PM -0500, J. Bruce Fields wrote: > Both rpciod and nfsiod already set WQ_MEM_RECLAIM. > > But, right, looking at kernel/workqueue.c, it seems that the dedicated > "rescuer" threads are invoked only in the case when work is stalled > because a new worker thread isn't allocated quickly enough. Because that's the *only* case where progress can't be guaranteed otherwise. > So, what to do that's simplest enough that it would work for > post-rc2/stable? I was happy having just a simple dedicated > thread--these are only started when nfsd is, so there's no real thread > proliferation problem. The analysis is likely completely wrong, so please don't go off doing something unnecessary. Please take look at what's causing the deadlocks again. Thanks. -- tejun -- 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