kernel panic: corrupted stack end in getsockopt

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cf256fbc Linux 4.14.231
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ef1cc5d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=403e68efdb1dcca6
dashboard link: https://syzkaller.appspot.com/bug?extid=181f97411908b4582ccf

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+181f97...@syzkaller.appspotmail.com

audit: type=1804 audit(1618675173.318:96): pid=32689 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir001023567/syzkaller.XTKLhr/1063/file0/file0" dev="ramfs" ino=92176 res=1
ceph: device name is missing path (no : separator in [dz:]:��z*�Nlx��GS �7PE�U���p��ʋ �/ x�D���f�WW����� A�C���Kh �������✘e �s�� ����
�h[J�0\� .��a�rxfAH�6�� ��]Z{�Gk~�!)
Kernel panic - not syncing: corrupted stack end detected inside scheduler

CPU: 1 PID: 29303 Comm: syz-executor.1 Not tainted 4.14.231-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
schedule_debug kernel/sched/core.c:3199 [inline]
__schedule+0x1ddf/0x1de0 kernel/sched/core.c:3308
preempt_schedule_common+0x45/0xc0 kernel/sched/core.c:3508
___preempt_schedule+0x16/0x18
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:161 [inline]
_raw_spin_unlock_irqrestore+0xaf/0xe0 kernel/locking/spinlock.c:192
try_to_wake_up+0x706/0x1100 kernel/sched/core.c:2091
wake_up_process kernel/sched/core.c:2160 [inline]
wake_up_q+0x82/0xd0 kernel/sched/core.c:468
__mutex_unlock_slowpath+0x261/0x770 kernel/locking/mutex.c:1070
nf_sockopt_find.constprop.0+0x1ad/0x220 net/netfilter/nf_sockopt.c:88
nf_sockopt net/netfilter/nf_sockopt.c:99 [inline]
nf_getsockopt+0x29/0xc0 net/netfilter/nf_sockopt.c:122
ip_getsockopt net/ipv4/ip_sockglue.c:1566 [inline]
ip_getsockopt+0x105/0x150 net/ipv4/ip_sockglue.c:1551
tcp_getsockopt+0x7b/0xc0 net/ipv4/tcp.c:3257
SYSC_getsockopt net/socket.c:1896 [inline]
SyS_getsockopt+0x102/0x1c0 net/socket.c:1878
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x467a6a
RSP: 002b:00007ffeffcaeff8 EFLAGS: 00000246 ORIG_RAX: 0000000000000037
RAX: ffffffffffffffda RBX: 00007ffeffcaf00c RCX: 0000000000467a6a
RDX: 0000000000000060 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 0000000000000003 R08: 00007ffeffcaf00c R09: 00007ffeffcaf070
R10: 00007ffeffcaf010 R11: 0000000000000246 R12: 00007ffeffcaf010
R13: 00000000000949e1 R14: 0000000000000000 R15: 00007ffeffcaf780
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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.