From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+6e5e7b23f2428f284e345f1855d18cb16c46a44e@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: kernel BUG at ./include/linux/mm.h:LINE! (2)
Date: Tue, 28 Nov 2017 21:00:48 -0800 [thread overview]
Message-ID: <20171129050048.GE24001@zzz.localdomain> (raw)
In-Reply-To: <001a1141c43aef50d6055f0e4899@google.com>
On Tue, Nov 28, 2017 at 09:24:01AM -0800, syzbot wrote:
> 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
#syz dup: WARNING: suspicious RCU usage (3)
parent reply other threads:[~2017-11-29 5:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <001a1141c43aef50d6055f0e4899@google.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171129050048.GE24001@zzz.localdomain \
--to=ebiggers3@gmail.com \
--cc=bot+6e5e7b23f2428f284e345f1855d18cb16c46a44e@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®