Message ID | 20191115105353.GA26176@jax (mailing list archive) |
---|---|
State | Mainlined, archived |
Commit | 03212e347f9443e524d6383c6806ac08295c1fb0 |
Headers | show |
Series | [GIT,PULL] tee subsys fixes for v5.4 (take two) | expand |
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. 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. -Olof -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#907): https://linux.kernel.org/g/patchwork-soc/message/907 Mute This Topic: https://linux.kernel.org/mt/59150726/1554929 Group Owner: patchwork-soc+owner@linux.kernel.org Unsubscribe: https://linux.kernel.org/g/patchwork-soc/unsub [patchwork-linux-kernel-org@patchwork.kernel.org] -=-=-=-=-=-=-=-=-=-=-=-
Hello: The following patches were marked "accepted", because they were applied to soc/soc.git (refs/heads/for-next): Patch: [GIT,PULL] tee subsys fixes for v5.4 (take two) Submitter: Jens Wiklander <jens.wiklander@linaro.org> Patchwork: https://patchwork.kernel.org/project/linux-soc/list/?series=203573 Total patches: 1
Hello: This pull request was applied to soc/soc.git (refs/heads/for-next). On Fri, 15 Nov 2019 11:53:53 +0100 you 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. > > [...] Here is a summary with links: - [GIT,PULL] tee subsys fixes for v5.4 (take two) https://git.kernel.org/soc/soc/c/db6efda85437d783dd921da5d67ec818826adb12 You are awesome, thank you!
Hello: The following patches were marked "accepted", because they were applied to soc/soc.git (refs/heads/arm/fixes): Patch: [GIT,PULL] tee subsys fixes for v5.4 (take two) Submitter: Jens Wiklander <jens.wiklander@linaro.org> Patchwork: https://patchwork.kernel.org/project/linux-soc/list/?series=203573 Total patches: 1
Hello: This pull request was applied to soc/soc.git (refs/heads/arm/fixes). On Fri, 15 Nov 2019 11:53:53 +0100 you 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. > > [...] Here is a summary with links: - [GIT,PULL] tee subsys fixes for v5.4 (take two) https://git.kernel.org/soc/soc/c/db6efda85437d783dd921da5d67ec818826adb12 You are awesome, thank you!
On Sun, Nov 17, 2019 at 12:45 AM Olof Johansson <olof@lixom.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. Great. Thanks, Jens > > > -Olof -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#912): https://linux.kernel.org/g/patchwork-soc/message/912 Mute This Topic: https://linux.kernel.org/mt/59150726/1554929 Group Owner: patchwork-soc+owner@linux.kernel.org Unsubscribe: https://linux.kernel.org/g/patchwork-soc/unsub [patchwork-linux-kernel-org@patchwork.kernel.org] -=-=-=-=-=-=-=-=-=-=-=-
Hi Olof, On Sun, Nov 17, 2019 at 3:22 PM Jens Wiklander <jens.wiklander@linaro.org> wrote: > > On Sun, Nov 17, 2019 at 12:45 AM Olof Johansson <olof@lixom.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? Thanks, Jens -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#968): https://linux.kernel.org/g/patchwork-soc/message/968 Mute This Topic: https://linux.kernel.org/mt/59150726/1554929 Group Owner: patchwork-soc+owner@linux.kernel.org Unsubscribe: https://linux.kernel.org/g/patchwork-soc/unsub [patchwork-linux-kernel-org@patchwork.kernel.org] -=-=-=-=-=-=-=-=-=-=-=-
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@linaro.org> wrote: > > > > On Sun, Nov 17, 2019 at 12:45 AM Olof Johansson <olof@lixom.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 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#973): https://linux.kernel.org/g/patchwork-soc/message/973 Mute This Topic: https://linux.kernel.org/mt/59150726/1554929 Group Owner: patchwork-soc+owner@linux.kernel.org Unsubscribe: https://linux.kernel.org/g/patchwork-soc/unsub [patchwork-linux-kernel-org@patchwork.kernel.org] -=-=-=-=-=-=-=-=-=-=-=-