[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <180b1a4fb9cf78c8905f275e0373e009224d4639.camel@linux.intel.com>
Date: Wed, 26 Oct 2022 15:48:35 -0700
From: srinivas pandruvada <srinivas.pandruvada@...ux.intel.com>
To: Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>,
LKML <linux-kernel@...r.kernel.org>, rjw@...ysocki.net
Cc: regressions@...ts.linux.dev, regressions@...mhuis.info,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
Robert Moore <robert.moore@...el.com>, devel@...ica.org
Subject: Re: BUG: bisected: thermald regression (MEMLEAK) in commit
c7ff29763989bd09c433f73fae3c1e1c15d9cda4
On Wed, 2022-10-26 at 19:52 +0200, Mirsad Goran Todorovac wrote:
> Dear all,
>
> On 24. 10. 2022. 20:56, Mirsad Goran Todorovac wrote:
> > On 24. 10. 2022. 20:39, srinivas pandruvada wrote:
> >
> > > > Thank you for the patch. Unfortunately, when applied to v6.0.3
> > > > it
> > > > didn't
> > > > fix the issue.
> > > Thanks for the test. I copied to acpi and acpica mailing list.
> > > Someone
> > > can tell us what is this call doing wrong here.
>
> I have worse news: after every
>
> # systemctl stop thermald
> # systemctl start thermald
>
> the number of leaks increases by one allocated block (apparently 80
> bytes). The effect appears to be
> cummulative.
>
> Please find the results of the MEMLEAK scan in the attachment.
>
> In theory, motivated adversary could theoretically exhaust i.e. 8
> GiB
> in a loop of 10 million thermald stops/starts,
Of course it needs to be debugged. To start/stop systemctl service you
need root access. If you have root access, there are other worse things
can be done.
Thanks,
Srinivas
> on my laptop and 2 sec for stop+start, it would be approx. 230 days.
>
> Hope this helps.
>
> Mirsad
>
> --
>
> Mirsad Goran Todorovac
> Sistem inženjer
> Grafički fakultet | Akademija likovnih umjetnosti
> Sveučilište u Zagrebu
Powered by blists - more mailing lists