mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [REGRESSION 4.13-rc] NFS returns -EACCESS at the first read
@ 2017-07-26 12:54 Takashi Iwai
  2017-07-26 12:57 ` Anna Schumaker
  0 siblings, 1 reply; 4+ messages in thread
From: Takashi Iwai @ 2017-07-26 12:54 UTC (permalink / raw)
  To: Trond Myklebust; +Cc: Anna Schumaker, linux-nfs, linux-kernel

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?


thanks,

Takashi

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [REGRESSION 4.13-rc] NFS returns -EACCESS at the first read
  2017-07-26 12:54 [REGRESSION 4.13-rc] NFS returns -EACCESS at the first read Takashi Iwai
@ 2017-07-26 12:57 ` Anna Schumaker
  2017-07-26 13:30   ` Takashi Iwai
  0 siblings, 1 reply; 4+ messages in thread
From: Anna Schumaker @ 2017-07-26 12:57 UTC (permalink / raw)
  To: Takashi Iwai, Trond Myklebust; +Cc: Anna Schumaker, linux-nfs, linux-kernel

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,
Anna
> 
> 
> thanks,
> 
> Takashi
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [REGRESSION 4.13-rc] NFS returns -EACCESS at the first read
  2017-07-26 12:57 ` Anna Schumaker
@ 2017-07-26 13:30   ` Takashi Iwai
  2017-07-26 13:37     ` Anna Schumaker
  0 siblings, 1 reply; 4+ messages in thread
From: Takashi Iwai @ 2017-07-26 13:30 UTC (permalink / raw)
  To: Anna Schumaker; +Cc: Trond Myklebust, Anna Schumaker, linux-nfs, linux-kernel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [REGRESSION 4.13-rc] NFS returns -EACCESS at the first read
  2017-07-26 13:30   ` Takashi Iwai
@ 2017-07-26 13:37     ` Anna Schumaker
  0 siblings, 0 replies; 4+ messages in thread
From: Anna Schumaker @ 2017-07-26 13:37 UTC (permalink / raw)
  To: Takashi Iwai; +Cc: Trond Myklebust, Anna Schumaker, linux-nfs, linux-kernel



On 07/26/2017 09:30 AM, Takashi Iwai wrote:
> 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?

I just started looking at that at the end of the day yesterday.  I think they work by accident, since all the bits in the mask are set by nfs_do_access().  They should probably be converted, but I don't think it's urgent.

Anna

> 
> 
> thanks,
> 
> Takashi
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-07-26 13:37 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-07-26 12:54 [REGRESSION 4.13-rc] NFS returns -EACCESS at the first read Takashi Iwai
2017-07-26 12:57 ` Anna Schumaker
2017-07-26 13:30   ` Takashi Iwai
2017-07-26 13:37     ` Anna Schumaker

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®