From: syzbot <syzbot+870ae3a4c7a251c996bd@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, elver@google.com,
jacob.e.keller@intel.com, kuba@kernel.org, leonro@nvidia.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ntfs3?] KASAN: stack-out-of-bounds Read in iput
Date: Sat, 09 Sep 2023 18:56:32 -0700 [thread overview]
Message-ID: <000000000000db589b0604f784dd@google.com> (raw)
In-Reply-To: <000000000000885d8605e91963fd@google.com>
syzbot suspects this issue was fixed by commit:
commit c1b05105573b2cd5845921eb0d2caa26e2144a34
Author: Jakub Kicinski <kuba@kernel.org>
Date: Wed Nov 9 18:32:54 2022 +0000
genetlink: fix single op policy dump when do is present
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17eb48a0680000
start commit: 105a36f3694e Merge tag 'kbuild-fixes-v6.0-3' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c221af36f6d1d811
dashboard link: https://syzkaller.appspot.com/bug?extid=870ae3a4c7a251c996bd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17274404880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: genetlink: fix single op policy dump when do is present
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-09-10 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000885d8605e91963fd@google.com>
2022-09-20 11:30 ` [syzbot] KASAN: stack-out-of-bounds Read in iput Marco Elver
2023-09-10 1:56 ` syzbot [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=000000000000db589b0604f784dd@google.com \
--to=syzbot+870ae3a4c7a251c996bd@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=elver@google.com \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).