linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Dave Chinner <david@fromorbit.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: remove "no-allocation" reservations for file creations
Date: Sun, 3 Sep 2017 08:31:50 -0700	[thread overview]
Message-ID: <20170903153150.GE4073@magnolia> (raw)
In-Reply-To: <20170903072513.GA14807@lst.de>

On Sun, Sep 03, 2017 at 09:25:13AM +0200, Christoph Hellwig wrote:
> Looks like this didn't make the 4.14 for-next branch either.  I guess
> we'll just consider it for the next round?

Yes, it caused a number of new xfstests failures due to new ENOSPC
messages in the golden output so I decided to defer action on it until
someone can assess and fix the problems appropriately.  The worst part
was that the new failures are intermittent.

--D

> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-09-03 15:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21  8:24 [PATCH] xfs: remove "no-allocation" reservations for file creations Christoph Hellwig
2017-08-23 20:22 ` Darrick J. Wong
2017-08-24  0:47   ` Dave Chinner
2017-08-24  0:57     ` Darrick J. Wong
2017-08-29 18:04     ` Darrick J. Wong
2017-09-03  7:25       ` Christoph Hellwig
2017-09-03 15:31         ` Darrick J. Wong [this message]
2017-12-05  1:34           ` Darrick J. Wong
2017-12-05 18:59             ` Darrick J. Wong
2017-12-07  0:02               ` Christoph Hellwig
2017-12-07  0:19                 ` Darrick J. Wong
2017-08-24 12:18   ` Christoph Hellwig
2017-12-07  0:15 ` Darrick J. Wong
2017-12-07  0:17   ` 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=20170903153150.GE4073@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --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 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).