WARNING: stack going in the wrong direction? ip=__schedule

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: b3a99fd3 Linux 4.19.129
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1348c711100000
kernel config: https://syzkaller.appspot.com/x/.config?x=afe60417c22a7f7a
dashboard link: https://syzkaller.appspot.com/bug?extid=5762a32a7a84bcb4832b
compiler: gcc (GCC) 10.1.0-syz 20200507

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

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+5762a3...@syzkaller.appspotmail.com

WARNING: stack going in the wrong direction? ip=__schedule+0x2d6/0x2040
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'.
device veth25 entered promiscuous mode
overlayfs: failed to resolve './file0Q�p ^2l& �w��bW� }͎': -2
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=16 sclass=netlink_audit_socket pid=20849 comm=syz-executor.3
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=16 sclass=netlink_audit_socket pid=20874 comm=syz-executor.3


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: f6d5cb9e Linux 4.19.142
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1595098e900000
kernel config: https://syzkaller.appspot.com/x/.config?x=30067df04d3254aa

dashboard link: https://syzkaller.appspot.com/bug?extid=5762a32a7a84bcb4832b
compiler: gcc (GCC) 10.1.0-syz 20200507

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1281768e900000

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

overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
WARNING: stack going in the wrong direction? ip=__schedule+0x1e1/0x2040
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
audit: type=1800 audit(1598766021.860:11): pid=30026 uid=0 auid=0 ses=6 subj=system_u:system_r:kernel_t:s0 op=collect_data cause=failed comm="syz-executor.4" name="file0" dev="sda1" ino=16270 res=0
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: './file0' not a directory
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2
overlayfs: failed to resolve './file0': -2