linux-kernel - [GIT PULL] iBFT fixes for v2.6.35-rc1

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

Message-ID: <20100812185247.GA28744@hera.kernel.org>
Date:	Thu, 12 Aug 2010 18:52:47 +0000
From:	Konrad Rzeszutek Wilk <konrad@...nel.org>
To:	torvalds@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, pjones@...hat.com,
	randy.dunlap@...cle.com, jayamohank@...verengines.com
Subject: [GIT PULL] iBFT fixes for v2.6.35-rc1

Hi Linus,

There were two bugs that got caught after the iBFT tree was merged.
One of them is quite embarrassing and it is a NULL pointer exception when
we rmmod the ibft module where there are no iBFT table present. The other
was spotted by Randy in the linux-next and is a compilation issue if you don't
have CONFIG_SCSI set.

Please pull from:

	git://git.kernel.org/pub/scm/linux/kernel/git/konrad/ibft-2.6.git stable/fixes

the patches since commit 5abd9ccced7a726c817dd6b5b96bc933859138d1
Author: Linus Torvalds <torvalds@...ux-foundation.org>
Date:   Wed Aug 4 11:25:58 2010 -0700

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/konrad/ibft-2.6


Thanks,

Konrad Rzeszutek Wilk (1):
      ibft: Kernel oops when rmmoding iscsi_ibft with no iBFT present.

Randy Dunlap (1):
      firmware: ibft depends on SCSI

 drivers/firmware/Kconfig      |    2 +-
 drivers/firmware/iscsi_ibft.c |    6 ++++--
 2 files changed, 5 insertions(+), 3 deletions(-)
--
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/