From: Michal Hocko <mhocko@suse.com>
To: junfei fang <jefexiaomi@gmail.com>
Cc: andrew.zhu@mediatek.com, colin.peng@mediatek.com,
wangbiao3@xiaomi.com, yangjianlong@xiaomi.com,
linux-kernel@vger.kernel.org
Subject: Re: kasan cgroup user-after-free in get_mem_cgroup_from_mm
Date: Wed, 21 Jun 2023 09:32:56 +0200 [thread overview]
Message-ID: <ZJKnqJ7XTvvt8MYM@dhcp22.suse.cz> (raw)
In-Reply-To: <CAFtB3FY-0uyJchUtUPph-pUeQVRpddi-3xDSGzhJEhFqWck4XQ@mail.gmail.com>
On Wed 21-06-23 10:18:31, junfei fang wrote:
> Thank you for your prompt response.
>
> We are using kernel-5.15 in our project and cannot change it.
It will be hard to get a community support for such a kernel I am
afraid. Especially when considering the kernel is heavily tainted
> CPU: 0 PID: 6071 Comm: elastic_postChe Tainted: P S WC OE
by proprietary, out-of-tree modules, pre-existing warnings that might be
related and TAINT_CPU_OUT_OF_SPEC doesn't add much confidence into setup
either.
> Do you have any suggestions on how to fix this issue?
No, not really. From what I can see the report complains about cset
associated with the process' mm. I do not recall any specific bug where
css would be released prematurely. Maybe somebody else who is more
familiar with the cgroup core would know better.
Btw. you should be sending the full UAF report after you have CCed LKML.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2023-06-21 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230620022120.27448-1-jefexiaomi@xiaomi.com>
[not found] ` <ZJFLfRCZuPXN+p9I@dhcp22.suse.cz>
2023-06-21 2:18 ` kasan cgroup user-after-free in get_mem_cgroup_from_mm junfei fang
2023-06-21 7:32 ` Michal Hocko [this message]
2023-06-23 3:29 ` junfei fang
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=ZJKnqJ7XTvvt8MYM@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=andrew.zhu@mediatek.com \
--cc=colin.peng@mediatek.com \
--cc=jefexiaomi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wangbiao3@xiaomi.com \
--cc=yangjianlong@xiaomi.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