From: syzbot <syzbot+5b6ed16da1077f45bc8e@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in attr_make_nonresident
Date: Mon, 15 Jul 2024 03:52:05 -0700 [thread overview]
Message-ID: <000000000000148de1061d4705bb@google.com> (raw)
In-Reply-To: <eb49b42d-61eb-4654-81e6-577a6199e0ee@paragon-software.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+5b6ed16da1077f45bc8e@syzkaller.appspotmail.com
Tested on:
commit: 911daf69 fs/ntfs3: Fix formatting, change comments, re..
git tree: https://github.com/Paragon-Software-Group/linux-ntfs3.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=12cb942d980000
kernel config: https://syzkaller.appspot.com/x/.config?x=bc26ad11927ab7fa
dashboard link: https://syzkaller.appspot.com/bug?extid=5b6ed16da1077f45bc8e
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-07-15 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eb49b42d-61eb-4654-81e6-577a6199e0ee@paragon-software.com>
2024-07-15 10:52 ` syzbot [this message]
[not found] <33ba315adf774817843093e3916393b3@paragon-software.com>
2024-08-27 17:35 ` [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in attr_make_nonresident syzbot
[not found] <654aa65d-c29b-449f-9df9-d8d6775b0355@paragon-software.com>
2024-07-17 8:42 ` syzbot
[not found] <62834558-1286-4af2-ab6b-7d1ef309c793@paragon-software.com>
2024-07-17 7:54 ` syzbot
2024-05-01 12:51 syzbot
2024-08-27 16:17 ` syzbot
2024-09-03 11:24 ` Konstantin Komarov
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=000000000000148de1061d4705bb@google.com \
--to=syzbot+5b6ed16da1077f45bc8e@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.