aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorLiu Bo <bo.li.liu@oracle.com>2013-04-16 09:20:28 +0000
committerJosef Bacik <jbacik@fusionio.com>2013-05-06 15:54:55 -0400
commit0abd5b17249ea5ca49a3a9ad4285cac3dfa8c30b (patch)
tree26b1399cc7b83ddabd2427d283a5a39a1dd878c5 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentBtrfs: fix reada debug code compilation (diff)
downloadwireguard-linux-0abd5b17249ea5ca49a3a9ad4285cac3dfa8c30b.tar.xz
wireguard-linux-0abd5b17249ea5ca49a3a9ad4285cac3dfa8c30b.zip
Btrfs: return error when we specify wrong start to defrag
We need such a sanity check for wrong start when we defrag a file, otherwise, even with a wrong start that's larger than file size, we can end up changing not only inode's force compress flag but also FS's incompat flags. Signed-off-by: Liu Bo <bo.li.liu@oracle.com> Reviewed-by: David Sterba <dsterba@suse.cz> Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions