From: Takashi Iwai <tiwai@suse.de>
To: Anna Schumaker <schumaker.anna@gmail.com>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION 4.13-rc] NFS returns -EACCESS at the first read
Date: Wed, 26 Jul 2017 15:30:09 +0200 [thread overview]
Message-ID: <s5hzibrjpge.wl-tiwai@suse.de> (raw)
In-Reply-To: <acfb6b19-b183-16ef-a6c5-2fc97cf8eb6b@gmail.com>
On Wed, 26 Jul 2017 14:57:07 +0200,
Anna Schumaker wrote:
>
> Hi Takashi,
>
> On 07/26/2017 08:54 AM, Takashi Iwai wrote:
> > Hi,
> >
> > I seem hitting a regression of NFS client on the today's Linus git
> > tree. The symptom is that the file read over NFS returns occasionally
> > -EACCESS at the first read. When I try to read the same file again
> > (or do some other thing), I can read it successfully.
> >
> > The git bisection leaded to the commit
> > bd8b2441742b49c76bec707757bd9c028ea9838e
> > NFS: Store the raw NFS access mask in the inode's access cache
> >
> >
> > Any further hint for debugging?
>
> Does the patch in this email thread help? http://www.spinics.net/lists/linux-nfs/msg64930.html
Thanks, I gave it a shot and the result looks good. Feel free to my
tested-by tag:
Tested-by: Takashi Iwai <tiwai@suse.de>
Though, when I look around the code, I feel somehow uneasy by that
still MAY_XXX is used for nfs_access_entry.mask, e.g. in
nfs3_proc_access() or nfs4_proc_access(). Are these function OK
without the similar conversion?
thanks,
Takashi
next prev parent reply other threads:[~2017-07-26 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 12:54 Takashi Iwai
2017-07-26 12:57 ` Anna Schumaker
2017-07-26 13:30 ` Takashi Iwai [this message]
2017-07-26 13:37 ` Anna Schumaker
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=s5hzibrjpge.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=schumaker.anna@gmail.com \
--cc=trond.myklebust@primarydata.com \
/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
all inboxes | Powered by JetHome®