Re: [PATCH v5 00/17] fs: introduce new writeback error reporting and convert... | linux-block

[PATCH v5 00/17] fs: introduce new writeback error reporting and convert ext2 and ext4 to use it · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 02/17] fs: new infrastructure for writeback error handling and reporting · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 03/17] mm: tracepoints for writeback error events · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 05/17] Documentation: flesh out the section in vfs.txt on storing and reporting writeback errors · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 06/17] fs: adapt sync_file_range to new reporting infrastructure · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 08/17] dax: set errors in mapping when writeback fails · Jeff Layton <hidden> · 2017-05-31
Re: [PATCH v5 08/17] dax: set errors in mapping when writeback fails · Ross Zwisler <hidden> · 2017-06-06
Re: [PATCH v5 08/17] dax: set errors in mapping when writeback fails · Jeff Layton <hidden> · 2017-06-06
[PATCH v5 09/17] block: convert to errseq_t based writeback error tracking · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 10/17] block: add sync_blockdev_since and sync_filesystem_since · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 12/17] fs: allow __generic_file_fsync to support both flavors of error reporting · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 15/17] fs: add a write_one_page_since · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 16/17] ext2: convert to errseq_t based writeback error tracking · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 17/17] fs: convert ext2 to use write_one_page_since · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 01/17] lib: add errseq_t type and infrastructure for handling it · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 04/17] fs: add a new fstype flag to indicate how writeback errors are tracked · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 14/17] ext4: convert to errseq_t based error tracking · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 11/17] fs: add f_md_wb_err field to struct file for tracking metadata errors · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 13/17] jbd2: conditionally handle errors using errseq_t based on FS_WB_ERRSEQ flag · Jeff Layton <hidden> · 2017-05-31
[PATCH v5 07/17] mm: add filemap_fdatawait_range_since and filemap_write_and_wait_range_since · Jeff Layton <hidden> · 2017-05-31
Re: [PATCH v5 00/17] fs: introduce new writeback error reporting and convert ext2 and ext4 to use it · Andrew Morton <akpm@linux-foundation.org> · 2017-05-31
Re: [PATCH v5 00/17] fs: introduce new writeback error reporting and convert ext2 and ext4 to use it · Jeff Layton <hidden> · 2017-05-31
Re: [PATCH v5 00/17] fs: introduce new writeback error reporting and convert ext2 and ext4 to use it · Andrew Morton <akpm@linux-foundation.org> · 2017-05-31
Re: [PATCH v5 00/17] fs: introduce new writeback error reporting and convert ext2 and ext4 to use it · Jeff Layton <hidden> · 2017-05-31
Re: [PATCH v5 00/17] fs: introduce new writeback error reporting and convert ext2 and ext4 to use it · Ross Zwisler <hidden> · 2017-06-02
Re: [PATCH v5 00/17] fs: introduce new writeback error reporting and convert ext2 and ext4 to use it · Jeff Layton <hidden> · 2017-06-02

Re: [PATCH v5 00/17] fs: introduce new writeback error reporting and convert ext2 and ext4 to use it

From: Andrew Morton <akpm@linux-foundation.org>
Date: 2017-05-31 20:27:28
Also in: linux-ext4, linux-fsdevel, lkml

On Wed, 31 May 2017 08:45:23 -0400 Jeff Layton [off-list ref] wrote:

This is v5 of the patchset to improve how we're tracking and reporting
errors that occur during pagecache writeback.

I'm curious to know how you've been testing this?  Is that testing
strong enough for us to be confident that all nature of I/O errors
will be reported to userspace?

`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