linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: "open list:KERNEL SELFTEST FRAMEWORK"  <linux-kselftest@vger.kernel.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 5.4 kselftest known issues
Date: Thu, 26 Sep 2019 11:41:25 -0600	[thread overview]
Message-ID: <a293684f-4ab6-51af-60b1-caf4eb97ff05@linuxfoundation.org> (raw)

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.

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/

bfp (two issues)

1. "make TARGETS=bpf kselftest" build fails
Makefile:127: tools/build/Makefile.include: No such file or directory

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

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.

I am working on a fix for this. no-pie-option defines aren't working
correctly and I suspect try-run miht not be defined in this kselftest
build case.

thanks,
-- Shuah












             reply	other threads:[~2019-09-26 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 17:41 Shuah Khan [this message]
2019-10-03 14:30 ` Linux 5.4 kselftest known issues - update shuah
2019-10-04  9:43   ` 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=a293684f-4ab6-51af-60b1-caf4eb97ff05@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@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;
as well as URLs for NNTP newsgroup(s).