From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:54180 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727084AbeLEJSH (ORCPT ); Wed, 5 Dec 2018 04:18:07 -0500 From: Carlos Maiolino To: linux-fsdevel@vger.kernel.org Cc: hch@lst.de, adilger@dilger.ca, sandeen@redhat.com, david@fromorbit.com Subject: [PATCH 07/10] fs: Use a void pointer to store fiemap_extent Date: Wed, 5 Dec 2018 10:17:25 +0100 Message-Id: <20181205091728.29903-8-cmaiolino@redhat.com> In-Reply-To: <20181205091728.29903-1-cmaiolino@redhat.com> References: <20181205091728.29903-1-cmaiolino@redhat.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Once fieinfo will carry either a kernel pointer or a user pointer for holding struct fiemap_extent location , use a void pointer to hold its address. Signed-off-by: Carlos Maiolino --- include/linux/fs.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/include/linux/fs.h b/include/linux/fs.h index a7ca228bd191..16a58dfe09cc 100644 --- a/include/linux/fs.h +++ b/include/linux/fs.h @@ -1701,9 +1701,8 @@ struct fiemap_extent_info { u64 fi_len; unsigned int fi_extents_mapped; /* Number of mapped extents */ unsigned int fi_extents_max; /* Size of fiemap_extent array */ - struct fiemap_extent __user *fi_extents_start; /* Start of - fiemap_extent - array */ + void *fi_extents_start; /* Start of fiemap_extent + array */ }; int fiemap_fill_next_extent(struct fiemap_extent_info *info, u64 logical, u64 phys, u64 len, u32 flags); -- 2.17.2