linux-kernel - Re: [PATCH 0/2] aio: fix the vectored aio routines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 04 May 2010 16:16:12 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-aio@...ck.org, linux-kernel@...r.kernel.org, mjt@....msk.ru,
	stable@...nel.org
Subject: Re: [PATCH 0/2] aio: fix the vectored aio routines

Andrew Morton <akpm@...ux-foundation.org> writes:

> On Fri, 30 Apr 2010 16:48:58 -0400
> Jeff Moyer <jmoyer@...hat.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?

That's fine with me.

Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/