From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 DABCC3EEAF2 for ; Tue, 16 Jun 2026 06:44:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781592291; cv=none; b=iSS9JQPykNelK8EL7J2PMhbj30W3361b4nwVPEvPcrXafvlryKM0/Rj7k8xajdm8i8rGTwaNwWM8vM+wGfYPua2U6YcNwocKrOwT5VkBhOCQ0TZgH7lj0+Cq+v4hGeUCmvV35HTSmAhMAIz/lWcb3CjUjhQHXc3oE6Yaul+qQus= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781592291; c=relaxed/simple; bh=RsjuNYE4llQgcDpdtx1xez6/ZssqVhlZ3OSb5gFFS9E=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Cw9Tz0fdPyAKW/mtS0OY6NiFwYsz6kYuSZsw+KcM7gxAsRrYppMpfrRibknb2eA+1K9qZoR+yBXKEUNNBScD9JY9SeW+vnhgK1oF4gruVYteWPCsg96Wb1+LNV+2F++k6qRmt9z/9I19af1BmylddrmvwXvpnU97e++psFfk/DA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=lLQcu3J5; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="lLQcu3J5" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E070D1F000E9; Tue, 16 Jun 2026 06:44:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1781592290; bh=9D0UOD8hJI6j+cwdcFWcWcuB2014gIQar2UbjXkYl18=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=lLQcu3J5tA/7uWuT9KRhO3Be4GipsBASKfO4kB7LbHJMzGhMAyNmCM8AgriQ+eE7Q YbzMy1LVJjVPpa8Sz5PKJEnPV5zuMuEVpUr9qBmTMs0zRjV1jrU0zpDc2DJmT62rjj BGoQpV4ujL6xBM05kBId2xC9FarQdNhQdkMwKCBtSlOzz/IxjWthCSwPXRdY86orDZ 2Nh2apsO5+7oUCobWMjhktAX+m+SiRjQCcHGqiX9dAQwdixiFMUk44rmePoIZlvgen SjwRKcIyM0lLsAAhKZN2RZsdLJs13eJ50lxziVHSrxLldvOsX4mEwbCxQzXV1ti+zl PUoVJgFWW9Zeg== Date: Tue, 16 Jun 2026 09:44:44 +0300 From: Mike Rapoport To: Tarun Sahu Cc: Pasha Tatashin , Pratyush Yadav , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, kexec@lists.infradead.org Subject: Re: [PATCH 0/1] mm/memfd_luo: use KHOSER_PTR for serialized_data checks Message-ID: References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Hi, On Mon, Jun 15, 2026 at 01:05:04PM +0000, Tarun Sahu wrote: > Use the KHOSER_PTR interface for serialized_data in memfd_luo to > perform type-safe pointer conversions and checks. > > I have tried to keep the changes minimal. So only changed > the memfd_luo. Would love the suggestions for if we should be changing > struct liveupdate_file_op_args like the following. > > @@ -46,7 +47,7 @@ struct liveupdate_file_op_args { > struct liveupdate_file_handler *handler; > int retrieve_status; > struct file *file; > - u64 serialized_data; > + DECLARE_KHOSER_PTR(serialized_data, void *); Yes, this one please :) > void *private_data; > }; > > Ofcourse, it will require change in liveupdate and luo_file. > > Tarun Sahu (1): > mm/memfd_luo: use KHOSER_PTR for serialized_data checks > > mm/memfd_luo.c | 30 +++++++++++++++++++++--------- > 1 file changed, 21 insertions(+), 9 deletions(-) > > > base-commit: 0e0611827f3349d0a2ac121c023a6d3260dcecdb > -- > 2.54.0.1136.gdb2ca164c4-goog > -- Sincerely yours, Mike.