netdev - Re: [PATCH 2/4] net: esp: check CRYPTO_TFM_REQ_DMA flag when allocating crypto request

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 13 Mar 2015 15:46:08 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	horia.geanta@...escale.com
Cc:	linux-crypto@...r.kernel.org, netdev@...r.kernel.org,
	herbert@...dor.apana.org.au, kim.phillips@...escale.com
Subject: Re: [PATCH 2/4] net: esp: check CRYPTO_TFM_REQ_DMA flag when
 allocating crypto request

From: Horia Geanta <horia.geanta@...escale.com>
Date: Fri, 13 Mar 2015 19:15:22 +0200

> Some crypto backends might require the requests' private contexts
> to be allocated in DMA-able memory.
> 
> Signed-off-by: Horia Geanta <horia.geanta@...escale.com>

No way.

Upper layers should be absolutely not required to know about such
requirements.

Such details _must_ be hidden inside of the crypto layer and drivers
and not leak out into the users of the crypto interfaces.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html