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  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]
Date:	Tue, 6 Oct 2015 10:54:42 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	"Gabriel L. Somlo" <somlo@....edu>
Cc:	Greg KH <gregkh@...uxfoundation.org>, paul@...an.com,
	galak@...eaurora.org, Will Deacon <will.deacon@....com>,
	agross@...eaurora.org, Mark Rutland <mark.rutland@....com>,
	zajec5@...il.com, hanjun.guo@...aro.org,
	Catalin Marinas <catalin.marinas@....com>,
	Linux API <linux-api@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	kernelnewbies@...nelnewbies.org,
	Matt Fleming <matt.fleming@...el.com>,
	Laszlo Ersek <lersek@...hat.com>,
	"Jordan Justen (Intel address)" <jordan.l.justen@...el.com>,
	"Michael S. Tsirkin" <mst@...hat.com>, peter.maydell@...aro.org,
	Leif Lindholm <leif.lindholm@...aro.org>,
	Ard Biesheuvel <ard.biesheuvel@...aro.org>,
	Paolo Bonzini <pbonzini@...hat.com>, kraxel@...hat.com,
	"qemu-devel@...gnu.org Developers" <qemu-devel@...gnu.org>
Subject: Re: [PATCH v3 1/4] firmware: introduce sysfs driver for QEMU's fw_cfg device

On Sat, Oct 3, 2015 at 4:28 PM, Gabriel L. Somlo <somlo@....edu> wrote:
> From: Gabriel Somlo <somlo@....edu>
>
> Make fw_cfg entries of type "file" available via sysfs. Entries
> are listed under /sys/firmware/qemu_fw_cfg/by_key, in folders
> named after each entry's selector key. Filename, selector value,
> and size read-only attributes are included for each entry. Also,
> a "raw" attribute allows retrieval of the full binary content of
> each entry.
>
> This patch also provides a documentation file outlining the
> guest-side "hardware" interface exposed by the QEMU fw_cfg device.
>

What's the status of "by_name"?  There's a single (presumably
incorrect) mention of it in a comment in this patch.

I would prefer if the kernel populated by_name itself rather than
deferring that to udev, since I'd like to use this facility in virtme,
and I'd like to use fw_cfg very early on boot before I even start
udev.

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

Powered by blists - more mailing lists