linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Walter Wu <walter-zh.wu@mediatek.com>
Cc: kbuild-all@lists.01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Dmitry Vyukov <dvyukov@google.com>,
	Andrey Konovalov <andreyknvl@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [hnaz-linux-mm:master 145/290] mm/kasan/report.c:185:20: error: 'struct kasan_alloc_meta' has no member named 'free_track'
Date: Thu, 9 Jul 2020 23:34:57 +0800	[thread overview]
Message-ID: <202007092350.t5BEzzME%lkp@intel.com> (raw)

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

tree:   https://github.com/hnaz/linux-mm master
head:   12c0de83d877ea6b9078782f10f7a4a196aa16b1
commit: 16d798d57643c9b50fe8922c8324081f3c5bec78 [145/290] rcu: kasan: record and print call_rcu() call stack
config: s390-allyesconfig (attached as .config)
compiler: s390-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
        git checkout 16d798d57643c9b50fe8922c8324081f3c5bec78
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=s390 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

Note: the hnaz-linux-mm/master HEAD 12c0de83d877ea6b9078782f10f7a4a196aa16b1 builds fine.
      It only hurts bisectibility.

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

   mm/kasan/report.c: In function 'kasan_addr_to_page':
   mm/kasan/report.c:130:12: warning: ordered comparison of pointer with null pointer [-Wextra]
     130 |  if ((addr >= (void *)PAGE_OFFSET) &&
         |            ^~
   mm/kasan/report.c: In function 'kasan_get_free_track':
>> mm/kasan/report.c:185:20: error: 'struct kasan_alloc_meta' has no member named 'free_track'
     185 |  return &alloc_meta->free_track[i];
         |                    ^~
>> mm/kasan/report.c:172:6: warning: variable 'i' set but not used [-Wunused-but-set-variable]
     172 |  int i = 0;
         |      ^
>> mm/kasan/report.c:186:1: warning: control reaches end of non-void function [-Wreturn-type]
     186 | }
         | ^
--
   mm/kasan/common.c: In function 'kasan_set_free_info':
>> mm/kasan/common.c:316:23: error: 'struct kasan_alloc_meta' has no member named 'free_track'
     316 |  set_track(&alloc_meta->free_track[idx], GFP_NOWAIT);
         |                       ^~
>> mm/kasan/common.c:306:5: warning: variable 'idx' set but not used [-Wunused-but-set-variable]
     306 |  u8 idx = 0;
         |     ^~~

vim +185 mm/kasan/report.c

0c06f1f86c87b1 Andrey Konovalov 2017-05-03  167  
ae8f06b31a83e5 Walter Wu        2019-09-23  168  static struct kasan_track *kasan_get_free_track(struct kmem_cache *cache,
ae8f06b31a83e5 Walter Wu        2019-09-23  169  		void *object, u8 tag)
ae8f06b31a83e5 Walter Wu        2019-09-23  170  {
ae8f06b31a83e5 Walter Wu        2019-09-23  171  	struct kasan_alloc_meta *alloc_meta;
ae8f06b31a83e5 Walter Wu        2019-09-23 @172  	int i = 0;
ae8f06b31a83e5 Walter Wu        2019-09-23  173  
ae8f06b31a83e5 Walter Wu        2019-09-23  174  	alloc_meta = get_alloc_info(cache, object);
ae8f06b31a83e5 Walter Wu        2019-09-23  175  
ae8f06b31a83e5 Walter Wu        2019-09-23  176  #ifdef CONFIG_KASAN_SW_TAGS_IDENTIFY
ae8f06b31a83e5 Walter Wu        2019-09-23  177  	for (i = 0; i < KASAN_NR_FREE_STACKS; i++) {
ae8f06b31a83e5 Walter Wu        2019-09-23  178  		if (alloc_meta->free_pointer_tag[i] == tag)
ae8f06b31a83e5 Walter Wu        2019-09-23  179  			break;
ae8f06b31a83e5 Walter Wu        2019-09-23  180  	}
ae8f06b31a83e5 Walter Wu        2019-09-23  181  	if (i == KASAN_NR_FREE_STACKS)
ae8f06b31a83e5 Walter Wu        2019-09-23  182  		i = alloc_meta->free_track_idx;
ae8f06b31a83e5 Walter Wu        2019-09-23  183  #endif
ae8f06b31a83e5 Walter Wu        2019-09-23  184  
ae8f06b31a83e5 Walter Wu        2019-09-23 @185  	return &alloc_meta->free_track[i];
ae8f06b31a83e5 Walter Wu        2019-09-23 @186  }
ae8f06b31a83e5 Walter Wu        2019-09-23  187  

:::::: The code at line 185 was first introduced by commit
:::::: ae8f06b31a83e54777514308a63f669a1fed519e kasan: add memory corruption identification for software tag-based mode

:::::: TO: Walter Wu <walter-zh.wu@mediatek.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 62670 bytes --]

             reply	other threads:[~2020-07-09 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 15:34 kernel test robot [this message]
2020-07-10  1:54 ` Walter Wu
2020-07-10 12:11   ` Andrey Konovalov
2020-07-10 15:32     ` Walter 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=202007092350.t5BEzzME%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@google.com \
    --cc=dvyukov@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=walter-zh.wu@mediatek.com \
    /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