From: "Theodore Ts'o" <tytso@mit.edu>
To: fengguang.wu@intel.com
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, hpa@zytor.com,
mingo@redhat.com, tglx@linutronix.de
Subject: checksyscall warning: #warning syscall getrandom not implemented
Date: Fri, 18 Jul 2014 04:15:22 -0400 [thread overview]
Message-ID: <20140718081522.GD1491@thunk.org> (raw)
In-Reply-To: <53c860e1.NmkuD6+D1cCHfXVw%fengguang.wu@intel.com>
On Fri, Jul 18, 2014 at 07:48:49AM +0800, kbuild test robot wrote:
> All warnings:
>
> <stdin>:1229:2: warning: #warning syscall sched_setattr not implemented [-Wcpp]
> <stdin>:1232:2: warning: #warning syscall sched_getattr not implemented [-Wcpp]
> <stdin>:1235:2: warning: #warning syscall renameat2 not implemented [-Wcpp]
> >> <stdin>:1238:2: warning: #warning syscall getrandom not implemented [-Wcpp]
> --
> kernel/time/Kconfig:162:warning: range is invalid
> <stdin>:1229:2: warning: #warning syscall sched_setattr not implemented [-Wcpp]
> <stdin>:1232:2: warning: #warning syscall sched_getattr not implemented [-Wcpp]
> <stdin>:1235:2: warning: #warning syscall renameat2 not implemented [-Wcpp]
> >> <stdin>:1238:2: warning: #warning syscall getrandom not implemented [-Wcpp]
I was trying to figure out why this warning was happening, because I
was pretty sure I had properly wired up the getrandom syscall. It
looks like the problem was a stale unistd_32.h.
At some point, apprently the generated unistd.h file migrated from:
arch/x86/include/generated/asm/unistd_32.h
to
arch/x86/include/generated/uapi/asm/unistd_32.h
The stale unistd_32.h which was getting picked up by the checksyscalls
script, and this was causing all of these warnings --- both in my
tree, and apparently, the kbuild test robot's tree. It looks like
after the migration, the Makefiles aren't deleting the old generated
unistd.h file automatically. I tried to go through the Makefiles,
quickly got a headache, and decided it was easier to report the
problem than to send a patch :-P
There's a simple workaround anyway. Once I deleted the old, stale,
generated unistd_32.h file, and reran the build, all of the
checksyscall warnings went away.
- Ted
parent reply other threads:[~2014-07-18 8:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <53c860e1.NmkuD6+D1cCHfXVw%fengguang.wu@intel.com>]
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=20140718081522.GD1491@thunk.org \
--to=tytso@mit.edu \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 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.