Return-Path: Received: from mail-qk0-f176.google.com ([209.85.220.176]:35739 "EHLO mail-qk0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751863AbdFNM3P (ORCPT ); Wed, 14 Jun 2017 08:29:15 -0400 Received: by mail-qk0-f176.google.com with SMTP id a199so34131967qkb.2 for ; Wed, 14 Jun 2017 05:29:15 -0700 (PDT) Message-ID: <1497443353.6752.5.camel@redhat.com> Subject: Re: "nfs4_discover_server_trunking unhandled error" on Ctrl-C From: Jeff Layton To: "Mkrtchyan, Tigran" , Olga Kornievskaia Cc: linux-nfs , Andy Adamson Date: Wed, 14 Jun 2017 08:29:13 -0400 In-Reply-To: <1087115680.14242025.1497381738583.JavaMail.zimbra@desy.de> References: <991293071.14131572.1497360717136.JavaMail.zimbra@desy.de> <1087115680.14242025.1497381738583.JavaMail.zimbra@desy.de> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-nfs-owner@vger.kernel.org List-ID: That warning has been around for a long time. We're running the server trunking check and caught a signal in the middle of it. It's harmless, AFAICT. Should we merge a patch like this (untested) one, just to silence it? It really is an expected situation that we needn't warn anyone about: diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c index b34de036501b..ae9a9ad2894d 100644 --- a/fs/nfs/nfs4state.c +++ b/fs/nfs/nfs4state.c @@ -2182,6 +2182,9 @@ int nfs4_discover_server_trunking(struct nfs_client *clp, * in nfs4_exchange_id */ status = -EKEYEXPIRED; break; + case -ERESTARTSYS: + status = -EINTR; + break; default: pr_warn("NFS: %s unhandled error %d. Exiting with error EIO\n", __func__, status); On Tue, 2017-06-13 at 21:22 +0200, Mkrtchyan, Tigran wrote: > Hi Olga, > > this is 4.12.-rc4. I will check packet capture tomorrow, however, I am pretty sure that > this is client internal interrupt processing. > > Tigran. > > ----- Original Message ----- > > From: "Olga Kornievskaia" > > To: "Tigran Mkrtchyan" > > Cc: "linux-nfs" , "Andy Adamson" > > Sent: Tuesday, June 13, 2017 6:21:01 PM > > Subject: Re: "nfs4_discover_server_trunking unhandled error" on Ctrl-C > > On Tue, Jun 13, 2017 at 9:31 AM, Mkrtchyan, Tigran > > wrote: > > > > > > If I hit Ctrl-C during mount, then I see following message in the log file: > > > > > > NFS: nfs4_discover_server_trunking unhandled error -512. Exiting with error EIO > > > > > > > > > produced at nfs4state.c:2533. Is this expected behavior? > > > > What kernel version (or upstream commit) is that? Is this > > reproducible? Anything on the network trace that server returns that > > could explain an error it doesn't expect. Also I'm thinking that > > nfs_wait_client_init_complete() could be interrupted by ctrl-c and > > return ERESTARTSYS and that could translate to "unhanded error". > > -- > > 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 > > -- > 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 -- Jeff Layton