[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220527165429.GJ11007@blackbody.suse.cz>
Date: Fri, 27 May 2022 18:54:29 +0200
From: Michal Koutný <mkoutny@...e.com>
To: Tadeusz Struk <tadeusz.struk@...aro.org>
Cc: Tejun Heo <tj@...nel.org>, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, Zefan Li <lizefan.x@...edance.com>,
Johannes Weiner <hannes@...xchg.org>,
Bui Quang Minh <minhquangbui99@...il.com>
Subject: Re: [PATCH 2/2] cgroup: Use separate work structs on css release path
Hello Tadeusz.
On Fri, May 27, 2022 at 09:39:20AM -0700, Tadeusz Struk <tadeusz.struk@...aro.org> wrote:
> As far as I can see we are trying to test the same thing suggested by Tejun.
> I just sent a test request to try this:
> https://github.com/tstruk/linux/commit/master
Yup, I've added few more prints to get more fine-grained resolution.
Also, I decided to use ftrace printk not to interfere with timing too
much (due to the original race hypothesis).
> Let me know if you have any more tests to run and I will hold off until
> you are done.
My latest attempt is [1] (tip 5500e05d82fd5b5db2203eedb3f786857d3ccbea).
So far, I'm not convinced, I extract the complete ftrace buffer from the
syzbot runs, so I'm not drawing any conclusions from the traces I've
got. I'm not going to continue today. You may have more luck with your
plain printk (if it's just imbalance and it avoids printk locking
sensitive paths).
HTH,
Michal
[1] https://github.com/Werkov/linux/tree/cgroup-ml/css-lifecycle-b2
Powered by blists - more mailing lists