From: shuah <shuah@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christian Brauner <christian@brauner.io>,
kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
bgolaszewski@baylibre.com, Daniel Borkmann <daniel@iogearbox.net>,
bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
shuah <shuah@kernel.org>
Subject: Re: Linux 5.4 kselftest known issues - update
Date: Thu, 3 Oct 2019 08:30:55 -0600 [thread overview]
Message-ID: <2a835150-d7f1-1c4a-80cb-d385f799dd14@kernel.org> (raw)
In-Reply-To: <a293684f-4ab6-51af-60b1-caf4eb97ff05@linuxfoundation.org>
On 9/26/19 11:41 AM, Shuah Khan wrote:
> Here are the know kselftest issues on Linux 5.4 with
> top commit commit 619e17cf75dd58905aa67ccd494a6ba5f19d6cc6
> on x86_64:
>
> The goal is to get these addressed before 5.4 comes out.
All of these issues are now fixed, except the bpf llvm dependency.
These fixes should all be in linux-next if they haven't already.
>
> 3 build failures and status:
>
> pidfd - undefined reference to `pthread_create' collect2: error: ld
> returned 1 exit status
>
> Fixed: https://patchwork.kernel.org/patch/11159517/
In
>
> bfp (two issues)
>
> 1. "make TARGETS=bpf kselftest" build fails
> Makefile:127: tools/build/Makefile.include: No such file or directory
https://patchwork.kernel.org/patch/11163601/
In bpf fixes tree
>
> This is due to recent kbuild changes and I have a patch ready to send.
>
> 2. Related to llvm latest version dependency. This is a hard dependency.
> Unless users upgrade to latest llvvm, bpf test won't run. The new llvm
> might not be supported on all distros yet, in which case bpf will not
> get tested in some rings and on some architectures.
>
> gpio
>
> "make TARGETS=gpio kselftest" build fails
>
> Makefile:23: tools/build/Makefile.include: No such file or directory
https://patchwork.kernel.org/patch/11163603/
>
> This is due to recent kbuild changes and I have a patch ready to send.
>
> kvm
>
> "make TARGETS=kvm kselftest" build fails due --no-pie flags.
https://patchwork.kernel.org/patch/11171893/
I haven't found any new ones on x86_64 as of 5.4-rc1
thanks,
-- Shuah
next prev parent reply other threads:[~2019-10-03 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 17:41 Linux 5.4 kselftest known issues Shuah Khan
2019-10-03 14:30 ` shuah [this message]
2019-10-04 9:43 ` Linux 5.4 kselftest known issues - update Christian Brauner
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=2a835150-d7f1-1c4a-80cb-d385f799dd14@kernel.org \
--to=shuah@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=bpf@vger.kernel.org \
--cc=christian@brauner.io \
--cc=daniel@iogearbox.net \
--cc=kvm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).