Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <08b1fc12a271688c908ad615c08f910c3ec19672.camel@kernel.org>
Subject: Re: [PATCH v1 26/27] SUNRPC: Set rq_accept_statp inside ->accept
 methods
From:   Jeff Layton <jlayton@kernel.org>
To:     Chuck Lever III <chuck.lever@oracle.com>
Cc:     Jiri Slaby <jirislaby@kernel.org>,
        Steve Dickson <SteveD@redhat.com>,
        Chuck Lever <cel@kernel.org>,
        Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
        Neil Brown <neilb@suse.de>,
        Alexander Ahring Oder Aring <aahringo@redhat.com>
Date:   Tue, 16 May 2023 17:25:19 -0400
In-Reply-To: <0DEDF045-8C95-463D-B5E7-D2A3DF3230FC@oracle.com>
References: <167319499150.7490.2294168831574653380.stgit@bazille.1015granger.net>
         <167319546521.7490.43383592461162363.stgit@bazille.1015granger.net>
         <3e34a2dc-7d72-b719-248f-e78361db8a5b@kernel.org>
         <4AB1ED03-57C8-42C1-9A04-6C224E98EDCC@oracle.com>
         <569be8e6eff7af373e6baaf2170edb8a8c52f262.camel@kernel.org>
         <0DEDF045-8C95-463D-B5E7-D2A3DF3230FC@oracle.com>
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.1 (3.48.1-1.fc38) 
MIME-Version: 1.0
Precedence: bulk

On Tue, 2023-05-16 at 19:25 +0000, Chuck Lever III wrote:
>=20
> > On May 16, 2023, at 3:23 PM, Jeff Layton <jlayton@kernel.org> wrote:
> >=20
> > On Tue, 2023-05-02 at 14:14 +0000, Chuck Lever III wrote:
> > >=20
> > > > On May 2, 2023, at 7:01 AM, Jiri Slaby <jirislaby@kernel.org> wrote=
:
> > > >=20
> > > > On 08. 01. 23, 17:31, Chuck Lever wrote:
> > > > > From: Chuck Lever <chuck.lever@oracle.com>
> > > > > To navigate around the space that svcauth_gss_accept() reserves
> > > > > for the RPC payload body length and sequence number fields,
> > > > > svcauth_gss_release() does a little dance with the reply's
> > > > > accept_stat, moving the accept_stat value in the response buffer
> > > > > down by two words.
> > > > > Instead, let's have the ->accept() methods each set the proper
> > > > > final location of the accept_stat to avoid having to move
> > > > > things.
> > > >=20
> > > > Hi,
> > > >=20
> > > > I bisected to this (4bcf0343e8)
> > >=20
> > > Assuming you did the bisect on the NFS server's kernel?
> > >=20
> > >=20
> > > > as it breaks nfs3-only servers in 6.3. I.e. /etc/nfs.conf containin=
g:
> > > > [nfsd]
> > > > vers4=3Dno
> > >=20
> > > Note: Changing the settings in /etc/nfs.conf had no effect
> > > on my server, so I effected the change by stopping the
> > > server and poking values into /proc/fs/nfsd/versions by
> > > hand.
> > >=20
> > > Steve?
> > >=20
> > >=20
> > > > The client sees:
> > > > mount("10.0.2.15:/tmp", "/mnt", "nfs", 0, "vers=3D4.2,addr=3D10.0.2=
.15,clientad"...) =3D -1 EIO (Input/output error)
> > > > write(2, "mount.nfs: mount system call fai"..., 45
> > > > mount.nfs: mount system call failed for /mnt
> > > >=20
> > > > And the kernel says:
> > > > nfs4_discover_server_trunking unhandled error -5. Exiting with erro=
r EIO
> > > >=20
> > > > I reported in downstream as:
> > > > https://bugzilla.suse.com/show_bug.cgi?id=3D1210995
> > > >=20
> > > > It cannot be reverted cleanly on the top of 6.3.
> > > >=20
> > > > Any ideas?
> > >=20
> > > I can reproduce a similar problem. Network capture shows
> > > that the server is responding with NFS4ERR_NOENT to the
> > > EXCHANGE_ID operation, and the client kernel log says:
> > >=20
> > > > nfs4_discover_server_trunking unhandled error -121. Exiting with er=
ror EIO
> > >=20
> > > That's not the failure mode I expected given the commit
> > > you bisected to, so it might not be the same problem you've
> > > hit. I'll troubleshoot this and send a fix for testing.
> > >=20
> >=20
> > Alex hit this problem in testing too, and I took a quick look.
> >=20
> > In the attached capture, the client should have gotten back a
> > RPC_PROG_MISMATCH error, but the server has recorded an extra successfu=
l
> > accept state before encoding the RPC_PROG_MISMATCH error, leading to a
> > malformed reply.
> >=20
> > I think that the problem is that encoding the accept status too early
> > means that we can't properly handle failures from the pg_init_request
> > call.
> >=20
> > Chuck, any thoughts on how you'd like to handle this?
>=20
> With this:
>=20
> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git/commit/?h=
=3Dnfsd-fixes&id=3D29cd2927fb914cc53b5ba4f67d2b74695c994ba4
>=20
> I plan to send the fix to Linus tomorrow.
>=20
>=20

Oh! I hadn't seen that cross the list. Did I miss it?
--=20
Jeff Layton <jlayton@kernel.org>