All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+0b74d367d6e80661d6df@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [v9fs?] WARNING in v9fs_begin_writeback
Date: Sun, 11 Aug 2024 03:43:03 -0700	[thread overview]
Message-ID: <000000000000804cad061f660ac2@google.com> (raw)
In-Reply-To: <tencent_8CEBCCA4E7D406EF12CD864A49942EFEEE06@qq.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in v9fs_begin_writeback

ino state: 393351, ino: 1901337, comm: kworker/u32:9, folio: ffffea0000b70480, netfs_writepages
ino: 1901337, v9fs_begin_writeback
------------[ cut here ]------------
folio expected an open fid inode->i_ino=1901337
WARNING: CPU: 0 PID: 1137 at fs/9p/vfs_addr.c:40 v9fs_begin_writeback+0x24c/0x2c0 fs/9p/vfs_addr.c:40
Modules linked in:
CPU: 0 UID: 0 PID: 1137 Comm: kworker/u32:9 Not tainted 6.11.0-rc1-syzkaller-00154-gc0ecd6388360-dirty #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: writeback wb_workfn (flush-9p-246)
RIP: 0010:v9fs_begin_writeback+0x24c/0x2c0 fs/9p/vfs_addr.c:40
Code: 00 fc ff df 48 8b 5b 48 48 8d 7b 40 48 89 fa 48 c1 ea 03 80 3c 02 00 75 7a 48 8b 73 40 48 c7 c7 e0 a2 8e 8b e8 15 3e 0d fe 90 <0f> 0b 90 90 eb 80 e8 39 27 a8 fe e9 6f ff ff ff e8 9f 26 a8 fe e9
RSP: 0018:ffffc90005b77478 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff88804550b9f0 RCX: ffffffff814cc379
RDX: ffff888022754880 RSI: ffffffff814cc386 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88804550b9f0
R13: dffffc0000000000 R14: ffffc90005b77840 R15: ffff88801b231958
FS:  0000000000000000(0000) GS:ffff88806b000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001000 CR3: 000000000db7c000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 netfs_writepages+0x6ee/0xec0 fs/netfs/write_issue.c:536
 do_writepages+0x1ae/0x940 mm/page-writeback.c:2683
 __writeback_single_inode+0x163/0xf90 fs/fs-writeback.c:1651
 writeback_sb_inodes+0x611/0x1150 fs/fs-writeback.c:1947
 wb_writeback+0x199/0xb50 fs/fs-writeback.c:2127
 wb_do_writeback fs/fs-writeback.c:2274 [inline]
 wb_workfn+0x28d/0xf40 fs/fs-writeback.c:2314
 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231
 process_scheduled_works kernel/workqueue.c:3312 [inline]
 worker_thread+0x6c8/0xf20 kernel/workqueue.c:3390
 kthread+0x2c1/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>


Tested on:

commit:         c0ecd638 Merge tag 'pci-v6.11-fixes-1' of git://git.ke..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=11288d7d980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8da8b059e43c5370
dashboard link: https://syzkaller.appspot.com/bug?extid=0b74d367d6e80661d6df
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=113ac96d980000


  reply	other threads:[~2024-08-11 10:43 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06  9:45 [syzbot] [v9fs?] WARNING in v9fs_begin_writeback syzbot
2024-08-06 11:35 ` Edward Adam Davis
2024-08-06 11:56   ` syzbot
2024-08-08 11:10 ` Edward Adam Davis
2024-08-08 11:24   ` syzbot
2024-08-08 11:44 ` Edward Adam Davis
2024-08-08 12:10   ` syzbot
2024-08-08 13:35 ` Edward Adam Davis
2024-08-08 13:56   ` syzbot
2024-08-08 15:02 ` Edward Adam Davis
2024-08-08 15:23   ` syzbot
2024-08-08 23:22 ` Edward Adam Davis
2024-08-08 23:43   ` syzbot
2024-08-09  1:44 ` [syzbot] " syzbot
2024-08-09  5:48 ` syzbot
2024-08-09  6:41 ` syzbot
2024-08-09  7:41 ` syzbot
2024-08-09  8:15 ` syzbot
2024-08-09  8:36 ` syzbot
2024-08-09  9:20 ` syzbot
2024-08-09 11:24 ` Edward Adam Davis
2024-08-09 11:36   ` syzbot
2024-08-09 12:05 ` Edward Adam Davis
2024-08-09 12:19   ` syzbot
2024-08-09 13:32 ` Edward Adam Davis
2024-08-09 13:53   ` syzbot
2024-08-09 14:52 ` Edward Adam Davis
2024-08-09 15:13   ` syzbot
2024-08-10  0:54 ` Edward Adam Davis
2024-08-10  1:21   ` syzbot
2024-08-10  2:56 ` Edward Adam Davis
2024-08-10  3:10   ` syzbot
2024-08-10  3:36 ` Edward Adam Davis
2024-08-10  4:02   ` syzbot
2024-08-10  4:53 ` Edward Adam Davis
2024-08-10  5:06   ` syzbot
2024-08-10  4:55 ` Edward Adam Davis
2024-08-10  5:29   ` syzbot
2024-08-11  4:49 ` Edward Adam Davis
2024-08-11  5:02   ` syzbot
2024-08-11  6:14 ` Edward Adam Davis
2024-08-11  6:35   ` syzbot
2024-08-11  8:42 ` Edward Adam Davis
2024-08-11  9:13   ` syzbot
2024-08-11 10:18 ` Edward Adam Davis
2024-08-11 10:43   ` syzbot [this message]
2024-08-11 11:57 ` Edward Adam Davis
2024-08-11 12:09   ` syzbot
2024-08-11 12:38 ` Edward Adam Davis
2024-08-11 13:04   ` syzbot
2024-08-11 14:05 ` Edward Adam Davis
2024-08-11 14:33   ` syzbot
2024-08-12 10:52 ` Edward Adam Davis
2024-08-12 11:18   ` syzbot
2024-08-13  0:29 ` Edward Adam Davis
2024-08-13  0:57   ` syzbot
2024-08-14  9:26 ` Edward Adam Davis
2024-08-14  9:47   ` syzbot
2024-08-14 10:25 ` Edward Adam Davis
2024-08-14 11:08   ` syzbot
2024-08-15  2:31 ` [syzbot] " syzbot
2024-08-15  3:00 ` syzbot
2024-08-15  8:13 ` syzbot
     [not found] <20240809014410.672145-1-lizhi.xu@windriver.com>
2024-08-09  2:04 ` syzbot
     [not found] <20240809054850.762409-1-lizhi.xu@windriver.com>
2024-08-09  6:09 ` syzbot
     [not found] <20240809064122.1490034-1-lizhi.xu@windriver.com>
2024-08-09  7:01 ` syzbot
     [not found] <20240809074103.2196689-1-lizhi.xu@windriver.com>
2024-08-09  8:01 ` syzbot
     [not found] <20240809081544.2529127-1-lizhi.xu@windriver.com>
2024-08-09  8:29 ` syzbot
     [not found] <20240809083558.2702436-1-lizhi.xu@windriver.com>
2024-08-09  8:56 ` syzbot
     [not found] <20240809092004.3109492-1-lizhi.xu@windriver.com>
2024-08-09  9:40 ` syzbot
     [not found] <20240815023135.340669-1-lizhi.xu@windriver.com>
2024-08-15  2:50 ` syzbot
     [not found] <20240815030030.564798-1-lizhi.xu@windriver.com>
2024-08-15  3:20 ` syzbot
     [not found] <20240815081319.3450173-1-lizhi.xu@windriver.com>
2024-08-15  8:34 ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=000000000000804cad061f660ac2@google.com \
    --to=syzbot+0b74d367d6e80661d6df@syzkaller.appspotmail.com \
    --cc=eadavis@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.