[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250811083356.7911039b@kernel.org>
Date: Mon, 11 Aug 2025 08:33:56 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Alexandra Winter <wintera@...ux.ibm.com>
Cc: "D. Wythe" <alibuda@...ux.alibaba.com>, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, martin.lau@...ux.dev,
pabeni@...hat.com, song@...nel.org, sdf@...gle.com, haoluo@...gle.com,
yhs@...com, edumazet@...gle.com, john.fastabend@...il.com,
kpsingh@...nel.org, jolsa@...nel.org, Mahanta.Jambigi@....com,
Sidraya.Jayagond@....com, wenjia@...ux.ibm.com, dust.li@...ux.alibaba.com,
tonylu@...ux.alibaba.com, guwen@...ux.alibaba.com, bpf@...r.kernel.org,
davem@...emloft.net, netdev@...r.kernel.org, jaka@...ux.ibm.com
Subject: Re: [PATCH bpf-next 2/5] net/smc: fix UAF on smcsk after
smc_listen_out()
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.
Powered by blists - more mailing lists