From: Paolo Abeni <pabeni@redhat.com>
To: David Howells <dhowells@redhat.com>, netdev@vger.kernel.org
Cc: Marc Dionne <marc.dionne@auristor.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net 2/2] rxrpc: Fix the rxrpc_connection attend queue handling
Date: Tue, 4 Feb 2025 12:12:32 +0100 [thread overview]
Message-ID: <716751b5-6907-4fbb-bb07-0223f5761299@redhat.com> (raw)
In-Reply-To: <20250203110307.7265-3-dhowells@redhat.com>
On 2/3/25 12:03 PM, David Howells wrote:
> The rxrpc_connection attend queue is never used because conn::attend_link
> is never initialised and so is always NULL'd out and thus always appears to
> be busy. This requires the following fix:
>
> (1) Fix this the attend queue problem by initialising conn::attend_link.
>
> And, consequently, two further fixes for things masked by the above bug:
>
> (2) Fix rxrpc_input_conn_event() to handle being invoked with a NULL
> sk_buff pointer - something that can now happen with the above change.
>
> (3) Fix the RXRPC_SKB_MARK_SERVICE_CONN_SECURED message to carry a pointer
> to the connection and a ref on it.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
> cc: Marc Dionne <marc.dionne@auristor.com>
> cc: Jakub Kicinski <kuba@kernel.org>
> cc: "David S. Miller" <davem@davemloft.net>
> cc: Eric Dumazet <edumazet@google.com>
> cc: Paolo Abeni <pabeni@redhat.com>
> cc: Simon Horman <horms@kernel.org>
> cc: linux-afs@lists.infradead.org
> cc: netdev@vger.kernel.org
A couple of minor nits: I think this deserves a 'Fixes' tag, and
possibly split into separate patches to address the reported problems
individually.
Thanks,
Paolo
next prev parent reply other threads:[~2025-02-04 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 11:03 [PATCH net 0/2] rxrpc: Miscellaneous fixes David Howells
2025-02-03 11:03 ` [PATCH net 1/2] rxrpc: Fix call state set to not include the SERVER_SECURING state David Howells
2025-02-03 11:03 ` [PATCH net 2/2] rxrpc: Fix the rxrpc_connection attend queue handling David Howells
2025-02-04 11:12 ` Paolo Abeni [this message]
2025-02-04 14:09 ` David Howells
2025-02-04 14:34 ` Paolo Abeni
2025-02-04 15:46 ` David Howells
2025-02-04 10:39 ` [PATCH net 1/2] rxrpc: Fix call state set to not include the SERVER_SECURING state David Howells
2025-02-04 14:40 ` [PATCH net 0/2] rxrpc: Miscellaneous fixes patchwork-bot+netdevbpf
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=716751b5-6907-4fbb-bb07-0223f5761299@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@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®