linux-kernel - [PATCH 000/193] remove CONFIG

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: <1351022666-6960-1-git-send-email-keescook@chromium.org>
Date:	Tue, 23 Oct 2012 13:01:13 -0700
From:	Kees Cook <keescook@...omium.org>
To:	linux-kernel@...r.kernel.org
Subject: [PATCH 000/193] remove CONFIG_EXPERIMENTAL

This config item has not carried much meaning for a while now and is
almost always enabled by default (especially in distro builds). As agreed
during the Linux kernel summit, it should be removed.

As such, this is the patch series for removing CONFIG_EXPERIMENTAL, 
with the hopes of all the various maintainers pulling these changes into
their trees.  I'm carrying the first patch (that makes CONFIG_EXPERIMENTAL
"default y") in my linux-next tree, so builds there will see the impact
immediately. 

Some patches remove "(EXPERIMENTAL)" from Kconfig titles when there was
no "depends on EXPERIMENTAL". I've removed the cases of these where I
know the maintainer intended it that way. I've left the others in case a
"depends on EXPERIMENTAL" had been removed in the past and it had been
accidentally forgotten in the title. If the title is correct as-is, 
just let me know, and I'll drop the patch from my series.

Here is an outline of how to handle things going forward, from the first
patch's commit message, based on earlier lkml discussions:

  For items that really are experimental, maintainers should use "default
  n", optionally include "(EXPERIMENTAL)" in the title, and add language to
  the help text indicating why the item should be considered experimental.

  For items that are dangerously experimental, the maintainer is encouraged
  to follow the above title recommendation, add stronger language to the
  help text, and optionally use (depending on the extent of the danger,
  from least to most dangerous): printk(), add_taint(TAINT_WARN),
  add_taint(TAINT_CRAP), WARN_ON(1), and CONFIG_BROKEN.

Thanks,

-Kees

--
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/