Re: [syzbot] [sysv?] [vfs?] WARNING in invalidate_bh_lru

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

To: syzbot <syzbot+9743a41f74f00e50fc77@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [syzbot] [sysv?] [vfs?] WARNING in invalidate_bh_lru
From: "Theodore Ts'o" <tytso@xxxxxxx>
Date: Sun, 30 Apr 2023 12:12:49 -0400
Cc: hch@xxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, syzkaller-bugs@xxxxxxxxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx
In-reply-to: <ZE4NVo6rTOeGQdK+@mit.edu>

#syz set subsystems: udf

There are two reproducers, one that mounts a sysv file system, and the
other which mounts a udf file system.  There is no mention of ext4 in
the stack trace, and yet syzbot has assigned this to the ext4
subsystem for some unknown reason.

					- Ted

References:
- [syzbot] [sysv?] [vfs?] WARNING in invalidate_bh_lru
  - From: syzbot
- Re: [syzbot] [sysv?] [vfs?] WARNING in invalidate_bh_lru
  - From: Theodore Ts'o

Prev by Date: Re: [syzbot] [fs?] INFO: task hung in eventpoll_release_file
Next by Date: [PATCH] nilfs2: fix infinite loop in nilfs_mdt_get_block()
Previous by thread: Re: [syzbot] [sysv?] [vfs?] WARNING in invalidate_bh_lru
Next by thread: Re: [syzbot] [sysv?] [vfs?] WARNING in invalidate_bh_lru
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux