diff options
| author | Dave Chinner <dchinner@redhat.com> | 2016-05-18 13:53:42 +1000 |
|---|---|---|
| committer | Willy Tarreau <w@1wt.eu> | 2016-08-22 07:28:57 +0200 |
| commit | 01ee4801e26c15e5bf3d0a9b563d125bbbd2ed66 (patch) | |
| tree | 70b849aee4bae44fc1d782a44f651cc314d44766 /fs/xfs/xfs_trace.c | |
| parent | 0ed4547f527c1410ff2a35af766ce5c3a29405c4 (diff) | |
| download | lwn-01ee4801e26c15e5bf3d0a9b563d125bbbd2ed66.tar.gz lwn-01ee4801e26c15e5bf3d0a9b563d125bbbd2ed66.zip | |
xfs: xfs_iflush_cluster fails to abort on error
commit b1438f477934f5a4d5a44df26f3079a7575d5946 upstream.
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.
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[wt: in kernels < 3.17, the error sign is positive, not negative]
Signed-off-by: Willy Tarreau <w@1wt.eu>
Diffstat (limited to 'fs/xfs/xfs_trace.c')
0 files changed, 0 insertions, 0 deletions