From: Jakub Kicinski <kuba@kernel.org>
To: patchwork-bot+netdevbpf@kernel.org
Cc: Kuniyuki Iwashima <kuniyu@amazon.com>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
allison.henderson@oracle.com, kuni1840@gmail.com,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
rds-devel@oss.oracle.com
Subject: Re: [PATCH v5 net 0/2] tcp/rds: Fix use-after-free around kernel TCP reqsk.
Date: Tue, 12 Mar 2024 19:02:35 -0700 [thread overview]
Message-ID: <20240312190235.7ac3bcb4@kernel.org> (raw)
In-Reply-To: <20240312085942.3601d2c6@kernel.org>
On Tue, 12 Mar 2024 08:59:42 -0700 Jakub Kicinski wrote:
> On Tue, 12 Mar 2024 15:10:32 +0000 patchwork-bot+netdevbpf@kernel.org
> wrote:
> > - [v5,net,1/2] tcp: Fix NEW_SYN_RECV handling in inet_twsk_purge()
> > https://git.kernel.org/netdev/net/c/a7b7079bc292
> > - [v5,net,2/2] rds: tcp: Fix use-after-free of net in reqsk_timer_handler().
> > https://git.kernel.org/netdev/net/c/a28895fc04fa
>
> I think I need to discard these, otherwise I won't be able to fast
> forward after Linus pulls :( I re-apply later.
Back in it goes, hopefully we didn't cause too much strife with
the reset.
prev parent reply other threads:[~2024-03-13 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 20:01 [PATCH v5 net 0/2] tcp/rds: Fix use-after-free around kernel TCP reqsk Kuniyuki Iwashima
2024-03-08 20:01 ` [PATCH v5 net 1/2] tcp: Fix NEW_SYN_RECV handling in inet_twsk_purge() Kuniyuki Iwashima
2024-03-08 20:01 ` [PATCH v5 net 2/2] rds: tcp: Fix use-after-free of net in reqsk_timer_handler() Kuniyuki Iwashima
2024-03-12 11:04 ` Paolo Abeni
2024-03-12 12:34 ` Eric Dumazet
2024-03-12 15:10 ` [PATCH v5 net 0/2] tcp/rds: Fix use-after-free around kernel TCP reqsk patchwork-bot+netdevbpf
2024-03-12 15:59 ` Jakub Kicinski
2024-03-13 2:02 ` Jakub Kicinski [this message]
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=20240312190235.7ac3bcb4@kernel.org \
--to=kuba@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=rds-devel@oss.oracle.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).