From: syzbot <syzbot+568dc81cd20b72d4a49f@syzkaller.appspotmail.com>
To: cgroups@vger.kernel.org, changbin.du@intel.com,
christian.brauner@ubuntu.com, davem@davemloft.net,
edumazet@google.com, hannes@cmpxchg.org, hkallweit1@gmail.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
lizefan.x@bytedance.com, longman@redhat.com, mkoutny@suse.com,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tj@kernel.org, yajun.deng@linux.dev
Subject: Re: [syzbot] WARNING in cpuset_write_resmask
Date: Mon, 04 Apr 2022 12:25:14 -0700 [thread overview]
Message-ID: <00000000000070561105dbd91673@google.com> (raw)
In-Reply-To: <000000000000264b2a05d44bca80@google.com>
syzbot suspects this issue was fixed by commit:
commit d068eebbd4822b6c14a7ea375dfe53ca5c69c776
Author: Michal Koutný <mkoutny@suse.com>
Date: Fri Dec 17 15:48:54 2021 +0000
cgroup/cpuset: Make child cpusets restrict parents on v1 hierarchy
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=142f17f7700000
start commit: e5313968c41b Merge branch 'Split bpf_sk_lookup remote_port..
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=c40b67275bfe2a58
dashboard link: https://syzkaller.appspot.com/bug?extid=568dc81cd20b72d4a49f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13bb97ce700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12062c8e700000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: cgroup/cpuset: Make child cpusets restrict parents on v1 hierarchy
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-04-04 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 16:54 [syzbot] WARNING in cpuset_write_resmask syzbot
2022-02-22 0:29 ` syzbot
2022-02-22 17:26 ` Tejun Heo
2022-02-22 17:51 ` Waiman Long
2022-02-22 18:22 ` Waiman Long
2022-02-22 18:23 ` Tejun Heo
2022-02-22 3:28 ` syzbot
2022-04-04 19:25 ` syzbot [this message]
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=00000000000070561105dbd91673@google.com \
--to=syzbot+568dc81cd20b72d4a49f@syzkaller.appspotmail.com \
--cc=cgroups@vger.kernel.org \
--cc=changbin.du@intel.com \
--cc=christian.brauner@ubuntu.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hannes@cmpxchg.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=yajun.deng@linux.dev \
/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).