| 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: <201008171201.10142.agruen@suse.de> Date: Tue, 17 Aug 2010 12:01:09 +0200 From: Andreas Gruenbacher <agruen@...e.de> To: Tvrtko Ursulin <tvrtko.ursulin@...hos.com> Cc: Eric Paris <eparis@...hat.com>, Christoph Hellwig <hch@...radead.org>, Matt Helsley <matthltc@...ibm.com>, "torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>, "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, Michael Kerrisk <michael.kerrisk@...il.com> Subject: Re: [GIT PULL] notification tree - try 37! On Tuesday 17 August 2010 11:45:25 Tvrtko Ursulin wrote: > Why no timeouts? It sounds like a feasible way to work around listeners > which have stopped working. (Timeout and -ETIME for example to be clear, > not allowing access). >From the kernel's point of view, there is no way to guess how long those timeouts should be. Watching for progress can be implemented in user space though. Setting errno to ETIME as a result of trying to access a file is likely to break some applications which are not prepared to receive this error condition; we cannot do that. I'm quite sure that both of these issues have been discussed already. Andreas -- 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