mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-16 17:23:55 +08:00
Btrfs: Don't allow written blocks from this transaction to be reallocated
When a block is freed, it can be immediately reused if it is from the current transaction. But, an extra check is required to make sure the block had not been written yet. If it were reused after being written, the transid in the block header might match the transid of the next time the block was allocated. The parent node records the transaction ID of the block it is pointing to, and this is used as part of validating the block on reads. So, there can only be one version of a block per transaction. Signed-off-by: Chris Mason <chris.mason@oracle.com>
This commit is contained in:
parent
611f0e00a2
commit
6bc34676c0
@ -1288,7 +1288,9 @@ static int pin_down_bytes(struct btrfs_root *root, u64 bytenr, u32 num_bytes,
|
||||
root->fs_info->running_transaction->transid;
|
||||
u64 header_transid =
|
||||
btrfs_header_generation(buf);
|
||||
if (header_transid == transid) {
|
||||
if (header_transid == transid &&
|
||||
!btrfs_header_flag(buf,
|
||||
BTRFS_HEADER_FLAG_WRITTEN)) {
|
||||
clean_tree_block(NULL, root, buf);
|
||||
free_extent_buffer(buf);
|
||||
return 1;
|
||||
|
Loading…
Reference in New Issue
Block a user