linux-kernel - Re: [PATCH 3/3] staging: wlags49_h2: Declare support for WEXT 21

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, 19 Sep 2011 16:22:51 -0400
From:	Valdis.Kletnieks@...edu
To:	David Kilroy <kilroyd@...glemail.com>
Cc:	linux-kernel@...r.kernel.org, greg@...ah.com, pe1dnn@...at.org
Subject: Re: [PATCH 3/3] staging: wlags49_h2: Declare support for WEXT 21

On Mon, 19 Sep 2011 21:08:16 BST, David Kilroy said:
> There may be a few areas where we don't actually support WE21,
> but by doing this it will make it easier to find those places.

I'll bite - what happens when we find such a place?  Kernel fails to build, or
user has a suboptimal usage experience, or?

What are the expected chances that sticking this in linux-next for a cycle will
result in most/all of the places being found before this all appears in an
official release?  I'm thinking this should probably go in linux-next right after
the next merge window closes, to maximize the chances we'll shake it
all out during almost 2 cycles before it hits the streets. (And yes, I know
it's a staging/ driver - if somebody else says "one cycle is more than enough"
I'm OK with that too...)

Content of type "application/pgp-signature" skipped