From: Jakub Kicinski <kuba@kernel.org>
To: Alexandra Winter <wintera@linux.ibm.com>
Cc: "D. Wythe" <alibuda@linux.alibaba.com>,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, pabeni@redhat.com, song@kernel.org,
sdf@google.com, haoluo@google.com, yhs@fb.com,
edumazet@google.com, john.fastabend@gmail.com,
kpsingh@kernel.org, jolsa@kernel.org, Mahanta.Jambigi@ibm.com,
Sidraya.Jayagond@ibm.com, wenjia@linux.ibm.com,
dust.li@linux.alibaba.com, tonylu@linux.alibaba.com,
guwen@linux.alibaba.com, bpf@vger.kernel.org,
davem@davemloft.net, netdev@vger.kernel.org, jaka@linux.ibm.com
Subject: Re: [PATCH bpf-next 2/5] net/smc: fix UAF on smcsk after smc_listen_out()
Date: Mon, 11 Aug 2025 08:33:56 -0700 [thread overview]
Message-ID: <20250811083356.7911039b@kernel.org> (raw)
In-Reply-To: <14ec76a2-e80e-44a8-a775-ebd4668959c4@linux.ibm.com>
On Mon, 11 Aug 2025 11:24:50 +0200 Alexandra Winter wrote:
> > Yes, it should be sent to net. But the problem is that if I don't carry
> > this patch, the BPF CI test will always crash. Maybe I should send a
> > copy to both net and bpf-next? Do you have any suggestions?
>
> I do not have any experience with bpf-next. But typically patches
> to 'net' are taken after one or two days, if there are no issues.
> I'd assume they are then picked to net-next and bpf-next(?) almost instantly.
> Then you would not need it in your bpf series anymore.
AFAIU the patches which land in net will make it to -next trees after
respective PR with fixes. So
patch ->
net ->
[next Thu] Linus ->
[same day] net-next
[at some point] bpf PR ->
Linux
-> bpf-next
What gets applied to net should be in net-next in a week,
and most -next trees within 2 weeks.
next prev parent reply other threads:[~2025-08-11 15:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 8:42 [PATCH bpf-next 0/5] net/smc: Introduce smc_hs_ctrl D. Wythe
2025-07-31 8:42 ` [PATCH bpf-next 1/5] bpf: export necessary sympols for modules with struct_ops D. Wythe
2025-07-31 12:53 ` Alexandra Winter
2025-08-11 2:23 ` D. Wythe
2025-07-31 8:42 ` [PATCH bpf-next 2/5] net/smc: fix UAF on smcsk after smc_listen_out() D. Wythe
2025-07-31 12:57 ` Alexandra Winter
2025-08-11 1:54 ` D. Wythe
2025-08-11 9:24 ` Alexandra Winter
2025-08-11 15:33 ` Jakub Kicinski [this message]
2025-08-18 5:39 ` D. Wythe
2025-07-31 8:42 ` [PATCH bpf-next 3/5] net/smc: bpf: Introduce generic hook for handshake flow D. Wythe
2025-07-31 19:55 ` kernel test robot
2025-07-31 8:42 ` [PATCH bpf-next 4/5] libbpf: fix error when st-prefix_ops and ops from differ btf D. Wythe
2025-07-31 8:42 ` [PATCH bpf-next 5/5] bpf/selftests: add selftest for bpf_smc_hs_ctrl D. Wythe
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=20250811083356.7911039b@kernel.org \
--to=kuba@kernel.org \
--cc=Mahanta.Jambigi@ibm.com \
--cc=Sidraya.Jayagond@ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=haoluo@google.com \
--cc=jaka@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.