linux-kernel - Re: [GIT PULL] ibft fix for 3.2-rc6

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:	Thu, 22 Dec 2011 16:45:58 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Konrad Rzeszutek Wilk <konrad@...nok.org>
Cc:	Greg KH <gregkh@...e.de>, stable@...r.kernel.org,
	linux-kernel@...r.kernel.org, pjones@...hat.com
Subject: Re: [GIT PULL] ibft fix for 3.2-rc6

On Sat, Dec 17, 2011 at 6:42 AM, Konrad Rzeszutek Wilk
<konrad@...nok.org> wrote:
>>
>> but 2.6.32 base kernel still could take iscsi_ibft.c related changes
>> in the patch, and ignore conflicts with iscs_ibft_find.c.
>> but that will add new feature to 2.6.32. Not sure if stable tree
>> should take that kind of change.
>
> It could, but I am not too thrilled about it.

RHEL 6.x are still with 2.6.32...

So under UEFI mode installation, users need to input iscsi target info
again during selecting storage for installation. Because kernel does
not to parse that from acpi iBFT table.

When legacy mode iscsi installation is used, installation program will
not need user install those info again.

QA are complaining that difference.

Thanks

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