linux-kernel - Re: [PATCH 1/1] intel_ips: blacklist ASUSTek G60JX laptops

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: <CA+55aFy09OfUb_ENi6NgVWaNM7YBvLovcf5FvyHfpXXBUGsQkg@mail.gmail.com>
Date:	Wed, 14 Aug 2013 14:11:31 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Joseph Salisbury <joseph.salisbury@...onical.com>,
	platform-driver-x86@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: [PATCH 1/1] intel_ips: blacklist ASUSTek G60JX laptops

On Wed, Aug 14, 2013 at 9:38 AM, Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
>
> Linus, you may want to pick this up directly, as I'm not sure if
> Matthew is still looking after the x86 drivers these days.

Can't we make the simpler patch be to just not spam the logs? Do it
once, and forget about it. Maybe make the timeouts long enough to make
sure that there are no other downsides from having the driver
occasionally testing if it's back?

I *detest* hardware-specific blacklists. They are impossible to
maintain, and we've had the situation more than once that we fixed the
real bug that caused the blacklist in the first place, but the entry
stays around because nobody knows/cares/tests it.

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