From: Waiman Long <longman@redhat.com>
To: Tejun Heo <tj@kernel.org>,
syzbot <syzbot+568dc81cd20b72d4a49f@syzkaller.appspotmail.com>
Cc: cgroups@vger.kernel.org, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, lizefan.x@bytedance.com,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in cpuset_write_resmask
Date: Tue, 22 Feb 2022 13:22:13 -0500 [thread overview]
Message-ID: <a1baa10e-2c73-1fdd-0228-820310455dd5@redhat.com> (raw)
In-Reply-To: <YhUc10UcAmot1AJK@slm.duckdns.org>
On 2/22/22 12:26, Tejun Heo wrote:
> (cc'ing Waiman and quoting whole body)
>
> Hello, Waiman.
>
> It looks like it's hitting
>
> WARN_ON(!is_in_v2_mode() && !nodes_equal(cp->mems_allowed, cp->effective_mems))
>
> Can you take a look?
My preliminary analysis is that the warning may be caused by my commit
1f1562fcd04a ("cgroup/cpuset: Don't let child cpusets restrict parent in
default hierarchy") since the merge branch e5313968c41b is missing the
fix commit d068eebbd482 ("cgroup/cpuset: Make child cpusets restrict
parents on v1 hierarchy"). I believe the problem should be gone once the
merge branch is updated to a later upstream baseline.
Cheers,
Longman
next prev parent reply other threads:[~2022-02-22 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000264b2a05d44bca80@google.com>
2022-02-22 0:29 ` [syzbot] WARNING in cpuset_write_resmask syzbot
2022-02-22 17:26 ` Tejun Heo
2022-02-22 17:51 ` Waiman Long
2022-02-22 18:22 ` Waiman Long [this message]
2022-02-22 18:23 ` Tejun Heo
2022-02-22 3:28 ` syzbot
2022-04-04 19:25 ` syzbot
2022-05-03 11:48 ` Dmitry Vyukov
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=a1baa10e-2c73-1fdd-0228-820310455dd5@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=netdev@vger.kernel.org \
--cc=syzbot+568dc81cd20b72d4a49f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).