Re: [syzbot] [ext4?] [jffs2?] [xfs?] kernel BUG in unrefer_xattr_datum

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Mon, Apr 08, 2024 at 09:04:18PM -0700, syzbot wrote:
> Hello,
> syzbot found the following issue on:
> HEAD commit:    707081b61156 Merge branch 'for-next/core', remote-tracking..
> git tree:       git:// for-kernelci
> console output:
> kernel config:
> dashboard link:
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: arm64
> syz repro:
> C reproducer:
> Downloadable assets:
> disk image:
> vmlinux:
> kernel image:
> mounted in repro #1:
> mounted in repro #2:
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+b417f0468b73945887f0@xxxxxxxxxxxxxxxxxxxxxxxxx
> jffs2: nextblock 0x0001d000, expected at 0001f000
> jffs2: argh. node added in wrong place at 0x0001e03c(2)
> jffs2: nextblock 0x0001d000, expected at 0001f000

Nothing to do with XFS or ext4 - they are simply being mounted with
invalid mount options at the same time.

#syz set subsystems: jffs2

Dave Chinner

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux