All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 2/2] btrfs: make btrfs_truncate_block() zero folio range for certain subpage corner cases
Date: Sat, 12 Apr 2025 13:12:46 +0800	[thread overview]
Message-ID: <202504121224.JBBIEqsn-lkp@intel.com> (raw)
In-Reply-To: <d66c922e591b3a57a230ca357b9085fe6ae53812.1744344865.git.wqu@suse.com>

Hi Qu,

kernel test robot noticed the following build warnings:

[auto build test WARNING on kdave/for-next]
[also build test WARNING on linus/master v6.15-rc1 next-20250411]
[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/Qu-Wenruo/btrfs-make-btrfs_truncate_block-to-zero-involved-blocks-in-a-folio/20250411-131525
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link:    https://lore.kernel.org/r/d66c922e591b3a57a230ca357b9085fe6ae53812.1744344865.git.wqu%40suse.com
patch subject: [PATCH 2/2] btrfs: make btrfs_truncate_block() zero folio range for certain subpage corner cases
config: arm-randconfig-002-20250412 (https://download.01.org/0day-ci/archive/20250412/202504121224.JBBIEqsn-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250412/202504121224.JBBIEqsn-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/202504121224.JBBIEqsn-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from include/linux/kernel.h:27:0,
                    from include/linux/cpumask.h:11,
                    from include/linux/smp.h:13,
                    from include/linux/lockdep.h:14,
                    from include/linux/spinlock.h:63,
                    from include/linux/swait.h:7,
                    from include/linux/completion.h:12,
                    from include/linux/crypto.h:15,
                    from include/crypto/hash.h:12,
                    from fs/btrfs/inode.c:6:
   fs/btrfs/inode.c: In function 'zero_range_folio':
>> include/linux/math.h:15:29: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
    #define __round_mask(x, y) ((__typeof__(x))((y)-1))
                                ^
   include/linux/math.h:35:34: note: in expansion of macro '__round_mask'
    #define round_down(x, y) ((x) & ~__round_mask(x, y))
                                     ^~~~~~~~~~~~
   fs/btrfs/inode.c:4843:16: note: in expansion of macro 'round_down'
     block_start = round_down(clamp_start, block_size);
                   ^~~~~~~~~~
>> include/linux/math.h:15:29: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
    #define __round_mask(x, y) ((__typeof__(x))((y)-1))
                                ^
   include/linux/math.h:25:36: note: in expansion of macro '__round_mask'
    #define round_up(x, y) ((((x)-1) | __round_mask(x, y))+1)
                                       ^~~~~~~~~~~~
   fs/btrfs/inode.c:4844:14: note: in expansion of macro 'round_up'
     block_end = round_up(clamp_end + 1, block_size) - 1;
                 ^~~~~~~~


vim +15 include/linux/math.h

aa6159ab99a9ab Andy Shevchenko 2020-12-15   8  
aa6159ab99a9ab Andy Shevchenko 2020-12-15   9  /*
aa6159ab99a9ab Andy Shevchenko 2020-12-15  10   * This looks more complex than it should be. But we need to
aa6159ab99a9ab Andy Shevchenko 2020-12-15  11   * get the type for the ~ right in round_down (it needs to be
aa6159ab99a9ab Andy Shevchenko 2020-12-15  12   * as wide as the result!), and we want to evaluate the macro
aa6159ab99a9ab Andy Shevchenko 2020-12-15  13   * arguments just once each.
aa6159ab99a9ab Andy Shevchenko 2020-12-15  14   */
aa6159ab99a9ab Andy Shevchenko 2020-12-15 @15  #define __round_mask(x, y) ((__typeof__(x))((y)-1))
aa6159ab99a9ab Andy Shevchenko 2020-12-15  16  

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

  reply	other threads:[~2025-04-12  5:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11  5:13 [PATCH 0/2] btrfs: fix corner cases for subpage generic/363 failures Qu Wenruo
2025-04-11  5:14 ` [PATCH 1/2] btrfs: make btrfs_truncate_block() to zero involved blocks in a folio Qu Wenruo
2025-04-11  7:02   ` Qu Wenruo
2025-04-11  5:14 ` [PATCH 2/2] btrfs: make btrfs_truncate_block() zero folio range for certain subpage corner cases Qu Wenruo
2025-04-12  5:12   ` kernel test robot [this message]
2025-04-12  5:54   ` kernel test robot
2025-04-12 18:35   ` Andy Shevchenko
2025-04-14  1:20     ` Qu Wenruo
2025-04-14  3:37       ` Qu Wenruo
2025-04-14 10:40       ` Andy Shevchenko
2025-04-15 18:18         ` David Sterba
2025-04-15 18:21           ` Andy Shevchenko
2025-04-15 23:57             ` Qu Wenruo
2025-04-16  5:57               ` Andy Shevchenko
2025-04-16  8:28                 ` David Sterba

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=202504121224.JBBIEqsn-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=wqu@suse.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 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.