linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@01.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 Andrey Konovalov <andreyknvl@google.com>,
	Andrey Ryabinin <aryabinin@virtuozzo.com>,
	 Andrew Morton <akpm@linux-foundation.org>,
	 Linux Memory Management List <linux-mm@kvack.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: [intel-linux-intel-lts:4.19/android_r 20723/22085] include/linux/page-flags-layout.h:95:2: error: #error "Not enough bits in page flags"
Date: Tue, 9 Mar 2021 16:13:06 +0100	[thread overview]
Message-ID: <CAK8P3a27NKFsVaJpXtPxJzjnhJ0uzGeFUU+S-md3J1iH6KyXzw@mail.gmail.com> (raw)
In-Reply-To: <202103092318.cXGjdBcl-lkp@intel.com>

On Tue, Mar 9, 2021 at 4:00 PM kernel test robot <lkp@intel.com> wrote:
>
> tree:   https://github.com/intel/linux-intel-lts.git 4.19/android_r
> head:   42da0a5bc28f55c05347ef8eb88d9e41f369333e
> commit: 7783c5c8ec0d6781dc180be5fd075f06f90e9cb5 [20723/22085] UPSTREAM: page flags: prioritize kasan bits over last-cpuid
> config: mips-lemote2f_defconfig (attached as .config)
> compiler: mips64el-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # https://github.com/intel/linux-intel-lts/commit/7783c5c8ec0d6781dc180be5fd075f06f90e9cb5
>         git remote add intel-linux-intel-lts https://github.com/intel/linux-intel-lts.git
>         git fetch --no-tags intel-linux-intel-lts 4.19/android_r
>         git checkout 7783c5c8ec0d6781dc180be5fd075f06f90e9cb5
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>    In file included from include/linux/mm_types.h:15,
>                     from arch/mips/include/asm/vdso.h:14,
>                     from arch/mips/include/asm/vdso/vdso.h:28,
>                     from arch/mips/include/asm/vdso/gettimeofday.h:16,
>                     from include/vdso/datapage.h:114,
>                     from lib/vdso/gettimeofday.c:5,
>                     from <command-line>:
> >> include/linux/page-flags-layout.h:95:2: error: #error "Not enough bits in page flags"

I think this happens because my patch fixed an error that happened on
multiple architectures but did not fix the mips specific error that remains.

I once tried fixing this as well, but there is no good way to express the
requirements in Kconfig -- there are simply not enough bits in the
page flags to allow all combinations that can happen in randconfig
builds.

       Arnd


      reply	other threads:[~2021-03-09 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 15:00 kernel test robot
2021-03-09 15:13 ` Arnd Bergmann [this message]

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=CAK8P3a27NKFsVaJpXtPxJzjnhJ0uzGeFUU+S-md3J1iH6KyXzw@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@google.com \
    --cc=aryabinin@virtuozzo.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=tsbogend@alpha.franken.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox