All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: asml.silence@gmail.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] io_uring: lock overflowing for IOPOLL" failed to apply to 5.15-stable tree
Date: Mon, 16 Jan 2023 15:47:24 +0100	[thread overview]
Message-ID: <Y8VjfOb5V9+sFiOL@kroah.com> (raw)
In-Reply-To: <3a32e477-4170-07e7-94fc-384d8e86a7d7@kernel.dk>

On Sat, Jan 14, 2023 at 09:48:34AM -0700, Jens Axboe wrote:
> On 1/14/23 9:21?AM, Jens Axboe wrote:
> > On 1/14/23 9:15?AM, Jens Axboe wrote:
> >> On 1/14/23 2:51?AM, gregkh@linuxfoundation.org wrote:
> >>>
> >>> The patch below does not apply to the 5.15-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>.
> >>
> >> This has to be done a bit differently, but this one should work. I tested
> >> it on 5.10-stable, but should apply to 5.15-stable as well as they are
> >> the same base now.
> > 
> > Oops, missed accounting for overflow. Please use this one instead! Sorry
> > about that.
> 
> Not batting 1000 on this one today. Wrote a test case for this
> specifically now and verified it, this one is good. For real.

Looks like Sasha grabbed all of these already, thanks for the backports!

greg k-h

      reply	other threads:[~2023-01-16 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14  9:51 FAILED: patch "[PATCH] io_uring: lock overflowing for IOPOLL" failed to apply to 5.15-stable tree gregkh
2023-01-14 16:15 ` Jens Axboe
2023-01-14 16:21   ` Jens Axboe
2023-01-14 16:48     ` Jens Axboe
2023-01-16 14:47       ` Greg KH [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=Y8VjfOb5V9+sFiOL@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.