linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+cd50d1708db841432d8a@syzkaller.appspotmail.com>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: BUG: unable to handle kernel paging request in aead_geniv_alloc
Date: Sun, 18 Nov 2018 11:23:03 -0800	[thread overview]
Message-ID: <0000000000004ae11b057af5543f@google.com> (raw)

Hello,

syzbot found the following crash on:

HEAD commit:    9c549a6b0573 selftests: add explicit test for multiple con..
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13a46f7b400000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d86f24333880b605
dashboard link: https://syzkaller.appspot.com/bug?extid=cd50d1708db841432d8a
compiler:       gcc (GCC) 8.0.1 20180413 (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+cd50d1708db841432d8a@syzkaller.appspotmail.com

BUG: unable to handle kernel paging request at fffffffffffffff0
PGD 946d067 P4D 946d067 PUD 946f067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 9032 Comm: cryptomgr_probe Not tainted 4.20.0-rc2+ #300
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS  
Google 01/01/2011
kobject: 'loop1' (00000000f780ed70): kobject_uevent_env
RIP: 0010:aead_geniv_alloc+0x2de/0x780 crypto/aead.c:240
Code: 00 00 fc ff df 49 8d 7c 24 f0 48 89 fa 48 c1 ea 03 0f b6 14 02 48 89  
f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 ea 03 00 00 <45> 8b 74 24 f0  
bf 07 00 00 00 48 c7 c3 ea ff ff ff 44 89 f6 e8 59
RSP: 0018:ffff8881946b7e40 EFLAGS: 00010246
kobject: 'loop1' (00000000f780ed70): fill_kobj_path: path  
= '/devices/virtual/block/loop1'
RAX: 0000000000000003 RBX: 0000000000000000 RCX: ffffffff835c1711
RDX: 0000000000000000 RSI: ffffffff835c171e RDI: fffffffffffffff0
RBP: ffff8881946b7e80 R08: ffff8881975da540 R09: ffffed10328d6fa3
R10: ffffed10328d6fa3 R11: 0000000000000003 R12: 0000000000000000
R13: ffff8881d3ee66b0 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8881daf00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff0 CR3: 000000019a8d0000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
  seqiv_aead_create crypto/seqiv.c:149 [inline]
  seqiv_create+0x99/0x290 crypto/seqiv.c:190
  cryptomgr_probe+0x6d/0x280 crypto/algboss.c:75
  kthread+0x35a/0x440 kernel/kthread.c:246
  ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
Modules linked in:
CR2: fffffffffffffff0
---[ end trace e6ac52e6f5849122 ]---
RIP: 0010:aead_geniv_alloc+0x2de/0x780 crypto/aead.c:240
Code: 00 00 fc ff df 49 8d 7c 24 f0 48 89 fa 48 c1 ea 03 0f b6 14 02 48 89  
f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 ea 03 00 00 <45> 8b 74 24 f0  
bf 07 00 00 00 48 c7 c3 ea ff ff ff 44 89 f6 e8 59
RSP: 0018:ffff8881946b7e40 EFLAGS: 00010246
RAX: 0000000000000003 RBX: 0000000000000000 RCX: ffffffff835c1711
RDX: 0000000000000000 RSI: ffffffff835c171e RDI: fffffffffffffff0
RBP: ffff8881946b7e80 R08: ffff8881975da540 R09: ffffed10328d6fa3
R10: ffffed10328d6fa3 R11: 0000000000000003 R12: 0000000000000000
R13: ffff8881d3ee66b0 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8881daf00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff0 CR3: 000000019a8d0000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 syzkaller@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with  
syzbot.

                 reply	other threads:[~2018-11-18 19:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0000000000004ae11b057af5543f@google.com \
    --to=syzbot+cd50d1708db841432d8a@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;
as well as URLs for NNTP newsgroup(s).