linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+44ae022028805f4600fc@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KASAN: slab-use-after-free Read in team_device_event
Date: Sat, 09 Sep 2023 20:52:38 -0700	[thread overview]
Message-ID: <0000000000000c7f5d0604f924b5@google.com> (raw)
In-Reply-To: <20230910031719.6205-1-hdanton@sina.com>

Hello,

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

Reported-and-tested-by: syzbot+44ae022028805f4600fc@syzkaller.appspotmail.com

Tested on:

commit:         f8fdd54e Merge branch 'sja1105-fixes'
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
console output: https://syzkaller.appspot.com/x/log.txt?x=112f3908680000
kernel config:  https://syzkaller.appspot.com/x/.config?x=634e05b4025da9da
dashboard link: https://syzkaller.appspot.com/bug?extid=44ae022028805f4600fc
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=14564e94680000

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

       reply	other threads:[~2023-09-10  3:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230910031719.6205-1-hdanton@sina.com>
2023-09-10  3:52 ` syzbot [this message]
     [not found] <20230909092011.5956-1-hdanton@sina.com>
2023-09-09  9:58 ` [syzbot] [net?] KASAN: slab-use-after-free Read in team_device_event syzbot
     [not found] <20230909040639.5886-1-hdanton@sina.com>
2023-09-09  5:02 ` syzbot
     [not found] <20230909025602.5753-1-hdanton@sina.com>
2023-09-09  3:36 ` syzbot
2023-09-07 15:22 syzbot

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=0000000000000c7f5d0604f924b5@google.com \
    --to=syzbot+44ae022028805f4600fc@syzkaller.appspotmail.com \
    --cc=hdanton@sina.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;
as well as URLs for NNTP newsgroup(s).