diff options
| author |   Josef Bacik <jbacik@fusionio.com> | 2013-07-11 10:34:59 -0400 |
|---|---|---|
| committer |   Chris Mason <chris.mason@fusionio.com> | 2013-08-09 19:30:09 -0400 |
| commit | ee20a98314e52a6675e94d1a07ca205ffdf09a72 (patch) | |
| tree | 7a4b93b7c6b3603795a36464944d8c479806e41c /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | Btrfs: make sure the backref walker catches all refs to our extent (diff) | |
| download | wireguard-linux-ee20a98314e52a6675e94d1a07ca205ffdf09a72.tar.xz wireguard-linux-ee20a98314e52a6675e94d1a07ca205ffdf09a72.zip | |
Btrfs: allow splitting of hole em's when dropping extent cache
I noticed while running multi-threaded fsync tests that sometimes fsck would
complain about an improper gap. This happens because we fail to add a hole
extent to the file, which was happening when we'd split a hole EM because
btrfs_drop_extent_cache was just discarding the whole em instead of splitting
it. So this patch fixes this by allowing us to split a hole em properly, which
means that added holes actually get logged properly and we no longer see this
fsck error. Thankfully we're tolerant of these sort of problems so a user would
not see any adverse effects of this bug, other than fsck complaining. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions