[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAD-N9QW6VGmAFPtJDcHahO=OQ=0Cy06-zaQf72mYL0=L_MEc_g@mail.gmail.com>
Date: Thu, 21 Jan 2021 19:33:23 +0800
From: 慕冬亮 <mudongliangabcd@...il.com>
To: andriin@...com, ast@...nel.org, bpf@...r.kernel.org,
cgroups@...r.kernel.org, christian@...uner.io,
Daniel Borkmann <daniel@...earbox.net>, hannes@...xchg.org,
john.fastabend@...il.com, kafai@...com, kpsingh@...omium.org,
linux-kernel <linux-kernel@...r.kernel.org>, lizefan@...wei.com,
netdev@...r.kernel.org, songliubraving@...com, tj@...nel.org,
yhs@...com
Cc: syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
syzkaller <syzkaller@...glegroups.com>
Subject: "WARNING in cgroup_finalize_control" and "WARNING in
cgroup_apply_control_disable" should be duplicate crash reports
Dear kernel developers,
I found that on the syzbot dashboard, “WARNING in
cgroup_finalize_control” [1] and "WARNING in
cgroup_apply_control_disable" [2] should share the same root cause.
The reasons for the above statement:
1) the stack trace is the same, and this title difference is due to
the inline property of "cgroup_apply_control_disable";
2) their PoCs are the same as each other;
If you can have any issues with this statement or our information is
useful to you, please let us know. Thanks very much.
[1] “WARNING in cgroup_finalize_control” -
https://syzkaller.appspot.com/bug?id=fe2fee189f1f8babd95615dcbb57871d6d18920a
[2] “WARNING in cgroup_apply_control_disable” -
https://syzkaller.appspot.com/bug?id=ba5a3ed954137643a9337f90782c90e90ba302ed
--
My best regards to you.
No System Is Safe!
Dongliang Mu
Powered by blists - more mailing lists