From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/2] xfs: fix stale disk exposure after crash
Date: Thu, 16 Jan 2020 15:00:14 -0800 [thread overview]
Message-ID: <20200116230014.GK8247@magnolia> (raw)
In-Reply-To: <20200116164955.GC4593@infradead.org>
On Thu, Jan 16, 2020 at 08:49:55AM -0800, Christoph Hellwig wrote:
> Btw, what happened to:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?h=djwong-wtf&id=c931d4b2a6634b94cc11958706592944f55870d4
Originally I thought that it was enough to decrease *wbc->range_start to
the ondisk EOF since the _flush_unmap function triggers a writepages
call. Maybe it's better to make that part explicit.
However, it's only necessary to extend writeback like that if you're
going to retain the delalloc -> written state change. I don't consider
applying patch 2 to be a good idea though.
--D
> ?
prev parent reply other threads:[~2020-01-16 23:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 6:15 [PATCH 0/2] xfs: fix stale disk exposure after crash Darrick J. Wong
2020-01-16 6:15 ` [PATCH 1/2] xfs: force writes to delalloc regions to unwritten Darrick J. Wong
2020-01-16 16:47 ` Christoph Hellwig
2020-01-16 23:16 ` Darrick J. Wong
2020-01-19 20:49 ` Dave Chinner
2020-02-03 20:14 ` Darrick J. Wong
2020-05-07 10:32 ` Brian Foster
2020-05-14 16:33 ` Darrick J. Wong
2020-05-14 17:44 ` Brian Foster
2020-05-17 7:48 ` Christoph Hellwig
2020-05-19 0:40 ` Darrick J. Wong
2020-05-20 1:03 ` Dave Chinner
2020-01-16 6:15 ` [PATCH 2/2] xfs: relax unwritten writeback overhead under some circumstances Darrick J. Wong
2020-01-16 16:49 ` Christoph Hellwig
2020-01-16 23:15 ` Darrick J. Wong
2020-01-16 16:49 ` [PATCH 0/2] xfs: fix stale disk exposure after crash Christoph Hellwig
2020-01-16 23:00 ` Darrick J. Wong [this message]
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=20200116230014.GK8247@magnolia \
--to=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--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.