All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vaughan Cao <vaughan.cao@oracle.com>
To: dgilbert@interlog.com, Christoph Hellwig <hch@infradead.org>
Cc: "SCSI development list" <linux-scsi@vger.kernel.org>,
	"James Bottomley" <james.bottomley@hansenpartnership.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Jörn Engel" <joern@logfs.org>
Subject: Re: [PATCH v2] sg: O_EXCL and other lock handling
Date: Sun, 03 Nov 2013 14:32:52 +0800	[thread overview]
Message-ID: <5275EE14.2000701@oracle.com> (raw)
In-Reply-To: <527542E3.7090809@interlog.com>


On 2013年11月03日 02:22, Douglas Gilbert wrote:
> On 13-11-01 01:16 AM, vaughan wrote:
>
> I do not follow the last point but that is not important.
>
>
> For reasons that I listed in a private post I think
> that my patch presented in this thread is closer to
> our goals than your patch (2013/6/17/319). Timing is
> important as well since we are approaching the lk 3.13
> merge window. Regressions are what will set us back.
>
Yes, I agree with you. My v2 patch lacks much consideration on 
release/detach cases, which is a very significant issue we should 
address along with o_excl bug.

Thanks,
Vaughan

  reply	other threads:[~2013-11-03  6:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 22:24 [PATCH v2] sg: O_EXCL and other lock handling Douglas Gilbert
2013-10-31 15:56 ` Christoph Hellwig
2013-10-31 19:20   ` Douglas Gilbert
2013-11-01  5:14     ` vaughan
2013-11-01  5:16     ` vaughan
2013-11-02 18:22       ` Douglas Gilbert
2013-11-03  6:32         ` Vaughan Cao [this message]
2013-11-06 15:50     ` Christoph Hellwig
2013-11-06 19:30       ` Douglas Gilbert
2013-11-07 21:44         ` Christoph Hellwig

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=5275EE14.2000701@oracle.com \
    --to=vaughan.cao@oracle.com \
    --cc=dgilbert@interlog.com \
    --cc=hch@infradead.org \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.