public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, io-uring@vger.kernel.org
Subject: Re: FAILED: Patch "io_uring/filetable: clamp alloc_hint to the configured alloc range" failed to apply to 6.1-stable tree
Date: Mon, 2 Mar 2026 14:08:34 -0700	[thread overview]
Message-ID: <02f9fd38-8062-4000-9198-723b98036c29@kernel.dk> (raw)
In-Reply-To: <aaX6AzNtFQ32exUW@laps>

On 3/2/26 1:58 PM, Sasha Levin wrote:
> On Mon, Mar 02, 2026 at 01:45:51PM -0700, Jens Axboe wrote:
>> On 3/2/26 1:41 PM, Sasha Levin wrote:
>>> On Mon, Mar 02, 2026 at 01:38:37PM -0700, Jens Axboe wrote:
>>>> On 3/1/26 6:15 AM, Jens Axboe wrote:
>>>>> On 2/28/26 6:47 PM, Sasha Levin wrote:
>>>>>> The patch below does not apply to the 6.1-stable tree.
>>>>>> If someone wants it applied there, or to any other stable or longterm
>>>>>> tree, then please email the backport, including the original git commit
>>>>>> id to <stable@vger.kernel.org>.
>>>>>
>>>>> And this one also picks cleanly into 6.1-stable. Not sure what is
>>>>> going on at your end?
>>>>
>>>> Are these and the other "FAILED" false positives getting applied or
>>>> not? I didn't hear anything back on any of them.
>>>
>>> Appologies for all of this. There's an explanation of what happened here:
>>> https://lore.kernel.org/all/aaWWE5uQqz_eG69i@laps/
>>>
>>> These should be part of the -rc2 I did earlier today.
>>
>> Gotcha, yeah it's not easy to know when you don't hear back, either
>> as a reply or as a new "added to stable" email. For those of us that
>> do take stable seriously, I 100% need to know if something is landing
>> or not.
> 
> You're right (and thanks for all the backports!). I had a plan to
> review all of these again after the release, but I should have sent
> something out first.

Sounds good, it was more of a note for the future, should something like
this happen again.

-- 
Jens Axboe

      reply	other threads:[~2026-03-02 21:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01  1:47 FAILED: Patch "io_uring/filetable: clamp alloc_hint to the configured alloc range" failed to apply to 6.1-stable tree Sasha Levin
2026-03-01 13:15 ` Jens Axboe
2026-03-02 20:38   ` Jens Axboe
2026-03-02 20:41     ` Sasha Levin
2026-03-02 20:45       ` Jens Axboe
2026-03-02 20:58         ` Sasha Levin
2026-03-02 21:08           ` Jens Axboe [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=02f9fd38-8062-4000-9198-723b98036c29@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=sashal@kernel.org \
    --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