linux-kernel - Re: [GIT PULL] tee driver fix for v4.21

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20181231210617.6cxtq2nqynil2ltw@localhost>
Date:   Mon, 31 Dec 2018 13:06:17 -0800
From:   Olof Johansson <olof@...om.net>
To:     Jens Wiklander <jens.wiklander@...aro.org>
Cc:     arm-soc <arm@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [GIT PULL] tee driver fix for v4.21

On Thu, Dec 13, 2018 at 08:29:06AM +0100, Jens Wiklander wrote:
> On Wed, Dec 12, 2018 at 11:16 PM Olof Johansson <olof@...om.net> wrote:
> >
> > On Wed, Dec 12, 2018 at 01:28:00PM +0100, Jens Wiklander wrote:
> > > Hello arm-soc maintainers,
> > >
> > > Please pull this tee driver fix for a possible double list_del() in the
> > > OP-TEE driver while uninitializing.
> > >
> > > Thanks,
> > > Jens
> > >
> > > The following changes since commit 40e020c129cfc991e8ab4736d2665351ffd1468d:
> > >
> > >   Linux 4.20-rc6 (2018-12-09 15:31:00 -0800)
> > >
> > > are available in the Git repository at:
> > >
> > >   https://git.linaro.org/people/jens.wiklander/linux-tee.git tags/tee-subsys-fix-for-4.21
> > >
> > > for you to fetch changes up to b2d102bd0146d9eb1fa630ca0cd19a15ef2f74c8:
> > >
> > >   tee: optee: avoid possible double list_del() (2018-12-11 14:38:21 +0100)
> > >
> > > ----------------------------------------------------------------
> > > Avoid possible double list_del in supplicant comms
> > >
> > > A fix for the OP-TEE driver to avoid possible double list_del during
> > > tee-supplicant communication while the system is shutting down.
> >
> > Do you want this for 4.20 or 4.21? Seems like .20 material to me but the tag
> > name is 4.21.
> 
> It's just that we're so late in the 4.20 cycle. If you're OK with
> taking it now I'm happy with that.

I dropped the ball on this before the holidays, I've queued it up in
a next/late branch now so we'll send it in towards the end of the merge window.


-Olof