From: Tomeu Vizoso <tomeu.vizoso@collabora.com>
To: Alyssa Rosenzweig <alyssa@collabora.com>,
Steven Price <steven.price@arm.com>
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Rob Herring <robh@kernel.org>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] drm/panfrost: Avoid user size passed to kvmalloc()
Date: Fri, 17 Dec 2021 08:38:34 +0100 [thread overview]
Message-ID: <aa7be5e4-591f-b7df-12e3-1eff77e53741@collabora.com> (raw)
In-Reply-To: <Ybt8QWEAooP++R7a@maud>
On 12/16/21 6:49 PM, Alyssa Rosenzweig wrote:
>> This provides an easy method for user
>> space to trigger the OOM killer (by temporarily allocating large amounts
>> of kernel memory)
>
> panfrost user space has a lot of easy ways to trigger to the OOM killer
> unfortunately .... if this is something we want to fix there are a lot
> more patches coming :(
What are you thinking of, Alyssa?
My understanding is that the problem are kernel allocations that aren't
accounted per userspace process. I would expect shmem-backed BOs to be
taken into account by the OOM killer, so the offending process would be
terminated without affecting the other processes in the system.
Cheers,
Tomeu
next prev parent reply other threads:[~2021-12-17 7:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 16:16 Steven Price
2021-12-16 17:12 ` Rob Herring
2021-12-17 8:55 ` Steven Price
2021-12-17 9:10 ` Dan Carpenter
2021-12-17 9:16 ` Steven Price
2021-12-17 9:28 ` Dan Carpenter
2021-12-17 9:48 ` Steven Price
2021-12-16 17:49 ` Alyssa Rosenzweig
2021-12-17 6:40 ` Dan Carpenter
2021-12-17 7:38 ` Tomeu Vizoso [this message]
2021-12-17 8:56 ` Steven Price
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=aa7be5e4-591f-b7df-12e3-1eff77e53741@collabora.com \
--to=tomeu.vizoso@collabora.com \
--cc=airlied@linux.ie \
--cc=alyssa.rosenzweig@collabora.com \
--cc=alyssa@collabora.com \
--cc=boris.brezillon@collabora.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=steven.price@arm.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
all inboxes | Powered by JetHome®