From: Qinxin Xia <xiaqinxin@huawei.com>
To: Barry Song <21cnbao@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: <yangyicong@huawei.com>, <hch@lst.de>, <iommu@lists.linux.dev>,
<jonathan.cameron@huawei.com>, <prime.zeng@huawei.com>,
<fanghao11@huawei.com>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] dma-mapping: benchmark: Add padding to ensure uABI remained consistent
Date: Fri, 9 May 2025 14:43:12 +0800 [thread overview]
Message-ID: <ab9c5f52-4648-42c4-8dd1-79c3bb0ce971@huawei.com> (raw)
In-Reply-To: <CAGsJ_4zrCiugrAPw-aExgSMZXYBBUqLyyWbcpKH8RdhKnHxj9g@mail.gmail.com>
On 2025/5/9 11:31:09, Barry Song <21cnbao@gmail.com> wrote:
> On Fri, May 9, 2025 at 2:02 PM Qinxin Xia <xiaqinxin@huawei.com> wrote:
>> The padding field in the structure was previously reserved to
>> maintain a stable interface for potential new fields, ensuring
>> compatibility with user-space shared data structures.
>> However,it was accidentally removed by tiantao in a prior commit,
>> which may lead to incompatibility between user space and the kernel.
>>
>> This patch reinstates the padding to restore the original structure
>> layout and preserve compatibility.
>>
>> Fixes: 8ddde07a3d28 ("dma-mapping: benchmark: extract a common header file for map_benchmark definition")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Qinxin Xia <xiaqinxin@huawei.com>
> +Marek, +Robin
>
> Acked-by: Barry Song <baohua@kernel.org>
OK!
>> ---
>> include/linux/map_benchmark.h | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/include/linux/map_benchmark.h b/include/linux/map_benchmark.h
>> index 62674c83bde4..2ac2fe52f248 100644
>> --- a/include/linux/map_benchmark.h
>> +++ b/include/linux/map_benchmark.h
>> @@ -27,5 +27,6 @@ struct map_benchmark {
>> __u32 dma_dir; /* DMA data direction */
>> __u32 dma_trans_ns; /* time for DMA transmission in ns */
>> __u32 granule; /* how many PAGE_SIZE will do map/unmap once a time */
>> + __u8 expansion[76]; /* For future use */
>> };
>> #endif /* _KERNEL_DMA_BENCHMARK_H */
>> --
>> 2.33.0
>>
> Thanks
> Barry
Thanks
Qinxin
next prev parent reply other threads:[~2025-05-09 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 2:02 [PATCH v3 0/4]{topost} dma-mapping: benchmark: Add support for dma_map_sg Qinxin Xia
2025-05-09 2:02 ` [PATCH v3 1/4] dma-mapping: benchmark: Add padding to ensure uABI remained consistent Qinxin Xia
2025-05-09 3:31 ` Barry Song
2025-05-09 6:43 ` Qinxin Xia [this message]
2025-05-09 2:02 ` [PATCH v3 2/4] dma-mapping: benchmark: modify the framework to adapt to more map modes Qinxin Xia
2025-05-09 2:02 ` [PATCH v3 3/4] dma-mapping: benchmark: add support for dma_map_sg Qinxin Xia
2025-05-09 2:04 ` kernel test robot
2025-05-09 2:02 ` [PATCH v3 4/4] selftests/dma: Add dma_map_sg support Qinxin Xia
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=ab9c5f52-4648-42c4-8dd1-79c3bb0ce971@huawei.com \
--to=xiaqinxin@huawei.com \
--cc=21cnbao@gmail.com \
--cc=fanghao11@huawei.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=m.szyprowski@samsung.com \
--cc=prime.zeng@huawei.com \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=yangyicong@huawei.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