Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37;
From:   Maxime Ripard <mripard@kernel.org>
To:     Frank Binns <frank.binns@imgtec.com>,
        Donald Robson <donald.robson@imgtec.com>,
        Matt Coster <matt.coster@imgtec.com>,
        Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
        Thomas Zimmermann <tzimmermann@suse.de>,
        Alex Bee <knaerzche@gmail.com>
Cc:     David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
        Sarah Walker <sarah.walker@imgtec.com>,
        dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
In-Reply-To: <20231208170856.1748413-1-knaerzche@gmail.com>
References: <20231208170856.1748413-1-knaerzche@gmail.com>
Subject: Re: (subset) [PATCH] drm/imagination: vm: Fix heap lookup
 condition
Message-Id: <170248095546.191897.14747854434891174089.b4-ty@kernel.org>
Date:   Wed, 13 Dec 2023 16:22:35 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 08 Dec 2023 18:08:56 +0100, Alex Bee wrote:
> When conditionally checking for heap existence of a certian address in
> pvr_vm_bind_op_map_init the condition whether the map request comes from a
> user is incorrect: The context must not be the kernel-context to be a
> user(space) context and should be looked up in pvr_heaps.
> 
> That makes addresses coming from userspace not being verfied against the
> defined ranges and prevents firmware loading for meta cores.
> 
> [...]

Applied to drm/drm-misc (drm-misc-next).

Thanks!
Maxime