Re: [PATCH v3 0/9] btrfs: check name_len before read name

2017-06-16 Thread Su Yue
On 06/15/2017 11:57 PM, David Sterba wrote: On Tue, Jun 06, 2017 at 05:56:59PM +0800, Su Yue wrote: When reading out name from inode_ref, dir_item, it's possible that corrupted name_len leads to read beyond boundary. Since there are already patches for btrfs-progs, this patchset is for btrfs.

Re: [PATCH v3 0/9] btrfs: check name_len before read name

2017-06-15 Thread David Sterba
On Tue, Jun 06, 2017 at 05:56:59PM +0800, Su Yue wrote: > When reading out name from inode_ref, dir_item, it's possible that > corrupted name_len leads to read beyond boundary. > Since there are already patches for btrfs-progs, this patchset is > for btrfs. > > Introduce 'btrfs_is_name_len_valid'

Re: [PATCH v3 0/9] btrfs: check name_len before read name

2017-06-06 Thread David Sterba
On Tue, Jun 06, 2017 at 05:56:59PM +0800, Su Yue wrote: > When reading out name from inode_ref, dir_item, it's possible that > corrupted name_len leads to read beyond boundary. > Since there are already patches for btrfs-progs, this patchset is > for btrfs. > > Introduce 'btrfs_is_name_len_valid'

[PATCH v3 0/9] btrfs: check name_len before read name

2017-06-06 Thread Su Yue
When reading out name from inode_ref, dir_item, it's possible that corrupted name_len leads to read beyond boundary. Since there are already patches for btrfs-progs, this patchset is for btrfs. Introduce 'btrfs_is_name_len_valid' to make check name_len with item boundary. If read name from