linux-kernel - RE: [-mm patch] the ASYNC_* options shouldn't be user visible

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-next>] [day] [month] [year] [list]

Message-ID: <0C7297FA1D2D244A9C7F6959C0BF1E5201F0351F@azsmsx413.amr.corp.intel.com>
Date:	Mon, 4 Jun 2007 11:25:02 -0700
From:	"Williams, Dan J" <dan.j.williams@...el.com>
To:	"Adrian Bunk" <bunk@...sta.de>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Herbert Xu" <herbert@...dor.apana.org.au>
Cc:	<linux-kernel@...r.kernel.org>
Subject: RE: [-mm patch] the ASYNC_* options shouldn't be user visible

> From: Williams, Dan J
> >
> > BTW: Please move the async_tx directory under drivers/ or lib/
> >
One caveat with this... md.o needs xor.o to be initialized first.
Moving xor.o under lib/ means this assumption is broken since the
top-level Makefile puts 'libs' after 'drivers'.

> Yes, I was feeling somewhat exposed with the options in the top level
config,
> but at least it got a few more eyes on the code.  I will fold in your
patch
> and move async_tx under lib/ for now, but at some point I would like
to
> investigate the potential synergies with crypto/.
> 

Herbert can I move async_tx under crypto since the engines I am working
with have support for algorithms like CRC32C and Galois Field Multiply
(raid6 p+q)?
-
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/