From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: LKML <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Douglas Gilbert <dgilbert@interlog.com>,
Mike Christie <michaelc@cs.wisc.edu>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/2] [Target_Core_Mod/Persistent_Reservations]: Add implict release and PROUT CLEAR SA
Date: Thu, 19 Mar 2009 01:55:27 -0700 [thread overview]
Message-ID: <1237452927.4138.35.camel@haakon2.linux-iscsi.org> (raw)
Greetings all,
This first patch series adds implict release of PR reservations/registrations when
a $FABRIC_MOD logical unit ACL is being released through target_core_mod/ConfigFS.
The second patch adds support for the PROUT CLEAR service action that allows a registered
I_T nexus (eg: initiator port) to release PR reservations/registrations. This is one of
the PROUT service actions that various client side cluster code / SCSI subsystem initiators
use with SCSI persistent reservations for fencing of failed nodes.
These patches are made against lio-core-2.6.git/master and tested on
v2.6.29-rc8 x86 32-bit HVM using sg_persist from sg3_utils. The lio-core-2.6.git tree
can be found at:
http://git.kernel.org/?p=linux/kernel/git/nab/lio-core-2.6.git;a=summary
[PATCH 1/2] [Target_Core_Mod/Persistent_Reservations]: Add implict PR RELEASE+UNREGISTER for LUN acl removal
[PATCH 2/2] [Target_Core_Mod/Persistent_Reservations]: Add PROUT CLEAR service action
drivers/lio-core/target_core_base.h | 1 +
drivers/lio-core/target_core_device.c | 14 ++-
drivers/lio-core/target_core_pr.c | 288 ++++++++++++++++++++++++++-------
drivers/lio-core/target_core_pr.h | 2 +
4 files changed, 239 insertions(+), 66 deletions(-)
--nab
reply other threads:[~2009-03-19 8:55 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=1237452927.4138.35.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dgilbert@interlog.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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
Powered by JetHome