linux-kernel - [GIT PULL] target fixes for v3.9-rc5

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]

Date:	Sat, 30 Mar 2013 12:43:15 -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>,
	"Michael S. Tsirkin" <mst@...hat.com>, Asias He <asias@...hat.com>
Subject: [GIT PULL] target fixes for v3.9-rc5

Hi Linus,

Here are two more target-pending fixes for v3.9-rc5 code.

Please go ahead and pull from:

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

This includes the bug-fix for a >= v3.8-rc1 regression specific to
iscsi-target persistent reservation conflict handling (CC'ed to stable),
and a tcm_vhost patch to drop VIRTIO_RING_F_EVENT_IDX usage so that
in-flight qemu vhost-scsi-pci device code can detect the proper vhost
feature bits.

Also, there are two more tcm_vhost patches still being discussed by MST
and Asias for v3.9 that will be required for the in-flight qemu
vhost-scsi-pci device patch to function properly, and that should
(hopefully) be the last target fixes for this round.

Thank you,

--nab

Nicholas Bellinger (2):
  tcm_vhost: Avoid VIRTIO_RING_F_EVENT_IDX feature bit
  target: Fix RESERVATION_CONFLICT status regression for iscsi-target
    special case

 drivers/target/target_core_transport.c |    4 +++-
 drivers/vhost/tcm_vhost.c              |   13 +++++++++++--
 2 files changed, 14 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/