public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+332fe1e67018625f63c9@syzkaller.appspotmail.com>
To: jchapman@katalix.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in l2tp_exit_net
Date: Wed, 06 Nov 2024 14:27:03 -0800	[thread overview]
Message-ID: <672bed37.050a0220.350062.027e.GAE@google.com> (raw)
In-Reply-To: <20241106180706.330326-1-jchapman@katalix.com>

Hello,

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

Reported-by: syzbot+332fe1e67018625f63c9@syzkaller.appspotmail.com
Tested-by: syzbot+332fe1e67018625f63c9@syzkaller.appspotmail.com

Tested on:

commit:         ccb35037 Merge branch 'net-lan969x-add-vcap-functional..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=16e85f40580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a9d1c42858837b59
dashboard link: https://syzkaller.appspot.com/bug?extid=332fe1e67018625f63c9
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=12b68d87980000

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

  reply	other threads:[~2024-11-06 22:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13  2:49 [syzbot] [net?] WARNING in l2tp_exit_net syzbot
2024-09-13 13:39 ` James Chapman
2024-11-06  6:00 ` syzbot
2024-11-06 17:21 ` [syzbot] " syzbot
2024-11-06 18:07   ` test fix for WARN_ON " James Chapman
2024-11-06 22:27     ` syzbot [this message]
2024-11-15 23:03 ` [syzbot] [net?] WARNING " syzbot
     [not found] <5e3c5bf9-5c8c-16cb-5b35-4fe57c636d65@katalix.com>
2024-11-06 22:10 ` 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=672bed37.050a0220.350062.027e.GAE@google.com \
    --to=syzbot+332fe1e67018625f63c9@syzkaller.appspotmail.com \
    --cc=jchapman@katalix.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