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] [day] [month] [year] [list]

Message-ID: <CAE9FiQUj6-OwjfeOzWDUufTy9DhkTvbVkmQeQLCW40RsUyRuaw@mail.gmail.com>
Date:	Fri, 23 Dec 2011 10:24:28 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	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 Thu, Dec 22, 2011 at 7:50 PM, Konrad Rzeszutek Wilk
<konrad@...nok.org> wrote:
>>
>> When legacy mode iscsi installation is used, installation program will
>> not need user install those info again.
>>
>> QA are complaining that difference.
>
> I think I understand your position. You are getting emails from QA
> testing some hardware saying it does not work with RHEL, so you try
> upstream, find the bug and fix it (awesome, thanks for doing that),
> and then you want to back-port the fix so RHEL picks it up (and can
> close the bug). Thr mechanism for that is by contacting the vendor
> about this - either using the Program Manager to open a feature
> request, or waiting for a customer to report this bug (on the Red Hat
> side) and then your fix will be magically picked up.

yes,

attached is the patch for 2.6.32 to close the loop.

Thanks

Yinghai

View attachment "fix_ibft_checking_2.6.32.patch" of type "text/x-patch" (2060 bytes)