linux-kernel - Re: [pnfs] [GIT BISECT] first bad commit: 1f36f774 Switch !O_CREAT case to use of do

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: <4BAB2937.6050703@panasas.com>
Date:	Thu, 25 Mar 2010 11:13:27 +0200
From:	Boaz Harrosh <bharrosh@...asas.com>
To:	Trond Myklebust <trond.myklebust@....uio.no>
CC:	Al Viro <viro@...IV.linux.org.uk>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	"J. Bruce Fields" <bfields@...i.umich.edu>,
	pNFS Mailing List <pnfs@...ux-nfs.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [pnfs] [GIT BISECT] first bad commit: 1f36f774 Switch !O_CREAT
 case to use of do_last()

On 03/24/2010 08:10 PM, Trond Myklebust wrote:
> On Wed, 2010-03-24 at 14:02 -0400, Trond Myklebust wrote: 
>> I'd say you have a corruption issue either on the server side or on your
>> client.
> 

It is surely a corruption on the client. I've tested with an old server
and it fails just the same.

> By the way. Does this issue happen with NFSv4 too, or is it only
> NFSv4.1?
> 
> Trond
> 

-o minorversion=0 or =1 does not matter.
nfsv3 does not have that problem. (Same client different server though)

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