linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Konstantin Khlebnikov <koct9i@gmail.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 1761/2084] mm/internal.h:226:19: note: in expansion of macro 'VM_STACK_FLAGS'
Date: Thu, 28 Jan 2016 16:33:14 +0800	[thread overview]
Message-ID: <201601281613.QRYLvzum%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4369 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   888c8375131656144c1605071eab2eb6ac49abc3
commit: 07dff8ae2bc5c3adf387f95c4d6864b1d06866f2 [1761/2084] mm: warn about VmData over RLIMIT_DATA
config: frv-defconfig (attached as .config)
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 07dff8ae2bc5c3adf387f95c4d6864b1d06866f2
        # save the attached .config to linux build tree
        make.cross ARCH=frv 

All error/warnings (new ones prefixed by >>):

   In file included from include/linux/mmzone.h:20:0,
                    from include/linux/gfp.h:5,
                    from include/linux/percpu_counter.h:15,
                    from include/linux/quota.h:40,
                    from include/linux/fs.h:268,
                    from include/linux/dax.h:4,
                    from mm/filemap.c:14:
   mm/internal.h: In function 'is_stack_mapping':
>> arch/frv/include/asm/page.h:68:27: error: 'READ_IMPLIES_EXEC' undeclared (first use in this function)
     ((current->personality & READ_IMPLIES_EXEC) ? VM_EXEC : 0 ) | \
                              ^
>> include/linux/mm.h:200:32: note: in expansion of macro 'VM_DATA_DEFAULT_FLAGS'
    #define VM_STACK_DEFAULT_FLAGS VM_DATA_DEFAULT_FLAGS
                                   ^
>> include/linux/mm.h:206:40: note: in expansion of macro 'VM_STACK_DEFAULT_FLAGS'
    #define VM_STACK_FLAGS (VM_GROWSDOWN | VM_STACK_DEFAULT_FLAGS | VM_ACCOUNT)
                                           ^
>> mm/internal.h:226:19: note: in expansion of macro 'VM_STACK_FLAGS'
     return (flags & (VM_STACK_FLAGS & (VM_GROWSUP | VM_GROWSDOWN))) != 0;
                      ^
   arch/frv/include/asm/page.h:68:27: note: each undeclared identifier is reported only once for each function it appears in
     ((current->personality & READ_IMPLIES_EXEC) ? VM_EXEC : 0 ) | \
                              ^
>> include/linux/mm.h:200:32: note: in expansion of macro 'VM_DATA_DEFAULT_FLAGS'
    #define VM_STACK_DEFAULT_FLAGS VM_DATA_DEFAULT_FLAGS
                                   ^
>> include/linux/mm.h:206:40: note: in expansion of macro 'VM_STACK_DEFAULT_FLAGS'
    #define VM_STACK_FLAGS (VM_GROWSDOWN | VM_STACK_DEFAULT_FLAGS | VM_ACCOUNT)
                                           ^
>> mm/internal.h:226:19: note: in expansion of macro 'VM_STACK_FLAGS'
     return (flags & (VM_STACK_FLAGS & (VM_GROWSUP | VM_GROWSDOWN))) != 0;
                      ^
   mm/internal.h: In function 'is_data_mapping':
>> arch/frv/include/asm/page.h:68:27: error: 'READ_IMPLIES_EXEC' undeclared (first use in this function)
     ((current->personality & READ_IMPLIES_EXEC) ? VM_EXEC : 0 ) | \
                              ^
>> include/linux/mm.h:200:32: note: in expansion of macro 'VM_DATA_DEFAULT_FLAGS'
    #define VM_STACK_DEFAULT_FLAGS VM_DATA_DEFAULT_FLAGS
                                   ^
>> include/linux/mm.h:206:40: note: in expansion of macro 'VM_STACK_DEFAULT_FLAGS'
    #define VM_STACK_FLAGS (VM_GROWSDOWN | VM_STACK_DEFAULT_FLAGS | VM_ACCOUNT)
                                           ^
   mm/internal.h:231:20: note: in expansion of macro 'VM_STACK_FLAGS'
     return (flags & ((VM_STACK_FLAGS & (VM_GROWSUP | VM_GROWSDOWN)) |
                       ^

vim +/VM_STACK_FLAGS +226 mm/internal.h

   210	 * use of the result.
   211	 */
   212	#define page_order_unsafe(page)		READ_ONCE(page_private(page))
   213	
   214	static inline bool is_cow_mapping(vm_flags_t flags)
   215	{
   216		return (flags & (VM_SHARED | VM_MAYWRITE)) == VM_MAYWRITE;
   217	}
   218	
   219	static inline bool is_exec_mapping(vm_flags_t flags)
   220	{
   221		return (flags & (VM_EXEC | VM_WRITE)) == VM_EXEC;
   222	}
   223	
   224	static inline bool is_stack_mapping(vm_flags_t flags)
   225	{
 > 226		return (flags & (VM_STACK_FLAGS & (VM_GROWSUP | VM_GROWSDOWN))) != 0;
   227	}
   228	
   229	static inline bool is_data_mapping(vm_flags_t flags)
   230	{
   231		return (flags & ((VM_STACK_FLAGS & (VM_GROWSUP | VM_GROWSDOWN)) |
   232						VM_WRITE | VM_SHARED)) == VM_WRITE;
   233	}
   234	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 8170 bytes --]

                 reply	other threads:[~2016-01-28  8:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201601281613.QRYLvzum%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=kbuild-all@01.org \
    --cc=koct9i@gmail.com \
    --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