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 1111336E484 for ; Tue, 23 Jun 2026 10:08:37 +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=1782209319; cv=none; b=tzYvXqHNIAmkAxcg3Hz+9Xoc/ptrP8VMtPX0JsV6BbXVl9xc+VhQfwwzktKK3VNE5O3VO/GrBF72E0EErlqNjEdSeJOP3JYOG6wK67W5eMst24T2UU0ngAhykOe2S3hLKGvSe7xQcDvbCgGvxgI4zdHx5/LUel8YgiWCAMBsGfk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782209319; c=relaxed/simple; bh=hQcypG+re3t6P3tkSTeQcnAx8XwpVe/MhHKKLFysLtE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=DtahlGfAAzyQp9is6MT+NS+Mf75eeyNdAG4JbGIQvrmMtbY98ZxwDzyD1hr0Z9PCZ8PFRet7GPxQUOFoWG+4CaaUdljn+tR26REhSa5/NGs84BL9o2Q124KYTIJVZviGcSp7TIxIo6qL4Ws/ayQ4Xj+ShokyIjSbr7r6oVKzTng= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=hL8dPLl2; 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="hL8dPLl2" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 600C91F000E9; Tue, 23 Jun 2026 10:08:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782209317; bh=EarkyJBnDqnFqSO5fYETAhufrAjwPx1wYCTrBDOh/fE=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=hL8dPLl2eSFhMWTGjZ58D9t0L2fZD36v4cEpXmeX2vod1MEQmC7X8hrlRv0Smn/Oh YJ7IK/mRmly7OCs+bJIQSS1HPFID+F5LJKbQ57m5dt9ZW/5NpNSQ4l5Szb1LSn6qw5 YJ52BgdHnrD+fKe5ZH37Gme6yEIj9PavF2ydwXFd0OFfGu2ButLzrPmFj4HvfJwAGc +uIn++yZEfbNM7UC6FYTz0/U+AppBVDLh1hVwEbomtV/AcBx5HQv5xbOo5VmijMA/w esMRBseeCQGVHTI+etOiDQSP2BFqrZQvKu5yfamQovWe5a3Fv8l+ocBeSVVf7lzxuf AJj63/YCOy+ow== Date: Tue, 23 Jun 2026 13:08:30 +0300 From: Mike Rapoport To: tarunsahu@google.com Cc: Pasha Tatashin , Pratyush Yadav , Alexander Graf , Andrew Morton , linux-mm@kvack.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Mike Rapoport , Breno Leitao Subject: Re: [PATCH v4 2/2] luo: Update serialized data to use KHOSER_PTR Message-ID: References: <20260622225736.2961438-1-tarunsahu@google.com> <20260622225736.2961438-3-tarunsahu@google.com> <178220761164.162773.6384380547612711985.b4-review@b4> <9huzpl1h37hj.fsf@tarunix.c.googlers.com> 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: <9huzpl1h37hj.fsf@tarunix.c.googlers.com> On Tue, Jun 23, 2026 at 09:56:40AM +0000, tarunsahu@google.com wrote: > Mike Rapoport writes: > > > On Mon, 22 Jun 2026 22:57:36 +0000, Tarun Sahu wrote: > >> Convert raw serialized_data to KHO serializeable pointer (KHOSER_PTR). > >> This series also takes care of resolving the bug with memfd of using > >> phys_to_virt before checking the args->serialized_data value. > > > > For easier backporting the memfd fix should be a standalone commit that > > comes first in the series. > > > > Other than that > > It will break compilation for individual patch. For example, memfd_luo > changes are hard coded dependent on the args->serialized_data > conversion to KHOSER_PTR? > > Maybe I did not understand, Could you please explain what you mean? Sorry I wasn't clear. If people think it's important to have the memfd_luo fix in 7.1, the fix should be the first patch in the series and shouldn't use KHOSER pointers. > > > > Acked-by: Mike Rapoport (Microsoft) > > > > -- > > Sincerely yours, > > Mike. -- Sincerely yours, Mike.