From: Greg KH <gregkh@linuxfoundation.org>
To: Tyler Hicks <code@tyhicks.com>
Cc: kernel test robot <lkp@intel.com>,
Hardik Garg <hargar@linux.microsoft.com>,
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
Date: Sun, 28 May 2023 08:40:11 +0100 [thread overview]
Message-ID: <2023052853-harvest-coasting-f857@gregkh> (raw)
In-Reply-To: <ZHFaw6k8+2+MM1jv@sequoia>
On Fri, May 26, 2023 at 08:20:03PM -0500, Tyler Hicks wrote:
> 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 <sha1> 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.
Yes, this is the right thing to do, you can ignore the bot :)
next prev parent reply other threads:[~2023-05-28 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 23:21 [PATCH 6.1 5.15 5.10 5.4 4.19 4.14] selftests/memfd: Fix unknown type name build failure Hardik Garg
2023-05-26 23:23 ` kernel test robot
2023-05-27 1:20 ` Tyler Hicks
2023-05-28 7:40 ` Greg KH [this message]
2023-05-27 1:21 ` Tyler Hicks
2023-05-28 7:42 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2023052853-harvest-coasting-f857@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=code@tyhicks.com \
--cc=hargar@linux.microsoft.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox