From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-aio@kvack.org
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: aio: compat_ioctl issue?
Date: Tue, 09 Mar 2010 00:38:35 +0300 [thread overview]
Message-ID: <4B956E5B.9020302@msgid.tls.msk.ru> (raw)
Hello.
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.
An application submits some aio job, and it is returned
immediately (from io_getevents()) with EINVAL error.
Here's what it does (it's a printf in the application -
actual arguments as passed to io_submit() and actual
result received in io_getevents()):
io_submit: lio_opcode=7 reqprio=0 iov=0x9cd7018{0xf5599000,4096}, niov=1, offset=0
io_getevents: expected 4096 got -22 (EINVAL)
Note that it is not io_submit() which fails (that one
returns success) but io_getevents(), so it has to be
down the pipeline somewhere.
Can someone comment this please? Somehow I was thinking this
codepath works as - I think anyway - I ran 32bit Oracle database
with aio support on 64bit kernel, but I may be mistaken.
Kernel is 2.6.33 from kernel.org.
Thanks!
/mjt
next reply other threads:[~2010-03-08 21:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 21:38 Michael Tokarev [this message]
2010-03-08 21:43 ` aio: compat_ioctl issue? Jeff Moyer
2010-03-08 21:50 ` Michael Tokarev
2010-03-08 22:25 ` Jeff Moyer
2010-03-08 22:32 ` Michael Tokarev
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=4B956E5B.9020302@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--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