From: jlayton@kernel.org To: Andrew Morton <akpm@linux-foundation.org>, Al Viro <viro@ZenIV.linux.org.uk>, Jan Kara <jack@suse.cz>, tytso@mit.edu, axboe@kernel.dk, mawilcox@microsoft.com, ross.zwisler@linux.intel.com, corbet@lwn.net, Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>, David Sterba <dsterba@suse.com>, "Darrick J . Wong" <darrick.wong@oracle.com> Cc: Carlos Maiolino <cmaiolino@redhat.com>, Eryu Guan <eguan@redhat.com>, David Howells <dhowells@redhat.com>, Christoph Hellwig <hch@infradead.org>, Liu Bo <bo.li.liu@oracle.com>, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-block@vger.kernel.org Subject: [PATCH v8 06/18] mm: clear AS_EIO/AS_ENOSPC when writeback initiation fails Date: Thu, 29 Jun 2017 09:19:42 -0400 [thread overview] Message-ID: <20170629131954.28733-7-jlayton@kernel.org> (raw) In-Reply-To: <20170629131954.28733-1-jlayton@kernel.org> From: Jeff Layton <jlayton@redhat.com> filemap_write_and_wait{_range} will return an error if writeback initiation fails, but won't clear errors in the address_space. This is particularly problematic on DAX, as it's effectively synchronous. Ensure that we clear the AS_EIO/AS_ENOSPC flags when filemap_fdatawrite returns an error. Signed-off-by: Jeff Layton <jlayton@redhat.com> --- mm/filemap.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/mm/filemap.c b/mm/filemap.c index e5711b2728f4..49bc9720fb00 100644 --- a/mm/filemap.c +++ b/mm/filemap.c @@ -515,6 +515,9 @@ int filemap_write_and_wait(struct address_space *mapping) int err2 = filemap_fdatawait(mapping); if (!err) err = err2; + } else { + /* Clear any previously stored errors */ + filemap_check_errors(mapping); } } else { err = filemap_check_errors(mapping); @@ -549,6 +552,9 @@ int filemap_write_and_wait_range(struct address_space *mapping, lstart, lend); if (!err) err = err2; + } else { + /* Clear any previously stored errors */ + filemap_check_errors(mapping); } } else { err = filemap_check_errors(mapping); -- 2.13.0
WARNING: multiple messages have this Message-ID (diff)
From: jlayton@kernel.org To: Andrew Morton <akpm@linux-foundation.org>, Al Viro <viro@ZenIV.linux.org.uk>, Jan Kara <jack@suse.cz>, tytso@mit.edu, axboe@kernel.dk, mawilcox@microsoft.com, ross.zwisler@linux.intel.com, corbet@lwn.net, Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>, David Sterba <dsterba@suse.com>, "Darrick J . Wong" <darrick.wong@oracle.com> Cc: Carlos Maiolino <cmaiolino@redhat.com>, Eryu Guan <eguan@redhat.com>, David Howells <dhowells@redhat.com>, Christoph Hellwig <hch@infradead.org>, Liu Bo <bo.li.liu@oracle.com>, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-block@vger.kernel.org Subject: [PATCH v8 06/18] mm: clear AS_EIO/AS_ENOSPC when writeback initiation fails Date: Thu, 29 Jun 2017 09:19:42 -0400 [thread overview] Message-ID: <20170629131954.28733-7-jlayton@kernel.org> (raw) In-Reply-To: <20170629131954.28733-1-jlayton@kernel.org> From: Jeff Layton <jlayton@redhat.com> filemap_write_and_wait{_range} will return an error if writeback initiation fails, but won't clear errors in the address_space. This is particularly problematic on DAX, as it's effectively synchronous. Ensure that we clear the AS_EIO/AS_ENOSPC flags when filemap_fdatawrite returns an error. Signed-off-by: Jeff Layton <jlayton@redhat.com> --- mm/filemap.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/mm/filemap.c b/mm/filemap.c index e5711b2728f4..49bc9720fb00 100644 --- a/mm/filemap.c +++ b/mm/filemap.c @@ -515,6 +515,9 @@ int filemap_write_and_wait(struct address_space *mapping) int err2 = filemap_fdatawait(mapping); if (!err) err = err2; + } else { + /* Clear any previously stored errors */ + filemap_check_errors(mapping); } } else { err = filemap_check_errors(mapping); @@ -549,6 +552,9 @@ int filemap_write_and_wait_range(struct address_space *mapping, lstart, lend); if (!err) err = err2; + } else { + /* Clear any previously stored errors */ + filemap_check_errors(mapping); } } else { err = filemap_check_errors(mapping); -- 2.13.0 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-06-29 13:19 UTC|newest] Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-06-29 13:19 [PATCH v8 00/18] fs: enhanced writeback error reporting with errseq_t (pile #1) jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` [PATCH v8 01/18] fs: remove call_fsync helper function jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` [PATCH v8 02/18] buffer: use mapping_set_error instead of setting the flag jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` [PATCH v8 03/18] fs: check for writeback errors after syncing out buffers in generic_file_fsync jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 14:19 ` Christoph Hellwig 2017-06-29 14:19 ` Christoph Hellwig 2017-06-29 20:17 ` Jeff Layton 2017-06-29 20:17 ` Jeff Layton 2017-06-29 20:17 ` Jeff Layton 2017-06-29 20:17 ` Jeff Layton 2017-06-29 13:19 ` [PATCH v8 04/18] buffer: set errors in mapping at the time that the error occurs jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` [PATCH v8 05/18] jbd2: don't clear and reset errors after waiting on writeback jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` jlayton [this message] 2017-06-29 13:19 ` [PATCH v8 06/18] mm: clear AS_EIO/AS_ENOSPC when writeback initiation fails jlayton 2017-06-29 13:19 ` [PATCH v8 07/18] mm: don't TestClearPageError in __filemap_fdatawait_range jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` [PATCH v8 08/18] mm: clean up error handling in write_one_page jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` [PATCH v8 09/18] lib: add errseq_t type and infrastructure for handling it jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` [PATCH v8 10/18] fs: new infrastructure for writeback error handling and reporting jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:45 ` Jeff Layton 2017-06-29 13:45 ` Jeff Layton 2017-06-29 13:45 ` Jeff Layton 2017-06-29 13:45 ` Jeff Layton 2017-06-29 17:52 ` Jeff Layton 2017-06-29 17:52 ` Jeff Layton 2017-06-29 17:52 ` Jeff Layton 2017-06-29 17:52 ` Jeff Layton 2017-06-29 13:19 ` [PATCH v8 11/18] mm: set both AS_EIO/AS_ENOSPC and errseq_t in mapping_set_error jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` [PATCH v8 12/18] Documentation: flesh out the section in vfs.txt on storing and reporting writeback errors jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 17:11 ` Darrick J. Wong 2017-06-29 17:11 ` Darrick J. Wong 2017-06-29 18:13 ` Jeff Layton 2017-06-29 18:13 ` Jeff Layton 2017-06-29 18:13 ` Jeff Layton 2017-06-29 18:13 ` Jeff Layton 2017-06-29 18:21 ` Matthew Wilcox 2017-06-29 18:21 ` Matthew Wilcox 2017-06-29 18:21 ` Matthew Wilcox 2017-06-29 20:42 ` Jeff Layton 2017-06-29 20:42 ` Jeff Layton 2017-06-29 20:42 ` Jeff Layton 2017-06-29 20:42 ` Jeff Layton 2017-06-29 20:42 ` Jeff Layton 2017-06-29 13:19 ` [PATCH v8 13/18] dax: set errors in mapping when writeback fails jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` [PATCH v8 14/18] block: convert to errseq_t based writeback error tracking jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 14:18 ` Christoph Hellwig 2017-06-29 14:18 ` Christoph Hellwig 2017-06-29 13:19 ` [PATCH v8 15/18] fs: convert __generic_file_fsync to use errseq_t based reporting jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 13:19 ` [PATCH v8 16/18] ext4: use errseq_t based error handling for reporting data writeback errors jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 14:12 ` Christoph Hellwig 2017-06-29 14:12 ` Christoph Hellwig 2017-06-29 20:26 ` Jeff Layton 2017-06-29 20:26 ` Jeff Layton 2017-06-29 20:26 ` Jeff Layton 2017-06-29 20:26 ` Jeff Layton 2017-06-29 13:19 ` [PATCH v8 17/18] xfs: minimal conversion to errseq_t writeback error reporting jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 14:12 ` Christoph Hellwig 2017-06-29 14:12 ` Christoph Hellwig 2017-06-30 16:45 ` Jeff Layton 2017-06-30 16:45 ` Jeff Layton 2017-06-30 16:45 ` Jeff Layton 2017-06-30 16:45 ` Jeff Layton 2017-06-30 16:49 ` Christoph Hellwig 2017-06-30 16:49 ` Christoph Hellwig 2017-06-29 17:13 ` Darrick J. Wong 2017-06-29 17:13 ` Darrick J. Wong 2017-06-29 13:19 ` [PATCH v8 18/18] btrfs: minimal conversion to errseq_t writeback error reporting on fsync jlayton 2017-06-29 13:19 ` jlayton 2017-06-29 14:17 ` Christoph Hellwig 2017-06-29 14:17 ` Christoph Hellwig 2017-06-29 20:32 ` Jeff Layton 2017-06-29 20:32 ` Jeff Layton 2017-06-29 20:32 ` Jeff Layton 2017-06-29 20:32 ` Jeff Layton
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=20170629131954.28733-7-jlayton@kernel.org \ --to=jlayton@kernel.org \ --cc=akpm@linux-foundation.org \ --cc=axboe@kernel.dk \ --cc=bo.li.liu@oracle.com \ --cc=clm@fb.com \ --cc=cmaiolino@redhat.com \ --cc=corbet@lwn.net \ --cc=darrick.wong@oracle.com \ --cc=dhowells@redhat.com \ --cc=dsterba@suse.com \ --cc=eguan@redhat.com \ --cc=hch@infradead.org \ --cc=jack@suse.cz \ --cc=jbacik@fb.com \ --cc=linux-block@vger.kernel.org \ --cc=linux-btrfs@vger.kernel.org \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-xfs@vger.kernel.org \ --cc=mawilcox@microsoft.com \ --cc=ross.zwisler@linux.intel.com \ --cc=tytso@mit.edu \ --cc=viro@ZenIV.linux.org.uk \ /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: linkBe 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.