From: syzbot <syzbot+0b74d367d6e80661d6df@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [v9fs?] WARNING in v9fs_begin_writeback
Date: Wed, 14 Aug 2024 20:00:35 -0700 [thread overview]
Message-ID: <000000000000ef1381061fb00b6c@google.com> (raw)
In-Reply-To: <0000000000007ec511061f00a7b2@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [v9fs?] WARNING in v9fs_begin_writeback
Author: lizhi.xu@windriver.com
clean dirty for the release inode, stop to worker wb it again.
#syz test: upstream c0ecd6388360
diff --git a/fs/9p/vfs_dir.c b/fs/9p/vfs_dir.c
index e0d34e4e9076..85161f0bb749 100644
--- a/fs/9p/vfs_dir.c
+++ b/fs/9p/vfs_dir.c
@@ -218,7 +218,12 @@ int v9fs_dir_release(struct inode *inode, struct file *filp)
if ((S_ISREG(inode->i_mode)) && (filp->f_mode & FMODE_WRITE))
retval = filemap_fdatawrite(inode->i_mapping);
+ printk("fid: %p, fidnum: %d, ino: %lx, ino is freeing:%d, will free: %d, dirty: %d, %s\n", fid, fid->fid, inode->i_ino,
+ inode->i_state & I_FREEING,
+ inode->i_state & I_WILL_FREE,
+ inode->i_state & I_DIRTY, __func__);
spin_lock(&inode->i_lock);
+ inode->i_state |= I_FREEING;
hlist_del(&fid->ilist);
spin_unlock(&inode->i_lock);
put_err = p9_fid_put(fid);
next prev parent reply other threads:[~2024-08-15 3:00 UTC|newest]
Thread overview: 63+ 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
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 [this message]
2024-08-15 8:13 ` 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=000000000000ef1381061fb00b6c@google.com \
--to=syzbot+0b74d367d6e80661d6df@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox