Messages in this thread | | | Date | Fri, 11 Nov 2022 11:09:16 +0100 | Subject | Re: BUG: kworker + systemd-udevd memory leaks found in 6.1.0-rc4 | From | Mirsad Goran Todorovac <> |
| |
On 10.11.2022. 9:28, Thorsten Leemhuis wrote:
> This bug is confirmed in 6.1-rc4, among the "thermald" and "systemd-dev" > kernel memory leaks, potentially exposing race conditions or other more > serious bug. >> Maybe, but that sadly is also true for a lot of other known issues, for >> example those in this quite long list: >> https://syzkaller.appspot.com/upstream#open >> >> It would help if you could pinpoint the problem, then we know who should >> look into this. You CCed me and the regression list, so I assume it's a >> regression. Hence: Could you try to bisect it? >> >> Ciao, Thorsten
Hi, Thorsten!
I am taking this task, however, it might not be a relatively easy bisect like the past two or three (probably were beginner's luck).
It appears to predate 4.19:
$ head -13 memleak-kwork-4.19.0-08-84df9525b0c2-memlk-menu-al.log unreferenced object 0xffff8ff917c79c40 (size 16): comm "kworker/u12:4", pid 422, jiffies 4294672757 (age 380.342s) hex dump (first 16 bytes): 6d 65 6d 73 74 69 63 6b 30 00 00 00 00 00 00 00 memstick0....... backtrace: [<000000004f7bc99c>] kobject_set_name_vargs+0x1e/0x90 [<00000000f00ab312>] dev_set_name+0x57/0x70 [<000000001fd9518e>] memstick_check+0x99/0x330 [memstick] [<000000008c797991>] process_one_work+0x1a7/0x3a0 [<00000000405c5133>] worker_thread+0x30/0x390 [<0000000060a58c2e>] kthread+0x112/0x130 [<000000004b138871>] ret_from_fork+0x35/0x40 [<0000000029f3e0aa>] 0xffffffffffffffff $
Cheers, Mirsad
P.S. This mail is re-sent because of forgetting to set "Plain text" mode to Thunderbird.
-- Mirsad Todorovac System engineer Faculty of Graphic Arts | Academy of Fine Arts University of Zagreb Republic of Croatia, the European Union -- Sistem inženjer Grafički fakultet | Akademija likovnih umjetnosti Sveučilište u Zagrebu
| |