WARNING: bad unlock balance in process_one_work

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6de6e46d27ef cls_flower: Fix inability to match GRE/IPIP p..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=10ddfb22b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a38b8c18ca03c4e
dashboard link: https://syzkaller.appspot.com/bug?extid=6c44377e21771712be7c
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org mi...@redhat.com qiang...@windriver.com ros...@goodmis.org t...@kernel.org net...@vger.kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6c4437...@syzkaller.appspotmail.com

=====================================
WARNING: bad unlock balance detected!
5.15.0-rc7-syzkaller #0 Not tainted
-------------------------------------
kworker/0:10/9554 is trying to release lock ((work_completion)(&({ do { const void *__vpp_verify = (typeof((worker) + 0))((void *)0); (void)__vpp_verify; } while (0); ({ unsigned long __ptr; __asm__ ("" : "=r"(__ptr) : "0"((typeof(*((worker))) *)((worker)))); (typeof((typeof(*((worker))) *)((worker)))) (__ptr + (((__per_cpu_offset[(cpu)])))); }); })->work)) at:
[<ffffffff814be4c6>] trace_workqueue_execute_end include/trace/events/workqueue.h:108 [inline]
[<ffffffff814be4c6>] process_one_work+0xa26/0x16b0 kernel/workqueue.c:2302
but there are no more locks to release!

other info that might help us debug this:
1 lock held by kworker/0:10/9554:
#0: ffff88803b406d38 ((wq_completion)wg-crypt-wg1#11){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
#0: ffff88803b406d38 ((wq_completion)wg-crypt-wg1#11){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
#0: ffff88803b406d38 ((wq_completion)wg-crypt-wg1#11){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1198 [inline]
#0: ffff88803b406d38 ((wq_completion)wg-crypt-wg1#11){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:634 [inline]
#0: ffff88803b406d38 ((wq_completion)wg-crypt-wg1#11){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:661 [inline]
#0: ffff88803b406d38 ((wq_completion)wg-crypt-wg1#11){+.+.}-{0:0}, at: process_one_work+0x8a3/0x16b0 kernel/workqueue.c:2268

stack backtrace:
CPU: 0 PID: 9554 Comm: kworker/0:10 Not tainted 5.15.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: wg-crypt-wg1 wg_packet_decrypt_worker
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
print_unlock_imbalance_bug include/trace/events/lock.h:58 [inline]
__lock_release kernel/locking/lockdep.c:5304 [inline]
lock_release.cold+0x34/0x4e kernel/locking/lockdep.c:5645
process_one_work+0xa3a/0x16b0 kernel/workqueue.c:2303
worker_thread+0x658/0x11f0 kernel/workqueue.c:2444
kthread+0x3e5/0x4d0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.