linux-kernel - Re: [PATCH v4 4/6] fpga manager: add sysfs interface document

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: <20141210145052.56f0b880@lxorguk.ukuu.org.uk>
Date:	Wed, 10 Dec 2014 14:50:52 +0000
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	<atull@...nsource.altera.com>
Cc:	<gregkh@...uxfoundation.org>, <jgunthorpe@...idianresearch.com>,
	<hpa@...or.com>, <monstr@...str.eu>, <michal.simek@...inx.com>,
	<rdunlap@...radead.org>, <linux-kernel@...r.kernel.org>,
	<devicetree@...r.kernel.org>, <pantelis.antoniou@...sulko.com>,
	<robh+dt@...nel.org>, <grant.likely@...aro.org>,
	<iws@...o.caltech.edu>, <linux-doc@...r.kernel.org>,
	<pavel@...x.de>, <broonie@...nel.org>, <philip@...ister.org>,
	<rubini@...dd.com>, <s.trumtrar@...gutronix.de>,
	<jason@...edaemon.net>, <kyle.teske@...com>, <nico@...aro.org>,
	<balbi@...com>, <m.chehab@...sung.com>, <davidb@...eaurora.org>,
	<rob@...dley.net>, <davem@...emloft.net>, <cesarb@...arb.net>,
	<sameo@...ux.intel.com>, <akpm@...ux-foundation.org>,
	<linus.walleij@...aro.org>, <pawel.moll@....com>,
	<mark.rutland@....com>, <ijc+devicetree@...lion.org.uk>,
	<galak@...eaurora.org>, <delicious.quinoa@...il.com>,
	<dinguyen@...nsource.altera.com>, <yvanderv@...nsource.altera.com>
Subject: Re: [PATCH v4 4/6] fpga manager: add sysfs interface document

On Tue, 9 Dec 2014 14:14:48 -0600
> +Contact:	Alan Tull <atull@...nsource.altera.com>
> +Description:	Read state of fpga framework state machine as a string.
> +		Valid states may vary by manufacturer; superset is:
> +		* unknown		= can't determine state
> +		* power_off		= FPGA power is off
> +		* power_up		= FPGA reports power is up
> +		* reset			= FPGA held in reset state
> +		* firmware_request	= firmware class request in progress
> +		* firmware_request_err	= firmware request failed
> +		* write_init		= FPGA being prepared for programming
> +		* write_init_err	= Error while preparing FPGA for
> +					  programming
> +		* write			= FPGA ready to receive image data
> +		* write_err		= Error while programming
> +		* write_complete	= Doing post programming steps
> +		* write_complete_err	= Error while doing post programming
> +		* operating		= FPGA is programmed and operating


How does this work as a security model?

I want to assign an FPGA resource to a specific end user. How do I do
that with a pile of sysfs nodes ?

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