From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/1] iommu/arm-smmu-v3: eliminate a potential memory corruption on Hi16xx soc
Date: Mon, 29 Oct 2018 17:59:05 +0000 [thread overview]
Message-ID: <20181029175905.GC16739@arm.com> (raw)
In-Reply-To: <1540021014-8176-1-git-send-email-thunder.leizhen@huawei.com>
On Sat, Oct 20, 2018 at 03:36:54PM +0800, Zhen Lei wrote:
> The standard GITS_TRANSLATER register in ITS is only 4 bytes, but
> Hisilicon expands the next 4 bytes to carry some IMPDEF information. That
> means, total 8 bytes data will be written to MSIAddress each time.
>
> MSIAddr: |----4bytes----|----4bytes----|
> | MSIData | IMPDEF |
>
> There is no problem for ITS, because the next 4 bytes space is reserved
> in ITS. But it will overwrite the 4 bytes memory following "sync_count".
> It's very fortunately that the previous and the next neighbour of the
> "sync_count" are both aligned by 8 bytes, so no problem is met now.
>
> It's good to explicitly add a workaround:
> 1. Add gcc __attribute__((aligned(8))) to make sure that "sync_count" is
> always aligned by 8 bytes.
> 2. Add a "int" struct member to make sure the 4 bytes padding is always
> exist.
>
> There is no functional change.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> drivers/iommu/arm-smmu-v3.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/arm-smmu-v3.c b/drivers/iommu/arm-smmu-v3.c
> index 5059d09..624fdd0 100644
> --- a/drivers/iommu/arm-smmu-v3.c
> +++ b/drivers/iommu/arm-smmu-v3.c
> @@ -586,7 +586,20 @@ struct arm_smmu_device {
>
> struct arm_smmu_strtab_cfg strtab_cfg;
>
> - u32 sync_count;
> + /*
> + * The alignment and padding is required by Hi16xx of Hisilicon.
> + * Because the ITS hardware on Hi16xx will truncate the MSIAddress(Here
> + * it's the address of "sync_count") to 8 bytes boundary first, then
> + * write 32 bits MSIdata at offset 0, and 32 bits IMPDEF data at offset
> + * 4. Without this workaround, the adjacent member maybe overwritten.
> + *
> + * |---4bytes---|---4bytes---|
> + * MSIAddress & (~0x7): MSIdata | IMPDEF data|
> + */
> + struct {
> + u32 sync_count;
> + int padding;
> + } __attribute__((aligned(8)));
I thought the conclusion after reviewing your original patch was to maintain
the union and drop the alignment directive? e.g.
union {
u32 sync_count;
u64 padding; /* Hi16xx writes an extra 32 bits of goodness */
};
Will
next prev parent reply other threads:[~2018-10-29 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 7:36 [PATCH v2 1/1] iommu/arm-smmu-v3: eliminate a potential memory corruption on Hi16xx soc Zhen Lei
2018-10-29 17:59 ` Will Deacon [this message]
2018-10-30 1:52 ` Leizhen (ThunderTown)
2018-10-30 9:26 ` John Garry
2018-10-30 14:02 ` Leizhen (ThunderTown)
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=20181029175905.GC16739@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).