linux-kernel - Re: drivers by default (was Re: Another HID problem this merge window..)

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: <CAHk-=whh44s8DyL04n2X_z2t_YJ7Cu2biYah-tDNKRorKJ_srg@mail.gmail.com>
Date:   Sun, 28 Oct 2018 13:21:57 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     kilobyte@...band.pl
Cc:     Jiri Kosina <jikos@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: drivers by default (was Re: Another HID problem this merge window..)

On Sun, Oct 28, 2018 at 4:16 AM Adam Borowski <kilobyte@...band.pl> wrote:
>
> Amen to that.  But, perhaps you could encourage people to do enable drivers
> once they become very popular?  For example, I just (72a9c673636) got hit by
> USB 3.0 being off in defconfigs, and not having keyboard is not that cool.

Yes, that seems reasonable.

I don't think we need much of an explicit "policy" for these things,
though. Things that get _so_ ubiquitous that they should be marked
default globally (as opposed to just being in a defconfig file for
some board) are pretty rare, and them being "new" things are rarer
still.

Yeah, usb3 sounds like it would count, but I think that's such a rare
exception that I don't think we need to make a policy for it, just a
"hey, once or twice in a decade we have a new bus that became so
common that we should update the 'default' to y".

               Linus