summaryrefslogtreecommitdiff
path: root/fs/jbd2
diff options
context:
space:
mode:
authorDave Chinner <dchinner@redhat.com>2016-05-18 06:53:42 +0300
committerDave Chinner <david@fromorbit.com>2016-05-18 06:53:42 +0300
commitb1438f477934f5a4d5a44df26f3079a7575d5946 (patch)
tree5eab8bfb381b7a9b20b95a099ebb9fbde917a65e /fs/jbd2
parent8179c03629de67f515d3ab825b5a9428687d4b85 (diff)
downloadlinux-b1438f477934f5a4d5a44df26f3079a7575d5946.tar.xz
xfs: xfs_iflush_cluster fails to abort on error
When a failure due to an inode buffer occurs, the error handling fails to abort the inode writeback correctly. This can result in the inode being reclaimed whilst still in the AIL, leading to use-after-free situations as well as filesystems that cannot be unmounted as the inode log items left in the AIL never get removed. Fix this by ensuring fatal errors from xfs_imap_to_bp() result in the inode flush being aborted correctly. cc: <stable@vger.kernel.org> # 3.10.x- Reported-by: Shyam Kaushik <shyam@zadarastorage.com> Diagnosed-by: Shyam Kaushik <shyam@zadarastorage.com> Tested-by: Shyam Kaushik <shyam@zadarastorage.com> Signed-off-by: Dave Chinner <dchinner@redhat.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'fs/jbd2')
0 files changed, 0 insertions, 0 deletions