From: Edward Adam Davis <eadavis@qq.com>
To: syzbot+c2ada45c23d98d646118@syzkaller.appspotmail.com
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] possible deadlock in ntfs_set_state (2)
Date: Tue, 13 Feb 2024 18:37:34 +0800 [thread overview]
Message-ID: <tencent_E2FE25978DA612195DF45DCD191D4FAF8D07@qq.com> (raw)
In-Reply-To: <000000000000998cff06113e1d91@google.com>
please test deadlock in ntfs_set_state
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
diff --git a/fs/ntfs3/frecord.c b/fs/ntfs3/frecord.c
index 3b42938a9d3b..1dfc933b58ad 100644
--- a/fs/ntfs3/frecord.c
+++ b/fs/ntfs3/frecord.c
@@ -3210,7 +3210,6 @@ static bool ni_update_parent(struct ntfs_inode *ni, struct NTFS_DUP_INFO *dup,
/* Check simple case when parent inode equals current inode. */
if (ino_get(&fname->home) == ni->vfs_inode.i_ino) {
- ntfs_set_state(sbi, NTFS_DIRTY_ERROR);
continue;
}
next prev parent reply other threads:[~2024-02-13 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 7:12 [syzbot] [ntfs3?] possible deadlock in ntfs_set_state (2) syzbot
2024-02-13 10:37 ` Edward Adam Davis [this message]
2024-02-13 11:10 ` syzbot
2024-02-13 11:41 ` Hillf Danton
2024-02-26 4:23 ` Boqun Feng
2024-02-26 10:55 ` Hillf Danton
2024-02-26 11:46 ` syzbot
2024-02-26 12:06 ` Hillf Danton
2024-02-26 15:00 ` syzbot
2024-07-17 6:31 ` [syzbot] ntfs3.git syzbot
2024-08-23 8:56 ` [syzbot] possible deadlock in ntfs_set_state (linux-ntfs3.git/master) syzbot
[not found] <6fb088e7-3385-4c06-945f-0a58da0bf138@paragon-software.com>
2024-07-17 7:27 ` [syzbot] [ntfs3?] possible deadlock in ntfs_set_state (2) syzbot
[not found] <e80cfc67-ff1c-484f-bf42-8c9d72408c36@paragon-software.com>
2024-08-23 9:26 ` 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=tencent_E2FE25978DA612195DF45DCD191D4FAF8D07@qq.com \
--to=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+c2ada45c23d98d646118@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox