From: "Chuck Lever" <cel@kernel.org>
To: "Mark Brown" <broonie@kernel.org>,
"Chuck Lever" <chuck.lever@oracle.com>
Cc: "Anna Schumaker" <anna.schumaker@hammerspace.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next" <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the nfsd tree with the nfs-anna tree
Date: Tue, 22 Sep 2026 09:09:57 -0400 [thread overview]
Message-ID: <c2820c5b-94c4-4b30-a6e1-cc7e49210d0d@app.fastmail.com> (raw)
In-Reply-To: <arI_XvccOKuOsjzo@sirena.co.uk>
On Tue, Sep 22, 2026, at 4:42 AM, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the nfsd tree got a conflict in:
>
> net/sunrpc/svcsock.c
>
> between commits:
>
> 2ecf0d2af5da8 ("SUNRPC: resume receiving after a TLS control record")
> 1a485d8e93a92 ("SUNRPC: treat every TLS error alert as fatal")
> d3b4fb1d30749 ("SUNRPC: reject a TLS alert record that is not two
> octets")
> f547743e6b51f ("SUNRPC: do not credit control-record octets to the
> RPC stream")
>
> from the nfs-anna tree and commits:
>
> a76d52a01792f ("SUNRPC: Do not credit control-record octets to the
> RPC stream")
> e263b5d674fcf ("SUNRPC: Reject a TLS alert record that is not two
> octets")
> ebcbe4a9a7779 ("SUNRPC: Treat every TLS error alert as fatal")
> 8f765d820c590 ("SUNRPC: Resume receiving after a TLS control record")
> 7f757c41a8beb ("SUNRPC: Reject a socket that already has an svc_sock
> attached")
> 35ab7140c7bfa ("SUNRPC: Separate the TLS control-record receive from
> its policy")
> 9a4ef884d00cd ("SUNRPC: Close the transport on an unhandled TLS
> record type")
> eaef7075c6a48 ("SUNRPC: Flush a received record's pages once it is
> complete")
> 1517c61f247f3 ("SUNRPC: Receive RPC records with ->read_sock")
> 23bec0f9631c2 ("SUNRPC: Bypass sock_recvmsg() for the TLS
> control-record receive")
> 0fce57f554fa6 ("SUNRPC: Skip xpt_reserved accounting for non-UDP
> transports")
>
> from the nfsd tree. This looks like different versions of patches being
> applied with extra stuff then stacked on top. I've taken the nfsd
> version but it's possible that's gone wrong, I'm not *super* confident
> in this. It feels like there's a coordination issue here.
I didn't realize Anna had picked up the TLS-related work. To resolve
these conflicts:
- I can drop the xprtsock.c three (91bdf2ae4a27, 6b91817001fb,
21bcc6ccc6cd) from nfsd-next
- I need to keep the svcsock.c four, as there is follow-on work in
the NFSD queue that depends on those
Anna, can you drop f547743e6b51, d3b4fb1d3074, 1a485d8e93a9,
2ecf0d2af5da from nfs-anna?
--
Chuck Lever (Come to NFS bake-a-thon! https://nfsv4bat.org)
next prev parent reply other threads:[~2026-09-22 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 8:42 Mark Brown
2026-09-22 13:09 ` Chuck Lever [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-22 8:42 Mark Brown
2025-10-02 11:08 Mark Brown
2020-05-29 1:05 Stephen Rothwell
2020-05-29 0:59 Stephen Rothwell
2020-05-29 19:27 ` Chuck Lever
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=c2820c5b-94c4-4b30-a6e1-cc7e49210d0d@app.fastmail.com \
--to=cel@kernel.org \
--cc=anna.schumaker@hammerspace.com \
--cc=broonie@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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
all inboxes | Powered by JetHome®