From: Baoquan He <bhe@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, tglx@linutronix.de, mingo@kernel.org,
hpa@zytor.com, thgarnie@google.com,
kirill.shutemov@linux.intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] mm: Add build time sanity chcek for struct page size
Date: Tue, 11 Sep 2018 15:47:33 +0800 [thread overview]
Message-ID: <20180911074733.GX1740@192.168.1.3> (raw)
In-Reply-To: <201809102133.gzaxoHWf%fengguang.wu@intel.com>
On 09/10/18 at 09:41pm, kbuild test robot wrote:
> include/linux/build_bug.h:69:2: note: in expansion of macro 'BUILD_BUG_ON_MSG'
> BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
> ^~~~~~~~~~~~~~~~
> >> mm/page_alloc.c:6852:2: note: in expansion of macro 'BUILD_BUG_ON'
> BUILD_BUG_ON(sizeof(struct page) < min(SZ_1K, PAGE_SIZE/4));
> ^~~~~~~~~~~~
Thanks, below code can mute the compiling warning. Will update and
repost.
+ BUILD_BUG_ON(sizeof(struct page) > min((size_t)SZ_1K, PAGE_SIZE));
next prev parent reply other threads:[~2018-09-11 7:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 12:49 [PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size Baoquan He
2018-09-09 12:49 ` [PATCH v2 2/3] x86/mm/KASLR: Calculate the actual size of vmemmap region Baoquan He
2018-09-10 6:11 ` Ingo Molnar
2018-09-11 7:30 ` Baoquan He
2018-09-11 7:59 ` Ingo Molnar
2018-09-11 8:18 ` Baoquan He
2018-09-11 9:28 ` Ingo Molnar
2018-09-11 12:08 ` Baoquan He
2018-09-12 3:18 ` Baoquan He
2018-09-12 6:31 ` Ingo Molnar
2018-09-12 9:41 ` Baoquan He
2018-09-12 10:01 ` Ingo Molnar
2018-09-21 2:10 ` Baoquan He
2018-09-09 12:49 ` [PATCH v2 3/3] mm: Add build time sanity chcek for struct page size Baoquan He
2018-09-10 13:41 ` kbuild test robot
2018-09-11 7:47 ` Baoquan He [this message]
2018-09-10 6:18 ` [PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size Ingo Molnar
2018-09-11 7:22 ` Baoquan He
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=20180911074733.GX1740@192.168.1.3 \
--to=bhe@redhat.com \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome