linux-kernel - Re: [PATCH] drivers: Update help for firmware loading options

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] [day] [month] [year] [list]

Message-ID: <20151004192455.GA8829@zyxyz>
Date:	Sun, 4 Oct 2015 14:24:55 -0500
From:	Eric Biggers <ebiggers3@...il.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers: Update help for firmware loading options

On Sun, Oct 04, 2015 at 08:14:16PM +0100, Greg KH wrote:
> 
> Are you sure?  I think this should stay as "Userspace..." as that is
> what it does, right?
> 
> Turning it off should only drop the userspace callouts, it shouldn't
> stop the kernel from loading firmware from the filesystem all on its own
> with no help.

As far as I can tell that's not true.  With FW_LOADER=n, firmware_class.c is
compiled out and request_firmware() always returns -EINVAL.  My patch tries to
make it more clear that FW_LOADER is the "top-level" option which covers all
three firmware loading mechanisms: built-in, directly from the filesystem, and
the user-mode helper.
--
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/