| commit | f983710758218c7aad4aae3e40a7312a21d6f55a | |
| author | Dave Chinner <dchinner@redhat.com> | |
| Wed, 14 Apr 2010 05:47:55 +0000 (14 15:47 +1000) | ||
| committer | Alex Elder <aelder@sgi.com> | |
| Wed, 19 May 2010 14:58:13 +0000 (19 09:58 -0500) | ||
| tree | c4647b60e06338c730ebaf0d65ed696cce5e1e68 | treesnapshot (tar.gz zip) |
| parent | 36adecff50b69df0369cc2022650c6087aeb255f | commitdiff |
xfs: make the log ticket transaction id random
The transaction ID that is written to the log for a transaction is
currently set by taking the lower 32 bits of the memory address of
the ticket structure. This is not guaranteed to be unique as
tickets comes from a slab and slots can be reallocated immediately
after being freed. As a result, there is no guarantee of uniqueness
in the ticket ID value.
Fix this by assigning a random number to the ticket ID field so that
it is extremely unlikely that duplicates will occur and remove the
possibility of transactions being mixed up during recovery due to
duplicate IDs.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
The transaction ID that is written to the log for a transaction is
currently set by taking the lower 32 bits of the memory address of
the ticket structure. This is not guaranteed to be unique as
tickets comes from a slab and slots can be reallocated immediately
after being freed. As a result, there is no guarantee of uniqueness
in the ticket ID value.
Fix this by assigning a random number to the ticket ID field so that
it is extremely unlikely that duplicates will occur and remove the
possibility of transactions being mixed up during recovery due to
duplicate IDs.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
| fs/xfs/xfs_log.c | diffblobblamehistory |