From: Yujie Liu <yujie.liu@intel.com>
To: Richard Weinberger <richard@nod.at>
Cc: kernel test robot <lkp@intel.com>,
Johannes Berg <johannes.berg@intel.com>,
<oe-kbuild-all@lists.linux.dev>, linux-mm <linux-mm@kvack.org>
Subject: Re: [linux-next:master 12780/13853] arch/um/drivers/harddog_user.c:6:10: fatal error: stdio.h: No such file or directory
Date: Fri, 9 Jun 2023 09:26:22 +0800 [thread overview]
Message-ID: <ZIJ/vvquEQXN8NBf@yujie-X299> (raw)
In-Reply-To: <280967570.292780.1682370047405.JavaMail.zimbra@nod.at>
Hi Richard,
On Mon, Apr 24, 2023 at 11:00:47PM +0200, Richard Weinberger wrote:
> ----- Ursprüngliche Mail -----
> > Von: "kernel test robot" <lkp@intel.com>
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > master
> > head: 3b85b9b39960c08f29fa91b8d984d055dde6017e
> > commit: fc54a4f15988e228cf88f888483e985c5f35031e [12780/13853] um: prevent user
> > code in modules
> > config: um-allmodconfig
> > (https://download.01.org/0day-ci/archive/20230425/202304250419.YtCLtUhG-lkp@intel.com/config)
> > compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> > reproduce (this is a W=1 build):
> > #
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=fc54a4f15988e228cf88f888483e985c5f35031e
> > git remote add linux-next
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > git fetch --no-tags linux-next master
> > git checkout fc54a4f15988e228cf88f888483e985c5f35031e
> > # save the config file
> > mkdir build_dir && cp config build_dir/.config
> > make W=1 O=build_dir ARCH=um olddefconfig
> > make W=1 O=build_dir ARCH=um SHELL=/bin/bash
> >
> > If you fix the issue, kindly add following tag where applicable
> >| Reported-by: kernel test robot <lkp@intel.com>
> >| Link: https://lore.kernel.org/oe-kbuild-all/202304250419.YtCLtUhG-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> >>> arch/um/drivers/harddog_user.c:6:10: fatal error: stdio.h: No such file or
> >>> directory
> > 6 | #include <stdio.h>
> > | ^~~~~~~~~
> > compilation terminated.
>
> Wild guess, is this a nolibc toolchain?
The bot is using the gcc-11 provided by debian distribution, so we think
it is not a "nolibc toolchain".
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
We can reproduce it on commit fc54a4f15988, and its parent commit is
clean. Please help give some guidance if anything wrong in our test
flow. Thanks.
$ git checkout fc54a4f15988e228cf88f888483e985c5f35031e
HEAD is now at fc54a4f15988 um: prevent user code in modules
$ make ARCH=um allmodconfig
$ make ARCH=um arch/um/drivers/
...
CC [M] arch/um/drivers/harddog_user.o
arch/um/drivers/harddog_user.c:6:10: fatal error: stdio.h: No such file or directory
6 | #include <stdio.h>
| ^~~~~~~~~
compilation terminated.
make[2]: *** [scripts/Makefile.build:252: arch/um/drivers/harddog_user.o] Error 1
make[1]: *** [scripts/Makefile.build:494: arch/um/drivers] Error 2
make: *** [Makefile:2025: .] Error 2
$ git checkout 5d90cf6dcc6a4cb85a51ffe007a8e34375799164
HEAD is now at 5d90cf6dcc6a um: further clean up user_syms
$ make ARCH=um allmodconfig
$ make ARCH=um arch/um/drivers/
...
CC [M] arch/um/drivers/harddog_kern.o
CC [M] arch/um/drivers/harddog_user.o <--
LD [M] arch/um/drivers/harddog.o
CC [M] arch/um/drivers/random.o
$ echo $?
0
Best Regards,
Yujie
next prev parent reply other threads:[~2023-06-09 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 20:53 kernel test robot
2023-04-24 21:00 ` Richard Weinberger
2023-06-09 1:26 ` Yujie Liu [this message]
2023-06-09 7:55 ` Johannes Berg
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=ZIJ/vvquEQXN8NBf@yujie-X299 \
--to=yujie.liu@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard@nod.at \
/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