From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+d8b02c920ae8f3e0be75@syzkaller.appspotmail.com>
Cc: almaz.alexandrovich@paragon-software.com, davem@davemloft.net,
edward.lo@ambergroup.io, glider@google.com, idosch@mellanox.com,
ivan.khoronzhuk@linaro.org, jiri@mellanox.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, ntfs3@lists.linux.dev,
petrm@mellanox.com, phind.uet@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] [ntfs3?] KMSAN: uninit-value in bcmp
Date: Mon, 20 Feb 2023 07:52:18 +0100 [thread overview]
Message-ID: <CACT4Y+asA1zb6A4SJTDgF+rpNyZoHmE27xjfQd5pqg2_wyhErA@mail.gmail.com> (raw)
In-Reply-To: <0000000000009fddba05f500c785@google.com>
On Sat, 18 Feb 2023 at 23:16, syzbot
<syzbot+d8b02c920ae8f3e0be75@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 4f1dc7d9756e66f3f876839ea174df2e656b7f79
> Author: Edward Lo <edward.lo@ambergroup.io>
> Date: Fri Sep 9 01:04:00 2022 +0000
>
> fs/ntfs3: Validate attribute name offset
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=149cdbcf480000
> start commit: b7b275e60bcd Linux 6.1-rc7
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=2325e409a9a893e1
> dashboard link: https://syzkaller.appspot.com/bug?extid=d8b02c920ae8f3e0be75
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=164c4a4b880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=152bfbc9880000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: fs/ntfs3: Validate attribute name offset
Looks reasonable to me"
#syz fix: fs/ntfs3: Validate attribute name offset
prev parent reply other threads:[~2023-02-20 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000008f00f7058ad13ec8@google.com>
2023-02-18 22:16 ` [syzbot] [net?] [ntfs3?] KMSAN: uninit-value in bcmp syzbot
2023-02-20 6:52 ` Dmitry Vyukov [this message]
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=CACT4Y+asA1zb6A4SJTDgF+rpNyZoHmE27xjfQd5pqg2_wyhErA@mail.gmail.com \
--to=dvyukov@google.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=davem@davemloft.net \
--cc=edward.lo@ambergroup.io \
--cc=glider@google.com \
--cc=idosch@mellanox.com \
--cc=ivan.khoronzhuk@linaro.org \
--cc=jiri@mellanox.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=petrm@mellanox.com \
--cc=phind.uet@gmail.com \
--cc=syzbot+d8b02c920ae8f3e0be75@syzkaller.appspotmail.com \
--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;
as well as URLs for NNTP newsgroup(s).