From: Mike Christie <michaelc@cs.wisc.edu>
To: linux-scsi@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [PATCH 1/1] RFC: scsi/dm-mpath: return -EACCES on reservation conflict
Date: Mon, 12 Oct 2009 23:03:29 -0500 [thread overview]
Message-ID: <4AD3FC11.7060003@cs.wisc.edu> (raw)
In-Reply-To: <1255406553-7054-1-git-send-email-michaelc@cs.wisc.edu>
michaelc@cs.wisc.edu wrote:
> So, I did another take just using lots of different -EXYZ values. See
> this patch
For got to add the link
http://www.kernel.org/pub/linux/kernel/people/mnc/multipath/dm-mpath-use-exyz.patch
>
> for an example. The problem is still that the transport error
> and generic error cases are the same so all I bought was the handling
> of the reservation conflict.
>
next prev parent reply other threads:[~2009-10-13 4:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 4:02 [PATCH 1/1] RFC: scsi/dm-mpath: return -EACCES on reservation conflict michaelc
2009-10-13 4:03 ` Mike Christie [this message]
2009-10-13 10:07 ` Boaz Harrosh
2010-12-17 16:59 ` Mike Snitzer
2011-02-25 18:40 ` Eddie Williams
2011-02-25 18:43 ` Eddie Williams
2011-02-26 2:39 ` Mike Snitzer
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=4AD3FC11.7060003@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).