From: Sabrina Dubroca <sd@queasysnail.net>
To: Xuanqiang Luo <xuanqiang.luo@linux.dev>
Cc: Jaeyoung Chung <jjy600901@snu.ac.kr>,
horms@kernel.org, linux-kernel@vger.kernel.org,
eulgyukim@snu.ac.kr, davem@davemloft.net, edumazet@google.com,
herbert@gondor.apana.org.au, kuba@kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
steffen.klassert@secunet.com, zylzyl2333@gmail.com
Subject: Re: [BUG] general protection fault in espintcp_sendmsg
Date: Thu, 24 Sep 2026 18:27:58 +0200 [thread overview]
Message-ID: <arVPjqf1LPVKWRK0@krikkit> (raw)
In-Reply-To: <15476f67-1484-4af8-bc5e-ce32fb24607f@linux.dev>
2026-08-20, 16:22:19 +0800, Xuanqiang Luo wrote:
> Hi Jaeyoung,
>
> 在 2026/8/19 23:53, Jaeyoung Chung 写道:
> > Hello,
> >
> > We found a "general protection fault in espintcp_sendmsg" on Linux v7.2.
> > The issue was found by our own race fuzzer. We have not analyzed the root
> > cause, so we do not have a proposed fix to offer.
> >
> > To reproduce the race reliably, we applied the delay patch below to the
> > kernel and ran the C reproducer as root inside an x86_64 QEMU guest. The
> > crash log we observed, the delay patch and the reproducer are all included
> > below.
> >
> > The following kernel config options are required to reproduce the issue:
> > CONFIG_XFRM=y
> > CONFIG_XFRM_USER=y
> > CONFIG_INET_ESP=y
> > CONFIG_INET_ESPINTCP=y
> > CONFIG_KASAN=y
> >
> > We hope this report is useful. Please let us know if any further
> > information would help.
> >
> > Reported-by: Eulgyu Kim <eulgyukim@snu.ac.kr>
> > Reported-by: Jaeyoung Chung <jjy600901@snu.ac.kr>
>
> Thanks for the report.
>
> I suspect the issue you reproduced is the same race that Yilin Zhu
> attempted to address a few months ago:
>
> https://lore.kernel.org/all/c30b645074a1b379e0f7fe297f917c66137d9964.1778464688.git.zylzyl2333@gmail.com/
>
> I have added Yilin and Sabrina back to Cc. Sabrina reviewed that patch,
> but as far as I can tell, no revised version was posted afterwards. I
> do not know the current status of that work.
Thanks. I made some comments on the patch and never got an answer or a
v2. I'll take over and add some tags for the reporters/authors of v1
and of this thread.
I should be able to send it either tonight or tomorrow.
--
Sabrina
next prev parent reply other threads:[~2026-09-24 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 15:53 Jaeyoung Chung
2026-08-20 8:22 ` Xuanqiang Luo
2026-09-24 16:27 ` Sabrina Dubroca [this message]
2026-08-20 9:49 ` Breno Leitao
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=arVPjqf1LPVKWRK0@krikkit \
--to=sd@queasysnail.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eulgyukim@snu.ac.kr \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=jjy600901@snu.ac.kr \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=xuanqiang.luo@linux.dev \
--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
all inboxes | Powered by JetHome®