WARNING in gfs2_kill_sb (3)

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: c6db52a8 Linux 4.14.183
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14ae5696100000
kernel config: https://syzkaller.appspot.com/x/.config?x=98bbe4d18401ff4
dashboard link: https://syzkaller.appspot.com/bug?extid=875c465426a08b23e0de
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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+875c46...@syzkaller.appspotmail.com

alloc_pages_current+0xe7/0x1e0 mm/mempolicy.c:2113
------------[ cut here ]------------
alloc_pages include/linux/gfp.h:520 [inline]
__get_free_pages+0xb/0x40 mm/page_alloc.c:4227
WARNING: CPU: 1 PID: 25098 at fs/super.c:1163 kill_block_super+0xbe/0xe0 fs/super.c:1163
selinux_sb_copy_data+0x28/0x380 security/selinux/hooks.c:2722
Kernel panic - not syncing: panic_on_warn set ...

security_sb_copy_data+0x6e/0xa0 security/security.c:368
mount_fs+0x1e7/0x2a0 fs/super.c:1232
vfs_kern_mount.part.0+0x5b/0x3c0 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0x3c9/0x25e0 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45f4ba
RSP: 002b:00007fb81a6b4a68 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000508980 RCX: 000000000045f4ba
RDX: 00007fb81a6b4ae0 RSI: 0000000020000040 RDI: 00007fb81a6b4b00
RBP: 000000000078bf00 R08: 00007fb81a6b4b40 R09: 00007fb81a6b4ae0
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000007
R13: 0000000000000bec R14: 00000000004ce30e R15: 00007fb81a6b56d4
CPU: 1 PID: 25098 Comm: syz-executor.2 Not tainted 4.14.183-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/0x283 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:kill_block_super+0xbe/0xe0 fs/super.c:1163
RSP: 0018:ffff8880386dfa98 EFLAGS: 00010246
RAX: 0000000000040000 RBX: 0000000000000000 RCX: ffffc90008543000
RDX: 0000000000040000 RSI: ffffffff818c06be RDI: ffff8880a6f5e528
RBP: ffff8880a8fdc040 R08: 0000000000000001 R09: 0000000000000001
R10: ffff88801a32ed18 R11: ffff88801a32e440 R12: ffff8880a6f5e180
R13: ffff8880a8fdc180 R14: dffffc0000000000 R15: ffffffff87b53300
gfs2_kill_sb+0x144/0x1a0 fs/gfs2/ops_fstype.c:1384
deactivate_locked_super+0x6c/0xd0 fs/super.c:319
sget_userns+0x9df/0xc30 fs/super.c:537
sget+0xd1/0x110 fs/super.c:572
gfs2_mount+0x10f/0x4f3 fs/gfs2/ops_fstype.c:1278
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x3c0 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0x3c9/0x25e0 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45f4ba
RSP: 002b:00007f21c56f9a68 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000508980 RCX: 000000000045f4ba
RDX: 00007f21c56f9ae0 RSI: 0000000020000fc0 RDI: 00007f21c56f9b00
RBP: 000000000078bf00 R08: 00007f21c56f9b40 R09: 00007f21c56f9ae0
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000007
R13: 0000000000000bec R14: 00000000004ce30e R15: 00007f21c56fa6d4
Kernel Offset: disabled
Rebooting in 86400 seconds..


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

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