summaryrefslogtreecommitdiffstats
path: root/fs/xfs/xfs_clnt.h
diff options
context:
space:
mode:
authorDavid Chinner <david@fromorbit.com>2008-10-30 17:40:09 +1100
committerLachlan McIlroy <lachlan@sgi.com>2008-10-30 17:40:09 +1100
commit5a792c4579af8466246408e38fd4eff45d8493b8 (patch)
tree33b9d578dc42fe47bf8fff9ca60326cf9a22bef0 /fs/xfs/xfs_clnt.h
parent783a2f656f9674c31d4019708a94af93fa1d1c22 (diff)
downloadop-kernel-dev-5a792c4579af8466246408e38fd4eff45d8493b8.zip
op-kernel-dev-5a792c4579af8466246408e38fd4eff45d8493b8.tar.gz
[XFS] XFS: Check for valid transaction headers in recovery
When we are about to add a new item to a transaction in recovery, we need to check that it is valid first. Currently we just assert that header magic number matches, but in production systems that is not present and we add a corrupted transaction to the list to be processed. This results in a kernel oops later when processing the corrupted transaction. Instead, if we detect a corrupted transaction, abort recovery and leave the user to clean up the mess that has occurred. SGI-PV: 988145 SGI-Modid: xfs-linux-melb:xfs-kern:32356a Signed-off-by: David Chinner <david@fromorbit.com> Signed-off-by: Tim Shimmin <tes@sgi.com> Signed-off-by: Eric Sandeen <sandeen@sandeen.net> Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
Diffstat (limited to 'fs/xfs/xfs_clnt.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud