From: Nathan Chancellor <nathan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
Kees Cook <keescook@chromium.org>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: stable@vger.kernel.org, llvm@lists.linux.dev
Subject: Apply a52f8a59aef46b59753e583bf4b28fccb069ce64 to 5.15 through 4.19
Date: Mon, 15 Nov 2021 11:39:18 -0700 [thread overview]
Message-ID: <YZKpVkYpYfYfHD50@archlinux-ax161> (raw)
Hi Greg and Sasha,
There is a build error with newer versions of clang due to a broken
FORTIFY_SOURCE implementation, which has never worked:
https://github.com/ClangBuiltLinux/linux/issues/1496
https://github.com/ClangBuiltLinux/continuous-integration2/actions/runs/1457787760
Please apply upstream commit a52f8a59aef4 ("fortify: Explicitly disable
Clang support") to 5.15 through 4.19 to resolve this. It should apply
cleanly.
Cheers,
Nathan
next reply other threads:[~2021-11-16 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 18:39 Nathan Chancellor [this message]
2021-11-19 12:35 ` Apply a52f8a59aef46b59753e583bf4b28fccb069ce64 to 5.15 through 4.19 Greg Kroah-Hartman
2021-11-19 16:16 ` Kees Cook
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=YZKpVkYpYfYfHD50@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--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