linux-ext4 - Re: [syzbot] [ext4?] [jffs2?] [xfs?] kernel BUG in unrefer_xattr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Wed, 10 Apr 2024 07:29:47 +1000
From: Dave Chinner <david@...morbit.com>
To: syzbot <syzbot+b417f0468b73945887f0@...kaller.appspotmail.com>
Cc: chandan.babu@...cle.com, dwmw2@...radead.org,
	linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org,
	linux-xfs@...r.kernel.org, richard@....at,
	syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [ext4?] [jffs2?] [xfs?] kernel BUG in
 unrefer_xattr_datum

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://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> console output: https://syzkaller.appspot.com/x/log.txt?x=1562c52d180000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=caeac3f3565b057a
> dashboard link: https://syzkaller.appspot.com/bug?extid=b417f0468b73945887f0
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: arm64
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14e74805180000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1613cca9180000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/6cad68bf7532/disk-707081b6.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/1a27e5400778/vmlinux-707081b6.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/67dfc53755d0/Image-707081b6.gz.xz
> mounted in repro #1: https://storage.googleapis.com/syzbot-assets/f039597bec42/mount_0.gz
> mounted in repro #2: https://storage.googleapis.com/syzbot-assets/b3fe5cff7c96/mount_4.gz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+b417f0468b73945887f0@...kaller.appspotmail.com
> 
> 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
david@...morbit.com