[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200915163907.GA35563@kroah.com>
Date: Tue, 15 Sep 2020 18:39:07 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Jordan Crouse <jcrouse@...eaurora.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Rob Clark <robdclark@...omium.org>
Subject: Re: [PATCH 5.4 105/132] drm/msm: Split the a5xx preemption record
On Tue, Sep 15, 2020 at 09:54:39AM -0600, Jordan Crouse wrote:
> On Tue, Sep 15, 2020 at 04:13:27PM +0200, Greg Kroah-Hartman wrote:
> > From: Jordan Crouse <jcrouse@...eaurora.org>
> >
> > commit 34221545d2069dc947131f42392fd4cebabe1b39 upstream.
> >
> > The main a5xx preemption record can be marked as privileged to
> > protect it from user access but the counters storage needs to be
> > remain unprivileged. Split the buffers and mark the critical memory
> > as privileged.
> >
> > Cc: stable@...r.kernel.org
> > Signed-off-by: Jordan Crouse <jcrouse@...eaurora.org>
> > Signed-off-by: Rob Clark <robdclark@...omium.org>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>
> Hi. The MSM_BO_MAP_PRIV feature was added after 5.4.
>
> Since we are pulling in 7b3f3948c8b7 ("drm/msm: Disable preemption on all
> 5xx targets)" preemption will be disabled in the 5.4 stable tree which is enough
> to cover the security concern that this patch helped address.
>
> This patch can be dropped.
Now dropped,t hanks!
greg k-h
Powered by blists - more mailing lists