All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [PATCH] mm: proc: add Sock to /proc/meminfo
Date: Sat, 10 Oct 2020 21:57:26 +0800	[thread overview]
Message-ID: <202010102103.vmgnx0aA-lkp@intel.com> (raw)

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

CC: kbuild-all(a)lists.01.org
In-Reply-To: <20201010103854.66746-1-songmuchun@bytedance.com>
References: <20201010103854.66746-1-songmuchun@bytedance.com>
TO: Muchun Song <songmuchun@bytedance.com>
TO: gregkh(a)linuxfoundation.org
TO: rafael(a)kernel.org
TO: mst(a)redhat.com
TO: jasowang(a)redhat.com
TO: davem(a)davemloft.net
TO: kuba(a)kernel.org
TO: adobriyan(a)gmail.com
TO: akpm(a)linux-foundation.org
TO: edumazet(a)google.com
TO: kuznet(a)ms2.inr.ac.ru

Hi Muchun,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on ipsec-next/master]
[also build test WARNING on ipsec/master linus/master hnaz-linux-mm/master v5.9-rc8]
[cannot apply to mmotm/master driver-core/driver-core-testing next-20201009]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Muchun-Song/mm-proc-add-Sock-to-proc-meminfo/20201010-184040
base:   https://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
:::::: branch date: 3 hours ago
:::::: commit date: 3 hours ago
config: x86_64-randconfig-s022-20201010 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.2-229-g0c6896f4-dirty
        # https://github.com/0day-ci/linux/commit/9befda995cb116f94e34d4ffdc8d9dd37a91dc49
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Muchun-Song/mm-proc-add-Sock-to-proc-meminfo/20201010-184040
        git checkout 9befda995cb116f94e34d4ffdc8d9dd37a91dc49
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64 

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


"sparse warnings: (new ones prefixed by >>)"
   security/keys/encrypted-keys/encrypted.c:52:9: sparse: sparse: preprocessor token HASH_SIZE redefined
   security/keys/encrypted-keys/encrypted.c: note: in included file (through include/linux/elevator.h, include/linux/blkdev.h, include/linux/blk-cgroup.h, ...):
>> include/linux/hashtable.h:27:9: sparse: this was the original definition

vim +27 include/linux/hashtable.h

d9b482c8ba1973 Sasha Levin  2012-10-30  15  
d9b482c8ba1973 Sasha Levin  2012-10-30  16  #define DEFINE_HASHTABLE(name, bits)						\
d9b482c8ba1973 Sasha Levin  2012-10-30  17  	struct hlist_head name[1 << (bits)] =					\
d9b482c8ba1973 Sasha Levin  2012-10-30  18  			{ [0 ... ((1 << (bits)) - 1)] = HLIST_HEAD_INIT }
d9b482c8ba1973 Sasha Levin  2012-10-30  19  
6180d9de61a5c4 Eric Dumazet 2015-11-18  20  #define DEFINE_READ_MOSTLY_HASHTABLE(name, bits)				\
6180d9de61a5c4 Eric Dumazet 2015-11-18  21  	struct hlist_head name[1 << (bits)] __read_mostly =			\
6180d9de61a5c4 Eric Dumazet 2015-11-18  22  			{ [0 ... ((1 << (bits)) - 1)] = HLIST_HEAD_INIT }
6180d9de61a5c4 Eric Dumazet 2015-11-18  23  
d9b482c8ba1973 Sasha Levin  2012-10-30  24  #define DECLARE_HASHTABLE(name, bits)                                   	\
d9b482c8ba1973 Sasha Levin  2012-10-30  25  	struct hlist_head name[1 << (bits)]
d9b482c8ba1973 Sasha Levin  2012-10-30  26  
d9b482c8ba1973 Sasha Levin  2012-10-30 @27  #define HASH_SIZE(name) (ARRAY_SIZE(name))
d9b482c8ba1973 Sasha Levin  2012-10-30  28  #define HASH_BITS(name) ilog2(HASH_SIZE(name))
d9b482c8ba1973 Sasha Levin  2012-10-30  29  

---
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: 28949 bytes --]

             reply	other threads:[~2020-10-10 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10 13:57 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-10 10:38 [PATCH] mm: proc: add Sock to /proc/meminfo Muchun Song
2020-10-10 13:06 ` kernel test robot
2020-10-10 13:27 ` kernel test robot
2020-10-10 16:36 ` Randy Dunlap
2020-10-10 16:36   ` Randy Dunlap
2020-10-11 13:52 ` Mike Rapoport
2020-10-11 18:39 ` Cong Wang
2020-10-11 18:39   ` Cong Wang
2020-10-11 18:39   ` Cong Wang

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=202010102103.vmgnx0aA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.