public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7e1e1bdb852961150198@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in cleanup_net (2)
Date: Sat, 08 Apr 2023 05:40:17 -0700	[thread overview]
Message-ID: <000000000000af3cea05f8d2710d@google.com> (raw)
In-Reply-To: <20230408121751.1444-1-hdanton@sina.com>

Hello,

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

Reported-and-tested-by: syzbot+7e1e1bdb852961150198@syzkaller.appspotmail.com

Tested on:

commit:         f3364222 ptp_qoriq: fix memory leak in probe()
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1078b369c80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ea09b0836073ee4
dashboard link: https://syzkaller.appspot.com/bug?extid=7e1e1bdb852961150198
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1623ac11c80000

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

       reply	other threads:[~2023-04-08 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230408121751.1444-1-hdanton@sina.com>
2023-04-08 12:40 ` syzbot [this message]
     [not found] <20230408104900.1375-1-hdanton@sina.com>
2023-04-08 11:03 ` [syzbot] [net?] WARNING in cleanup_net (2) syzbot
     [not found] <20230408075220.1312-1-hdanton@sina.com>
2023-04-08  8:06 ` syzbot
     [not found] <20230408020425.1227-1-hdanton@sina.com>
2023-04-08  2:18 ` syzbot
     [not found] <20230407145900.1126-1-hdanton@sina.com>
2023-04-07 15:14 ` syzbot
2023-04-07 10:48 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=000000000000af3cea05f8d2710d@google.com \
    --to=syzbot+7e1e1bdb852961150198@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