| 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: <AANLkTimfHrXViu0Zm75i4cFED7pXqAvv2edmKRpIi4me@mail.gmail.com> Date: Tue, 25 May 2010 10:10:28 -0400 From: "William A. (Andy) Adamson" <androsadamson@...il.com> To: Lukas Hejtmanek <xhejtman@....muni.cz> Cc: linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, salvet@....muni.cz Subject: Re: Deadlock in NFSv4 in all kernels 2010/5/25 Lukas Hejtmanek <xhejtman@....muni.cz>: > On Tue, May 25, 2010 at 09:45:32AM -0400, William A. (Andy) Adamson wrote: >> Not get into the problem in the first place: this means >> >> 1) determine a 'lead time' where the NFS client declares a context >> expired even though it really as 'lead time' until it actually >> expires. >> >> 2) flush all writes on any contex that will expire within the lead >> time which needs to be long enough for flushes to take place. > > I think you cannot give any guarantees that the flush happens on time. There > can be server overload, network overload, anything and you are out of luck. True - but this will be the case no matter what scheme is in place. The above is to handle the normal working situation. When this fails due to network, server overload, server reboot, i.e. not-normal situation, then use the machine credential. -->Andy > > -- > Lukáš Hejtmánek > -- 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