From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org,
mjt@tls.msk.ru, stable@kernel.org
Subject: Re: [PATCH 0/2] aio: fix the vectored aio routines
Date: Tue, 4 May 2010 13:13:53 -0700 [thread overview]
Message-ID: <20100504131353.adf8c186.akpm@linux-foundation.org> (raw)
In-Reply-To: <1272660540-6567-1-git-send-email-jmoyer@redhat.com>
On Fri, 30 Apr 2010 16:48:58 -0400
Jeff Moyer <jmoyer@redhat.com> wrote:
> Hi,
>
> It was reported[1] that 32 bit readv and writev AIO operations were
> not functioning properly. It turns out that the code to convert the
> 32bit io vectors to 64 bits was never written. The results of that
> can be pretty bad, but in my testing, it mostly ended up in generating
> EFAULT as we walked off the list of I/O vectors provided.
>
> This patch set fixes the problem in my environment. Comments, as always,
> are greatly appreciated.
>
> Cheers,
> Jeff
>
> [1] http://lkml.org/lkml/2010/3/8/309
>
> [PATCH 1/2] compat: factor out compat_rw_copy_check_uvector from compat_do_readv_writev
> [PATCH 2/2] aio: fix the compat vectored operations
The patches are large(ish) and we're at -rc6. I'm inclined to merge
these into 2.6.35-rc1 with a -stable tag so they get backported into 2.6.34.1
after a bit of mainline testing, OK?
next prev parent reply other threads:[~2010-05-04 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 20:48 [PATCH 0/2] aio: fix the vectored aio routines Jeff Moyer
2010-04-30 20:48 ` [PATCH 1/2] compat: factor out compat_rw_copy_check_uvector from compat_do_readv_writev Jeff Moyer
2010-04-30 20:49 ` [PATCH 2/2] aio: fix the compat vectored operations Jeff Moyer
2010-05-04 20:13 ` Andrew Morton [this message]
2010-05-04 20:16 ` [PATCH 0/2] aio: fix the vectored aio routines 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=20100504131353.adf8c186.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jmoyer@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=stable@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