[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=WgUNySbRE9dZys28fFo3eZwf_2=cj68jaw1ftakJDzVQ@mail.gmail.com>
Date: Wed, 29 Apr 2020 16:26:41 -0700
From: Doug Anderson <dianders@...omium.org>
To: Ohad Ben-Cohen <ohad@...ery.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
linux-remoteproc@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Cc: Clement Leger <cleger@...ray.eu>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
Evan Green <evgreen@...omium.org>
Subject: Re: [PATCH] remoteproc: Fix wrong rvring index computation
Hi,
On Fri, 4 Oct 2019 Clement Leger <cleger@...ray.eu> wrote:
>
> Index of rvring is computed using pointer arithmetic. However, since
> rvring->rvdev->vring is the base of the vring array, computation
> of rvring idx should be reversed. It previously lead to writing at negative
> indices in the resource table.
>
> Signed-off-by: Clement Leger <cleger@...ray.eu>
> ---
> drivers/remoteproc/remoteproc_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Randomly stumbled upon this in a list of patches. This patch landed
in mainline as:
00a0eec59ddb remoteproc: Fix wrong rvring index computation
Should it be queued up for stable? I'm guessing:
Fixes: c0d631570ad5 ("remoteproc: set vring addresses in resource table")
-Doug
Powered by blists - more mailing lists