[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172599899804.385892.17266018060492319071.b4-ty@kernel.org>
Date: Tue, 10 Sep 2024 21:11:52 +0100
From: Marc Zyngier <maz@...nel.org>
To: Oliver Upton <oliver.upton@...ux.dev>,
Snehal Koukuntla <snehalreddy@...gle.com>,
Wei-Lin Chang <r09922117@...e.ntu.edu.tw>
Cc: James Morse <james.morse@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Zenghui Yu <yuzenghui@...wei.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Sudeep Holla <sudeep.holla@....com>,
Sebastian Ene <sebastianene@...gle.com>,
Vincent Donnefort <vdonnefort@...gle.com>,
Jean-Philippe Brucker <jean-philippe@...aro.org>,
linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev,
linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH v3] KVM: arm64: Add memory length checks and remove inline in do_ffa_mem_xfer
On Mon, 09 Sep 2024 18:01:54 +0000, Snehal Koukuntla wrote:
> When we share memory through FF-A and the description of the buffers
> exceeds the size of the mapped buffer, the fragmentation API is used.
> The fragmentation API allows specifying chunks of descriptors in subsequent
> FF-A fragment calls and no upper limit has been established for this.
> The entire memory region transferred is identified by a handle which can be
> used to reclaim the transferred memory.
> To be able to reclaim the memory, the description of the buffers has to fit
> in the ffa_desc_buf.
> Add a bounds check on the FF-A sharing path to prevent the memory reclaim
> from failing.
>
> [...]
Applied to next, with the BUILD_BUG_ON() issue fixed.
[1/1] KVM: arm64: Add memory length checks and remove inline in do_ffa_mem_xfer
commit: f26a525b77e040d584e967369af1e018d2d59112
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists