All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] mm: proc: add Sock to /proc/meminfo
Date: Sat, 10 Oct 2020 21:06:59 +0800	[thread overview]
Message-ID: <202010102004.SLNzQD4k-lkp@intel.com> (raw)
In-Reply-To: <20201010103854.66746-1-songmuchun@bytedance.com>

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

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
config: powerpc-randconfig-r031-20201010 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project 9b5b3050237db3642ed7ab1bdb3ffa2202511b99)
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
        # install powerpc cross compiling tool for clang build
        # apt-get install binutils-powerpc-linux-gnu
        # 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
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=powerpc 

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

All warnings (new ones prefixed by >>):

>> security/keys/encrypted-keys/encrypted.c:52:9: warning: 'HASH_SIZE' macro redefined [-Wmacro-redefined]
   #define HASH_SIZE SHA256_DIGEST_SIZE
           ^
   include/linux/hashtable.h:27:9: note: previous definition is here
   #define HASH_SIZE(name) (ARRAY_SIZE(name))
           ^
   1 warning generated.

vim +/HASH_SIZE +52 security/keys/encrypted-keys/encrypted.c

7e70cb4978507cf security/keys/encrypted_defined.c        Mimi Zohar    2010-11-23  48  
3b1826cebe1d534 security/keys/encrypted_defined.c        Mimi Zohar    2010-12-13  49  #define KEY_TRUSTED_PREFIX_LEN (sizeof (KEY_TRUSTED_PREFIX) - 1)
3b1826cebe1d534 security/keys/encrypted_defined.c        Mimi Zohar    2010-12-13  50  #define KEY_USER_PREFIX_LEN (sizeof (KEY_USER_PREFIX) - 1)
79a73d188726b47 security/keys/encrypted.c                Roberto Sassu 2011-06-27  51  #define KEY_ECRYPTFS_DESC_LEN 16
3b1826cebe1d534 security/keys/encrypted_defined.c        Mimi Zohar    2010-12-13 @52  #define HASH_SIZE SHA256_DIGEST_SIZE
3b1826cebe1d534 security/keys/encrypted_defined.c        Mimi Zohar    2010-12-13  53  #define MAX_DATA_SIZE 4096
3b1826cebe1d534 security/keys/encrypted_defined.c        Mimi Zohar    2010-12-13  54  #define MIN_DATA_SIZE  20
9db67581b91d9e9 security/keys/encrypted-keys/encrypted.c Dave Jiang    2018-12-04  55  #define KEY_ENC32_PAYLOAD_LEN 32
3b1826cebe1d534 security/keys/encrypted_defined.c        Mimi Zohar    2010-12-13  56  

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

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

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

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10 10:38 [PATCH] mm: proc: add Sock to /proc/meminfo Muchun Song
2020-10-10 13:06 ` kernel test robot [this message]
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  4:42   ` [External] " Muchun Song
2020-10-11 13:52 ` Mike Rapoport
2020-10-11 16:00   ` [External] " Muchun Song
2020-10-11 18:39 ` Cong Wang
2020-10-11 18:39   ` Cong Wang
2020-10-12  4:22   ` [External] " Muchun Song
2020-10-12  7:42     ` Eric Dumazet
2020-10-12  8:39       ` Muchun Song
2020-10-12  9:24         ` Eric Dumazet
2020-10-12  9:24           ` Eric Dumazet
2020-10-12  9:53           ` Muchun Song
2020-10-12 22:12             ` Cong Wang
2020-10-12 22:12               ` Cong Wang
2020-10-13  3:52               ` Muchun Song
2020-10-13  6:55             ` Eric Dumazet
2020-10-13  6:55               ` Eric Dumazet
2020-10-13  8:09             ` Mike Rapoport
2020-10-13 14:43               ` Randy Dunlap
2020-10-13 14:43                 ` Randy Dunlap
2020-10-13 15:12                 ` Mike Rapoport
2020-10-13 15:21                   ` Randy Dunlap
2020-10-13 15:21                     ` Randy Dunlap
2020-10-14  5:34                     ` Mike Rapoport
2020-10-13 15:28               ` Muchun Song
2020-10-16 15:38               ` Vlastimil Babka
2020-10-16 15:38                 ` Vlastimil Babka
2020-10-16 20:53                 ` Minchan Kim
2020-10-16 20:53                   ` Minchan Kim
2020-10-19 17:23                   ` Shakeel Butt
2020-10-12 21:46     ` Cong Wang
2020-10-12 21:46       ` Cong Wang
2020-10-13  3:29       ` Muchun Song
  -- strict thread matches above, loose matches on Subject: below --
2020-10-10 13:57 kernel test robot

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=202010102004.SLNzQD4k-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@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.