kernel BUG at ./include/linux/mm.h:LINE! (2)

12 views
Skip to first unread message

syzbot

unread,
Nov 28, 2017, 12:24:04 PM11/28/17
to da...@davemloft.net, her...@gondor.apana.org.au, linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com
Hello,

syzkaller hit the following crash on
1d3b78bbc6e983fabb3fbf91b76339bf66e4a12c
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

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


flags: 0x2fffc0000000000()
raw: 02fffc0000000000 0000000000000000 0000000000000000 00000000ffffffff
raw: 0000000000000000 0000000100000001 0000000000000000 0000000000000000
page dumped because: VM_BUG_ON_PAGE(page_ref_count(page) == 0)
------------[ cut here ]------------
kernel BUG at ./include/linux/mm.h:482!
invalid opcode: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 31102 Comm: syz-executor7 Not tainted 4.14.0+ #130
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff8801d2a7a180 task.stack: ffff8801d43a8000
RIP: 0010:put_page_testzero include/linux/mm.h:482 [inline]
RIP: 0010:__free_pages+0x118/0x150 mm/page_alloc.c:4288
RSP: 0018:ffff8801d43af700 EFLAGS: 00010203
RAX: 0000000000000000 RBX: ffffea000750ebc0 RCX: 0000000000000000
RDX: 0000000000000f47 RSI: ffffc900033f6000 RDI: ffffed003a875ed0
RBP: ffff8801d43af790 R08: 1ffff1003a875e04 R09: 0000000000000000
R10: dffffc0000000000 R11: 0000000000000000 R12: 1ffff1003a875ee1
R13: 1ffff1003a875ee5 R14: 0000000000000000 R15: ffff8801d43af768
FS: 00007ff1eaddf700(0000) GS:ffff8801db500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000202f0fc8 CR3: 00000001b29a0000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
free_pages+0x51/0x90 mm/page_alloc.c:4302
blkcipher_walk_done+0x767/0xde0 crypto/blkcipher.c:141
encrypt+0x50a/0xaf0 crypto/salsa20_generic.c:208
skcipher_crypt_blkcipher crypto/skcipher.c:619 [inline]
skcipher_decrypt_blkcipher+0x213/0x310 crypto/skcipher.c:637
crypto_skcipher_decrypt include/crypto/skcipher.h:463 [inline]
_skcipher_recvmsg crypto/algif_skcipher.c:133 [inline]
skcipher_recvmsg+0xb06/0xf30 crypto/algif_skcipher.c:164
sock_recvmsg_nosec net/socket.c:805 [inline]
sock_recvmsg+0xc9/0x110 net/socket.c:812
___sys_recvmsg+0x29b/0x630 net/socket.c:2207
__sys_recvmsg+0xe2/0x210 net/socket.c:2252
SYSC_recvmsg net/socket.c:2264 [inline]
SyS_recvmsg+0x2d/0x50 net/socket.c:2259
entry_SYSCALL_64_fastpath+0x1f/0x96
RIP: 0033:0x4529d9
RSP: 002b:00007ff1eaddec58 EFLAGS: 00000212 ORIG_RAX: 000000000000002f
RAX: ffffffffffffffda RBX: 0000000000758020 RCX: 00000000004529d9
RDX: 0000000000012163 RSI: 0000000020d63fc8 RDI: 0000000000000014
RBP: 0000000000000086 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000212 R12: 0000000000000000
R13: 0000000000a6f7ff R14: 00007ff1eaddf9c0 R15: 0000000000000000
Code: 20 08 00 00 00 00 48 83 c4 68 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 29
f5 ff ff eb cf 48 c7 c6 80 2a 30 85 48 89 df e8 38 61 0c 00 <0f> 0b 4c 89
ef 89 b5 74 ff ff ff e8 78 f1 19 00 8b b5 74 ff ff
RIP: put_page_testzero include/linux/mm.h:482 [inline] RSP: ffff8801d43af700
RIP: __free_pages+0x118/0x150 mm/page_alloc.c:4288 RSP: ffff8801d43af700
---[ end trace 09af96c7bb27df21 ]---


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
Please credit me with: Reported-by: syzbot <syzk...@googlegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is committed, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
config.txt
raw.log

Eric Biggers

unread,
Nov 29, 2017, 12:00:51 AM11/29/17
to syzbot, da...@davemloft.net, her...@gondor.apana.org.au, linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com
#syz dup: WARNING: suspicious RCU usage (3)
Reply all
Reply to author
Forward
0 new messages