[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <87f35e58-f45c-1209-3eb6-9c2a69880dfd@gmail.com>
Date: Mon, 2 Nov 2020 05:02:04 +0100
From: Jacek <wampir990@...il.com>
To: lkrg-users@...ts.openwall.com
Subject: P_LKRG error in Linux 5.9.3
HI
LKRG version:
# root ~> modinfo p_lkrg
filename: /lib/modules/5.9.3-g1/extra/p_lkrg.ko
license: GPL v2
description: pi3's Linux kernel Runtime Guard
author: Adam 'pi3' Zabrocki (http://pi3.com.pl)
srcversion: EEC95B0840D6CC7AA27D2E3
depends:
retpoline: Y
name: p_lkrg
vermagic: 5.9.3-g1 SMP preempt mod_unload modversions
RANDSTRUCT_PLUGIN_366bedefd89976f1b4c46144945391fda92f7f7735ea0773c232d89a1537a832
sig_id: PKCS#7
signer: domek.cert
sig_key: 9B:90:A7:9D:13:60:77:B8
sig_hashalgo: sha512
The following message appears periodically in logs and tty consoles:
[ 1753.134389] BUG: workqueue leaked lock or atomic:
kworker/u8:0/0x00000001/1102
last function: p_check_integrity [p_lkrg]
[ 1753.134397] CPU: 3 PID: 1102 Comm: kworker/u8:0 Tainted: G WC
O T 5.9.3-g1 #2
[ 1753.134400] Hardware name: Gigabyte Technology Co., Ltd.
Z97-D3H/Z97-D3H-CF, BIOS F9 09/18/2015
[ 1753.134408] Workqueue: events_unbound p_check_integrity [p_lkrg]
[ 1753.134411] Call Trace:
[ 1753.134422] dump_stack+0x57/0x70
[ 1753.134430] process_one_work.cold+0x2b/0x30
[ 1753.134436] ? process_one_work+0x2e0/0x2e0
[ 1753.134440] worker_thread+0x4b/0x390
[ 1753.134445] ? process_one_work+0x2e0/0x2e0
[ 1753.134449] kthread+0x118/0x160
[ 1753.134453] ? kthread_park+0x80/0x80
[ 1753.134458] ret_from_fork+0x22/0x30
[ 1753.134465] BUG: scheduling while atomic: kworker/u8:0/1102/0x00000002
[ 1753.134467] Modules linked in: p_lkrg(O) r8188eu(C) lib80211
[ 1753.134473] Preemption disabled at:
[ 1753.134480] [<ffffffffc0423328>] p_check_integrity+0xf8/0x1140 [p_lkrg]
[ 1753.134484] CPU: 3 PID: 1102 Comm: kworker/u8:0 Tainted: G WC
O T 5.9.3-g1 #2
[ 1753.134486] Hardware name: Gigabyte Technology Co., Ltd.
Z97-D3H/Z97-D3H-CF, BIOS F9 09/18/2015
[ 1753.134489] Workqueue: 0x0 (events_unbound)
[ 1753.134492] Call Trace:
[ 1753.134497] dump_stack+0x57/0x70
[ 1753.134503] __schedule_bug.cold+0x83/0x91
[ 1753.134509] __schedule+0x5fc/0x6c0
[ 1753.134514] ? process_one_work+0x2e0/0x2e0
[ 1753.134518] schedule+0x44/0xe0
[ 1753.134522] worker_thread+0xc1/0x390
[ 1753.134527] ? process_one_work+0x2e0/0x2e0
[ 1753.134530] kthread+0x118/0x160
[ 1753.134534] ? kthread_park+0x80/0x80
[ 1753.134537] ret_from_fork+0x22/0x30
[ 1768.493370] BUG: workqueue leaked lock or atomic:
kworker/u8:0/0x00000001/1102
last function: p_check_integrity [p_lkrg]
[ 1768.493378] CPU: 0 PID: 1102 Comm: kworker/u8:0 Tainted: G WC
O T 5.9.3-g1 #2
[ 1768.493381] Hardware name: Gigabyte Technology Co., Ltd.
Z97-D3H/Z97-D3H-CF, BIOS F9 09/18/2015
[ 1768.493390] Workqueue: events_unbound p_check_integrity [p_lkrg]
[ 1768.493393] Call Trace:
[ 1768.493405] dump_stack+0x57/0x70
[ 1768.493414] process_one_work.cold+0x2b/0x30
[ 1768.493420] ? process_one_work+0x2e0/0x2e0
[ 1768.493424] worker_thread+0x4b/0x390
[ 1768.493430] ? process_one_work+0x2e0/0x2e0
[ 1768.493434] kthread+0x118/0x160
[ 1768.493438] ? kthread_park+0x80/0x80
[ 1768.493443] ret_from_fork+0x22/0x30
[ 1768.493451] BUG: scheduling while atomic: kworker/u8:0/1102/0x00000002
[ 1768.493453] Modules linked in: p_lkrg(O) r8188eu(C) lib80211
[ 1768.493459] Preemption disabled at:
[ 1768.493467] [<ffffffffc0423328>] p_check_integrity+0xf8/0x1140 [p_lkrg]
[ 1768.493471] CPU: 0 PID: 1102 Comm: kworker/u8:0 Tainted: G WC
O T 5.9.3-g1 #2
[ 1768.493473] Hardware name: Gigabyte Technology Co., Ltd.
Z97-D3H/Z97-D3H-CF, BIOS F9 09/18/2015
[ 1768.493477] Workqueue: 0x0 (events_unbound)
[ 1768.493480] Call Trace:
[ 1768.493485] dump_stack+0x57/0x70
[ 1768.493491] __schedule_bug.cold+0x83/0x91
[ 1768.493497] __schedule+0x5fc/0x6c0
[ 1768.493503] ? process_one_work+0x2e0/0x2e0
[ 1768.493507] schedule+0x44/0xe0
[ 1768.493512] worker_thread+0xc1/0x390
[ 1768.493517] ? process_one_work+0x2e0/0x2e0
[ 1768.493521] kthread+0x118/0x160
[ 1768.493524] ? kthread_park+0x80/0x80
[ 1768.493528] ret_from_fork+0x22/0x30
Cheers
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
