Linux NFS development
 help / color / mirror / Atom feed
From: Max Vozeler <max@vozeler.com>
To: Chuck Lever <chuck.lever@oracle.com>,
	Sasha Levin <sashal@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Chris Mason <clm@meta.com>, Jeff Layton <jlayton@kernel.org>
Cc: linux-nfs@vger.kernel.org, stable@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [Regression linux-6.1.y]: NFSv4 server: sec=krb5p mount fails with EIO in 6.1.192
Date: Sat, 21 Nov 2026 13:30:49 +0100	[thread overview]
Message-ID: <awGO-R42ggk_WEga@dp.vpn.hinterhof.net> (raw)
In-Reply-To: <awFyZbQE8pDyOxUy@dp.vpn.hinterhof.net>

[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]

#regzbot introduced: 82cf21374fb7ee55b37be9afb6704ba0eeffb236

On Sat, Nov 21, 2026 at 11:28:53AM +0100, Max Vozeler wrote:
> On Fri, Nov 20, 2026 at 02:17:43PM +0100, Max Vozeler wrote:
> > after upgrading an NFS server (Debian bookworm) to 6.1.192
> > (Debian linux-image-6.1.0-55-amd64), NFSv4 clients fail to mount exports
> > using sec=krb5p with EIO.
> > 
> > Downgrading the server back to 6.1.190 (linux-image-6.1.0-54-amd64)
> > makes things work again.
> > 
> > Good: 6.1.190 (Debian linux-image-6.1.0-54-amd64)
> > Bad:  6.1.192 (Debian linux-image-6.1.0-55-amd64, linux-image-6.1.0-56-amd64)
> 
> Reproduced with vanilla 6.1.191 and 6.1.192
> 
> Good: 6.1.190
> Bad: 6.1.191, 6.1.192

bisect points to

commit 82cf21374fb7ee55b37be9afb6704ba0eeffb236
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Mon Jan 2 12:07:07 2023 -0500

    SUNRPC: Convert unwrap_priv_data() to use xdr_stream
    
    [ Upstream commit 42140718ea26c47fb06c679451a6aa6703545136 ]
    
    Done as part of hardening the server-side RPC header decoding path.
    
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Stable-dep-of: a919c5c88769 ("SUNRPC: svcauth_gss: enforce krb5 token minimum length")
    Signed-off-by: Sasha Levin <sashal@kernel.org>

This seems to have been part of a larger series, only parts of which
were backported for a919c5c88769 ?

Best regards,
Max

[-- Attachment #2: bisect.log --]
[-- Type: text/plain, Size: 1637 bytes --]

git bisect start
# status: waiting for both good and bad commits
# bad: [08889840163ebcdb7e24bf7ec311bc2e6fc3aaea] Linux 6.1.191
git bisect bad 08889840163ebcdb7e24bf7ec311bc2e6fc3aaea
# status: waiting for good commit(s), bad commit known
# good: [79807e970724c1f90cee1316361d61b80db4eef6] Linux 6.1.190
git bisect good 79807e970724c1f90cee1316361d61b80db4eef6
# good: [91c2a5d201daf66fa3f42b8a383bb89174bde2c8] serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN
git bisect good 91c2a5d201daf66fa3f42b8a383bb89174bde2c8
# bad: [ab8c8e027fa8f9314340a96999dd3309b7f80d61] fbdev: ssd1307fb: defer I2C transfers from damage callbacks
git bisect bad ab8c8e027fa8f9314340a96999dd3309b7f80d61
# good: [35b46918d5deee01fade7e2f2075a7c238a2a0e8] cifs: prevent readdir from changing file size due to stale directory metadata
git bisect good 35b46918d5deee01fade7e2f2075a7c238a2a0e8
# good: [91abd8383fd0588d1fcc31120d6344150a64ba5a] net: sched: cls_api: add filter counter
git bisect good 91abd8383fd0588d1fcc31120d6344150a64ba5a
# bad: [ed126ca71d4d949ad99f40b974a8f7685e808f8b] net/packet: defer vmalloc TX_RING free until skbs finish
git bisect bad ed126ca71d4d949ad99f40b974a8f7685e808f8b
# bad: [82cf21374fb7ee55b37be9afb6704ba0eeffb236] SUNRPC: Convert unwrap_priv_data() to use xdr_stream
git bisect bad 82cf21374fb7ee55b37be9afb6704ba0eeffb236
# good: [8da6f765098d46e5b3178ef4b2f8273c9ba1d3bb] SUNRPC: Rename automatic variables in unwrap_priv_data()
git bisect good 8da6f765098d46e5b3178ef4b2f8273c9ba1d3bb
# first bad commit: [82cf21374fb7ee55b37be9afb6704ba0eeffb236] SUNRPC: Convert unwrap_priv_data() to use xdr_stream

  reply	other threads:[~2026-11-21 12:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 13:17 [Regression linux-6.1.y]: NFSv4 server: sec=krb5p mount fails with EIO in 6.1.192 Max Vozeler
2026-11-21 10:28 ` Max Vozeler
2026-11-21 12:30   ` Max Vozeler [this message]
2026-11-21 12:54     ` Max Vozeler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=awGO-R42ggk_WEga@dp.vpn.hinterhof.net \
    --to=max@vozeler.com \
    --cc=chuck.lever@oracle.com \
    --cc=clm@meta.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox