All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jens Axboe <axboe@kernel.dk>,
	akpm@linux-foundation.org, broonie@kernel.org, mhocko@suse.cz,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org
Subject: Re: mmotm 2021-04-11-20-47 uploaded (fs/io_uring.c)
Date: Mon, 12 Apr 2021 08:13:15 -0700	[thread overview]
Message-ID: <99c73206-8273-665a-0c66-2582873ffa48@infradead.org> (raw)
In-Reply-To: <9533afdd-208e-c25d-2e11-cc7f2c9d147b@kernel.dk>

On 4/12/21 5:39 AM, Jens Axboe wrote:
> On 4/12/21 1:21 AM, Randy Dunlap wrote:
>> On 4/11/21 8:48 PM, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2021-04-11-20-47 has been uploaded to
>>>
>>>    https://www.ozlabs.org/~akpm/mmotm/
>>>
>>> mmotm-readme.txt says
>>>
>>> README for mm-of-the-moment:
>>>
>>> https://www.ozlabs.org/~akpm/mmotm/
>>>
>>> This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
>>> more than once a week.
>>>
>>> You will need quilt to apply these patches to the latest Linus release (5.x
>>> or 5.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
>>> https://ozlabs.org/~akpm/mmotm/series
>>>
>>> The file broken-out.tar.gz contains two datestamp files: .DATE and
>>> .DATE-yyyy-mm-dd-hh-mm-ss.  Both contain the string yyyy-mm-dd-hh-mm-ss,
>>> followed by the base kernel version against which this patch series is to
>>> be applied.
>>>
>>> This tree is partially included in linux-next.  To see which patches are
>>> included in linux-next, consult the `series' file.  Only the patches
>>> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
>>> linux-next.
>>
>> on i386:
>> # CONFIG_BLOCK is not set
>>
>> ../fs/io_uring.c: In function ‘kiocb_done’:
>> ../fs/io_uring.c:2766:7: error: implicit declaration of function ‘io_resubmit_prep’; did you mean ‘io_put_req’? [-Werror=implicit-function-declaration]
>>    if (io_resubmit_prep(req)) {
> 
> I'll apply the below to take care of that.
> 

Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested


Thanks.

> 
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 3a837d2b8331..aa29918944f6 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -2464,6 +2464,10 @@ static bool io_rw_should_reissue(struct io_kiocb *req)
>  	return true;
>  }
>  #else
> +static bool io_resubmit_prep(struct io_kiocb *req)
> +{
> +	return false;
> +}
>  static bool io_rw_should_reissue(struct io_kiocb *req)
>  {
>  	return false;
> @@ -2504,14 +2508,8 @@ static void io_complete_rw_iopoll(struct kiocb *kiocb, long res, long res2)
>  	if (kiocb->ki_flags & IOCB_WRITE)
>  		kiocb_end_write(req);
>  	if (unlikely(res != req->result)) {
> -		bool fail = true;
> -
> -#ifdef CONFIG_BLOCK
> -		if (res == -EAGAIN && io_rw_should_reissue(req) &&
> -		    io_resubmit_prep(req))
> -			fail = false;
> -#endif
> -		if (fail) {
> +		if (!(res == -EAGAIN && io_rw_should_reissue(req) &&
> +		    io_resubmit_prep(req))) {
>  			req_set_fail_links(req);
>  			req->flags |= REQ_F_DONT_REISSUE;
>  		}
> 


-- 
~Randy


  reply	other threads:[~2021-04-12 15:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  3:48 mmotm 2021-04-11-20-47 uploaded akpm
2021-04-12  7:21 ` mmotm 2021-04-11-20-47 uploaded (fs/io_uring.c) Randy Dunlap
2021-04-12 12:39   ` Jens Axboe
2021-04-12 15:13     ` Randy Dunlap [this message]
2021-04-12 16:38 ` mmotm 2021-04-11-20-47 uploaded (bpf: xsk.c) Randy Dunlap
2021-04-13 22:18   ` Andrii Nakryiko
2021-04-13 22:18     ` Andrii Nakryiko
2021-04-13 22:44     ` Randy Dunlap
2021-04-12 17:27 ` mmotm 2021-04-11-20-47 uploaded (ni_routes_test.c) Randy Dunlap
2021-04-13  9:16   ` Ian Abbott

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=99c73206-8273-665a-0c66-2582873ffa48@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=broonie@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.