fuzz testing gave today : "kernel: NFS: nfs4_reclaim_open_state: unhandled error -13"

[Toralf Förster]

happens within a 32 bit user mode linux guest running latest git tree v3.17-9981-g929254d
It occurred few times about half an hour after the test case was started.

Well, it is very early in the current release cycle, so just asking, if this is already known / worth to investigate ?

[Trond Myklebust]

happens within a 32 bit user mode linux guest running latest git tree=

v3.17-9981-g929254d

It occurred few times about half an hour after the test case was star=

ted.

Well, it is very early in the current release cycle, so just asking, =

if this is already known / worth to investigate ?

Errno 13 is EACCES. Might the test case involve changing the mode
bits/acls on an open file, then putting the client in situation where
an expired lease causes it to attempt open state recovery?

Cheers
Trond
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Toralf Förster]

Post by Trond Myklebust
Errno 13 is EACCES. Might the test case involve changing the mode
bits/acls on an open file, then putting the client in situation where
an expired lease causes it to attempt open state recovery?

right - that's likely possible due to 2 trinity childs running in parallel