This is a note to let you know that I've just added the patch titled
xfs: skip stale inodes in xfs_iflush_cluster
to the 4.6-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
xfs-skip-stale-inodes-in-xfs_iflush_cluster.patch
and it can be found in the queue-4.6 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 7d3aa7fe970791f1a674b14572a411accf2f4d4e Mon Sep 17 00:00:00 2001
From: Dave Chinner <dchinner@xxxxxxxxxx>
Date: Wed, 18 May 2016 13:54:23 +1000
Subject: xfs: skip stale inodes in xfs_iflush_cluster
From: Dave Chinner <dchinner@xxxxxxxxxx>
commit 7d3aa7fe970791f1a674b14572a411accf2f4d4e upstream.
We don't write back stale inodes so we should skip them in
xfs_iflush_cluster, too.
Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx>
Reviewed-by: Brian Foster <bfoster@xxxxxxxxxx>
Reviewed-by: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Dave Chinner <david@xxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
fs/xfs/xfs_inode.c | 1 +
1 file changed, 1 insertion(+)
--- a/fs/xfs/xfs_inode.c
+++ b/fs/xfs/xfs_inode.c
@@ -3207,6 +3207,7 @@ xfs_iflush_cluster(
*/
spin_lock(&iq->i_flags_lock);
if (!iq->i_ino ||
+ __xfs_iflags_test(iq, XFS_ISTALE) ||
(XFS_INO_TO_AGINO(mp, iq->i_ino) & mask) != first_index) {
spin_unlock(&iq->i_flags_lock);
continue;
Patches currently in stable-queue which might be from dchinner@xxxxxxxxxx are
queue-4.6/xfs-xfs_iflush_cluster-fails-to-abort-on-error.patch
queue-4.6/xfs-disallow-rw-remount-on-fs-with-unknown-ro-compat-features.patch
queue-4.6/xfs-fix-inode-validity-check-in-xfs_iflush_cluster.patch
queue-4.6/xfs-skip-stale-inodes-in-xfs_iflush_cluster.patch
queue-4.6/xfs-remove-xfs_fs_evict_inode.patch
queue-4.6/xfs-don-t-wrap-growfs-agfl-indexes.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html