Linux io-uring development
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@suse.de>
To: axboe@kernel.dk
Cc: io-uring@vger.kernel.org, Gabriel Krisman Bertazi <krisman@suse.de>
Subject: [PATCH liburing 0/2] Fix op_recv stack corruption
Date: Wed, 22 Jul 2026 14:17:08 -0400	[thread overview]
Message-ID: <20260722181710.79099-1-krisman@suse.de> (raw)

Jens,

These two tests were failing on my debug infrastructure. It seems gcc
hides the issue with a higher level of optimization, most likely by
smarting out the local variable allocation straight to registers, which
is why we don't observe it more often.  When building with '-O0 -g3', I
could trigger it 100% of time.  Tested with kernel 7.2-rc4.

Gabriel Krisman Bertazi (2):
  test/send_recvmsg: Preserve msghdr until op_recvmsg completes
  test/recv-msgall-stream: Preserve msghdr until op_recvmsg completes

 test/recv-msgall-stream.c | 14 +++++++-------
 test/send_recvmsg.c       | 16 ++++++++--------
 2 files changed, 15 insertions(+), 15 deletions(-)

-- 
2.54.0


             reply	other threads:[~2026-07-22 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 18:17 Gabriel Krisman Bertazi [this message]
2026-07-22 18:17 ` [PATCH liburing 1/2] test/send_recvmsg: Preserve msghdr until op_recvmsg completes Gabriel Krisman Bertazi
2026-07-22 18:24   ` Gabriel Krisman Bertazi
2026-07-22 19:21   ` Jens Axboe
2026-07-22 20:00     ` Gabriel Krisman Bertazi
2026-07-22 20:33       ` Gabriel Krisman Bertazi
2026-07-22 18:17 ` [PATCH liburing 2/2] test/recv-msgall-stream: " Gabriel Krisman Bertazi

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=20260722181710.79099-1-krisman@suse.de \
    --to=krisman@suse.de \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    /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