WARNING in mark_buffer

Title	Replies (including bot)	Last reply
WARNING in mark_buffer_dirty (3)	0 (1)	2021/02/14 16:48

Title

Replies (including bot)

Last reply

0 (1)

2021/02/14 16:48

Kernel	Title	Rank 🛈	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
linux-4.19	WARNING in mark_buffer_dirty bfs	-1	C		error	10	1150d	1496d	0/1	upstream: reported C repro on 2022/01/20 22:23
upstream	WARNING in mark_buffer_dirty (6) fs	-1	C	error		11669	294d	861d	28/29	fixed on 2025/05/06 15:33
upstream	WARNING in mark_buffer_dirty (4) bfs nilfs	-1	C	inconclusive		1152	992d	1331d	22/29	fixed on 2023/06/08 14:41
android-44	WARNING in mark_buffer_dirty	-1				2	2610d	2508d	0/2	auto-closed as invalid on 2019/07/01 11:44
upstream	WARNING in mark_buffer_dirty fs	-1	C			21	2640d	3022d	0/29	closed as invalid on 2019/07/24 04:22
linux-4.14	WARNING in mark_buffer_dirty (2) nilfs2	-1	C		error	8	1092d	1475d	0/1	upstream: reported C repro on 2022/02/10 08:17
upstream	WARNING in mark_buffer_dirty (2) ext4	-1				665	2142d	2274d	0/29	auto-closed as invalid on 2020/07/14 01:44
linux-6.6	WARNING in mark_buffer_dirty origin:lts-only	-1	C		inconclusive	382	6d23h	227d	0/2	upstream: reported C repro on 2025/07/12 17:25
upstream	WARNING in mark_buffer_dirty (5) nilfs	-1	C	done		172	869d	988d	23/29	fixed on 2023/10/12 12:48
upstream	WARNING in mark_buffer_dirty (7) bfs hfs	-1	C	error		958	2h49m	290d	0/29	upstream: reported C repro on 2025/05/10 17:11
android-49	WARNING in mark_buffer_dirty	-1				7	2456d	2508d	0/3	auto-closed as invalid on 2019/10/25 08:47
linux-4.14	WARNING in mark_buffer_dirty	-1				1	2235d	2235d	0/1	auto-closed as invalid on 2020/05/11 07:45
linux-5.15	WARNING in mark_buffer_dirty origin:upstream	-1	C		error	300	7d16h	1077d	0/3	upstream: reported C repro on 2023/03/15 22:22
linux-6.1	WARNING in mark_buffer_dirty origin:lts-only	-1	C		inconclusive	371	11d	1079d	0/3	upstream: reported C repro on 2023/03/13 14:09

------------[ cut here ]------------ WARNING: CPU: 1 PID: 4954 at fs/buffer.c:1113 mark_buffer_dirty+0x488/0x5d0 fs/buffer.c:1113 Modules linked in: CPU: 1 PID: 4954 Comm: jbd2/sda1-8 Not tainted 5.11.0-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 RIP: 0010:mark_buffer_dirty+0x488/0x5d0 fs/buffer.c:1113 Code: c1 ea 03 80 3c 02 00 0f 85 52 01 00 00 48 8b 3b be 04 00 00 00 e8 28 ad fc ff 5b 5d 41 5c 41 5d e9 7d 46 a1 ff e8 78 46 a1 ff <0f> 0b e9 bf fb ff ff e8 6c 46 a1 ff 0f 0b e9 e3 fb ff ff e8 60 46 RSP: 0000:ffffc9000d36fa20 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff888043731040 RCX: 0000000000000000 RDX: ffff88801b2fa240 RSI: ffffffff81d21348 RDI: 0000000000000003 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff81d20f05 R11: 0000000000000000 R12: ffff888043731040 R13: ffff888027e96380 R14: ffff88801ffa65a0 R15: ffff88801ffea960 FS: 0000000000000000(0000) GS:ffff88802cb00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000be5000 CR3: 0000000012c36000 CR4: 0000000000150ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: __jbd2_journal_temp_unlink_buffer+0x3ba/0x500 fs/jbd2/transaction.c:2021 __jbd2_journal_unfile_buffer+0x60/0xb0 fs/jbd2/transaction.c:2035 __jbd2_journal_refile_buffer+0x3d2/0x4a0 fs/jbd2/transaction.c:2581 jbd2_journal_commit_transaction+0x440d/0x6ba0 fs/jbd2/commit.c:1084 kjournald2+0x1d0/0x930 fs/jbd2/journal.c:213 kthread+0x3b1/0x4a0 kernel/kthread.c:292 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

Crashes (2):
Time	Kernel	Commit	Syzkaller	Config	Log	Report	Syz repro	C repro	VM info	Assets (help?)	Manager	Title
2021/02/27 09:00	upstream	3fb6d0e00efc	4c37c133	.config	console log	report			info		ci-qemu-upstream	WARNING in mark_buffer_dirty
2021/02/10 16:37	upstream	e0756cfc7d7c	9c8b8541	.config	console log	report			info		ci-qemu-upstream	WARNING in mark_buffer_dirty

Crashes (2):

Assets (help?)