diff options
| author | Dave Chinner <dchinner@redhat.com> | 2016-05-18 13:53:42 +1000 |
|---|---|---|
| committer | Dave Chinner <david@fromorbit.com> | 2016-05-18 13:53:42 +1000 |
| commit | b1438f477934f5a4d5a44df26f3079a7575d5946 (patch) | |
| tree | 5eab8bfb381b7a9b20b95a099ebb9fbde917a65e /fs/xfs/xfs_icache.h | |
| parent | 8179c03629de67f515d3ab825b5a9428687d4b85 (diff) | |
| download | linux-b1438f477934f5a4d5a44df26f3079a7575d5946.tar.gz linux-b1438f477934f5a4d5a44df26f3079a7575d5946.tar.bz2 linux-b1438f477934f5a4d5a44df26f3079a7575d5946.zip | |
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/xfs/xfs_icache.h')
0 files changed, 0 insertions, 0 deletions