From: David Drysdale <drysdale@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [next:master 10653/11539] arch/x86/ia32/audit.c:38:14: sparse: incompatible types for 'case' statement
Date: Tue, 9 Dec 2014 09:02:02 +0000 [thread overview]
Message-ID: <CAHse=S-7g77Dv+j7mUXgmAACs4czLQSv0VA361t=hecwQr03rg@mail.gmail.com> (raw)
In-Reply-To: <20141208130344.9dc58fda1862a4a4a14c7c6b@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]
On Mon, Dec 8, 2014 at 9:03 PM, Andrew Morton <akpm@linux-foundation.org>
wrote:
> On Tue, 9 Dec 2014 02:40:09 +0800 kbuild test robot <
> fengguang.wu@intel.com> wrote:
>
> > tree: git://
> git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: cf12164be498180dc466ef97194ca7755ea39f3b
> > commit: b4baa9e36be0651f7eb15077af5e0eff53b7691b [10653/11539] x86: hook
> up execveat system call
> > reproduce:
> > # apt-get install sparse
> > git checkout b4baa9e36be0651f7eb15077af5e0eff53b7691b
> > make ARCH=x86_64 allmodconfig
> > make C=1 CF=-D__CHECK_ENDIAN__
> >
> >
> > sparse warnings: (new ones prefixed by >>)
> >
> > arch/x86/ia32/audit.c:38:14: sparse: undefined identifier
> '__NR_execveat'
> > >> arch/x86/ia32/audit.c:38:14: sparse: incompatible types for 'case'
> statement
> > arch/x86/ia32/audit.c:38:14: sparse: Expected constant expression in
> case statement
> > arch/x86/ia32/audit.c: In function 'ia32_classify_syscall':
> > arch/x86/ia32/audit.c:38:7: error: '__NR_execveat' undeclared (first
> use in this function)
> > case __NR_execveat:
> > ^
> > arch/x86/ia32/audit.c:38:7: note: each undeclared identifier is
> reported only once for each function it appears in
> > --
>
> Confused. This makes no sense and I can't reproduce it.
>
Ditto.
Someone else did previously[1] have a build problem from a stale copy of
arch/x86/include/generated/asm/unistd_32.h in their tree, but I don't know
how that could happen.
[1] https://lkml.org/lkml/2014/11/25/542
[-- Attachment #2: Type: text/html, Size: 2768 bytes --]
next prev parent reply other threads:[~2014-12-09 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 18:40 kbuild test robot
2014-12-08 21:03 ` Andrew Morton
2014-12-09 9:02 ` David Drysdale [this message]
2014-12-09 19:27 ` Fengguang Wu
2014-12-09 20:08 ` Fengguang Wu
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='CAHse=S-7g77Dv+j7mUXgmAACs4czLQSv0VA361t=hecwQr03rg@mail.gmail.com' \
--to=drysdale@google.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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