linux-kernel - Re: loading firmware while usermodehelper disabled.

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+55aFyHvmvast_kuNddU3iotReR1mOpKM4HGAw80ma8kn+2-g@mail.gmail.com>
Date:	Mon, 2 Jan 2012 14:19:37 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Matthew Garrett <mjg@...hat.com>
Cc:	Jack Stone <jwjstone@...tmail.fm>,
	Alan Stern <stern@...land.harvard.edu>,
	Oliver Neukum <oliver@...kum.org>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Larry Finger <Larry.Finger@...inger.net>,
	Chaoming Li <chaoming_li@...lsil.com.cn>,
	"John W. Linville" <linville@...driver.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	USB list <linux-usb@...r.kernel.org>,
	Linux Wireless List <linux-wireless@...r.kernel.org>
Subject: Re: loading firmware while usermodehelper disabled.

On Mon, Jan 2, 2012 at 2:12 PM, Matthew Garrett <mjg@...hat.com> wrote:
>
> The kernel that loaded the firmware to make the device work is not
> required to be the same kernel that we're running when we suspend.

Why do you make up all these idiotic theoretical cases that nobody
cares about and has no relevance what-so-ever for the 99%?

Seriously? It's just stupid.

If you have some multi-kernel setup, or depend on booting windows
before booting Linux in order to have the firmware there, or you use
hibernate and switch things around (hibernate, not suspend - different
thing), and cannot load the firmware in the regular kernel, who the
hell cares?

And if you *can* load the firmware in the new kernel, just do it
before the suspend event. Problem solved.

And once more: your made-up scenario has *nothing* what-so-ever to do
with the actual warnings that started this whole thread.

You seem to *intentionally* be off in some random alternate reality
that is not relevant to anybody else, or to the actual reported
problems at hand.

Why?

                        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/