From: Jeff Layton <jlayton@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Bruce Fields <bfields@fieldses.org>, Jan Kara <jack@suse.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] writeback error handling fixes for v4.14
Date: Tue, 05 Sep 2017 07:39:33 -0400 [thread overview]
Message-ID: <1504611573.4728.23.camel@redhat.com> (raw)
The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/wberr-v4.14-1
for you to fetch changes up to 6d4b51241394664fffbf68ea86c96d2699344583:
ecryptfs: convert to file_write_and_wait in ->fsync (2017-08-03 14:20:22 -0400)
----------------------------------------------------------------
This pile continues the work from last cycle on better tracking
writeback errors. In v4.13 we added some basic errseq_t infrastructure
and converted a few filesystems to use it.
This set continues refining that infrastructure, adds documentation, and
converts most of the other filesystems to use it. The main exception at
this point is the NFS client.
----------------------------------------------------------------
Jeff Layton (10):
errseq: rename __errseq_set to errseq_set
Documentation: add some docs for errseq_t
mm: consolidate dax / non-dax checks for writeback
fuse: convert to errseq_t based error tracking for fsync
mm: add file_fdatawait_range and file_write_and_wait
fs: convert sync_file_range to use errseq_t based error-tracking
gfs2: convert to errseq_t based writeback error reporting for fsync
fs: convert a pile of fsync routines to errseq_t based reporting
mm: remove optimizations based on i_size in mapping writeback waits
ecryptfs: convert to file_write_and_wait in ->fsync
Documentation/errseq.rst | 149 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
arch/powerpc/platforms/cell/spufs/file.c | 2 +-
drivers/staging/lustre/lustre/llite/file.c | 2 +-
drivers/video/fbdev/core/fb_defio.c | 2 +-
fs/9p/vfs_file.c | 4 ++--
fs/affs/file.c | 2 +-
fs/afs/write.c | 2 +-
fs/cifs/file.c | 4 ++--
fs/ecryptfs/file.c | 2 +-
fs/exofs/file.c | 2 +-
fs/f2fs/file.c | 2 +-
fs/fuse/file.c | 6 +++---
fs/gfs2/file.c | 6 ++++--
fs/hfs/inode.c | 2 +-
fs/hfsplus/inode.c | 2 +-
fs/hostfs/hostfs_kern.c | 2 +-
fs/hpfs/file.c | 2 +-
fs/jffs2/file.c | 2 +-
fs/jfs/file.c | 2 +-
fs/ncpfs/file.c | 2 +-
fs/ntfs/dir.c | 2 +-
fs/ntfs/file.c | 2 +-
fs/ocfs2/file.c | 2 +-
fs/reiserfs/dir.c | 2 +-
fs/reiserfs/file.c | 2 +-
fs/sync.c | 4 ++--
fs/ubifs/file.c | 2 +-
include/linux/errseq.h | 14 ++++----------
include/linux/fs.h | 20 +++++++++++++++----
lib/errseq.c | 17 +++++++----------
mm/filemap.c | 64 ++++++++++++++++++++++++++++++-------------------------------
31 files changed, 241 insertions(+), 89 deletions(-)
create mode 100644 Documentation/errseq.rst
--
Jeff Layton <jlayton@redhat.com>
reply other threads:[~2017-09-05 11:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1504611573.4728.23.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=bfields@fieldses.org \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox