diff options
| author |   Daeho Jeong <daeho.jeong@samsung.com> | 2016-02-21 18:31:41 -0500 |
|---|---|---|
| committer |   Theodore Ts'o <tytso@mit.edu> | 2016-02-21 18:31:41 -0500 |
| commit | f96c450dabf5497794af8c45f589d44b4549d1fc (patch) | |
| tree | aeeeb84bc86dbf70fc392539c0f955fae2c6a486 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | ext4: fix crashes in dioread_nolock mode (diff) | |
| download | wireguard-linux-f96c450dabf5497794af8c45f589d44b4549d1fc.tar.xz wireguard-linux-f96c450dabf5497794af8c45f589d44b4549d1fc.zip | |
ext4: make sure to revoke all the freeable blocks in ext4_free_blocks
Now, ext4_free_blocks() doesn't revoke data blocks of per-file data
journalled inode and it can cause file data inconsistency problems.
Even though data blocks of per-file data journalled inode are already
forgotten by jbd2_journal_invalidatepage() in advance of invoking
ext4_free_blocks(), we still need to revoke the data blocks here.
Moreover some of the metadata blocks, which are not found by
sb_find_get_block(), are still needed to be revoked, but this is also
missing here.
Signed-off-by: Daeho Jeong <daeho.jeong@samsung.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reviewed-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions