From: Andreas Radke <a.radke@arcor.de>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 ACL issues since 3.0.72 leading to corrupt files (xfs)
Date: Sun, 12 May 2013 12:19:58 +0200 [thread overview]
Message-ID: <20130512121958.1c1be5ec@workstation64.home> (raw)
In-Reply-To: <1368331183.7978.6.camel@leira.trondhjem.org>
Am Sun, 12 May 2013 03:59:47 +0000
schrieb "Myklebust, Trond" <Trond.Myklebust@netapp.com>:
> Only one of those is an NFS server change (the one which rejects
> negative server lengths). Unless your NFS server is also acting as an
> NFS client, it is highly unlikely that the other patches are relevant.
>
> So the relevant commit to revert should be
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.0.y&id=7e36f505caf7882b6cc89ecedcd7f26749ef917a
>
Thanks for your help. Unfortunately even reverting all 4 commits didn't
solve my file corrupting issues. Now I need to check what other
commit in 3.0.72 could cause this.
Sorry for noise here.
-Andy
prev parent reply other threads:[~2013-05-12 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 19:55 NFSv4 ACL issues since 3.0.72 leading to corrupt files (xfs) Andreas Radke
2013-05-11 2:56 ` Myklebust, Trond
2013-05-11 9:56 ` Andreas Radke
2013-05-12 3:59 ` Myklebust, Trond
2013-05-12 10:19 ` Andreas Radke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130512121958.1c1be5ec@workstation64.home \
--to=a.radke@arcor.de \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox