From: Jens Axboe <axboe@kernel.dk>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.1.y 0/8] io_uring fixes for 6.1-stable
Date: Wed, 4 Nov 2026 13:53:15 -0700 [thread overview]
Message-ID: <0503e43c-5a26-4ee2-9781-083f16ce5cb4@kernel.dk> (raw)
In-Reply-To: <2026110410-coasting-snowplow-6509@gregkh>
On 11/4/26 1:51 PM, Greg KH wrote:
> On Wed, Nov 04, 2026 at 11:43:20AM -0700, Jens Axboe wrote:
>> Hi Greg,
>>
>> Here are io_uring fixes for 6.1-stable.
>
> Thanks for all of these different series, all now queued up!
Let's thank my tireless virtual assistant. Have the entire
process dialed in now, we'll never miss another stable
patch again and may even proactively backport things that
are in the "good to have" bucket in terms of behavior or
fixes.
Which makes me ponder if I should just switch the io_uring
side to be entirely self-provided, rather than have any kind
of automatic picking?
--
Jens Axboe
next prev parent reply other threads:[~2026-11-04 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 18:43 [PATCH 6.1.y 0/8] io_uring fixes for 6.1-stable Jens Axboe
2026-11-04 18:43 ` [PATCH 6.1.y 1/8] io_uring/net: keep recvmsg buffer select length within MAX_RW_COUNT Jens Axboe
2026-11-04 18:43 ` [PATCH 6.1.y 2/8] io_uring/net: don't retry a non-blocking connect() that fails with -EAGAIN Jens Axboe
2026-11-04 18:43 ` [PATCH 6.1.y 3/8] io_uring/io-wq: no new workers once the exit has begun Jens Axboe
2026-11-04 18:43 ` [PATCH 6.1.y 4/8] io_uring/rsrc: charge buffer arrays and nodes to memcg Jens Axboe
2026-11-04 18:43 ` [PATCH 6.1.y 5/8] io_uring: charge tctx nodes and personalities Jens Axboe
2026-11-04 18:43 ` [PATCH 6.1.y 6/8] io_uring: free XArray nodes left by a failed store Jens Axboe
2026-11-04 18:43 ` [PATCH 6.1.y 7/8] io_uring/sqpoll: don't wait for the thread to exit Jens Axboe
2026-11-04 18:43 ` [PATCH 6.1.y 8/8] io_uring/timeout: count cancelled timeouts in cq_timeouts Jens Axboe
2026-11-04 20:51 ` [PATCH 6.1.y 0/8] io_uring fixes for 6.1-stable Greg KH
2026-11-04 20:53 ` Jens Axboe [this message]
2026-11-04 21:00 ` Greg KH
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=0503e43c-5a26-4ee2-9781-083f16ce5cb4@kernel.dk \
--to=axboe@kernel.dk \
--cc=greg@kroah.com \
--cc=stable@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