Thanks to the folks at bigstorage and to Willi Langenberger for
pointing this one out. In some circumstances the code that finds
the log head could end up getting an uninitialized block number for
the log head, leading to all sorts of interesting behavior...
Date: Wed May 15 14:23:31 PDT 2002
Workarea:
stout.americas.sgi.com:/localhome/src/sandeen/2.4.x-xfs/workarea-alwaysclean
The following file(s) were checked into:
bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs
Modid: xfs-cmds:slinx:119239a
cmd/xfsprogs/libxlog/xfs_log_recover.c - 1.6
- Return EIO from xlog_find_zeroed if xlog_find_verify_log_record
can't find the header. Otherwise the block number from
xlog_find_zeroed will be used uninitialized.
Modid: 2.4.x-xfs:slinx:119239b
linux/fs/xfs/xfs_log_recover.c - 1.227
- Return EIO from xlog_find_zeroed if xlog_find_verify_log_record
can't find the header. Otherwise the block number from
xlog_find_zeroed will be used uninitialized.
|