linux-kernel - Re: [PATCH 4/4] BKL: move 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110119154419.GA21411@elliptictech.com>
Date:	Wed, 19 Jan 2011 10:44:19 -0500
From:	Nick Bowler <nbowler@...iptictech.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4] BKL: move CONFIG_BKL to staging

On 2011-01-18 22:17 +0100, Arnd Bergmann wrote:
> Instead of moving the actual code to staging for stuff that
> depends on CONFIG_BKL, this moves just the configuration
> option it depends on.
> 
> As a consequence, the remaining non-staging drivers that use
> the BKL (i830, appletalk, ipx, x25, adfs, hpfs and ufs)
> implicitly depend on staging until they get fixed.
> 
> This sets 2.6.39 as the arbitrary date when we actually remove
> the option along with its last users.

I think this patch is not very nice.  It will cause working kernel
configurations to turn into broken kernel configurations when the user
does 'make oldconfig', with no warning.

These drivers that use the BKL work fine.  Removing working features
with no adequate replacement available seems like a serious regression
to me.

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
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/