From: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
linux-kernel@vger.kernel.org
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
Tejun Heo <tj@kernel.org>, Florian Mickler <florian@mickler.org>
Subject: Re: BUG: kworker + systemd-udevd memory leaks found in 6.1.0-rc4
Date: Fri, 11 Nov 2022 11:09:16 +0100 [thread overview]
Message-ID: <7d2c05b9-ca22-8cde-216b-b418da6c7428@alu.unizg.hr> (raw)
In-Reply-To: <96903e75-63b4-8c59-6c78-0e641b1fc2c5@alu.unizg.hr>
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
next prev parent reply other threads:[~2022-11-11 10:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 10:40 BUG: kworker memory leak found in 6.1.0-rc3 Mirsad Goran Todorovac
2022-11-10 4:57 ` BUG: kworker + systemd-udevd memory leaks found in 6.1.0-rc4 Mirsad Goran Todorovac
2022-11-10 8:28 ` Thorsten Leemhuis
2022-11-11 8:44 ` Mirsad Goran Todorovac
2022-11-11 10:09 ` Mirsad Goran Todorovac [this message]
2022-11-10 9:20 ` Greg KH
2022-11-17 15:34 ` Mirsad Goran Todorovac
2022-11-29 3:35 ` Mirsad Goran Todorovac
2022-11-29 8:36 ` Greg KH
2022-11-29 9:59 ` Mirsad Goran Todorovac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d2c05b9-ca22-8cde-216b-b418da6c7428@alu.unizg.hr \
--to=mirsad.todorovac@alu.unizg.hr \
--cc=florian@mickler.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).