From: Jens Axboe <axboe@kernel.dk>
To: Sasha Levin <sashal@kernel.org>,
gregkh@linuxfoundation.org, yi1tang.yang@gmail.com
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] io_uring/rw: fix missing ERESTARTSYS conversion in read paths" failed to apply to 6.12-stable tree
Date: Sat, 1 Aug 2026 22:18:11 -0600 [thread overview]
Message-ID: <8ebae381-f1cc-4cd2-8afd-8508cf9cb217@kernel.dk> (raw)
In-Reply-To: <20260802030154.ab05caca123c@kernel.org>
On 8/1/26 9:15 PM, Sasha Levin wrote:
> On Wed, Jul 29, 2026 at 10:35:51AM -0600, Jens Axboe wrote:
>> Seems that's already in 6.12-stable?
>
> Not quite - stable/linux-6.12.y has no io_fixup_restart_res() at all.
>
> What 6.12 does already have is the older inline ERESTART* -> -EINTR
> switch inside io_rw_done(), which is the code ab05caca123c refactors
> rather than the fix itself. The actual bug is still there: io_read()
> ends with a bare "return ret;" after __io_read(), and io_read_mshot()'s
> "ret <= 0" branch only does req_set_fail(), so an -ERESTARTSYS coming
> out of __io_read() reaches userspace as -512 unconverted.
Right, this original email was superseded by the later ones. As long
as the sent out patches got queued up, we should be fine.
--
Jens Axboe
next prev parent reply other threads:[~2026-08-02 4:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 13:50 FAILED: patch "[PATCH] io_uring/rw: fix missing ERESTARTSYS conversion in read paths" failed to apply to 6.12-stable tree gregkh
2026-07-29 16:35 ` Jens Axboe
2026-07-29 16:44 ` Jens Axboe
2026-07-29 17:39 ` Jens Axboe
2026-08-02 3:15 ` Sasha Levin
2026-08-02 4:18 ` Jens Axboe [this message]
2026-08-03 20:46 ` Sasha Levin
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=8ebae381-f1cc-4cd2-8afd-8508cf9cb217@kernel.dk \
--to=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yi1tang.yang@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