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>] [day] [month] [year] [list]
Date:	Fri, 29 May 2009 14:41:50 +0100
From:	"Sosnowski, Maciej" <maciej.sosnowski@...el.com>
To:	"Williams, Dan J" <dan.j.williams@...el.com>
CC:	"neilb@...e.de" <neilb@...e.de>,
	"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
	"maan@...temlinux.org" <maan@...temlinux.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"yur@...raft.com" <yur@...raft.com>,
	"hpa@...or.com" <hpa@...or.com>
Subject: RE: [PATCH v2 04/11] async_xor: permit callers to pass in a
 'dma/page scribble' region

Dan Williams wrote:
> async_xor() needs space to perform dma and page address conversions.  In
> most cases the code can simply reuse the struct page * array because the
> size of the native pointer matches the size of a dma/page address.  In
> order to support archs where sizeof(dma_addr_t) is larger than
> sizeof(struct page *), or to preserve the input parameters, we utilize a
> memory region passed in by the caller.
> 
> Since the code is now prepared to handle the case where it cannot
> perform address conversions on the stack, we no longer need the
> !HIGHMEM64G dependency in drivers/dma/Kconfig.
> 
> [ Impact: don't clobber input buffers for address conversions ]
> 
> Signed-off-by: Dan Williams <dan.j.williams@...el.com>
> ---
>  crypto/async_tx/async_xor.c |   59 ++++++++++++++++++++-----------------------
>  drivers/dma/Kconfig         |    2 +
>  2 files changed, 29 insertions(+), 32 deletions(-)

Acked-by: Maciej Sosnowski <maciej.sosnowski@...el.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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ