Re: [PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback... | linux-block

[PATCH v6 00/20] fs: enhanced writeback error reporting with errseq_t (pile #1) · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 01/20] mm: fix mapping_set_error call in me_pagecache_dirty · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 02/20] buffer: use mapping_set_error instead of setting the flag · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 03/20] fs: check for writeback errors after syncing out buffers in generic_file_fsync · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 04/20] buffer: set errors in mapping at the time that the error occurs · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 05/20] mm: don't TestClearPageError in __filemap_fdatawait_range · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 06/20] mm: drop "wait" parameter from write_one_page · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 07/20] mm: clean up error handling in write_one_page · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 08/20] lib: add errseq_t type and infrastructure for handling it · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 09/20] fs: new infrastructure for writeback error handling and reporting · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 10/13] ext4: add more robust reporting of metadata writeback errors · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 10/20] mm: tracepoints for writeback error events · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 11/13] Documentation: flesh out the section in vfs.txt on storing and reporting writeback errors · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 11/20] mm: set both AS_EIO/AS_ENOSPC and errseq_t in mapping_set_error · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback errors are tracked · Jeff Layton <hidden> · 2017-06-12
Re: [PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback errors are tracked · Christoph Hellwig <hch@infradead.org> · 2017-06-12
Re: [PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback errors are tracked · Jeff Layton <hidden> · 2017-06-13
Re: [PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback errors are tracked · Christoph Hellwig <hch@infradead.org> · 2017-06-14
Re: [PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback errors are tracked · Jeff Layton <hidden> · 2017-06-14
Re: [PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback errors are tracked · Christoph Hellwig <hch@infradead.org> · 2017-06-15
Re: [PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback errors are tracked · Jeff Layton <hidden> · 2017-06-15
Re: [PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback errors are tracked · Christoph Hellwig <hch@infradead.org> · 2017-06-15
Re: [PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback errors are tracked · Jeff Layton <hidden> · 2017-06-15
[PATCH v6 12/13] xfs: minimal conversion to errseq_t writeback error reporting · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 13/13] btrfs: minimal conversion to errseq_t writeback error reporting on fsync · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 13/20] Documentation: flesh out the section in vfs.txt on storing and reporting writeback errors · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 14/20] dax: set errors in mapping when writeback fails · Jeff Layton <hidden> · 2017-06-12
Re: [PATCH v6 14/20] dax: set errors in mapping when writeback fails · Christoph Hellwig <hch@infradead.org> · 2017-06-12
[PATCH v6 15/20] fs: have call_fsync call filemap_report_wb_err if FS_WB_ERRSEQ is set · Jeff Layton <hidden> · 2017-06-12
Re: [PATCH v6 15/20] fs: have call_fsync call filemap_report_wb_err if FS_WB_ERRSEQ is set · Christoph Hellwig <hch@infradead.org> · 2017-06-12
[PATCH v6 16/20] block: convert to errseq_t based writeback error tracking · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 17/20] fs: add f_md_wb_err field to struct file for tracking metadata errors · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 18/20] ext4: use errseq_t based error handling for reporting data writeback errors · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 20/20] btrfs: minimal conversion to errseq_t writeback error reporting on fsync · Jeff Layton <hidden> · 2017-06-12
[PATCH v6 19/20] xfs: minimal conversion to errseq_t writeback error reporting · Jeff Layton <hidden> · 2017-06-12
Re: [PATCH v6 19/20] xfs: minimal conversion to errseq_t writeback error reporting · Darrick J. Wong <hidden> · 2017-06-13
Re: [PATCH v6 19/20] xfs: minimal conversion to errseq_t writeback error reporting · Jeff Layton <hidden> · 2017-06-13

Re: [PATCH v6 12/20] fs: add a new fstype flag to indicate how writeback errors are tracked

From: Christoph Hellwig <hch@infradead.org>
Date: 2017-06-15 14:57:24
Also in: linux-btrfs, linux-ext4, linux-fsdevel, linux-mm, linux-xfs

On Thu, Jun 15, 2017 at 06:42:12AM -0400, Jeff Layton wrote:

Correct.

But if there is a data writeback error, should we report an error on all
open fds at that time (like we will for fsync)?

We should in theory, but I don't see how to properly do it.  In addition
sync_file_range just can't be used for data integrity to start with, so
I don't think it's worth it.  At some point we should add a proper
fsync_range syscall, though.

`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