linux-kernel - Re: maturity and status and attributes, oh my!

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]

Message-ID: <Pine.LNX.4.64.0709010533260.29190@localhost.localdomain>
Date:	Sat, 1 Sep 2007 05:41:06 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: maturity and status and attributes, oh my!

On Sat, 1 Sep 2007, Stefan Richter wrote:

> Robert P. J. Day wrote:
> > you take advantage of that?  you'd have to add a new
> > structure to "make config" along the following lines:
> >
> >   Along with maturity-untagged features, what other maturity levels
> >   would you like to see and be able to select?
>
> Most (all?) users and presumably most distributors/packagers don't
> decide this globally.  They look at a feature and decide, based on
> their need for this feature, whether they enable or disable it,
> whether they look into alternative hardware/drivers/apps, whether
> they get in touch with the maintainer.

agreed.  but i'm not proposing that *every* feature in the kernel be
investigated to see what category it falls into -- that's clearly an
unreasonable thing to do.

all this new construct is doing is implementing a new way to globally
select or de-select large sets of kernel features to display for user
selection, in exactly the way that EXPERIMENTAL does it now, that's
all.  these attributes would not *force* selection, they would simply
*filter* what to display, nothing more.

this whole attribute thing is not adding anything breathtaking new,
it's simply taking the example set by EXPERIMENTAL and generalizing
it and making it more convenient in the process.

and, as a start, the first thing to do is apply a patch that defines
an attribute and its possible values, and allows kernel features (via
Kconfig files) to be tagged with that attribute, without being able to
do anything with it yet.  one step at a time.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================
-
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/