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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1342032143.2190.22.camel@iscandar.digidescorp.com>
Date:	Wed, 11 Jul 2012 13:42:23 -0500
From:	"Steven J. Magnani" <steve@...idescorp.com>
To:	Jeff Layton <jlayton@...hat.com>
Cc:	viro@...IV.linux.org.uk, linux-fsdevel@...r.kernel.org,
	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	michael.brantley@...haw.com, hch@...radead.org, miklos@...redi.hu,
	pstaubach@...grid.com
Subject: Re: [PATCH v3 00/17] vfs: add the ability to retry on ESTALE to
 several syscalls

Jeff -

On Fri, 2012-06-29 at 14:57 -0400, Jeff Layton wrote: 
> This patchset is the third version of the patchset to add ESTALE
> handling to several syscalls. The basic idea is to allow the client to
> gracefully retry the lookup and call when a NFS server returns ESTALE.

I exercised this using 3.5-rc5 against a memory-starved server that
exports a FAT-backed filesystem. Where normally I see lots of ESTALE
errors due to inode eviction, with this patchset I see none. And, the
performance is much better than the only other way I know to eliminate
the errors, which is to mount with 'lookupcache=none'.

It's not an exhaustive test by any means, just a data point for you. 
Thanks!

Lightly-tested-by: Steve Magnani <steve@...idescorp.com>
------------------------------------------------------------------------
Steven J. Magnani               "I claim this network for MARS!
www.digidescorp.com              Earthling, return my space modulator!"

#include <standard.disclaimer>


--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ