diff options
| author | Theodore Ts'o <tytso@mit.edu> | 2023-06-08 10:06:40 -0400 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2023-06-08 10:06:40 -0400 |
| commit | dea9d8f7643fab07bf89a1155f1f94f37d096a5e (patch) | |
| tree | 9b8efb75f3ffe7a7c22100b0b2d46527ed256a0a | |
| parent | 1b29243933098cdbc31b579b5616e183b4275e2f (diff) | |
| download | perf-tools-dea9d8f7643fab07bf89a1155f1f94f37d096a5e.tar.gz | |
ext4: only check dquot_initialize_needed() when debugging
ext4_xattr_block_set() relies on its caller to call dquot_initialize()
on the inode. To assure that this has happened there are WARN_ON
checks. Unfortunately, this is subject to false positives if there is
an antagonist thread which is flipping the file system at high rates
between r/o and rw. So only do the check if EXT4_XATTR_DEBUG is
enabled.
Link: https://lore.kernel.org/r/20230608044056.GA1418535@mit.edu
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
| -rw-r--r-- | fs/ext4/xattr.c | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/fs/ext4/xattr.c b/fs/ext4/xattr.c index 13d7f17a9c8cc..321e3a888c20b 100644 --- a/fs/ext4/xattr.c +++ b/fs/ext4/xattr.c @@ -2056,8 +2056,9 @@ inserted: else { u32 ref; +#ifdef EXT4_XATTR_DEBUG WARN_ON_ONCE(dquot_initialize_needed(inode)); - +#endif /* The old block is released after updating the inode. */ error = dquot_alloc_block(inode, @@ -2120,8 +2121,9 @@ inserted: /* We need to allocate a new block */ ext4_fsblk_t goal, block; +#ifdef EXT4_XATTR_DEBUG WARN_ON_ONCE(dquot_initialize_needed(inode)); - +#endif goal = ext4_group_first_block_no(sb, EXT4_I(inode)->i_block_group); block = ext4_new_meta_blocks(handle, inode, goal, 0, |