linux-kernel - Re: [PATCH v3] x86/iosf: Make IOSF driver modular and usable by more drivers

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]

Date:	Wed, 7 May 2014 18:10:42 +0100
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"David E. Box" <david.e.box@...ux.intel.com>, tglx@...utronix.de,
	mingo@...hat.com, x86@...nel.org, rafael.j.wysocki@...el.com,
	linux-kernel@...r.kernel.org, kristen.c.accardi@...el.com,
	jacob.jun.pan@...ux.intel.com
Subject: Re: [PATCH v3] x86/iosf: Make IOSF driver modular and usable by
 more drivers

On Wed, 07 May 2014 10:04:56 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:

> On 05/07/2014 09:48 AM, One Thousand Gnomes wrote:
> > On Fri,  2 May 2014 10:36:39 -0700
> >> +bool iosf_mbi_available(void)
> >> +{
> >> +	return mbi_pdev;
> >> +}
> >> +EXPORT_SYMBOL(iosf_mbi_available);
> > 
> > Probably worth a follow up patch that comments this so the assumption
> > that iosf can never be unloaded or hot-unplugged is clear.
> > 
> 
> When you say unloaded you mean the module or the hardware?

Both. Currently the hardware isn't removable (but could be virtually
removed by playing with unplugging) and the module can't be unloaded so
the assumption is fine.

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