From: Tom Saeger <tom.saeger@oracle.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Michal Marek <michal.lkml@markovi.net>,
Nathan Chancellor <nathan@kernel.org>,
Nick Clifton <nickc@redhat.com>,
Jose Marchesi <jose.marchesi@oracle.com>,
stable@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 5.15 5.10 5.4 1/1] arm64: fix Build ID if CONFIG_MODVERSIONS
Date: Fri, 9 Dec 2022 13:57:43 -0600 [thread overview]
Message-ID: <20221209195743.dkk4b52gvm2hej3h@oracle.com> (raw)
In-Reply-To: <CAKwvOdkRrNZk_kWp-WvHduPzfqqDj=FyGbeJpNr-26QbCcyqoA@mail.gmail.com>
On Fri, Dec 09, 2022 at 09:58:42AM -0800, Nick Desaulniers wrote:
> On Thu, Dec 8, 2022 at 3:31 PM Tom Saeger <tom.saeger@oracle.com> wrote:
> >
> > Can folks confirm/deny ld behavior is expected (arm64)?
> > And whether the above patch would be an acceptable fix for these kernel
> > versions?
>
> If you remove `-z noexecstack`, aren't you just going to trigger
> warnings from BFD again?
hmm, probably so, let me check
>
> At the least consider adding a fixes tag for 0d362be5b142, and note
> that stable doesn't have
> 7b4537199a4a, in the commit message.
> --
> Thanks,
> ~Nick Desaulniers
prev parent reply other threads:[~2022-12-09 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1670358255.git.tom.saeger@oracle.com>
[not found] ` <9e387b71ce45d8b7fe9f2b9c52694e3df33f0c7a.1670358255.git.tom.saeger@oracle.com>
[not found] ` <Y5JKYA53GnPrsr+f@kroah.com>
2022-12-08 23:31 ` [PATCH 5.15 5.10 5.4 1/1] arm64: fix Build ID if CONFIG_MODVERSIONS Tom Saeger
2022-12-09 6:50 ` Greg Kroah-Hartman
2022-12-09 17:58 ` Nick Desaulniers
2022-12-09 19:57 ` Tom Saeger [this message]
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=20221209195743.dkk4b52gvm2hej3h@oracle.com \
--to=tom.saeger@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jose.marchesi@oracle.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nickc@redhat.com \
--cc=npiggin@gmail.com \
--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