From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>,
linux-kernel@vger.kernel.org
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
Tejun Heo <tj@kernel.org>, Florian Mickler <florian@mickler.org>,
systemd-devel@lists.freedesktop.org
Subject: Re: BUG: kworker + systemd-udevd memory leaks found in 6.1.0-rc4
Date: Thu, 10 Nov 2022 09:28:33 +0100 [thread overview]
Message-ID: <3f1721d6-e5d9-8861-4e3c-802a711e71da@leemhuis.info> (raw)
In-Reply-To: <a6b76ce0-0fb3-4434-cc3e-ab6f39fb1cf9@alu.unizg.hr>
On 10.11.22 05:57, Mirsad Goran Todorovac wrote:
> On 04. 11. 2022. 11:40, Mirsad Goran Todorovac 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
next prev parent reply other threads:[~2022-11-10 8:28 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 [this message]
2022-11-11 8:44 ` Mirsad Goran Todorovac
2022-11-11 10:09 ` Mirsad Goran Todorovac
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=3f1721d6-e5d9-8861-4e3c-802a711e71da@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=florian@mickler.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=regressions@lists.linux.dev \
--cc=systemd-devel@lists.freedesktop.org \
--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).