From: Marko Rauhamaa Subject: Re: fanotify read returns with errno == EOPENSTALE Date: Mon, 24 Apr 2017 10:40:50 +0300 Message-ID: <87shky6ynx.fsf@drapion.f-secure.com> References: <20170322193122.GV29622@ZenIV.linux.org.uk> <87a88c2yxq.fsf@drapion.f-secure.com> <1490270212.3921.10.camel@poochiereds.net> <8760j02mfz.fsf@drapion.f-secure.com> <87lgqwa4tg.fsf@drapion.f-secure.com> <20170420142035.GE22135@quack2.suse.cz> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: (Amir Goldstein's message of "Sat, 22 Apr 2017 10:22:20 +0300") Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Amir Goldstein Cc: Jan Kara , Jeff Layton , Al Viro , linux-fsdevel , Linux NFS Mailing List , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-api@vger.kernel.org Amir Goldstein : > Were you able to verify that both blocking and non-blocking mode work > correctly? May I add your Tested-by and Reported-by tags? I have only verified the nonblocking case in my tests (which are by no means extensive). The reported issue can no longer be reproduced with the patched kernel, and the regular OPEN_PERM function is still operational. Feel free to add me to the tags. Marko