From: syzbot <syzbot+c2ada45c23d98d646118@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] possible deadlock in ntfs_set_state (2)
Date: Fri, 23 Aug 2024 02:26:01 -0700 [thread overview]
Message-ID: <0000000000001efcd70620565d36@google.com> (raw)
In-Reply-To: <e80cfc67-ff1c-484f-bf42-8c9d72408c36@paragon-software.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+c2ada45c23d98d646118@syzkaller.appspotmail.com
Tested-by: syzbot+c2ada45c23d98d646118@syzkaller.appspotmail.com
Tested on:
commit: 7529036a fs/ntfs3: Rename ntfs3_setattr into ntfs_seta..
git tree: https://github.com/Paragon-Software-Group/linux-ntfs3.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=164f6c33980000
kernel config: https://syzkaller.appspot.com/x/.config?x=2fa1c21de29b7e1c
dashboard link: https://syzkaller.appspot.com/bug?extid=c2ada45c23d98d646118
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-08-23 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e80cfc67-ff1c-484f-bf42-8c9d72408c36@paragon-software.com>
2024-08-23 9:26 ` syzbot [this message]
[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
2024-02-13 7:12 syzbot
2024-02-13 10:37 ` Edward Adam Davis
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
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=0000000000001efcd70620565d36@google.com \
--to=syzbot+c2ada45c23d98d646118@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox