Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751739AbdGZMyR (ORCPT ); Wed, 26 Jul 2017 08:54:17 -0400 Received: from mx2.suse.de ([195.135.220.15]:34101 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751089AbdGZMyP (ORCPT ); Wed, 26 Jul 2017 08:54:15 -0400 Date: Wed, 26 Jul 2017 14:54:13 +0200 Message-ID: From: Takashi Iwai To: Trond Myklebust Cc: Anna Schumaker , linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [REGRESSION 4.13-rc] NFS returns -EACCESS at the first read User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.2 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 466 Lines: 18 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