linux-kernel - Re: declare MODULE

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: <1294202192.7879.30.camel@mulgrave.site>
Date:	Tue, 04 Jan 2011 22:36:32 -0600
From:	James Bottomley <James.Bottomley@...e.de>
To:	DuanZhenzhong <zhenzhong.duan@...cle.com>
Cc:	Jeff Garzik <jeff@...zik.org>, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: declare MODULE_FIRMWARE in libsas

On Wed, 2011-01-05 at 11:18 +0800, DuanZhenzhong wrote:
> Jeff Garzik 写道:
> > On 01/04/2011 09:08 AM, James Bottomley wrote:
> >> On Tue, 2011-01-04 at 15:43 +0800, DuanZhenzhong wrote:
> >>> Signed-off-by: Zhenzhong Duan<zhenzhong.duan@...cle.com>
> >>>
> >>> ---
> >>
> >> Description?  Since libsas has no firmware, surely some explanation is
> >> required.
> >
> > Indeed.  Looks bogus at first glance?
> >
> >
> I was finding all requested but not exported firmware in scsi driver for 
> generating dump initrd use.
> In sas_scsi_host.c, request_firmware is called with "sas_addr", sas_addr 
> neither builtin nor exported. Don't sas_addr a firmware? Please correct 
> me. thanks

No, it's not requesting any firmware ... it's a slight misuse of the
firmware mechanism that allows a libsas based driver to be given a SAS
address if it doesn't have an internal nsvram to store one.

James


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