Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: ovidiu.panait@windriver.com
Cc: stable@vger.kernel.org, qyousef@layalina.io
Subject: Re: [PATCH 5.10 0/4] cgroup: Fix suspicious rcu_dereference_check() warning
Date: Tue, 3 Oct 2023 07:32:05 -0400	[thread overview]
Message-ID: <ZRv7tW8/+g3JTOnS@sashalap> (raw)
In-Reply-To: <20230929131418.821640-1-ovidiu.panait@windriver.com>

On Fri, Sep 29, 2023 at 04:14:14PM +0300, ovidiu.panait@windriver.com wrote:
>Backport commit f2aa197e4794 ("cgroup: Fix suspicious rcu_dereference_check()
>usage warning") and its dependencies to get rid of this warning.
>
>Andrey Ryabinin (1):
>  sched/cpuacct: Fix user/system in shown cpuacct.usage*
>
>Chengming Zhou (3):
>  sched/cpuacct: Fix charge percpu cpuusage
>  sched/cpuacct: Optimize away RCU read lock
>  cgroup: Fix suspicious rcu_dereference_check() usage warning

I've queued up this and the 5.15 fix, thanks!

-- 
Thanks,
Sasha

      parent reply	other threads:[~2023-10-03 11:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 13:14 [PATCH 5.10 0/4] cgroup: Fix suspicious rcu_dereference_check() warning ovidiu.panait
2023-09-29 13:14 ` [PATCH 5.10 1/4] sched/cpuacct: Fix user/system in shown cpuacct.usage* ovidiu.panait
2023-09-29 13:14 ` [PATCH 5.10 2/4] sched/cpuacct: Fix charge percpu cpuusage ovidiu.panait
2023-09-29 13:14 ` [PATCH 5.10 3/4] sched/cpuacct: Optimize away RCU read lock ovidiu.panait
2023-09-29 13:14 ` [PATCH 5.10 4/4] cgroup: Fix suspicious rcu_dereference_check() usage warning ovidiu.panait
2023-10-03 11:32 ` Sasha Levin [this message]

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=ZRv7tW8/+g3JTOnS@sashalap \
    --to=sashal@kernel.org \
    --cc=ovidiu.panait@windriver.com \
    --cc=qyousef@layalina.io \
    --cc=stable@vger.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