From: syzbot <syzbot+07bb74aeafc88ba7d5b4@syzkaller.appspotmail.com>
To: bst@pengutronix.de, dania@coconnect-ltd.com, davem@davemloft.net,
dev.kurt@vandijck-laurijssen.be, ecathinds@gmail.com,
kernel@pengutronix.de, linux-can@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@rempel-privat.de,
lkp@intel.com, maxime.jayat@mobile-devices.fr,
mkl@pengutronix.de, netdev@vger.kernel.org, nogikh@google.com,
o.rempel@pengutronix.de, robin@protonic.nl,
socketcan@hartkopp.net, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Write in j1939_sock_pending_del
Date: Tue, 11 Jul 2023 06:53:34 -0700 [thread overview]
Message-ID: <000000000000dd5c040600366c6f@google.com> (raw)
In-Reply-To: <000000000000de1eec059692c021@google.com>
This bug is marked as fixed by commit:
can: j1939: socket: rework socket locking for
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
Kernel: Linux
Dashboard link: https://syzkaller.appspot.com/bug?extid=07bb74aeafc88ba7d5b4
---
[1] I expect the commit to be present in:
1. for-kernelci branch of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
2. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
3. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
4. main branch of
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
The full list of 9 trees can be found at
https://syzkaller.appspot.com/upstream/repos
next prev parent reply other threads:[~2023-07-11 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 5:32 KASAN: use-after-free Write in j1939_sock_pending_del syzbot
2019-11-05 11:45 ` syzbot
2023-07-11 13:53 ` syzbot [this message]
2023-07-17 12:32 ` Re: [syzbot] " Aleksandr Nogikh
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=000000000000dd5c040600366c6f@google.com \
--to=syzbot+07bb74aeafc88ba7d5b4@syzkaller.appspotmail.com \
--cc=bst@pengutronix.de \
--cc=dania@coconnect-ltd.com \
--cc=davem@davemloft.net \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=ecathinds@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=lkp@intel.com \
--cc=maxime.jayat@mobile-devices.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=o.rempel@pengutronix.de \
--cc=robin@protonic.nl \
--cc=socketcan@hartkopp.net \
--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).