From: syzbot <syzbot+36bb70085ef6edc2ebb9@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 attr_data_get_block
Date: Wed, 17 Jul 2024 02:31:03 -0700 [thread overview]
Message-ID: <000000000000fc6bc5061d6e1ee3@google.com> (raw)
In-Reply-To: <087fb68c-7c33-4bbb-8b9d-281ea1dc1129@paragon-software.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
SYZFAIL: write(/proc/sys/fs/binfmt_misc/register) failed
2024/07/17 09:30:00 parsed 1 programs
2024/07/17 09:30:00 [FATAL] failed to run ["./syz-executor" "setup" "fault" "binfmt_misc" "usb" "802154" "swap"]: exit status 67
mkdir(/syzcgroup) failed: 17
mount(binfmt_misc) failed: 16
write(/proc/sys/fs/binfmt_misc/register) failed: 17
SYZFAIL: write(/proc/sys/fs/binfmt_misc/register) failed
(errno 17: File exists)
Tested on:
commit: d57431c6 fs/ntfs3: Do copy_to_user out of run_lock
git tree: https://github.com/Paragon-Software-Group/linux-ntfs3.git
console output: https://syzkaller.appspot.com/x/log.txt?x=168672e9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=47d282ddffae809f
dashboard link: https://syzkaller.appspot.com/bug?extid=36bb70085ef6edc2ebb9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
next parent reply other threads:[~2024-07-17 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <087fb68c-7c33-4bbb-8b9d-281ea1dc1129@paragon-software.com>
2024-07-17 9:31 ` syzbot [this message]
[not found] <c2d1b569-9b50-42db-991e-a295b3e304bc@paragon-software.com>
2024-07-17 7:13 ` [syzbot] [ntfs3?] possible deadlock in attr_data_get_block syzbot
[not found] <d0e71ba0-d0bf-4ec2-8222-1c1b6c49353b@paragon-software.com>
2024-06-19 14:06 ` 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=000000000000fc6bc5061d6e1ee3@google.com \
--to=syzbot+36bb70085ef6edc2ebb9@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