All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andy Lutomirski <luto@kernel.org>
Subject: selftests broke upstream
Date: Wed, 1 Mar 2017 10:24:28 +0100	[thread overview]
Message-ID: <20170301092428.GA18547@gmail.com> (raw)


Hi,

The x86 selftests build broke upstream:

 triton:~/tip/tools/testing/selftests/x86> make
 Makefile:44: warning: overriding recipe for target 'clean'
 ../lib.mk:51: warning: ignoring old recipe for target 'clean'
 gcc -m32 -o /single_step_syscall_32 -O2 -g -std=gnu99 -pthread -Wall  
 single_step_syscall.c -lrt -ldl -lm
 /usr/bin/ld: cannot open output file /single_step_syscall_32: Permission denied
 collect2: error: ld returned 1 exit status
 Makefile:47: recipe for target '/single_step_syscall_32' failed
 make: *** [/single_step_syscall_32] Error 1

It used to be possible to build only the x86 testcases in that directory.

Another problem is that the pkeys testcases are still very noisy:

gcc -m64 -o /home/mingo/tip/tools/testing/selftests/x86/protection_keys_64 -O2 -g -std=gnu99 -pthread -Wall  protection_keys.c -lrt -ldl
In file included from protection_keys.c:45:0:
pkey-helpers.h: In function ‘sigsafe_printf’:
pkey-helpers.h:41:3: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
   write(1, dprint_in_signal_buffer, len);
   ^
protection_keys.c: In function ‘dumpit’:
protection_keys.c:407:3: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
   write(1, buf, nr_read);
   ^
gcc -m64 -o /home/mingo/tip/tools/testing/selftests/x86/test_vdso_64 -O2 -g -std=gnu99 -pthread -Wall  test_vdso.c -lrt -ldl
test_vdso.c: In function ‘main’:
test_vdso.c:98:37: warning: ‘node’ may be used uninitialized in this function [-Wmaybe-uninitialized]
   if (!ret_vsys && (cpu_vsys != cpu || node_vsys != node))
                                     ^
test_vdso.c:78:12: note: ‘node’ was declared here
   unsigned node;
            ^

I thought all this got already fixed?

Thanks,

	Ingo

             reply	other threads:[~2017-03-01  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01  9:24 Ingo Molnar [this message]
2017-03-01 14:29 ` selftests broke upstream Shuah Khan
2017-03-01 22:50   ` Shuah Khan

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=20170301092428.GA18547@gmail.com \
    --to=mingo@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=shuahkh@osg.samsung.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.