From: syzbot <syzbot+9af29acd8f27fbce94bc@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] general protection fault in run_is_mapped_full
Date: Tue, 27 Aug 2024 10:23:04 -0700 [thread overview]
Message-ID: <0000000000008dc0d40620ad7ec8@google.com> (raw)
In-Reply-To: <706373e55157441da446a4d634784706@paragon-software.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+9af29acd8f27fbce94bc@syzkaller.appspotmail.com
Tested-by: syzbot+9af29acd8f27fbce94bc@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=1598d17b980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5ee621e7c3df264
dashboard link: https://syzkaller.appspot.com/bug?extid=9af29acd8f27fbce94bc
compiler: Debian clang version 15.0.6, 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-27 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <706373e55157441da446a4d634784706@paragon-software.com>
2024-08-27 17:23 ` syzbot [this message]
[not found] <20240902130045.6945-1-almaz.alexandrovich@paragon-software.com>
2024-09-12 13:19 ` [syzbot] [ntfs3?] general protection fault in run_is_mapped_full syzbot
[not found] <be1ba54b-80a1-4cf2-9a2d-395e87c53a28@paragon-software.com>
2024-07-15 10:01 ` syzbot
[not found] <8f3f2481-c970-4019-b39d-6f0d280ba147@paragon-software.com>
2024-07-15 9:39 ` syzbot
[not found] <6da7776f-51a3-4d3c-83e9-e3b710eef541@paragon-software.com>
2024-07-15 9:23 ` syzbot
2024-07-13 6:10 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=0000000000008dc0d40620ad7ec8@google.com \
--to=syzbot+9af29acd8f27fbce94bc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.