From: Mark Brown <broonie@kernel.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Tejun Heo <tj@kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] cgroup1: fix leaked context root causing sporadic NULL deref in LTP
Date: Thu, 1 Jul 2021 13:11:33 +0100 [thread overview]
Message-ID: <20210701121133.GA4641@sirena.org.uk> (raw)
In-Reply-To: <696dc58209707ce364616430673998d0124a9a31.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
On Wed, Jun 30, 2021 at 11:31:06PM +0100, Richard Purdie wrote:
> Out of interest are you also seeing the proc01 test hang on a non-blocking
> read of /proc/kmsg periodically?
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14460
> I've not figured out a way to reproduce it at will yet and it seems strace
I've been talking to Ross, he mentioned it but no, rings no bells.
> was enough to unblock it. It seems arm specific.
If it's 32 bit I'm not really doing anything that looks at it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-01 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 12:51 [PATCH] cgroup1: fix leaked context root causing sporadic NULL deref in LTP Paul Gortmaker
2021-06-16 15:23 ` Tejun Heo
2021-06-30 16:10 ` Mark Brown
2021-06-30 22:31 ` Richard Purdie
2021-07-01 12:11 ` Mark Brown [this message]
2021-07-01 12:43 ` Richard Purdie
2021-07-12 17:34 ` Tejun Heo
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=20210701121133.GA4641@sirena.org.uk \
--to=broonie@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=paul.gortmaker@windriver.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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