From: syzbot <syzbot+675c45cea768b3819803@syzkaller.appspotmail.com>
To: bp@alien8.de, davem@davemloft.net, herbert@gondor.apana.org.au,
hpa@zytor.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: general protection fault in gcmaes_crypt_by_sg (2)
Date: Sat, 14 Dec 2019 17:11:08 -0800 [thread overview]
Message-ID: <00000000000011c6720599b3c5ae@google.com> (raw)
In-Reply-To: <000000000000ca89a80598db0ae5@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: 1d1997db Revert "nfp: abm: fix memory leak in nfp_abm_u32_..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1051508ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=cef1fd5032faee91
dashboard link: https://syzkaller.appspot.com/bug?extid=675c45cea768b3819803
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10d635a6e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=114489a9e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+675c45cea768b3819803@syzkaller.appspotmail.com
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 183 Comm: kworker/u4:3 Not tainted 5.5.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: pencrypt_parallel padata_parallel_worker
RIP: 0010:scatterwalk_start include/crypto/scatterwalk.h:68 [inline]
RIP: 0010:scatterwalk_pagedone include/crypto/scatterwalk.h:93 [inline]
RIP: 0010:scatterwalk_done include/crypto/scatterwalk.h:101 [inline]
RIP: 0010:gcmaes_crypt_by_sg.constprop.0+0x1035/0x1aa0
arch/x86/crypto/aesni-intel_glue.c:786
Code: e8 90 e8 52 02 48 89 84 24 a8 00 00 00 48 83 c0 08 48 89 c2 48 89 84
24 90 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <0f> b6 04 02 84
c0 74 08 3c 03 0f 8e 30 09 00 00 48 8b 84 24 a8 00
RSP: 0018:ffffc900012e7750 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000004000 RCX: ffffffff838cc029
RDX: 0000000000000001 RSI: ffffffff838cc07b RDI: 0000000000000007
RBP: ffffc900012e7b20 R08: ffff8880a8c46080 R09: 000000000000000d
R10: ffff8880a3efe660 R11: 00000000000000d0 R12: 0000000000004000
R13: 0000000000000000 R14: ffff8880a3efe300 R15: 0000000000004000
FS: 0000000000000000(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff220a2d90 CR3: 00000000a8d5d000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
gcmaes_encrypt arch/x86/crypto/aesni-intel_glue.c:840 [inline]
generic_gcmaes_encrypt+0x10d/0x160 arch/x86/crypto/aesni-intel_glue.c:1019
crypto_aead_encrypt+0xaf/0xf0 crypto/aead.c:94
simd_aead_encrypt+0x1a6/0x2b0 crypto/simd.c:335
crypto_aead_encrypt+0xaf/0xf0 crypto/aead.c:94
pcrypt_aead_enc+0x19/0x80 crypto/pcrypt.c:76
padata_parallel_worker+0x28f/0x470 kernel/padata.c:81
process_one_work+0x9af/0x1740 kernel/workqueue.c:2264
worker_thread+0x98/0xe40 kernel/workqueue.c:2410
kthread+0x361/0x430 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
Modules linked in:
------------[ cut here ]------------
WARNING: CPU: 1 PID: 183 at kernel/locking/mutex.c:1419
mutex_trylock+0x279/0x2f0 kernel/locking/mutex.c:1427
next prev parent reply other threads:[~2019-12-15 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 6:37 general protection fault in gcmaes_crypt_by_sg (2) syzbot
2019-12-15 1:11 ` syzbot [this message]
2020-02-19 11:48 ` syzbot
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=00000000000011c6720599b3c5ae@google.com \
--to=syzbot+675c45cea768b3819803@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.