linux-kernel - Re: Inserting code from userspace to kernel space

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: <483AA3D2.3@davidnewall.com>
Date:	Mon, 26 May 2008 21:19:38 +0930
From:	David Newall <davidn@...idnewall.com>
To:	Jiri Kosina <jkosina@...e.cz>
CC:	Shuduo Sang <sangshuduo@...il.com>, devzero@....de,
	bosko.radivojevic@...il.com, linux-kernel@...r.kernel.org
Subject: Re: Inserting code from userspace to kernel space

Jiri Kosina wrote:
> This is different, because the firmware that is loaded by 
> request_firmware() is not meant to be interpreted/executed by the kernel, 
> drivers usually just pass it over to the device.

Usually, but not obligatory.  It seems like it might be useful to
overload the mechanism for the specified requirement.  It's just an idea.
--
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/