linux-kernel - [GIT PULL] target fixes for v3.4-rc7

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

Date:	Fri, 11 May 2012 14:52:16 -0700
From:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	target-devel <target-devel@...r.kernel.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] target fixes for v3.4-rc7

Hi Linus !

This time around for -rc7, there is only a single outstanding target
pending bugfix ready to be merged..

Please go ahead and pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git 3.4-urgent

This patch removes some incorrect legacy code to free se_lun_acl memory
in the NodeACL release path that could potentially trigger an OOPs
during shutdown once dynamic -> explicit initiator NodeACL conversion
has occurred.

That said, we've been able to trigger an OOPs in v4.0 code for this
special case when the associated MappedLUNs had not also been made
explicit based on active TPG LUN layout during the conversion, so it
really makes senses to go ahead and drop this extra cruft to avoid any
possible issues here.

This ends up only effecting iscsi-target module code (it's the only
user) and is CC'ed to stable.

Thanks!

--nab

Nicholas Bellinger (1):
  target: Drop incorrect se_lun_acl release for dynamic -> explict ACL
    conversion

 drivers/target/target_core_tpg.c |   21 ---------------------
 1 files changed, 0 insertions(+), 21 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/