lkml.org 
[lkml]   [2021]   [May]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [syzbot] kernel BUG in assertfail
From
Date


On 31.05.21 г. 10:53, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 1434a312 Merge branch 'for-5.13-fixes' of git://git.kernel..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=162843f3d00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=9f3da44a01882e99
> dashboard link: https://syzkaller.appspot.com/bug?extid=a6bf271c02e4fe66b4e4
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+a6bf271c02e4fe66b4e4@syzkaller.appspotmail.com
>
> assertion failed: !memcmp(fs_info->fs_devices->fsid, fs_info->super_copy->fsid, BTRFS_FSID_SIZE), in fs/btrfs/disk-io.c:3282

This means a device contains a btrfs filesystem which has a different
FSID in its superblock than the fsid which all devices part of the same
fs_devices should have. This can happen in 2 ways - memory corruption
where either of the ->fsid member are corrupted or if there was a crash
while a filesystem's fsid was being changed. We need more context about
what the test did?

\
 
 \ /
  Last update: 2021-05-31 10:45    [W:0.056 / U:0.772 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site