mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+8ed98cbd0161632bce95@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [can?] general protection fault in can_rx_unregister (2)
Date: Sun, 24 May 2026 21:32:02 -0700	[thread overview]
Message-ID: <6a13d0c2.820a0220.e7972.0002.GAE@google.com> (raw)
In-Reply-To: <tencent_E820E80EECC6CDFC793A6DA02D696CD8940A@qq.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+8ed98cbd0161632bce95@syzkaller.appspotmail.com
Tested-by: syzbot+8ed98cbd0161632bce95@syzkaller.appspotmail.com

Tested on:

commit:         4b436297 Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1657155e580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a834c6344141a58b
dashboard link: https://syzkaller.appspot.com/bug?extid=8ed98cbd0161632bce95
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
userspace arch: arm64
patch:          https://syzkaller.appspot.com/x/patch.diff?x=11d2047a580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2026-05-25  4:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-24  0:38 syzbot
2026-05-25  3:35 ` Edward Adam Davis
2026-05-25  4:32   ` syzbot [this message]
2026-05-25 11:48 ` Edward Adam Davis
2026-05-25 13:30   ` syzbot
2026-05-25 13:56 ` [PATCH] can: af_can: reject can rx unregister if dev is not can Edward Adam Davis
2026-05-25 18:15   ` Oliver Hartkopp
2026-05-25 23:46     ` Edward Adam Davis
2026-05-26 14:16       ` Oliver Hartkopp

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=6a13d0c2.820a0220.e7972.0002.GAE@google.com \
    --to=syzbot+8ed98cbd0161632bce95@syzkaller.appspotmail.com \
    --cc=eadavis@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome