From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: John David Anglin <dave.anglin@bell.net>,
Helge Deller <deller@gmx.de>,
stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
linux-parisc@vger.kernel.org, Vidra.Jonas@seznam.cz,
Sam James <sam@gentoo.org>
Subject: Re: [STABLE] stable backport request for 6.1 for io_uring
Date: Sun, 3 Sep 2023 15:50:38 +0200 [thread overview]
Message-ID: <2023090325-clover-extortion-1e2e@gregkh> (raw)
In-Reply-To: <64efa654-300d-421b-9fd7-817a381f4ba7@kernel.dk>
On Sun, Sep 03, 2023 at 07:25:11AM -0600, Jens Axboe wrote:
> On 9/2/23 11:32 PM, Greg Kroah-Hartman wrote:
> > On Sat, Sep 02, 2023 at 06:45:56PM -0600, Jens Axboe wrote:
> >> On 9/2/23 5:04 PM, John David Anglin wrote:
> >>> On 2023-08-30 12:17 p.m., Jens Axboe wrote:
> >>>> On 8/28/23 3:55 PM, Helge Deller wrote:
> >>>>> Hello Greg, Hello Jens, Hello stable team,
> >>>>>
> >>>>> would you please accept some backports to v6.1-stable for io_uring()?
> >>>>> io_uring() fails on parisc because of some missing upstream patches.
> >>>>> Since 6.1 is currently used in debian and gentoo as main kernel we
> >>>>> face some build errors due to the missing patches.
> >>>> Fine with me.
> >>> This is probably not a problem with the backport but I see this fail in liburing tests:
> >>>
> >>> Running test wq-aff.t open: No such file or directory
> >>> test sqpoll failed
> >>> Test wq-aff.t failed with ret 1
> >>> Running test xattr.t 0 sec [0]
> >>> Running test statx.t 0 sec [0]
> >>> Running test sq-full-cpp.t 0 sec [0]
> >>> Tests failed (1): <wq-aff.t>
> >>
> >> That's because 6.1-stable is missing:
> >>
> >> commit ebdfefc09c6de7897962769bd3e63a2ff443ebf5
> >> Author: Jens Axboe <axboe@kernel.dk>
> >> Date: Sun Aug 13 11:05:36 2023 -0600
> >>
> >> io_uring/sqpoll: fix io-wq affinity when IORING_SETUP_SQPOLL is used
> >>
> >> which went in recently and hasn't been backported to stable yet.
> >
> > We can add that now to the stable queues if you want, otherwise we are
> > supposed to wait until -rc1.
>
> It's fine to wait for -rc1, it's not an urgent fix by any stretch. I
> just always queue up test cases when a fix is headed upstream. Hence not
> unusual that a test or two will fail until the kernel side (and stable
> too) catches up.
Ok, thanks for the info, will wait on these until -rc1 is out.
greg k-h
prev parent reply other threads:[~2023-09-03 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 21:55 [STABLE] stable backport request for 6.1 for io_uring Helge Deller
2023-08-30 16:17 ` Jens Axboe
2023-08-31 10:50 ` Greg Kroah-Hartman
2023-09-02 23:04 ` John David Anglin
2023-09-03 0:45 ` Jens Axboe
2023-09-03 5:32 ` Greg Kroah-Hartman
2023-09-03 13:25 ` Jens Axboe
2023-09-03 13:50 ` Greg Kroah-Hartman [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=2023090325-clover-extortion-1e2e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Vidra.Jonas@seznam.cz \
--cc=axboe@kernel.dk \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=sam@gentoo.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 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.