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
| ||
|
Message-ID: <20240904111415.eo22zmhpggdavlzj@quack3> Date: Wed, 4 Sep 2024 13:14:15 +0200 From: Jan Kara <jack@...e.cz> To: syzbot <syzbot+c28d8da3e83b3cc68dc6@...kaller.appspotmail.com> Cc: jack@...e.cz, jack@...e.com, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com, tytso@....edu Subject: Re: [syzbot] [ext4?] kernel BUG in jbd2_journal_dirty_metadata On Wed 04-09-24 04:06:50, syzbot wrote: > > On Tue 03-09-24 21:50:20, syzbot wrote: > >> syzbot found the following issue on: > >> > >> HEAD commit: fb24560f31f9 Merge tag 'lsm-pr-20240830' of git://git.kern.. > >> git tree: upstream > >> console output: https://syzkaller.appspot.com/x/log.txt?x=1739530b980000 > >> kernel config: https://syzkaller.appspot.com/x/.config?x=996585887acdadb3 > >> dashboard link: https://syzkaller.appspot.com/bug?extid=c28d8da3e83b3cc68dc6 > >> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 > >> > >> Unfortunately, I don't have any reproducer for this issue yet. > >> > >> Downloadable assets: > >> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-fb24560f.raw.xz > >> vmlinux: https://storage.googleapis.com/syzbot-assets/2d39db26a2bc/vmlinux-fb24560f.xz > >> kernel image: https://storage.googleapis.com/syzbot-assets/8910481ae16e/bzImage-fb24560f.xz > >> > >> IMPORTANT: if you fix the issue, please add the following tag to the commit: > >> Reported-by: syzbot+c28d8da3e83b3cc68dc6@...kaller.appspotmail.com > >> > >> loop0: detected capacity change from 0 to 32768 > >> ======================================================= > >> WARNING: The mand mount option has been deprecated and > >> and is ignored by this kernel. Remove the mand > >> option from the mount to silence this warning. > >> ======================================================= > >> ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode. > >> loop0: detected capacity change from 32768 to 0 > >> syz.0.0: attempt to access beyond end of device > >> loop0: rw=0, sector=10576, nr_sectors = 1 limit=0 > >> (syz.0.0,5108,0):__ocfs2_xattr_set_value_outside:1385 ERROR: status = -5 > > > > Looks like ocfs2 issue, not ext4. > > > > #syz set ocfs2 #syz set subsystems: ocfs2 Honza -- Jan Kara <jack@...e.com> SUSE Labs, CR
Powered by blists - more mailing lists