From: Sabrina Dubroca <sd@queasysnail.net>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: netdev-bot+sashiko@kernel.org, netdev@vger.kernel.org,
herbert@gondor.apana.org.au, stable@vger.kernel.org,
yuantan098@gmail.com, yifanwucs@gmail.com,
tomapufckgml@gmail.com, bird@lzu.edu.cn, ronbogo@outlook.com,
zylzyl2333@gmail.com, n05ec@lzu.edu.cn, eulgyukim@snu.ac.kr,
jjy600901@snu.ac.kr, kuba@kernel.org
Subject: Re: [PATCH ipsec] xfrm: espintcp: reorder operations within espintcp_init_sk
Date: Thu, 8 Oct 2026 14:38:40 +0200 [thread overview]
Message-ID: <aseO0MuammN_z0he@krikkit> (raw)
In-Reply-To: <asXrPCMX747L5_tq@secunet.com>
2026-10-07, 08:48:28 +0200, Steffen Klassert wrote:
> On Thu, Oct 01, 2026 at 12:55:11PM +0000, netdev-bot+sashiko@kernel.org wrote:
> > Thank you for your contribution! Sashiko AI review found 1 potential
> > issue(s) to consider.
> >
> > Critical: 0 · High: 1 · Medium: 0 · Low: 0
> >
> > If you believe none of the issues are legitimate, please reply to each
> > issue of Medium severity or higher and explain why the AI is wrong.
> > If any of them are legitimate and you plan to respin, please let patchwork
> > know by including "pw-bot: cr" as a separate line at the end of your reply
> > (one such reply per series is enough).
> >
> > - [High] The patch does not fully close the race it targets.
> >
> > --
> >
> > xfrm: espintcp: reorder operations within espintcp_init_sk
> >
[...]
> Sabrina, do you plan to update this one?
Sorry Steffen, too much stuff happening at the same time and this one
was a bit complex. Let's see if the AI is happy with v2.
--
Sabrina
prev parent reply other threads:[~2026-10-08 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 17:53 [PATCH ipsec] xfrm: espintcp: reorder operations within espintcp_init_sk Sabrina Dubroca
2026-09-28 17:59 ` netdev-bot+sinfo
2026-10-01 12:55 ` netdev-bot+sashiko
2026-10-07 6:48 ` Steffen Klassert
2026-10-08 12:38 ` Sabrina Dubroca [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=aseO0MuammN_z0he@krikkit \
--to=sd@queasysnail.net \
--cc=bird@lzu.edu.cn \
--cc=eulgyukim@snu.ac.kr \
--cc=herbert@gondor.apana.org.au \
--cc=jjy600901@snu.ac.kr \
--cc=kuba@kernel.org \
--cc=n05ec@lzu.edu.cn \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ronbogo@outlook.com \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=tomapufckgml@gmail.com \
--cc=yifanwucs@gmail.com \
--cc=yuantan098@gmail.com \
--cc=zylzyl2333@gmail.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