rt kernel BUG: using smp_processor_id() in preemptible code modprobe
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
zhao.shuai |
Bug Description
Brief Description
-----------------
Boot an rt load on hardware with a c6xx (qat) device present. As soon as the device goes enabled, bug reports start happening:
[ 20.065605] c6xx 0000:3f:00.0: enabling device (0140 -> 0142)
[ 20.071492] BUG: using smp_processor_id() in preemptible [00000000] code: systemd-udevd/1026
[ 20.071515] caller is qat_rsa_
[ 20.071516] BUG: using smp_processor_id() in preemptible [00000000] code: systemd-udevd/1032
[ 20.071518] CPU: 16 PID: 1026 Comm: systemd-udevd Tainted: G O --------- - - 4.18.0-
[ 20.071526] caller is qat_rsa_
[ 20.071526] Hardware name: Intel Corporation S2600WFQ/S2600WFQ, BIOS SE5C620.
[ 20.071527] Call Trace:
[ 20.071532] dump_stack+
[ 20.071537] check_preemptio
[ 20.071542] qat_rsa_
[ 20.071548] crypto_
[ 20.071549] crypto_
[ 20.071553] pkcs1pad_
[ 20.071555] crypto_
[ 20.071557] crypto_
[ 20.071560] public_
[ 20.071566] ? keyring_
[ 20.071567] ? key_default_
[ 20.071569] ? find_asymmetric
[ 20.071572] pkcs7_validate_
[ 20.071578] verify_
[ 20.071584] mod_verify_
[ 20.071587] load_module+
[ 20.071591] ? map_vm_
[ 20.071593] ? __vmalloc_
[ 20.071594] ? __do_sys_
[ 20.071596] __do_sys_
[ 20.071601] do_syscall_
[ 20.071604] entry_SYSCALL_
[ 20.071605] RIP: 0033:0x7fe1d70264ea
[ 20.071607] Code: 48 8b 0d a9 79 2c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 76 79 2c 00 f7 d8 64 89 01 48
[ 20.071608] RSP: 002b:00007ffdb1
[ 20.071609] RAX: ffffffffffffffda RBX: 0000562d0ecb3b80 RCX: 00007fe1d70264ea
[ 20.071611] BUG: using smp_processor_id() in preemptible [00000000] code: systemd-udevd/1035
[ 20.071612] RDX: 00007fe1d7941039 RSI: 0000000000038f4c RDI: 0000562d0f4e4ac0
[ 20.071618] caller is qat_rsa_
[ 20.071619] RBP: 00007fe1d7941039 R08: 0000000000000000 R09: 0000562d0ecb85a0
[ 20.071619] R10: 0000562d0ecb8500 R11: 0000000000000246 R12: 0000562d0f4e4ac0
[ 20.071620] R13: 0000562d0ecb7e30 R14: 0000000000020000 R15: 0000000000000000
The kernel logs are flooded with such entries which happen every time a modprobe or anything else does a load_module. The module loading works but the code is evidently violating the use of smp_processor_id() with respect to preemptibility.
Severity
--------
Major: usable but *kernel* log flooding with BUG reports is visibly bad, not minor imo
Workaround
----------
Not needed. Just hold your nose.
Not bothering with the rest of the template, everything you need is above.
Changed in starlingx: | |
assignee: | Austin Sun (sunausti) → zhao.shuai (zhao.shuai.neusoft) |
stx.4.0 / high priority - issue w/ 4.18 kernel (rt)
Assigning to distro.other PL to assign to the appropriate dev prime