From: Matthew Wilcox <willy@infradead.org>
To: "Christian A. Ehrhardt" <lk@c--e.de>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org,
Steven Price <steven.price@arm.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/panthor: Check VMA boundaries for PMD mappings
Date: Tue, 23 Jun 2026 19:33:42 +0100 [thread overview]
Message-ID: <ajrRhpVH6uhOABnV@casper.infradead.org> (raw)
In-Reply-To: <20260623181942.1536598-1-lk@c--e.de>
On Tue, Jun 23, 2026 at 08:19:42PM +0200, Christian A. Ehrhardt wrote:
> The panthor version is only compile tested because I don't
> have the hardware. However, the code is identical to that
> fixed in [1] and I have a reproducer for that.
>
> No need for for stable backports. The code is new in 7.1.
What documentation did you need to see to persuade you to use
map_pages instead of writing a huge_fault handler?
(yes, you're all Doing It Wrong, please stop, but help us help you)
next prev parent reply other threads:[~2026-06-23 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 18:19 Christian A. Ehrhardt
2026-06-23 18:33 ` Matthew Wilcox [this message]
2026-06-23 20:03 ` Boris Brezillon
2026-06-23 20:44 ` Boris Brezillon
2026-06-24 9:18 ` Boris Brezillon
2026-06-24 10:26 ` Boris Brezillon
2026-06-24 10:33 ` Boris Brezillon
2026-06-24 15:34 ` Steven Price
2026-08-06 7:46 ` Boris Brezillon
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=ajrRhpVH6uhOABnV@casper.infradead.org \
--to=willy@infradead.org \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liviu.dudau@arm.com \
--cc=lk@c--e.de \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=tzimmermann@suse.de \
/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®