public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: io-uring <[email protected]>,
	Pavel Begunkov <[email protected]>
Subject: Re: Issue with splice 32-bit compatability?
Date: Fri, 28 Feb 2020 08:25:54 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 2/28/20 8:16 AM, Jens Axboe wrote:
> Hey Pavel,
> 
> Since I yesterday found that weirdness with networking and using
> a separate flag for compat mode, I went to check everything else.
> Outside of all the syzbot reproducers not running in 32-bit mode,
> the only other error was splice:
> 
> splice: returned -29, expected 16384
> basic splice-copy failed
> test_splice failed -29 0
> Test splice failed with ret 227
> 
> Can you take a look? I just edit test/Makefile and src/Makefile and
> add -m32 to the CFLAGS for testing.

It's in the liburing prep, fixed it:

https://git.kernel.dk/cgit/liburing/commit/?id=566180209fc4d9e3ee8852315a4411ee0c3d5510

-- 
Jens Axboe


  reply	other threads:[~2020-02-28 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28 15:16 Issue with splice 32-bit compatability? Jens Axboe
2020-02-28 15:25 ` Jens Axboe [this message]
2020-02-28 22:52   ` Pavel Begunkov

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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