public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: yongli-oc <yongli-oc@zhaoxin.com>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	yongli@zhaoxin.com, cobechen@zhaoxin.com, louisqi@zhaoxin.com,
	jiangbowang@zhaoxin.com
Subject: Re: [PATCH] Support lockref reference count if enable LOCK_STAT
Date: Thu, 14 Nov 2024 06:08:09 +0800	[thread overview]
Message-ID: <202411140548.NBssFC0E-lkp@intel.com> (raw)
In-Reply-To: <20241113085703.148839-1-yongli-oc@zhaoxin.com>

Hi yongli-oc,

kernel test robot noticed the following build warnings:

[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on akpm-mm/mm-nonmm-unstable linus/master v6.12-rc7 next-20241113]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/yongli-oc/Support-lockref-reference-count-if-enable-LOCK_STAT/20241113-171348
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20241113085703.148839-1-yongli-oc%40zhaoxin.com
patch subject: [PATCH] Support lockref reference count if enable LOCK_STAT
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20241114/202411140548.NBssFC0E-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241114/202411140548.NBssFC0E-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411140548.NBssFC0E-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from arch/s390/purgatory/purgatory.c:10:
   In file included from include/linux/kexec.h:18:
   In file included from include/linux/vmcore_info.h:6:
   In file included from include/linux/elfcore.h:11:
   In file included from include/linux/ptrace.h:10:
   In file included from include/linux/pid_namespace.h:7:
   In file included from include/linux/mm.h:1120:
   In file included from include/linux/huge_mm.h:7:
   In file included from include/linux/fs.h:8:
>> include/linux/dcache.h:369:13: warning: taking address of packed member 'lock' of class or structure 'lockref::(anonymous union)::struct (anonymous at include/linux/lockref.h:39:3)' may result in an unaligned pointer value [-Waddress-of-packed-member]
     369 |         spin_lock(&dentry->d_lock);
         |                    ^~~~~~~~~~~~~~
   include/linux/dcache.h:371:15: warning: taking address of packed member 'lock' of class or structure 'lockref::(anonymous union)::struct (anonymous at include/linux/lockref.h:39:3)' may result in an unaligned pointer value [-Waddress-of-packed-member]
     371 |         spin_unlock(&dentry->d_lock);
         |                      ^~~~~~~~~~~~~~
   2 warnings generated.


vim +369 include/linux/dcache.h

d83c49f3e36cec Al Viro 2010-04-30  366  
d83c49f3e36cec Al Viro 2010-04-30  367  static inline void dont_mount(struct dentry *dentry)
d83c49f3e36cec Al Viro 2010-04-30  368  {
d83c49f3e36cec Al Viro 2010-04-30 @369  	spin_lock(&dentry->d_lock);
d83c49f3e36cec Al Viro 2010-04-30  370  	dentry->d_flags |= DCACHE_CANT_MOUNT;
d83c49f3e36cec Al Viro 2010-04-30  371  	spin_unlock(&dentry->d_lock);
d83c49f3e36cec Al Viro 2010-04-30  372  }
d83c49f3e36cec Al Viro 2010-04-30  373  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2024-11-13 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13  8:57 [PATCH] Support lockref reference count if enable LOCK_STAT yongli-oc
2024-11-13 22:08 ` kernel test robot
2024-11-13 22:08 ` kernel test robot [this message]
2024-11-15  0:14 ` Andrew Morton
2024-11-15  7:30   ` yongli-oc

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=202411140548.NBssFC0E-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=cobechen@zhaoxin.com \
    --cc=jiangbowang@zhaoxin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=louisqi@zhaoxin.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yongli-oc@zhaoxin.com \
    --cc=yongli@zhaoxin.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