linux-kernel - Re: [RESEND][PATCH] Cleanup of rw_copy_check_uvector and compat_rw_copy_check

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]

Message-ID: <20120412215410.GB31852@redhat.com>
Date:	Thu, 12 Apr 2012 23:54:10 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Christopher Yeoh <cyeoh@....ibm.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [RESEND][PATCH] Cleanup of rw_copy_check_uvector and
	compat_rw_copy_check_uvector

On 04/11, Christopher Yeoh wrote:
>
> Resending this patch which I first sent a couple of months ago and
> didn't notice it didn't go in at the time.
>
> This is the cleanup of rw_copy_check_uvector and
> compat_rw_copy_check_uvector after changes made to support CMA in an
> earlier patch. Rather than having an additional check_access parameter
> to these functions, the first paramater type is overloaded to allow the
> caller to specify CHECK_IOVEC_ONLY which means check that the contents
> of the iovec are valid, but do not check the memory that they point to.
> This is used by process_vm_readv/writev where we need to validate that a
> iovec passed to the syscall is valid but do not want to check the
> memory that it points to at this point because it refers to an address
> space in another process.

Reviewed-by: Oleg Nesterov <oleg@...hat.com>

--
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/