Project

General

Profile

Actions

Bug #3370

open

panic: crypto: malloc limit exceeded

Added by mneumann 5 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Crypto
Target version:
Start date:
06/14/2024
Due date:
% Done:

0%

Estimated time:

Description

This bug is reproducible (I got this 4 times within one hour), when "tcplay -i -d /dev/da8" is used and then I open up "mutt" (I guess any SSL connection would trigger the bug):

/var/crash # vmstat -M vmcore.0 -N kern.0 -m | grep " crypto "
Type Count MemUse SlabUse Limit Requests
crypto 2.63M 756M 0 756M 5.25M

(kgdb) bt
#0 _get_mycpu () at ./machine/thread.h:69
#1 panic (fmt=fmt@entry=0xffffffff80d0c09d "%s: malloc limit exceeded")
at /usr/src/sys/kern/kern_shutdown.c:868
#2 0xffffffff806582e9 in _kmalloc (size=260, type=0xffffffff81132bc0 <M_CRYPTO_DATA>,
flags=<optimized out>, flags@entry=258) at /usr/src/sys/kern/kern_slaballoc.c:877
#3 0xffffffff80a07491 in __kmalloc (_flags=258, _type=<optimized out>, _size=<optimized out>)
at /usr/src/sys/sys/malloc.h:287
#4 swcr_newsession (dev=<optimized out>, sid=<optimized out>, cri=0xfffff802035357b8)
at /usr/src/sys/opencrypto/cryptosoft.c:903
#5 0xffffffff80a031d2 in CRYPTODEV_NEWSESSION (cri=0xfffff802035357b8, sid=0xfffff802035356e4,
dev=0xfffff800cf2640a0) at ./cryptodev_if.h:24
#6 crypto_newsession (sid=sid@entry=0xfffff80203535780, cri=0xfffff802035357b8,
crid=<optimized out>) at /usr/src/sys/opencrypto/crypto.c:418
#7 0xffffffff80a05e9a in cryptof_ioctl (fp=<optimized out>, cmd=3224396645,
data=0xfffff80203535878 "\027", cred=<optimized out>, msg=<optimized out>)
at /usr/src/sys/opencrypto/cryptodev.c:306
#8 0xffffffff806ad3fa in fo_ioctl (msg=<optimized out>, cred=<optimized out>,
data=<optimized out>, com=<optimized out>, fp=0xfffff801ea7cf400)
at /usr/src/sys/sys/file2.h:84
#9 mapped_ioctl (fd=<optimized out>, com=<optimized out>, uspc_data=<optimized out>, map=0x0,
msg=<optimized out>) at /usr/src/sys/kern/sys_generic.c:717
#10 0xffffffff80be9dce in syscall2 (frame=0xfffff802035359f8)
at /usr/src/sys/platform/pc64/x86_64/trap.c:1284
#11 0xffffffff80bace8d in Xfast_syscall () at /usr/src/sys/platform/pc64/x86_64/exception.S:448
#12 0x000000000000002b in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)


Related issues 2 (2 open0 closed)

Related to Bug #3311: TrueCrypt support may cause kernel crashNew01/30/2022

Actions
Related to Bug #3371: Installer fails to encrypt diskNew08/10/2024

Actions
Actions #1

Updated by mneumann about 1 month ago

  • Related to Bug #3311: TrueCrypt support may cause kernel crash added
Actions #2

Updated by mneumann about 1 month ago

  • Related to Bug #3371: Installer fails to encrypt disk added
Actions

Also available in: Atom PDF