[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191206162919.vilrybgbiewdl4d2@localhost>
Date: Fri, 6 Dec 2019 08:29:19 -0800
From: Olof Johansson <olof@...om.net>
To: Jens Wiklander <jens.wiklander@...aro.org>
Cc: arm-soc <arm@...nel.org>, soc@...nel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [GIT PULL] tee subsys fixes for v5.4 (take two)
On Fri, Dec 06, 2019 at 10:57:47AM +0100, Jens Wiklander wrote:
> Hi Olof,
>
> On Sun, Nov 17, 2019 at 3:22 PM Jens Wiklander
> <jens.wiklander@...aro.org> wrote:
> >
> > On Sun, Nov 17, 2019 at 12:45 AM Olof Johansson <olof@...om.net> wrote:
> > >
> > > On Fri, Nov 15, 2019 at 11:53:53AM +0100, Jens Wiklander wrote:
> > > > Hello arm-soc maintainers,
> > > >
> > > > Please pull these OP-TEE driver fixes. There's one user-after-free issue if
> > > > in the error handling path when the OP-TEE driver is initializing. There's
> > > > also one fix to to register dynamically allocated shared memory needed by
> > > > kernel clients communicating with secure world via memory references.
> > > >
> > > > "tee: optee: Fix dynamic shm pool allocations" is now from version 2 which
> > > > includes a fix up with a small but vital dependency.
> > > >
> > > > If you think it's too late for v5.4 please queue this for v5.5 instead.
> > >
> > > Hi,
> > >
> > > I noticed you based this on -rc3 -- all our other branches are on -rc2 or
> > > older.
> >
> > I'm sorry, I thought -rc3 was old enough. I'll stick to -rc2 or older
> > in next time.
> >
> > >
> > > Anyway, I brought this in to the fixes branch, it's the only thing we have
> > > queued up at this time so I'll give it a few days in -next before I send it in.
>
> It looks like the two patches in this pull request
> (https://git.linaro.org/people/jens.wiklander/linux-tee.git/tag/?h=tee-fixes-for-v5.4)
> are still in -next and haven't got any further. Is there anything
> wrong? Something I should fix?
They were in our fixes branch and didn't go in yet, but will shortly.
-Olof
Powered by blists - more mailing lists