From: Dhananjay Phadke <dphadke@linux.microsoft.com>
To: allen.lkml@gmail.com
Cc: apais@linux.microsoft.com, jens.wiklander@linaro.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
op-tee@lists.trustedfirmware.org, zajec5@gmail.com,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com
Subject: [PATCH 0/2] optee: fix OOM seen due to tee_shm_free()
Date: Thu, 18 Feb 2021 10:12:38 -0800 [thread overview]
Message-ID: <1613671958-1307-1-git-send-email-dphadke@linux.microsoft.com> (raw)
In-Reply-To: <20210217092714.121297-1-allen.lkml@gmail.com>
From: Allen Pais <apais@linux.microsoft.com>
On Wed, 17 Feb 2021 14:57:12 +0530, Allen Pais wrote:
> The following out of memory errors are seen on kexec reboot
> from the optee core.
>
> [ 0.368428] tee_bnxt_fw optee-clnt0: tee_shm_alloc failed
> [ 0.368461] tee_bnxt_fw: probe of optee-clnt0 failed with error -22
>
> tee_shm_release() is not invoked on dma shm buffer.
>
> Implement .shutdown() in optee core as well as bnxt firmware driver
> to handle the release of the buffers correctly.
>
> More info:
> https://github.com/OP-TEE/optee_os/issues/3637
CC: linux-kernel@vger.kernel.org instead of linux-mips?
TEE / TrustZone is ARM.
Also, for Broadcom specific -
CC: bcm-kernel-feedback-list@broadcom.com
next prev parent reply other threads:[~2021-02-18 19:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 9:27 [PATCH 0/2] optee: fix OOM seen due to tee_shm_free() Allen Pais
2021-02-17 9:27 ` [PATCH 1/2] optee: fix tee out of memory failure seen during kexec reboot Allen Pais
2021-02-18 20:03 ` Dhananjay Phadke
2021-02-22 12:45 ` Allen Pais
2021-02-23 8:19 ` Jens Wiklander
2021-02-23 16:26 ` Allen Pais
2021-02-24 8:15 ` Jens Wiklander
2021-02-24 16:53 ` Allen Pais
2021-02-17 9:27 ` [PATCH 2/2] firmware: tee_bnxt: implement shutdown method to handle kexec reboots Allen Pais
2021-02-18 18:12 ` Dhananjay Phadke [this message]
2021-02-23 6:17 ` [PATCH 0/2] optee: fix OOM seen due to tee_shm_free() Allen Pais
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1613671958-1307-1-git-send-email-dphadke@linux.microsoft.com \
--to=dphadke@linux.microsoft.com \
--cc=allen.lkml@gmail.com \
--cc=apais@linux.microsoft.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox