linux-kernel - Getting request_firmware() filename info from user 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-next>] [day] [month] [year] [list]

Message-ID: <B2150E1E4418E1438554A300EA5040E40DDE603CE3@ITSVLEX06.it.maxim-ic.internal>
Date:	Mon, 20 Jun 2011 18:20:52 -0700
From:	Peter Hsiang <Peter.Hsiang@...im-ic.com>
To:	Manuel Estrada Sainz <ranty@...ian.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Getting request_firmware() filename info from user space

Hi,

Using the kernel request_firmware() function, it seems one can send any file by:
    cat myfile.bin > /sys/class/firmware/xxxx/data

How does the user space code obtain the filename parameter specified in the request_firmware() call?

The documentation says $DEVPATH and $FIRMWARE variables are provided in 
the environment, but "echo $FIRMWARE" prints an empty string.

I loaded the driver with an & just so I can get the shell prompt back to start the sysfs script.
How would one load the driver and run the sysfs script to send the file from the same shell?

Thanks,

Peter

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