From: Sudeep Holla <sudeep.holla@kernel.org>
To: Sebastian Ene <sebastianene@google.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jens Wiklander <jens.wiklander@linaro.org>
Subject: Re: [PATCH 3/8] firmware: arm_ffa: Align RxTx buffer size before mapping
Date: Mon, 27 Apr 2026 13:42:16 +0100 [thread overview]
Message-ID: <20260427-witty-light-hyrax-ea65d1@sudeepholla> (raw)
In-Reply-To: <ae8sqehR7yQFheuj@google.com>
On Mon, Apr 27, 2026 at 09:30:17AM +0000, Sebastian Ene wrote:
> On Thu, Apr 23, 2026 at 06:22:53PM +0100, Sudeep Holla wrote:
> > Commit 83210251fd70 ("firmware: arm_ffa: Use the correct buffer size during
> > RXTX_MAP") advertises PAGE_ALIGN(rxtx_bufsz) to firmware when mapping the
> > buffers but the driver continues to stores the minimum FF-A buffer size
> > in drv_info->rxtx_bufsz which is used elsewhere in the driver.
>
> Hello Sudeep,
>
> >
> > Align the size before storing it so that the allocation, validation and
> > FFA_RXTX_MAP all use the same buffer size.
> >
>
> Thanks for fixing this,
It was my fault, I wasn't expecting sashiko was covering most of the lists
now, so didn't check for it in time.
> Reviewed-by: Sebastian Ene <sebastianene@google.com>.
>
Thanks!
--
Regards,
Sudeep
next prev parent reply other threads:[~2026-04-27 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 17:22 [PATCH 0/8] firmware: arm_ffa: Fix cleanup, notification, and discovery paths Sudeep Holla
2026-04-23 17:22 ` [PATCH 1/8] firmware: arm_ffa: Check for NULL FF-A ID table while driver registration Sudeep Holla
2026-04-23 17:22 ` [PATCH 2/8] firmware: arm_ffa: Skip free_pages on RX buffer alloc failure Sudeep Holla
2026-04-23 17:22 ` [PATCH 3/8] firmware: arm_ffa: Align RxTx buffer size before mapping Sudeep Holla
2026-04-27 9:30 ` Sebastian Ene
2026-04-27 12:42 ` Sudeep Holla [this message]
2026-04-23 17:22 ` [PATCH 4/8] firmware: arm_ffa: Fix Rx buffer release in fwk notification handler Sudeep Holla
2026-04-23 17:22 ` [PATCH 5/8] firmware: arm_ffa: Validate framework notification payload bounds Sudeep Holla
2026-04-23 17:22 ` [PATCH 6/8] firmware: arm_ffa: Unregister v1.0 bus notifier on teardown Sudeep Holla
2026-04-23 17:22 ` [PATCH 7/8] firmware: arm_ffa: Fix sched-recv callback partition lookup Sudeep Holla
2026-04-23 17:22 ` [PATCH 8/8] firmware: arm_ffa: Bound PARTITION_INFO_GET_REGS copies Sudeep Holla
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=20260427-witty-light-hyrax-ea65d1@sudeepholla \
--to=sudeep.holla@kernel.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastianene@google.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