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 16014393DDB for ; Fri, 19 Jun 2026 14:11:35 +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=1781878297; cv=none; b=qARy5xxuLV9bGRSemlZgbTBK3DptCRg6JypABKWf439vnxKer73AgN3qdwrqhTaPchUO8/xlAmHd6uPOaY/7JVfsMr3BkVt9E+i4+P6EMw7PNHZ8mLHonZ9h9eOUeTlc8dROI1iMbJuRnXusyUpo2c0ZCdQ7DZlU0Ut8LTahIgU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781878297; c=relaxed/simple; bh=mLX7Gx5fvpI9D3i+MsHXnwHC32HWiqL/SIchBzBxt4s=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=myE+YqKiWJAaDYBY8TPNsjnihLahTaswUhaP9NVcEiRrHnPAV80yX6gHIpToQFL/0NPdmt9d72H6RAHXs6eGnUNoi515r3HsaNUhd+ILZi8sTLHt7YiT4tW+e72TJb4KpWPvRvk148cxc3o0zyN5VRRCtBQEYqIChUd2STGFMgo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=L+HldSM1; 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="L+HldSM1" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2E4A31F00ACA; Fri, 19 Jun 2026 14:11:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1781878295; bh=Ipm4VnnCUVKjt+hErgryje+qavsLSdr26B/MMNK2kNQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=L+HldSM1+o+tWkDbIG8K43jsuVzgtp7NdNSEk+Jfu5jaNR8rxpCcgZQ1MW+aX0c84 ouXIbhwhAm5lGTM1WmZActEB2i26IaKhRotfbVrV6y7ZtrJFbUSh8fyun8qtAftWem /zWPuOMsg5zELZf+0Ns/LUncVu87F4uUCHkmHWFSedkUVNDkXLW3w30OT/4k/nxMx0 uWnROWM2Wa1zp5kmF86bOyH8vgVmiXn6lepY2aJlhkfkhLCJpu9AT1MjcbTcVQZ66u 5ZOTyvO9Gx5ZSwSrtrL8e8MfzACbVoRLnAmhuTcrUtEsF94lZ7t3KEtMpEPmkIrYne G74ICyfzZFn2A== From: Pratyush Yadav To: tarunsahu@google.com Cc: Alexander Graf , Pratyush Yadav , Mike Rapoport , Andrew Morton , Pasha Tatashin , linux-kernel@vger.kernel.org, linux-mm@kvack.org, kexec@lists.infradead.org Subject: Re: [PATCH v2 0/2] luo: migrate serialized_data to type-safe KHO pointers In-Reply-To: <9huzv7beloza.fsf@tarunix.c.googlers.com> (tarunsahu@google.com's message of "Fri, 19 Jun 2026 12:00:09 +0000") References: <9huzv7beloza.fsf@tarunix.c.googlers.com> Date: Fri, 19 Jun 2026 16:11:32 +0200 Message-ID: <2vxzmrwqoc17.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Fri, Jun 19 2026, tarunsahu@google.com wrote: > +Mike, +Pasha > > This is currently rebased on top of mailine, also can be applied to > liveupdate/fixes with no conflict. I would like to know which release > cycle we are targeting for this, so That I can rebase it accordingly? > > As for liveupdate/next, it needs some conlfict resolution. Base it on liveupdate/next after the merge window. Since nothing is actively broken (as far as I can tell), I don't think we should take it via fixes. We should do it via the 7.3 merge window. > > Tarun Sahu writes: > >> Covvert 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. [...] -- Regards, Pratyush Yadav