diff options
| author | Filipe David Borba Manana <[email protected]> | 2013-09-16 08:53:28 +0000 |
|---|---|---|
| committer | Chris Mason <[email protected]> | 2013-11-12 02:49:51 +0000 |
| commit | f06becc4119856c984e3beef54aa75538e656c6d (patch) | |
| tree | be4cb96d6cec6bccf8c17117e74cb14a0328fddb /fs/btrfs/tests/extent-buffer-tests.c | |
| parent | Btrfs: eliminate the exceptional root_tree refs=0 (diff) | |
| download | kernel-f06becc4119856c984e3beef54aa75538e656c6d.tar.gz kernel-f06becc4119856c984e3beef54aa75538e656c6d.zip | |
Btrfs: don't store NULL byte in symlink extents
It is not necessary to store the NULL byte in a symlink inline file
extent. There's currently no code that requires the NULL byte to be
present in the extent. This change also doesn't break file format
compatibility nor the send/receive feature.
The VFS also doesn't need the NULL byte to be present in the extent,
as it reads up to inode->i_size bytes (which already excluded the NULL
byte) and sets the NULL byte for us (in fs/namei.c:page_getlink()).
So with this change we save 1 byte per symlink file extent (which is
always inlined in the btree leaf) without losing backward and forward
compatibility.
Signed-off-by: Filipe David Borba Manana <[email protected]>
Signed-off-by: Josef Bacik <[email protected]>
Signed-off-by: Chris Mason <[email protected]>
Diffstat (limited to 'fs/btrfs/tests/extent-buffer-tests.c')
0 files changed, 0 insertions, 0 deletions