From: Shuah Khan <skhan@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>, Tejun Heo <tj@kernel.org>
Cc: Edward Liaw <edliaw@google.com>,
John Hubbard <jhubbard@nvidia.com>,
linux-kselftest@vger.kernel.org, torvalds@linux-foundation.org,
shuah <shuah@kernel.org>,
skhan@linuxfoundation.org
Subject: Re: -D_GNU_SOURCE kselftest breakage in mainline
Date: Thu, 16 May 2024 21:41:10 -0600 [thread overview]
Message-ID: <24975952-b1fa-44a5-bac5-aef538ad0c09@linuxfoundation.org> (raw)
In-Reply-To: <d885eba8-8fda-4e36-af5c-38eefd6f0af7@sirena.org.uk>
On 5/16/24 09:09, Mark Brown wrote:
> On Thu, May 16, 2024 at 08:53:52AM -0600, Shuah Khan wrote:
>> On 5/16/24 08:02, Mark Brown wrote:
>
>>> I'm seeing quite a lot of breakage in mainline as a result of
>>> daef47b89efd0b7 ("selftests: Compile kselftest headers with
>>> -D_GNU_SOURCE") and daef47b89efd0 ("selftests: Compile kselftest headers
>>> with -D_GNU_SOURCE") - thus far I've found that the use of
>>> static_assert() is triggering build breaks where testsuites aren't
>>> picking up the addition of _GNU_SOURCE (including stopping installing
>>> the other tests in the same directory), and there's a bunch of tests
>>> which #define _GNU_SOURCE in their code and now trigger build warnings.
>>> I'm looking at fixes and mitigations now.
>
>> Would it be better to revert this for now and get this for now? I wouldn't
>> want you to extra busy work to workaround this.
>
I determined the best option now is reverting the 3 patches.
commit daef47b89efd0b745e8478d69a3ad724bd8b4dc6
"selftests: Compile kselftest headers with -D_GNU_SOURCE"
"selftests/sgx: Include KHDR_INCLUDES in Makefile"
commit 2c3b8f8f37c6c0c926d584cf4158db95e62b960c
"selftests/cgroup: Drop define _GNU_SOURCE"
commit c1457d9aad5ee2feafcf85aa9a58ab50500159d2
I have this in linux-kselftest next now and will send pull
request to Linus this weekend.
Tejun, I made sure cgroup compiles after reverting the framework
patch and the cgroup test patch.
Mark,
Thank you Mark for finding the problem and sending in mitigation
fixes. I will hold off on your alsa patch:
kselftest/alsa: Ensure _GNU_SOURCE is defined
https://patchwork.kernel.org/project/linux-kselftest/patch/20240516-kselftest-fix-gnu-source-v1-1-e482ca6bfff7@kernel.org/
There is no need to for the following patch
kselftest: Desecalate reporting of missing _GNU_SOURCE
https://patchwork.kernel.org/project/linux-kselftest/patch/20240516-kselftest-mitigate-gnu-source-v1-1-a0e814ff2874@kernel.org/
thanks,
-- Shuah
prev parent reply other threads:[~2024-05-17 3:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 14:02 -D_GNU_SOURCE kselftest breakage in mainline Mark Brown
2024-05-16 14:53 ` Shuah Khan
2024-05-16 15:09 ` Mark Brown
2024-05-17 3:41 ` Shuah Khan [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=24975952-b1fa-44a5-bac5-aef538ad0c09@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=edliaw@google.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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