linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
	"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-block\@vger.kernel.org" <linux-block@vger.kernel.org>,
	linux-aio@kvack.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] fs: replace the ki_complete two integer arguments with a single argument
Date: Thu, 21 Oct 2021 16:58:34 -0400	[thread overview]
Message-ID: <x49wnm6t7r9.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <7a697483-8e44-6dc3-361e-ae7b62b82074@kernel.dk> (Jens Axboe's message of "Thu, 21 Oct 2021 14:41:18 -0600")

Jens Axboe <axboe@kernel.dk> writes:

> On 10/21/21 12:05 PM, Jeff Moyer wrote:
>> 
>>>> I'll follow up if there are issues.
>> 
>> s390 (big endian, 64 bit) is failing libaio test 21:
>> 
>> # harness/cases/21.p
>> Expected -EAGAIN, got 4294967285
>> 
>> If I print out both res and res2 using %lx, you'll see what happened:
>> 
>> Expected -EAGAIN, got fffffff5,ffffffff
>> 
>> The sign extension is being split up.
>
> Funky, does it work if you apply this on top?
>
> diff --git a/fs/aio.c b/fs/aio.c
> index 3674abc43788..c56437908339 100644
> --- a/fs/aio.c
> +++ b/fs/aio.c
> @@ -1442,8 +1442,8 @@ static void aio_complete_rw(struct kiocb *kiocb, u64 res)
>  	 * 32-bits of value at most for either value, bundle these up and
>  	 * pass them in one u64 value.
>  	 */
> -	iocb->ki_res.res = lower_32_bits(res);
> -	iocb->ki_res.res2 = upper_32_bits(res);
> +	iocb->ki_res.res = (long) (res & 0xffffffff);
> +	iocb->ki_res.res2 = (long) (res >> 32);
>  	iocb_put(iocb);
>  }

I think you'll also need to clamp any ki_complete() call sites to 32
bits (cast to int, or what have you).  Otherwise that sign extension
will spill over into res2.

fwiw, I tested with this:

	iocb->ki_res.res = (long)(int)lower_32_bits(res);
	iocb->ki_res.res2 = (long)(int)upper_32_bits(res);

Coupled with the call site changes, that made things work for me.

-Jeff


  reply	other threads:[~2021-10-21 20:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 19:08 [PATCH v2] fs: replace the ki_complete two integer arguments with a single argument Jens Axboe
2021-10-21  8:06 ` Greg KH
2021-10-21  8:32 ` Christoph Hellwig
2021-10-21 10:57   ` Christoph Hellwig
2021-10-21 14:34     ` Jens Axboe
2021-10-21 14:42       ` Christoph Hellwig
2021-10-21 14:44         ` Jens Axboe
2021-10-21 14:47           ` Christoph Hellwig
2021-10-21 15:18           ` Jeff Moyer
2021-10-21 15:19             ` Jens Axboe
2021-10-21 18:05               ` Jeff Moyer
2021-10-21 20:41                 ` Jens Axboe
2021-10-21 20:58                   ` Jeff Moyer [this message]
2021-10-21 21:03                     ` Jeff Moyer
2021-10-22 14:19                       ` Jens Axboe
2021-10-22 15:29                         ` Jens Axboe
2021-10-22 15:47                           ` 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=x49wnm6t7r9.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-aio@kvack.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).