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 BE4F018EB0; Thu, 4 Jun 2026 00:05:56 +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=1780531557; cv=none; b=p+092E1E0B3gR6Wv7u6SnLX29UaOYywm9/Q5wddmxuI4bJjRhUBiLN5ASNx5d0qmOHjUec8H9BH8XYsoc1SfEhmUcfM9dIKKksRNOHOp0Ssghs540LJOAxjpXDwTVQ89bDf8PXkCNSNDfNWE+T10d8Xv4JOvre5swEXvYmr3gRg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780531557; c=relaxed/simple; bh=kxp8vw8zN5QjoR+2FH+m9rOdIREfk1SQW9Cl1AogwWI=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=tic/LZffMlYbGcz0RFnlrjuyceaLRGT8U9JMsp2X/JjDMdjQaUcFsRDYSm9PzvY08tIF9yJ1YANsAjsP9gq9iF8ZvWKXNjtVTj11IWIgxWNEXv9mf28/wekyAKnss3SnH4hgePRg6WVaA648kYKZLU3nessftDrdXJQCN7yqy8k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=lppVKYK8; 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="lppVKYK8" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4EC8A1F00898; Thu, 4 Jun 2026 00:05:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1780531556; bh=qrSyg3+Cl1koNj1o41wo6dzgLaX0j53jxM9J07df6Qw=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=lppVKYK83KW4zPNCNEVHEThHQVDFHEbbugJ4F4uvGsuA0j7ZC53CX+NP5ajNnVpc7 ZY42LWJlI/N763ux95UtcslZ01dNmblkidj57ACGe/4h7hODk+81uZMafHNr6dFJJP m2NZRZpJWPhx1Ci0oRcuPJQ6UQTo3eWIb5boV1NmtKjnjE760+WWsoBoipoAiizdgg YrqQGhvXdgB/NsEt3gvIC7h8k3483CCGjC1gJiBSglrjVg+40MIW3MWmPxDeuLHv4Z 31K0iXDGrhnio1ZR2iQ8fsP2vbJyI8P2l7RGQoxs4LOtlLPwOYO55VJW+owhtQo04H WY5To6j+AYxeg== From: Sasha Levin To: gregkh@linuxfoundation.org, sashal@kernel.org, stable@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Harshit Mogalapalli , Mimi Zohar , Alexander Graf , Ard Biesheuvel , Borislav Betkov , guoweikang , Henry Willard , "H. Peter Anvin" , Ingo Molnar , Jiri Bohac , Joel Granados , Jonathan McDowell , Mike Rapoport , Paul Webb , Sohil Mehta , Sourabh Jain , Thomas Gleinxer , Yifei Liu , Baoquan He , Andrew Morton , Wenshan Lan Subject: Re: [PATCH 6.6.y 1/3] ima: verify the previous kernel's IMA buffer lies in addressable RAM Date: Wed, 3 Jun 2026 20:05:41 -0400 Message-ID: <20260603210831.item006@kernel.org> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260603130239.81400-1-jetlan9@163.com> References: <20260603130239.81400-1-jetlan9@163.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit > [PATCH 6.6.y 1/3] ima: verify the previous kernel's IMA buffer lies in > addressable RAM > [PATCH 6.6.y 2/3] of/kexec: refactor ima_get_kexec_buffer() to use > ima_validate_range() > [PATCH 6.6.y 3/3] x86/kexec: add a sanity check on previous kernel's > ima kexec buffer All three queued for 6.6.y as an ordered series, thanks. This also resolves the earlier build failure from cherry-picking 3/3 alone (which I'd had to revert) since 1/3 now provides ima_validate_range() ahead of its x86 caller. -- Thanks, Sasha