From: syzbot <syzbot+bc7ca0ae4591cb2550f9@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 mi_read
Date: Mon, 02 Sep 2024 07:18:02 -0700 [thread overview]
Message-ID: <000000000000d859210621239b1c@google.com> (raw)
In-Reply-To: <20240902131729.8411-1-almaz.alexandrovich@paragon-software.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+bc7ca0ae4591cb2550f9@syzkaller.appspotmail.com
Tested-by: syzbot+bc7ca0ae4591cb2550f9@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=176192fb980000
kernel config: https://syzkaller.appspot.com/x/.config?x=2258b49cd9b339fa
dashboard link: https://syzkaller.appspot.com/bug?extid=bc7ca0ae4591cb2550f9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=14586b47980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-09-02 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240902131729.8411-1-almaz.alexandrovich@paragon-software.com>
2024-09-02 14:18 ` syzbot [this message]
[not found] <ddcf93e3-df0d-442c-a490-f6607f313fe3@paragon-software.com>
2024-10-16 11:32 ` [syzbot] [ntfs3?] possible deadlock in mi_read syzbot
[not found] <f59e3f6ca8134a6b9735b5c0477e9c7f@paragon-software.com>
2024-08-23 16:36 ` 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=000000000000d859210621239b1c@google.com \
--to=syzbot+bc7ca0ae4591cb2550f9@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