From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D2D0BC77B73 for ; Sat, 27 May 2023 01:20:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229762AbjE0BUL (ORCPT ); Fri, 26 May 2023 21:20:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58208 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229716AbjE0BUL (ORCPT ); Fri, 26 May 2023 21:20:11 -0400 Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2FFDCD9 for ; Fri, 26 May 2023 18:20:10 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id C3D7E320090B; Fri, 26 May 2023 21:20:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 26 May 2023 21:20:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tyhicks.com; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1685150406; x=1685236806; bh=1d 7oKPGVdWB5JAEgMj9dkOXHwQuyjIMmlSbKS0bEYuk=; b=QfQ9unCm3iciiXRh6f V7W/J1OfSjCOSBSgAKv0QLLxkU1E+74aqKQCauR71jmTRE+jCCcJWqUKUe2Bq8DU vtKYPtUI9gp3t/bm2txM0tXS2WHI858sp9Ak9p2mQU3Jic1NDoTyRAOGoCv65D6p ZbAr3oqkfhFdj36kOqj3m9kzP6Ojqnpn4ZFRoyy6Rzy21BzzOrK6YUK9eQRh272a 5+tdUKrSrgQeUALGJRIRFfTmmSv32ssPKcQQnpxzpfZ3yJXbxWkbmXsBtuC8H0Ca S27fv8BJdf1pbixqlKlhdtMNYKdSYWC28f8UL9EI/0Rfuz1TpzzEHsBpBFzucAwE YtoQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1685150406; x=1685236806; bh=1d7oKPGVdWB5J AEgMj9dkOXHwQuyjIMmlSbKS0bEYuk=; b=DtLlItFUFURx8AO3WVuiUA2QdvVRc dGlV2AA1jVoj+jhOMi0VZ8gGN3+e78jtxddQaqooOqF5X51H3U0ibVD0S9u6QtMv yczHHhxKm2+PVpmdLqIGJ4HMoQkElCExTJQcVRa/ZeyoCJM+CKiniRJCPb46JFiV TyEihR8F7Pv7fHZfOIPLGmEnefXNxB4uetBstALK3nAEQCvSiB1g/BxjXmT64ZOD wjBWnBEi0qZbqpsw4lCwEHY2p3FUYvBaEZBhmCtkcpcvUay7+r6c8gIUyuCpOO0/ ngs1UjjglKoHdGbj/GZ2hxgZG39duodP1z4aeej6rISHaFA8H/finY0fQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeektddggeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepvfihlhgv rhcujfhitghkshcuoegtohguvgesthihhhhitghkshdrtghomheqnecuggftrfgrthhtvg hrnhepjeeigfdvheejhefgtdfgfffgfeejveejueejfedvgfefveevudfgtdfgteegueff necuffhomhgrihhnpehkvghrnhgvlhdrohhrghdpghhithhhuhgsrdgtohhmnecuvehluh hsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheptghouggvsehthihh ihgtkhhsrdgtohhm X-ME-Proxy: Feedback-ID: i78e14604:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 26 May 2023 21:20:05 -0400 (EDT) Date: Fri, 26 May 2023 20:20:03 -0500 From: Tyler Hicks To: kernel test robot Cc: Hardik Garg , stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev Subject: Re: [PATCH 6.1 5.15 5.10 5.4 4.19 4.14] selftests/memfd: Fix unknown type name build failure Message-ID: References: <20230526232136.255244-1-hargar@linux.microsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On 2023-05-27 07:23:22, kernel test robot wrote: > Hi, > > Thanks for your patch. > > FYI: kernel test robot notices the stable kernel rule is not satisfied. > > Rule: 'Cc: stable@vger.kernel.org' or 'commit upstream.' > Subject: [PATCH 6.1 5.15 5.10 5.4 4.19 4.14] selftests/memfd: Fix unknown type name build failure > Link: https://lore.kernel.org/stable/20230526232136.255244-1-hargar%40linux.microsoft.com > > The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > > Please ignore this mail if the patch is not relevant for upstream. I think Hardik did the right thing here. This is a build failure bug that's present in stable kernels but was fixed in upstream by an unrelated commit: 11f75a01448f ("selftests/memfd: add tests for MFD_NOEXEC_SEAL MFD_EXEC") It wouldn't be right to backport that patch because MFD_NOEXEC_SEAL and MFD_EXEC weren't introduced until v6.3. There was an (unmerged) attempt to fix this specific build failure in upstream: https://lore.kernel.org/all/20211203024706.10094-1-luke.nowakowskikrijger@canonical.com/ Hardik opted to follow what was done upstream in a patch specifically for the stable tree. Tyler > > -- > 0-DAY CI Kernel Test Service > https://github.com/intel/lkp-tests/wiki > > >