All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/4] xfs: remove xfs_bmbt_validate_extent
Date: Tue, 24 Oct 2017 22:24:26 -0700	[thread overview]
Message-ID: <20171025052426.GB20669@magnolia> (raw)
In-Reply-To: <20171024075415.GA14823@lst.de>

On Tue, Oct 24, 2017 at 09:54:15AM +0200, Christoph Hellwig wrote:
> > By removing this, I think we no longer report corruption if we encounter
> > 'unwritten' attr fork extents, which (AFAIK) aren't allowed.
> 
> True.  Oh well, skip this patch for now if you apply the rest, and
> I'll have to do some gymnastics to keep it.

Ok.  I can try to fix it up in the patch stack tomorrow, but feel free
to beat me to it. :P

--D

  reply	other threads:[~2017-10-25  5:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23  6:30 even more extent mapping cleanups Christoph Hellwig
2017-10-23  6:30 ` [PATCH 1/4] xfs: add asserts for the mmap lock in xfs_{insert,collapse}_file_space Christoph Hellwig
2017-10-23 15:42   ` Darrick J. Wong
2017-10-23  6:30 ` [PATCH 2/4] xfs: remove xfs_bmbt_validate_extent Christoph Hellwig
2017-10-23 15:41   ` Darrick J. Wong
2017-10-24  7:54     ` Christoph Hellwig
2017-10-25  5:24       ` Darrick J. Wong [this message]
2017-10-25  6:19         ` Christoph Hellwig
2017-10-23  6:30 ` [PATCH 3/4] xfs: merge xfs_bmap_read_extents into xfs_iread_extents Christoph Hellwig
2017-10-23 23:19   ` Darrick J. Wong
2017-10-23  6:30 ` [PATCH 4/4] xfs: add a new xfs_iext_lookup_extent_before helper Christoph Hellwig
2017-10-23 23:32   ` Darrick J. Wong

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=20171025052426.GB20669@magnolia \
    --to=darrick.wong@oracle.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 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.