From: Dan Williams <dan.j.williams@intel.com> To: xfs@oss.sgi.com Cc: linux-block@vger.kernel.org, linux-nvdimm@lists.01.org, Dave Chinner <david@fromorbit.com>, Jens Axboe <axboe@fb.com>, linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.com>, Tejun Heo <tj@kernel.org>, Matthew Wilcox <willy@linux.intel.com>, Ross Zwisler <ross.zwisler@linux.intel.com> Subject: [resend PATCH 0/3] fs, bdev: handle end of life Date: Mon, 04 Jan 2016 10:20:00 -0800 [thread overview] Message-ID: <20160104181220.24118.96661.stgit@dwillia2-desk3.amr.corp.intel.com> (raw) Per Dave, resend to include the xfs list on the full set. These are against v4.4-rc5. --- As mentioned in [PATCH 1/3] "block, fs: reliably communicate bdev end-of-life", historically we have waited for filesystem specific heuristics to attempt to guess when a block device is gone. Sometimes this works, but in other cases the system can hang waiting for the fs to trigger its shutdown protocol. Now with DAX we need new actions, like unmapping all inodes, to be taken upon a shutdown event. Those actions need to be taken whether the shutdown event comes from the block device being torn down, or some other file system specific event. For now, the approach taken in the following patches only affects xfs and block drivers that are converted to use del_gendisk_queue(). We can add more filesystems and driver support over time. Note that 'bdi_gone' was chosen over 'shutdown' so as not to be confused with generic_shutdown_super() --- Dan Williams (3): block, fs: reliably communicate bdev end-of-life xfs: handle shutdown notifications writeback: fix false positive WARN in __mark_inode_dirty block/genhd.c | 87 +++++++++++++++++++++++++++++++++++------- drivers/block/brd.c | 3 - drivers/nvdimm/pmem.c | 3 - drivers/s390/block/dcssblk.c | 6 +-- fs/block_dev.c | 79 +++++++++++++++++++++++++++++++++----- fs/xfs/xfs_super.c | 9 ++++ include/linux/fs.h | 4 ++ include/linux/genhd.h | 1 mm/backing-dev.c | 7 +++ 9 files changed, 166 insertions(+), 33 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com> To: xfs@oss.sgi.com Cc: Jens Axboe <axboe@fb.com>, linux-nvdimm@lists.01.org, linux-block@vger.kernel.org, Tejun Heo <tj@kernel.org>, Jan Kara <jack@suse.com>, linux-fsdevel@vger.kernel.org, Matthew Wilcox <willy@linux.intel.com>, Ross Zwisler <ross.zwisler@linux.intel.com> Subject: [resend PATCH 0/3] fs, bdev: handle end of life Date: Mon, 04 Jan 2016 10:20:00 -0800 [thread overview] Message-ID: <20160104181220.24118.96661.stgit@dwillia2-desk3.amr.corp.intel.com> (raw) Per Dave, resend to include the xfs list on the full set. These are against v4.4-rc5. --- As mentioned in [PATCH 1/3] "block, fs: reliably communicate bdev end-of-life", historically we have waited for filesystem specific heuristics to attempt to guess when a block device is gone. Sometimes this works, but in other cases the system can hang waiting for the fs to trigger its shutdown protocol. Now with DAX we need new actions, like unmapping all inodes, to be taken upon a shutdown event. Those actions need to be taken whether the shutdown event comes from the block device being torn down, or some other file system specific event. For now, the approach taken in the following patches only affects xfs and block drivers that are converted to use del_gendisk_queue(). We can add more filesystems and driver support over time. Note that 'bdi_gone' was chosen over 'shutdown' so as not to be confused with generic_shutdown_super() --- Dan Williams (3): block, fs: reliably communicate bdev end-of-life xfs: handle shutdown notifications writeback: fix false positive WARN in __mark_inode_dirty block/genhd.c | 87 +++++++++++++++++++++++++++++++++++------- drivers/block/brd.c | 3 - drivers/nvdimm/pmem.c | 3 - drivers/s390/block/dcssblk.c | 6 +-- fs/block_dev.c | 79 +++++++++++++++++++++++++++++++++----- fs/xfs/xfs_super.c | 9 ++++ include/linux/fs.h | 4 ++ include/linux/genhd.h | 1 mm/backing-dev.c | 7 +++ 9 files changed, 166 insertions(+), 33 deletions(-) _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-01-04 18:20 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-01-04 18:20 Dan Williams [this message] 2016-01-04 18:20 ` [resend PATCH 0/3] fs, bdev: handle end of life Dan Williams 2016-01-04 18:20 ` [resend PATCH 1/3] block, fs: reliably communicate bdev end-of-life Dan Williams 2016-01-04 18:20 ` Dan Williams 2016-01-05 3:51 ` Dave Chinner 2016-01-05 3:51 ` Dave Chinner 2016-01-05 4:25 ` Dan Williams 2016-01-05 4:25 ` Dan Williams 2016-01-05 22:32 ` Dave Chinner 2016-01-05 22:32 ` Dave Chinner 2016-01-09 7:54 ` Al Viro 2016-01-09 7:54 ` Al Viro 2016-01-09 14:17 ` Dan Williams 2016-01-09 14:17 ` Dan Williams 2016-01-11 7:15 ` Hannes Reinecke 2016-01-11 7:15 ` Hannes Reinecke 2016-01-11 15:24 ` Hannes Reinecke 2016-01-11 15:24 ` Hannes Reinecke 2016-01-11 15:55 ` Dan Williams 2016-01-11 15:55 ` Dan Williams 2016-01-04 18:20 ` [resend PATCH 2/3] xfs: handle shutdown notifications Dan Williams 2016-01-04 18:20 ` Dan Williams 2016-01-05 4:03 ` Dave Chinner 2016-01-05 4:03 ` Dave Chinner 2016-01-04 18:20 ` [resend PATCH 3/3] writeback: fix false positive WARN in __mark_inode_dirty Dan Williams 2016-01-04 18:20 ` Dan Williams 2016-01-05 4:23 ` Dave Chinner 2016-01-05 4:23 ` Dave Chinner 2016-01-05 19:59 ` Dan Williams 2016-01-05 19:59 ` Dan Williams 2016-01-05 21:10 ` Dave Chinner 2016-01-05 21:10 ` Dave Chinner 2016-01-05 21:29 ` Dan Williams 2016-01-05 21:29 ` Dan Williams
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=20160104181220.24118.96661.stgit@dwillia2-desk3.amr.corp.intel.com \ --to=dan.j.williams@intel.com \ --cc=axboe@fb.com \ --cc=david@fromorbit.com \ --cc=jack@suse.com \ --cc=linux-block@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-nvdimm@lists.01.org \ --cc=ross.zwisler@linux.intel.com \ --cc=tj@kernel.org \ --cc=willy@linux.intel.com \ --cc=xfs@oss.sgi.com \ /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.