From nobody Mon Feb 9 12:25:33 2026 Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [45.249.212.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C10D9242D75; Fri, 9 May 2025 02:18:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.190 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746757096; cv=none; b=nHyMdoNGvIHTirr7NfZgNVoqFJxu0K5puAJVfV2PNKBwYj0/pi83lOhyTT1ur0PE9+gTSdM5/VXy9+mcVnHa3a4Q5wf696lXR9C1r8FabzSF4TeYGFKIvz3x2sYsMZKOwo/wALBj9GljBR2i/nA/xlVlXv63mONKnPbr+2yGiCA= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746757096; c=relaxed/simple; bh=mxDVPjsDKcDaT0A+7FtJ1iu07Vwd+q9XbsTcO2uDOZc=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=qQ4QkoVfx6MnUNWoMP97y8QjYC6j+0gzpDjYRDZ4qwwJQlbMv5KZ5efZ9eWKt+syMddg49gB0vWdioMDBVdFdwWpKQwmJ0GmBuViovpzyaEORhl9hv3MNJAT1FQLnG26JHnUCbHEb85VZmseAjZTKYhCKDz7kkakiiDDVT3x0H8= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=45.249.212.190 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.19.88.163]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4ZtscS3hC9z2CddF; Fri, 9 May 2025 09:59:04 +0800 (CST) Received: from kwepemj200003.china.huawei.com (unknown [7.202.194.15]) by mail.maildlp.com (Postfix) with ESMTPS id D8FCD18001B; Fri, 9 May 2025 10:02:40 +0800 (CST) Received: from localhost.huawei.com (10.90.30.45) by kwepemj200003.china.huawei.com (7.202.194.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Fri, 9 May 2025 10:02:40 +0800 From: Qinxin Xia To: <21cnbao@gmail.com>, CC: , , , , , , , , Subject: [PATCH v3 1/4] dma-mapping: benchmark: Add padding to ensure uABI remained consistent Date: Fri, 9 May 2025 10:02:35 +0800 Message-ID: <20250509020238.3378396-2-xiaqinxin@huawei.com> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20250509020238.3378396-1-xiaqinxin@huawei.com> References: <20250509020238.3378396-1-xiaqinxin@huawei.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To kwepemj200003.china.huawei.com (7.202.194.15) Content-Type: text/plain; charset="utf-8" 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 Acked-by: Barry Song --- 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 */ --=20 2.33.0