From: Greg KH <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Andres Freund <andres@anarazel.de>,
asml.silence@gmail.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] io_uring: Use io_schedule* in cqring wait" failed to apply to 6.1-stable tree
Date: Sun, 16 Jul 2023 21:29:24 +0200 [thread overview]
Message-ID: <2023071616-flatworm-emptier-bbd0@gregkh> (raw)
In-Reply-To: <46c1075b-0daf-14db-cf48-5a5105b996de@kernel.dk>
On Sun, Jul 16, 2023 at 01:19:31PM -0600, Jens Axboe wrote:
> On 7/16/23 1:11?PM, Andres Freund wrote:
> > Hi,
> >
> > On 2023-07-16 12:13:45 -0600, Jens Axboe wrote:
> >> Here's one for 6.1-stable.
> >
> > Thanks for working on that!
> >
> >
> >> diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
> >> index cc35aba1e495..de117d3424b2 100644
> >> --- a/io_uring/io_uring.c
> >> +++ b/io_uring/io_uring.c
> >> @@ -2346,7 +2346,7 @@ static inline int io_cqring_wait_schedule(struct io_ring_ctx *ctx,
> >> struct io_wait_queue *iowq,
> >> ktime_t *timeout)
> >> {
> >> - int ret;
> >> + int token, ret;
> >> unsigned long check_cq;
> >>
> >> /* make sure we run task_work before checking for signals */
> >> @@ -2362,9 +2362,18 @@ static inline int io_cqring_wait_schedule(struct io_ring_ctx *ctx,
> >> if (check_cq & BIT(IO_CHECK_CQ_DROPPED_BIT))
> >> return -EBADR;
> >> }
> >> +
> >> + /*
> >> + * Use io_schedule_prepare/finish, so cpufreq can take into account
> >> + * that the task is waiting for IO - turns out to be important for low
> >> + * QD IO.
> >> + */
> >> + token = io_schedule_prepare();
> >> + ret = 0;
> >> if (!schedule_hrtimeout(timeout, HRTIMER_MODE_ABS))
> >> - return -ETIME;
> >> - return 1;
> >> + ret = -ETIME;
> >> + io_schedule_finish(token);
> >> + return ret;
> >> }
> >
> > To me it looks like this might have changed more than intended? Previously
> > io_cqring_wait_schedule() returned 0 in case schedule_hrtimeout() returned
> > non-zero, now io_cqring_wait_schedule() returns 1 in that case? Am I missing
> > something?
>
> Ah shoot yes indeed. Greg, can you drop the 5.10/5.15/6.1 ones for now?
> I'll get it sorted tomorrow. Sorry about that, and thanks for catching
> that Andres!
Sure, will go drop it now, thanks.
greg k-h
next prev parent reply other threads:[~2023-07-16 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 8:41 FAILED: patch "[PATCH] io_uring: Use io_schedule* in cqring wait" failed to apply to 6.1-stable tree gregkh
2023-07-16 18:13 ` Jens Axboe
2023-07-16 19:11 ` Andres Freund
2023-07-16 19:19 ` Jens Axboe
2023-07-16 19:29 ` Greg KH [this message]
2023-07-17 16:32 ` Jens Axboe
2023-07-17 16:39 ` Jens Axboe
2023-07-17 17:33 ` Andres Freund
2023-07-17 20:12 ` Greg KH
2023-07-17 20:13 ` Jens Axboe
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=2023071616-flatworm-emptier-bbd0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andres@anarazel.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox