xfs: ensure buffer types are set correctly
authorDave Chinner <dchinner@redhat.com>
Wed, 21 Jan 2015 22:29:05 +0000 (09:29 +1100)
committerDave Chinner <david@fromorbit.com>
Wed, 21 Jan 2015 22:29:05 +0000 (09:29 +1100)
commit0d612fb570b71ea2e49554a770cff4c489018b2c
tree65d2a976802155e9de2c33b271a1e590c78022d8
parent97bf6af1f928216fd6c5a66e8a57bfa95a659672
xfs: ensure buffer types are set correctly

Jan Kara reported that log recovery was finding buffers with invalid
types in them. This should not happen, and indicates a bug in the
logging of buffers. To catch this, add asserts to the buffer
formatting code to ensure that the buffer type is in range when the
transaction is committed.

We don't set a type on buffers being marked stale - they are not
going to get replayed, the format item exists only for recovery to
be able to prevent replay of the buffer, so the type does not
matter. Hence that needs special casing here.

cc: <stable@vger.kernel.org> # 3.10 to current
Reported-by: Jan Kara <jack@suse.cz>
Tested-by: Jan Kara <jack@suse.cz>
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/xfs_buf_item.c
This page took 0.027758 seconds and 5 git commands to generate.