The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Changwoo Min <changwoo@igalia.com>
To: arighi@nvidia.com
Cc: tj@kernel.org, void@manifault.com, kernel-dev@igalia.com,
	linux-kernel@vger.kernel.org, changwoo@igalia.com
Subject: Re: [PATCH v2] sched_ext: add a missing rcu_read_lock/unlock pair at scx_select_cpu_dfl()
Date: Sun, 10 Nov 2024 01:01:47 +0900	[thread overview]
Message-ID: <bafcc246-78ec-4b4b-a7f1-fd35f0c073eb@igalia.com> (raw)
In-Reply-To: <Zy9n1qhuraDfHV7e@gpd3>

Hi Andrea,

On 24. 11. 9. 22:47, Andrea Righi wrote:
> Thanks for catching this! I'm wondering why we didn't hit this in our
> CI... I'll investigate.

Yes, that's what I am also curious about. I triggered the warning
on a 2-socket virtual machine using virtme-ng.

Regards,
Changwoo Min

  reply	other threads:[~2024-11-09 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-09  6:29 [PATCH v2] sched_ext: add a missing rcu_read_lock/unlock pair at scx_select_cpu_dfl() Changwoo Min
2024-11-09 13:47 ` Andrea Righi
2024-11-09 16:01   ` Changwoo Min [this message]
2024-11-09 15:48 ` 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=bafcc246-78ec-4b4b-a7f1-fd35f0c073eb@igalia.com \
    --to=changwoo@igalia.com \
    --cc=arighi@nvidia.com \
    --cc=kernel-dev@igalia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=void@manifault.com \
    /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