linux-kernel - Re: [RFC PATCH] x86: Moving probe_roms_32 to probe

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: <AANLkTikimHCsFmavDoXn3Pka8WWMePqk+hNUK8h=DqSQ@mail.gmail.com>
Date:	Thu, 24 Feb 2011 17:27:07 -0800
From:	Dan Williams <dan.j.williams@...el.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Dave Jiang <dave.jiang@...el.com>, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org, David Milburn <dmilburn@...hat.com>
Subject: Re: [RFC PATCH] x86: Moving probe_roms_32 to probe_roms

On Tue, Feb 22, 2011 at 12:16 PM, Dan Williams <dan.j.williams@...el.com> wrote:
> From: Dave Jiang <dave.jiang@...el.com>
>
> Moving the probe_roms_32 code to probe_roms and make available for all x86. The
> end result adapter roms data structure is made available read-only to drivers.
> The Intel isci SAS driver needs to scan the OROM memory in order to pull OEM
> parameters from the OROM.
>
> Signed-off-by: Dan Williams <dan.j.williams@...el.com>
> Signed-off-by: Dave Jiang <dave.jiang@...el.com>
> ---
>
> We could just export adapter_rom_resources directly and be done with it, but
> it seemed reasonable to have a compile time catch for drivers that try to
> modify the resources, and that drivers should not assume the number of
> available adapter roms.
>

Ping?  The "RFC" was probably not needed, just wanted clarification if
the interface for modules to retrieve the adapter rom data was in good
taste.

Thanks,
Dan
--
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/