From: syzbot <syzbot+703d9e154b3b58277261@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, davem@davemloft.net, edumazet@google.com,
frederic@kernel.org, gnault@redhat.com, jacob.e.keller@intel.com,
jakub@cloudflare.com, jiri@nvidia.com, johannes@sipsolutions.net,
juri.lelli@redhat.com, kirill.shutemov@linux.intel.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, netdev@vger.kernel.org,
nicolas.dichtel@6wind.com, pabeni@redhat.com,
paul@paul-moore.com, peterz@infradead.org, razor@blackwall.org,
sathyanarayanan.kuppuswamy@linux.intel.com, steven.price@arm.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tparkin@katalix.com
Subject: Re: [syzbot] BUG: sleeping function called from invalid context in static_key_slow_inc
Date: Thu, 17 Nov 2022 17:56:19 -0800 [thread overview]
Message-ID: <00000000000011ec5105edb50386@google.com> (raw)
In-Reply-To: <0000000000004e78ec05eda79749@google.com>
syzbot has bisected this issue to:
commit b68777d54fac21fc833ec26ea1a2a84f975ab035
Author: Jakub Sitnicki <jakub@cloudflare.com>
Date: Mon Nov 14 19:16:19 2022 +0000
l2tp: Serialize access to sk_user_data with sk_callback_lock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1600bb49880000
start commit: 064bc7312bd0 netdevsim: Fix memory leak of nsim_dev->fa_co..
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=1500bb49880000
console output: https://syzkaller.appspot.com/x/log.txt?x=1100bb49880000
kernel config: https://syzkaller.appspot.com/x/.config?x=a33ac7bbc22a8c35
dashboard link: https://syzkaller.appspot.com/bug?extid=703d9e154b3b58277261
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13cd2f79880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=109e1695880000
Reported-by: syzbot+703d9e154b3b58277261@syzkaller.appspotmail.com
Fixes: b68777d54fac ("l2tp: Serialize access to sk_user_data with sk_callback_lock")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-11-18 1:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 9:55 [syzbot] BUG: sleeping function called from invalid context in static_key_slow_inc syzbot
2022-11-17 12:03 ` syzbot
2022-11-18 1:56 ` syzbot [this message]
2022-11-18 11:51 ` [PATCH 6.1-rc6] l2tp: call udp_tunnel_encap_enable() and sock_release() without sk_callback_lock Tetsuo Handa
2022-11-18 12:36 ` Eric Dumazet
2022-11-18 13:19 ` Tetsuo Handa
2022-11-18 15:04 ` Eric Dumazet
2022-11-18 17:50 ` Jakub Sitnicki
2022-11-19 10:08 ` Tetsuo Handa
2022-11-19 13:13 ` Jakub Sitnicki
[not found] ` <a2199ab7c03e71af3ac791e119e52c94e9f023f56c8b0d8014dd70aceee2784e@mu>
2022-11-18 22:10 ` Jakub Sitnicki
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=00000000000011ec5105edb50386@google.com \
--to=syzbot+703d9e154b3b58277261@syzkaller.appspotmail.com \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=gnault@redhat.com \
--cc=jacob.e.keller@intel.com \
--cc=jakub@cloudflare.com \
--cc=jiri@nvidia.com \
--cc=johannes@sipsolutions.net \
--cc=juri.lelli@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=peterz@infradead.org \
--cc=razor@blackwall.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=steven.price@arm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tparkin@katalix.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).