All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: don't block on the ilock for RWF_NOWAIT
Date: Fri, 23 Feb 2018 03:19:16 +0100	[thread overview]
Message-ID: <20180223021916.GA5787@lst.de> (raw)
In-Reply-To: <20180223020243.GA5611@lst.de>

FYI, I've pushed a iomap-locking branch to my xfs.git on how
to start the urgent fixes (4.16-rc) in this area.  I think most
of the additional changes in your WIP patch can be nicely rebased
on top of that.

On Fri, Feb 23, 2018 at 03:02:43AM +0100, Christoph Hellwig wrote:
> On Fri, Feb 23, 2018 at 12:03:26PM +1100, Dave Chinner wrote:
> > Where can I find all of your patches, because it seems we're
> > unnecessarily duplicating a lot of work in this area...
> 
> I've pushed my current O_ATOMIC WIP tree here:
> 
>     git://git.infradead.org/users/hch/xfs.git O_ATOMIC-wip
> 
> gitweb:
> 
>     http://git.infradead.org/users/hch/xfs.git/shortlog/refs/heads/O_ATOMIC-wip
> 
> Note that at least the last commit is most certainly actually broken
> at the moment, and also too ugly to live without further refactoring.
---end quoted text---

  reply	other threads:[~2018-02-23  2:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 15:06 [PATCH] xfs: don't block on the ilock for RWF_NOWAIT Christoph Hellwig
2018-02-23  0:08 ` Dave Chinner
2018-02-23  0:22   ` Christoph Hellwig
2018-02-23  1:03     ` Dave Chinner
2018-02-23  2:02       ` Christoph Hellwig
2018-02-23  2:19         ` Christoph Hellwig [this message]
2018-02-23  4:10           ` Dave Chinner

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=20180223021916.GA5787@lst.de \
    --to=hch@lst.de \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@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.