From: Yicong Yang <yangyicong@huawei.com>
To: Barry Song <21cnbao@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Qinxin Xia <xiaqinxin@huawei.com>
Cc: <robin.murphy@arm.com>, <jonathan.cameron@huawei.com>,
<prime.zeng@huawei.com>, <fanghao11@huawei.com>,
<linux-kernel@vger.kernel.org>, <iommu@lists.linux.dev>,
<yangyicong@hisilicon.com>
Subject: Re: [PATCH 2/2] dma-mapping: benchmark: Add padding to ensure uABI remained consistent
Date: Mon, 4 Aug 2025 16:12:39 +0800 [thread overview]
Message-ID: <c5170042-ac38-b0db-ba51-c5fce5363d40@huawei.com> (raw)
In-Reply-To: <CAGsJ_4zs8=n+J4Xtd=Un8+p3c=FCOTji9qMfBsOKcc8sFG0v9A@mail.gmail.com>
Hi Barry,
On 2025/8/4 12:47, Barry Song wrote:
> On Tue, Jul 29, 2025 at 8:32 PM Marek Szyprowski
> <m.szyprowski@samsung.com> wrote:
>>
>> On 24.07.2025 11:42, Barry Song wrote:
>>> On Thu, Jul 24, 2025 at 5:35 PM Qinxin Xia <xiaqinxin@huawei.com> wrote:
>>>> On 2025/7/24 17:07:08, Barry Song <21cnbao@gmail.com> wrote:
>>>>> On Thu, Jul 24, 2025 at 4:56 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
>>>>>> Acked-by: Barry Song <baohua@kernel.org>
>>>>>> Signed-off-by: Qinxin Xia <xiaqinxin@huawei.com>
>>>>> I don’t think these two patches should be part of the same series. This
>>>>> one is a bug fix and should be handled separately—ideally picked up on
>>>>> its own and backported to stable.
>>>>>
>>>>> Also, the subject should not say "Add"—it should be "Restore". I assume
>>>>> Marek can handle it?
>>> ...
>>>> Ok, I will send a new version to fix it.
>>> If Marek can help fix it while picking it up into the dma-mapping tree, you
>>> might not need to send a new version.
>>>
>>> Honestly, I hope this gets merged soon—it feels like it's been
>>> overdue for quite a while.
>>
>> I'm sorry, I wasn't aware that this need to go via dma-mapping tree. I
>> will take it after this merge window.
>
> Thank you, Marek! I also noticed that Xiang Chen’s email has been invalid
> for quite a while, likely he moved to another company some time ago. It looks
> like Yicong has volunteered to take this on:
>
> https://lkml.indiana.edu/2408.1/08865.html
>
> I'm not sure if that's still the case. If it is, would Yicong be able to
> resend the email with my ack?
>
thanks for reminding. I think currently Qinxin is more suitable to help with this.
she's working on the smmu stuffs and help look after this benchmark tool internally
for some time :)
Maybe she can help along with you (ack the fact that you're always helping to review
the codes) if it's ok with you.
Thanks.
next prev parent reply other threads:[~2025-08-04 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 8:55 [PATCH 0/2] dma-mapping: benchmark: modify the dma_map_benchmark directory Qinxin Xia
2025-07-24 8:55 ` [PATCH 1/2] tools/dma: move dma_map_benchmark from selftests to tools/dma Qinxin Xia
2025-07-24 9:25 ` Barry Song
2025-07-24 9:33 ` Qinxin Xia
2025-07-24 8:56 ` [PATCH 2/2] dma-mapping: benchmark: Add padding to ensure uABI remained consistent Qinxin Xia
2025-07-24 9:07 ` Barry Song
2025-07-24 9:35 ` Qinxin Xia
2025-07-24 9:42 ` Barry Song
2025-07-29 12:32 ` Marek Szyprowski
2025-08-04 4:47 ` Barry Song
2025-08-04 8:12 ` Yicong Yang [this message]
2025-08-04 21:57 ` Barry Song
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=c5170042-ac38-b0db-ba51-c5fce5363d40@huawei.com \
--to=yangyicong@huawei.com \
--cc=21cnbao@gmail.com \
--cc=fanghao11@huawei.com \
--cc=iommu@lists.linux.dev \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=prime.zeng@huawei.com \
--cc=robin.murphy@arm.com \
--cc=xiaqinxin@huawei.com \
--cc=yangyicong@hisilicon.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
all inboxes | Powered by JetHome®