From: syzbot <syzbot+5b6ed16da1077f45bc8e@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in attr_make_nonresident
Date: Tue, 27 Aug 2024 09:17:03 -0700 [thread overview]
Message-ID: <0000000000006ab89d0620ac92fc@google.com> (raw)
In-Reply-To: <000000000000be9914061763f17a@google.com>
syzbot suspects this issue was fixed by commit:
commit 0f9579d9e0331b6255132ac06bdf2c0a01cceb90
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Mon Jun 3 06:58:13 2024 +0000
fs/ntfs3: Add missing .dirty_folio in address_space_operations
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=116e278d980000
start commit: 34afb82a3c67 Merge tag '6.10-rc6-smb3-server-fixes' of git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=42a432cfd0e579e0
dashboard link: https://syzkaller.appspot.com/bug?extid=5b6ed16da1077f45bc8e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=110a2c7e980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1312ea4e980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Add missing .dirty_folio in address_space_operations
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-08-27 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 12:51 [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in attr_make_nonresident syzbot
2024-07-15 9:41 ` [syzbot] " syzbot
2024-07-17 6:36 ` [syzbot] possible fix syzbot
2024-07-17 8:20 ` [syzbot] before " syzbot
2024-08-23 16:04 ` [syzbot] BUG: unable to handle kernel NULL pointer dereference in attr_make_nonresident syzbot
2024-08-27 16:17 ` syzbot [this message]
2024-09-03 11:24 ` [syzbot] [ntfs3?] " Konstantin Komarov
[not found] <eb49b42d-61eb-4654-81e6-577a6199e0ee@paragon-software.com>
2024-07-15 10:52 ` syzbot
[not found] <62834558-1286-4af2-ab6b-7d1ef309c793@paragon-software.com>
2024-07-17 7:54 ` syzbot
[not found] <654aa65d-c29b-449f-9df9-d8d6775b0355@paragon-software.com>
2024-07-17 8:42 ` syzbot
[not found] <33ba315adf774817843093e3916393b3@paragon-software.com>
2024-08-27 17:35 ` 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=0000000000006ab89d0620ac92fc@google.com \
--to=syzbot+5b6ed16da1077f45bc8e@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--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.