Re: [PATCH v8 17/18] xfs: minimal conversion to errseq_t writeback error reporting

[PATCH v8 00/18] fs: enhanced writeback error reporting with errseq_t (pile #1) · jlayton@kernel.org · 2017-06-29
[PATCH v8 01/18] fs: remove call_fsync helper function · jlayton@kernel.org · 2017-06-29
[PATCH v8 02/18] buffer: use mapping_set_error instead of setting the flag · jlayton@kernel.org · 2017-06-29
[PATCH v8 03/18] fs: check for writeback errors after syncing out buffers in generic_file_fsync · jlayton@kernel.org · 2017-06-29
Re: [PATCH v8 03/18] fs: check for writeback errors after syncing out buffers in generic_file_fsync · Christoph Hellwig <hch@infradead.org> · 2017-06-29
Re: [PATCH v8 03/18] fs: check for writeback errors after syncing out buffers in generic_file_fsync · Jeff Layton <hidden> · 2017-06-29
[PATCH v8 04/18] buffer: set errors in mapping at the time that the error occurs · jlayton@kernel.org · 2017-06-29
[PATCH v8 05/18] jbd2: don't clear and reset errors after waiting on writeback · jlayton@kernel.org · 2017-06-29
[PATCH v8 06/18] mm: clear AS_EIO/AS_ENOSPC when writeback initiation fails · jlayton@kernel.org · 2017-06-29
[PATCH v8 07/18] mm: don't TestClearPageError in __filemap_fdatawait_range · jlayton@kernel.org · 2017-06-29
[PATCH v8 08/18] mm: clean up error handling in write_one_page · jlayton@kernel.org · 2017-06-29
[PATCH v8 09/18] lib: add errseq_t type and infrastructure for handling it · jlayton@kernel.org · 2017-06-29
[PATCH v8 10/18] fs: new infrastructure for writeback error handling and reporting · jlayton@kernel.org · 2017-06-29
Re: [PATCH v8 10/18] fs: new infrastructure for writeback error handling and reporting · Jeff Layton <hidden> · 2017-06-29
Re: [PATCH v8 10/18] fs: new infrastructure for writeback error handling and reporting · Jeff Layton <hidden> · 2017-06-29
[PATCH v8 11/18] mm: set both AS_EIO/AS_ENOSPC and errseq_t in mapping_set_error · jlayton@kernel.org · 2017-06-29
[PATCH v8 12/18] Documentation: flesh out the section in vfs.txt on storing and reporting writeback errors · jlayton@kernel.org · 2017-06-29
Re: [PATCH v8 12/18] Documentation: flesh out the section in vfs.txt on storing and reporting writeback errors · Darrick J. Wong <hidden> · 2017-06-29
Re: [PATCH v8 12/18] Documentation: flesh out the section in vfs.txt on storing and reporting writeback errors · Jeff Layton <hidden> · 2017-06-29
RE: [PATCH v8 12/18] Documentation: flesh out the section in vfs.txt on storing and reporting writeback errors · Matthew Wilcox <hidden> · 2017-06-29
Re: [PATCH v8 12/18] Documentation: flesh out the section in vfs.txt on storing and reporting writeback errors · Jeff Layton <hidden> · 2017-06-29
[PATCH v8 13/18] dax: set errors in mapping when writeback fails · jlayton@kernel.org · 2017-06-29
[PATCH v8 14/18] block: convert to errseq_t based writeback error tracking · jlayton@kernel.org · 2017-06-29
Re: [PATCH v8 14/18] block: convert to errseq_t based writeback error tracking · Christoph Hellwig <hch@infradead.org> · 2017-06-29
[PATCH v8 15/18] fs: convert __generic_file_fsync to use errseq_t based reporting · jlayton@kernel.org · 2017-06-29
[PATCH v8 16/18] ext4: use errseq_t based error handling for reporting data writeback errors · jlayton@kernel.org · 2017-06-29
Re: [PATCH v8 16/18] ext4: use errseq_t based error handling for reporting data writeback errors · Christoph Hellwig <hch@infradead.org> · 2017-06-29
Re: [PATCH v8 16/18] ext4: use errseq_t based error handling for reporting data writeback errors · Jeff Layton <hidden> · 2017-06-29
[PATCH v8 17/18] xfs: minimal conversion to errseq_t writeback error reporting · jlayton@kernel.org · 2017-06-29
Re: [PATCH v8 17/18] xfs: minimal conversion to errseq_t writeback error reporting · Christoph Hellwig <hch@infradead.org> · 2017-06-29
Re: [PATCH v8 17/18] xfs: minimal conversion to errseq_t writeback error reporting · Jeff Layton <hidden> · 2017-06-30
Re: [PATCH v8 17/18] xfs: minimal conversion to errseq_t writeback error reporting · Christoph Hellwig <hch@infradead.org> · 2017-06-30
Re: [PATCH v8 17/18] xfs: minimal conversion to errseq_t writeback error reporting · Darrick J. Wong <hidden> · 2017-06-29
[PATCH v8 18/18] btrfs: minimal conversion to errseq_t writeback error reporting on fsync · jlayton@kernel.org · 2017-06-29
Re: [PATCH v8 18/18] btrfs: minimal conversion to errseq_t writeback error reporting on fsync · Christoph Hellwig <hch@infradead.org> · 2017-06-29
Re: [PATCH v8 18/18] btrfs: minimal conversion to errseq_t writeback error reporting on fsync · Jeff Layton <hidden> · 2017-06-29

From: Christoph Hellwig <hch@infradead.org>
Date: 2017-06-30 16:49:59
Also in: linux-btrfs, linux-ext4, linux-fsdevel, linux-mm, linux-xfs

On Fri, Jun 30, 2017 at 12:45:54PM -0400, Jeff Layton wrote:

Should I aim to do that with an individual patch for each fs, or is it
better to do a swath of them all at once in a single patch here?

I'd be perfectly happy with one big patch for all the trivial
conversions.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help