linux-kernel - Re: [syzbot] WARNING in cpuset_write

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 22 Feb 2022 13:22:13 -0500
From:   Waiman Long <longman@...hat.com>
To:     Tejun Heo <tj@...nel.org>,
        syzbot <syzbot+568dc81cd20b72d4a49f@...kaller.appspotmail.com>
Cc:     cgroups@...r.kernel.org, hannes@...xchg.org,
        linux-kernel@...r.kernel.org, lizefan.x@...edance.com,
        netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] WARNING in cpuset_write_resmask

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