From: Michael Tokarev <mjt@tls.msk.ru>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: linux-aio@kvack.org, Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: aio: compat_ioctl issue?
Date: Tue, 09 Mar 2010 01:32:19 +0300 [thread overview]
Message-ID: <4B957AF3.6040801@msgid.tls.msk.ru> (raw)
In-Reply-To: <x49mxyi78ob.fsf@segfault.boston.devel.redhat.com>
Jeff Moyer wrote:
[]
>>>> I just come across a situation (next in a long row :)
>>>> when on x86, 32bit userspace does not work with 64bit
>>>> kernel. This time this is about aio requests.
> [snip]
> Well, I'm not experiencing such problems. I can run a 32bit aio
> application on a 64bit kernel just fine with 2.6.31, 2.6.32 and
> 2.6.34-rc1.
Interesting. I mentioned that I _think_ I used Oracle 32bit with
AIO on 64bit kernel, but I'm not sure.
> Could you maybe print out the values that are passed to io_getevents?
They were in my first email, here it goes again:
io_submit: lio_opcode=7 reqprio=0 iov=0x9cd7018{0xf5599000,4096}, niov=1, offset=0
io_getevents: expected 4096 got -22 (EINVAL)
This is what gets passed to libaio -- strace here
does not decode the arguments unfortunately.
The file in question is raw partition open with O_DIRECT,
if that makes any difference.
64bit binary uses very similar arguments except that
addresses are different.
My *guess* is that it handles read/write correctly but
does not properly handle preadv/pwritev (opcode=7 is
IO_CMD_PREADV as far as I can see). That'll explain
my "testcase" with Oracle which does not use preadv.
Thanks!
/mjt
next prev parent reply other threads:[~2010-03-08 22:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 21:38 aio: compat_ioctl issue? Michael Tokarev
2010-03-08 21:43 ` Jeff Moyer
2010-03-08 21:50 ` Michael Tokarev
2010-03-08 22:25 ` Jeff Moyer
2010-03-08 22:32 ` Michael Tokarev [this message]
2010-03-08 22:41 ` Michael Tokarev
2010-03-11 16:06 ` Jeff Moyer
2010-03-11 19:10 ` Michael Tokarev
2010-03-11 19:13 ` Jeff Moyer
2010-03-11 19:46 ` Michael Tokarev
2010-03-11 19:57 ` Jeff Moyer
2010-03-11 20:13 ` Michael Tokarev
2010-03-16 18:52 ` Jeff Moyer
2010-03-16 20:36 ` Michael Tokarev
2010-03-16 20:44 ` Jeff Moyer
2010-04-28 18:00 ` Avi Kivity
2010-04-28 18:11 ` Jeff Moyer
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=4B957AF3.6040801@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=jmoyer@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@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