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

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

> From: Adrian Bunk [mailto:bunk@...sta.de]
> >...
> > Changes since 2.6.22-rc2-mm1:
> >...
> >  git-md-accel.patch
> >...
> >  git trees
> >...
> 
> 
> The ASYNC_* options are for internal helper code and should therefore
> not be user visible.
> 
> Signed-off-by: Adrian Bunk <bunk@...sta.de>
> 
> ---
> 
> BTW: Please move the async_tx directory under drivers/ or lib/
> 
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/.

Thanks,
Dan
-
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/