All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e953a8f3071f5c0a28fd@syzkaller.appspotmail.com>
To: danielyangkang@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] possible deadlock in gtp_encap_enable_socket
Date: Mon, 30 Sep 2024 18:20:03 -0700	[thread overview]
Message-ID: <66fb4e43.050a0220.aab67.003c.GAE@google.com> (raw)
In-Reply-To: <CAGiJo8TzPyoxUoTV=48uowQPPywbCZ6X1fRRF5KGYFJyhkY5_A@mail.gmail.com>

Hello,

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

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

Tested on:

commit:         c824deb1 cxgb4: clip_tbl: Fix spelling mistake "wont" ..
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17aaf127980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b2d4fdf18a83ec0b
dashboard link: https://syzkaller.appspot.com/bug?extid=e953a8f3071f5c0a28fd
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10257d07980000

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

       reply	other threads:[~2024-10-01  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGiJo8TzPyoxUoTV=48uowQPPywbCZ6X1fRRF5KGYFJyhkY5_A@mail.gmail.com>
2024-10-01  1:20 ` syzbot [this message]
     [not found] <CAGiJo8QbFa1ygs7e3T8uZbvRb+e-+Eu8UBef1k6ZLkr5eJ3x1Q@mail.gmail.com>
2024-10-05  3:36 ` [syzbot] [net?] possible deadlock in gtp_encap_enable_socket syzbot
2024-09-23 15:46 syzbot
2024-10-05  9:28 ` Hillf Danton
2024-10-05  9:57   ` syzbot
2024-10-30 12:02 ` Pablo Neira Ayuso
2025-05-12 16:08 ` syzbot
2025-05-12 22:10   ` Kuniyuki Iwashima

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=66fb4e43.050a0220.aab67.003c.GAE@google.com \
    --to=syzbot+e953a8f3071f5c0a28fd@syzkaller.appspotmail.com \
    --cc=danielyangkang@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.