From: syzbot <syzbot+a9dce1ff45c3bbeceb3a@syzkaller•appspotmail.com>
To: davem@davemloft•net, elver@google•com, hdanton@sina•com,
john.ogness@linutronix•de, kernel@pengutronix•de,
kuba@kernel•org, linux-can@vger•kernel.org,
linux-kernel@vger•kernel.org, linux@rempel-privat•de,
mkl@pengutronix•de, netdev@vger•kernel.org, pabeni@redhat•com,
pmladek@suse•com, robin@protonic•nl, rostedt@goodmis•org,
socketcan@hartkopp•net, syzkaller-bugs@googlegroups•com
Subject: Re: [syzbot] KASAN: use-after-free Read in j1939_xtp_rx_dat_one (3)
Date: Sat, 28 May 2022 08:54:06 -0700 [thread overview]
Message-ID: <000000000000cee18105e0146e2d@google.com> (raw)
In-Reply-To: <000000000000ae0adf05db4b6f66@google.com>
syzbot suspects this issue was fixed by commit:
commit 701850dc0c31bfadf75a0a74af7d2c97859945ec
Author: Marco Elver <elver@google•com>
Date: Tue May 3 07:38:44 2022 +0000
printk, tracing: fix console tracepoint
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=153df725f00000
start commit: ae085d7f9365 mm: kfence: fix missing objcg housekeeping fo..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=6bae4cd50262530e
dashboard link: https://syzkaller.appspot.com/bug?extid=a9dce1ff45c3bbeceb3a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12529653700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b64ea5700000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: printk, tracing: fix console tracepoint
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-05-28 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 18:25 [syzbot] KASAN: use-after-free Read in j1939_xtp_rx_dat_one (3) syzbot
2022-05-28 15:54 ` 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=000000000000cee18105e0146e2d@google.com \
--to=syzbot+a9dce1ff45c3bbeceb3a@syzkaller$(echo .)appspotmail.com \
--cc=davem@davemloft$(echo .)net \
--cc=elver@google$(echo .)com \
--cc=hdanton@sina$(echo .)com \
--cc=john.ogness@linutronix$(echo .)de \
--cc=kernel@pengutronix$(echo .)de \
--cc=kuba@kernel$(echo .)org \
--cc=linux-can@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@rempel-privat$(echo .)de \
--cc=mkl@pengutronix$(echo .)de \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pmladek@suse$(echo .)com \
--cc=robin@protonic$(echo .)nl \
--cc=rostedt@goodmis$(echo .)org \
--cc=socketcan@hartkopp$(echo .)net \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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