public inbox for op-tee@lists.trustedfirmware.org
 help / color / mirror / Atom feed
From: Sumit Garg via OP-TEE <op-tee@lists.trustedfirmware.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Marco Felsch <m.felsch@pengutronix.de>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Matthew Wilcox <willy@infradead.org>, arm <arm@kernel.org>,
	soc@kernel.org, linux-kernel@vger.kernel.org,
	op-tee@lists.trustedfirmware.org
Subject: Re: [GIT PULL] TEE shared memory fix for 7.0
Date: Mon, 23 Mar 2026 17:41:14 +0530	[thread overview]
Message-ID: <acEt4roJbZJoRCJC@sumit-xelite> (raw)
In-Reply-To: <c3f1a10d-8437-4d17-8dfc-286935ba9e51@app.fastmail.com>

On Wed, Mar 18, 2026 at 01:39:41PM +0100, Arnd Bergmann wrote:
> On Tue, Mar 17, 2026, at 13:53, Marco Felsch wrote:
> > On 26-03-17, Jens Wiklander wrote:
> >> 
> >> I'm under the impression that it is a fix rather than an improvement.
> >> However, since it has been stewing for a while, it's clearly not
> >> urgent. I don't have anything specific on the bug fix, other than that
> >> we're supposed to stop taking those refcounts. Perhaps Sumit, Marco,
> >> or Matthew can add something?
> >
> > It's a long outstanding fix regarding memory page management. The
> > userspace gets informed about this memory API misuse via a warning print
> > incl. a backtrace. This gets triggered only if userspace uses OP-TEE
> > trusted-keys or the OP-TEE EFI variables. Therefore I would like to get
> > it into 7.0 but 7.1 fine too.
> 
> Yes, that is clearly a bugfix. I think we'd also want this to be
> marked 'Cc: stable@vger.kernel.org' as it should also apply
> to 6.18-LTS and 6.19. Greg tends to also pick up bugfixes that
> don't have this, but it's generally better to be explicit here,
> especially when it's not obvious what the impact of the fix is.
> 
> I've merge the pull request now. If you think this should be
> in 6.18-lts and Greg doesn't pick it up by himself, maybe
> let him know about it.

Thanks Arnd for picking up this fix. Last week I was on business travel
hence the delay in my response. I see Sasha already picked it up for
backports.

-Sumit

      reply	other threads:[~2026-03-23 12:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16  7:41 [GIT PULL] TEE shared memory fix for 7.0 Jens Wiklander
2026-03-17  8:51 ` Krzysztof Kozlowski via OP-TEE
2026-03-17 12:21   ` Jens Wiklander
2026-03-17 12:53     ` Marco Felsch
2026-03-18 12:39       ` Arnd Bergmann
2026-03-23 12:11         ` Sumit Garg via OP-TEE [this message]

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=acEt4roJbZJoRCJC@sumit-xelite \
    --to=op-tee@lists.trustedfirmware.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=soc@kernel.org \
    --cc=sumit.garg@kernel.org \
    --cc=willy@infradead.org \
    /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