From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bernhard Kohl <bernhard.kohl@nsn.com>,
Christoph Hellwig <hch@lst.de>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] target urgent updates for v3.4-final
Date: Thu, 17 May 2012 13:12:00 -0700 [thread overview]
Message-ID: <1337285520.32217.269.camel@haakon2.linux-iscsi.org> (raw)
Hi Linus,
Here are two more target-core urgent updates for v3.4-final. Please go
ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git 3.4-urgent
The first patch addresses a SPC-2 reservations RELEASE bug in a special
(iscsi specific) multi-ISID setup case that was allowing the same
initiator to be able to incorrect release it's own reservation on a
different SCSI path with enforce_pr_isid=1 operation. This bug was
caught by Bernhard Kohl.
The second patch is to address a bug with FILEIO backends where the
incorrect number of blocks for READ_CAPACITY was being reported after an
underlying device-mapper block_device size change. This patch uses now
i_size_read() in fd_get_blocks() for FILEIO backends with an underlying
block_device, instead of trying to determine this value at setup time
during fd_create_virtdevice(). (hch CC'ed)
Both are CC'ed to stable.
Thank you,
--nab
Bernhard Kohl (1):
target: Fix SPC-2 RELEASE bug for multi-session iSCSI client setups
Nicholas Bellinger (1):
target: Fix bug in handling of FILEIO + block_device resize ops
drivers/target/target_core_file.c | 22 ++++++++++++++++------
drivers/target/target_core_pr.c | 3 +++
2 files changed, 19 insertions(+), 6 deletions(-)
reply other threads:[~2012-05-17 20:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1337285520.32217.269.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=bernhard.kohl@nsn.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®