linux-kernel - Re: [PATCH 1/2] RFC: iscsi ibft: separate ibft parsing from sysfs interface

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, 11 Aug 2010 08:54:35 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Konrad Rzeszutek Wilk <konrad@...nok.org>
Cc:	michaelc@...wisc.edu, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org, pjones@...hat.com,
	open-iscsi@...glegroups.com
Subject: Re: [PATCH 1/2] RFC: iscsi ibft: separate ibft parsing from sysfs
 interface

On Mon, 12 Apr 2010 22:20:29 -0400 Konrad Rzeszutek Wilk wrote:

> On Monday 12 April 2010 14:06:17 michaelc@...wisc.edu wrote:
> > From: Mike Christie <michaelc@...wisc.edu>
> >
> > Not all iscsi drivers support ibft. For drivers like be2iscsi
> > that do not but are bootable through a vendor firmware specific
> > format/process this patch moves the sysfs interface from the ibft code
> > to a lib module. This then allows userspace tools to search for iscsi boot
> > info in a common place and in a common format.
> >
> > ibft iscsi boot info is exported in the same place as it was
> > before: /sys/firmware/ibft.
> >
> > vendor/fw boot info gets export in /sys/firmware/iscsi_bootX, where X is
> > the scsi host number of the HBA. Underneath these parent dirs, the
> > target, ethernet, and initiator dirs are the same as they were before.
> >
> > This patch was made over the ibft-2.6 tree's ibft-1.03 branch:
> > http://git.kernel.org/?p=linux/kernel/git/konrad/ibft-2.6.git;a=shortlog;h=
> >refs/heads/ibft-1.03
> >
> >
> > Signed-off-by: Mike Christie <michaelc@...wisc.edu>
> > ---
> Looks good to my eyes.
> 
> Let me run it tomorrow through my regression bucket before I stick on the git 
> tree.

Can we get this patch into linux-next, please?

or if it's there, there are still errors like this that need to be checked.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/