[FS#3070] kmod-cryptodev: WARNING: possible circular locking dependency detected

OpenWrt Bugs openwrt-bugs at lists.openwrt.org
Tue Mar 2 21:15:51 GMT 2021


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#3070 - kmod-cryptodev: WARNING: possible circular locking dependency detected
User who did this - michael-dev (michael-dev)

----------
I'm seeing the same on a custom OpenWRT build:

[   45.669944] ======================================================
[   45.676115] WARNING: possible circular locking dependency detected
[   45.682292] 5.4.99 #0 Not tainted
[   45.685598] ------------------------------------------------------
[   45.691772] nrpe/3560 is trying to acquire lock:
[   45.696382] ef68f23c (&pcr->fcrypt.sem){+.+.}, at: crypto_get_session_by_sid+0x38/0xc4 [cryptodev]
[   45.705360]
[   45.705360] but task is already holding lock:
[   45.711184] ef68fa3c (&ses_new->sem){+.+.}, at: crypto_get_session_by_sid+0xa8/0xc4 [cryptodev]
[   45.719884]
[   45.719884] which lock already depends on the new lock.
[   45.719884]
[   45.728052]
[   45.728052] the existing dependency chain (in reverse order) is:
[   45.735526]
[   45.735526] -> #1 (&ses_new->sem){+.+.}:
[   45.740942]        __mutex_lock+0x94/0x84c
[   45.745037]        crypto_get_session_by_sid+0xa8/0xc4 [cryptodev]
[   45.751213]        cryptodev_ioctl+0xa4/0x9c8 [cryptodev]
[   45.756609]        do_vfs_ioctl+0xc4/0x948
[   45.760698]        ksys_ioctl+0x50/0xbc
[   45.764535]        ret_from_syscall+0x0/0x38
[   45.768797]
[   45.768797] -> #0 (&pcr->fcrypt.sem){+.+.}:
[   45.774467]        __lock_acquire+0x1004/0x2100
[   45.778992]        lock_acquire+0xe0/0x1ec
[   45.783085]        __mutex_lock+0x94/0x84c
[   45.787179]        crypto_get_session_by_sid+0x38/0xc4 [cryptodev]
[   45.793356]        cryptodev_ioctl+0x538/0x9c8 [cryptodev]
[   45.798835]        do_vfs_ioctl+0xc4/0x948
[   45.802925]        ksys_ioctl+0x50/0xbc
[   45.806756]        ret_from_syscall+0x0/0x38
[   45.811017]
[   45.811017] other info that might help us debug this:
[   45.811017]
[   45.819012]  Possible unsafe locking scenario:
[   45.819012]
[   45.824923]        CPU0                    CPU1
[   45.829444]        ----                    ----
[   45.833965]   lock(&ses_new->sem);
[   45.837360]                                lock(&pcr->fcrypt.sem);
[   45.843534]                                lock(&ses_new->sem);
[   45.849446]   lock(&pcr->fcrypt.sem);
[   45.853102]
[   45.853102]  *** DEADLOCK ***
[   45.853102]
[   45.859015] 1 lock held by nrpe/3560:
[   45.862668]  #0: ef68fa3c (&ses_new->sem){+.+.}, at: crypto_get_session_by_sid+0xa8/0xc4 [cryptodev]
[   45.871803]
[   45.871803] stack backtrace:
[   45.876156] CPU: 1 PID: 3560 Comm: nrpe Not tainted 5.4.99 #0
[   45.881894] Call Trace:
[   45.884342] [ef5b7ba8] [c06844a8] dump_stack+0xb0/0x124 (unreliable)
[   45.890695] [ef5b7bc8] [c0092404] check_noncircular+0x16c/0x1f4
[   45.896611] [ef5b7c08] [c0094b5c] __lock_acquire+0x1004/0x2100
[   45.902439] [ef5b7cc8] [c00964ac] lock_acquire+0xe0/0x1ec
[   45.907838] [ef5b7d08] [c06a429c] __mutex_lock+0x94/0x84c
[   45.913236] [ef5b7d78] [f13d53e4] crypto_get_session_by_sid+0x38/0xc4 [cryptodev]
[   45.920716] [ef5b7d98] [f13d59a8] cryptodev_ioctl+0x538/0x9c8 [cryptodev]
[   45.927500] [ef5b7ec8] [c01c5028] do_vfs_ioctl+0xc4/0x948
[   45.932894] [ef5b7f18] [c01c58fc] ksys_ioctl+0x50/0xbc
[   45.938030] [ef5b7f38] [c0012298] ret_from_syscall+0x0/0x38
[   45.943599] --- interrupt: c01 at 0xfb2aa74

Though, no actual deadlock occurs.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3070#comment9448

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the openwrt-bugs mailing list