All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+bbd35b345c7cab0d9a08@syzkaller.appspotmail.com>
To: cong.wang@bytedance.com, davem@davemloft.net,
	edumazet@google.com, eric.dumazet@gmail.com, gnault@redhat.com,
	jakub@cloudflare.com, kuba@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in release_sock
Date: Wed, 18 Jan 2023 05:11:23 -0800	[thread overview]
Message-ID: <000000000000941ee205f2898d65@google.com> (raw)
In-Reply-To: <000000000000fbb2d505f27398cb@google.com>

syzbot has bisected this issue to:

commit 0b2c59720e65885a394a017d0cf9cab118914682
Author: Cong Wang <cong.wang@bytedance.com>
Date:   Sat Jan 14 03:01:37 2023 +0000

    l2tp: close all race conditions in l2tp_tunnel_register()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15331c61480000
start commit:   87b93b678e95 octeontx2-pf: Avoid use of GFP_KERNEL in atom..
git tree:       net
final oops:     https://syzkaller.appspot.com/x/report.txt?x=17331c61480000
console output: https://syzkaller.appspot.com/x/log.txt?x=13331c61480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2b6ecad960fc703e
dashboard link: https://syzkaller.appspot.com/bug?extid=bbd35b345c7cab0d9a08
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1716b3a1480000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14e57a91480000

Reported-by: syzbot+bbd35b345c7cab0d9a08@syzkaller.appspotmail.com
Fixes: 0b2c59720e65 ("l2tp: close all race conditions in l2tp_tunnel_register()")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2023-01-18 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 10:59 [syzbot] possible deadlock in release_sock syzbot
2023-01-17 11:04 ` Eric Dumazet
2023-01-18 13:11 ` syzbot [this message]

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=000000000000941ee205f2898d65@google.com \
    --to=syzbot+bbd35b345c7cab0d9a08@syzkaller.appspotmail.com \
    --cc=cong.wang@bytedance.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=gnault@redhat.com \
    --cc=jakub@cloudflare.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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.