From: kernel test robot <lkp@intel.com>
To: Daniel Rosenberg <drosen@google.com>,
linux-f2fs-devel@lists.sourceforge.net
Cc: Daniel Rosenberg <drosen@google.com>,
Chao Yu <yuchao0@huawei.com>,
linux-kernel@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
Jaegeuk Kim <jaegeuk@kernel.org>,
kernel-team@android.com
Subject: Re: [f2fs-dev] [PATCH 1/1] ANDROID: f2fs: Support Block Size == Page Size
Date: Wed, 16 Aug 2023 12:11:25 +0800 [thread overview]
Message-ID: <202308161231.MjDoxlOG-lkp@intel.com> (raw)
In-Reply-To: <20230816011432.1966838-2-drosen@google.com>
Hi Daniel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 0cc81b1ad51287847e494e055e5d3426f95e7921]
url: https://github.com/intel-lab-lkp/linux/commits/Daniel-Rosenberg/ANDROID-f2fs-Support-Block-Size-Page-Size/20230816-091721
base: 0cc81b1ad51287847e494e055e5d3426f95e7921
patch link: https://lore.kernel.org/r/20230816011432.1966838-2-drosen%40google.com
patch subject: [PATCH 1/1] ANDROID: f2fs: Support Block Size == Page Size
config: m68k-randconfig-r013-20230816 (https://download.01.org/0day-ci/archive/20230816/202308161231.MjDoxlOG-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230816/202308161231.MjDoxlOG-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/202308161231.MjDoxlOG-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/printk.h:7,
from include/asm-generic/bug.h:22,
from arch/m68k/include/asm/bug.h:32,
from include/linux/bug.h:5,
from include/linux/thread_info.h:13,
from include/asm-generic/preempt.h:5,
from ./arch/m68k/include/generated/asm/preempt.h:1,
from include/linux/preempt.h:79,
from include/linux/spinlock.h:56,
from include/linux/wait.h:9,
from include/linux/wait_bit.h:8,
from include/linux/fs.h:6,
from fs/f2fs/inode.c:8:
fs/f2fs/inode.c: In function 'sanity_check_inode':
>> include/linux/kern_levels.h:5:25: warning: format '%zu' expects argument of type 'size_t', but argument 6 has type 'long unsigned int' [-Wformat=]
5 | #define KERN_SOH "\001" /* ASCII Start Of Header */
| ^~~~~~
include/linux/kern_levels.h:12:25: note: in expansion of macro 'KERN_SOH'
12 | #define KERN_WARNING KERN_SOH "4" /* warning conditions */
| ^~~~~~~~
fs/f2fs/f2fs.h:2315:26: note: in expansion of macro 'KERN_WARNING'
2315 | f2fs_printk(sbi, KERN_WARNING fmt, ##__VA_ARGS__)
| ^~~~~~~~~~~~
fs/f2fs/inode.c:325:25: note: in expansion of macro 'f2fs_warn'
325 | f2fs_warn(sbi, "%s: inode (ino=%lx) has corrupted i_inline_xattr_size: %d, max: %zu",
| ^~~~~~~~~
vim +5 include/linux/kern_levels.h
314ba3520e513a Joe Perches 2012-07-30 4
04d2c8c83d0e3a Joe Perches 2012-07-30 @5 #define KERN_SOH "\001" /* ASCII Start Of Header */
04d2c8c83d0e3a Joe Perches 2012-07-30 6 #define KERN_SOH_ASCII '\001'
04d2c8c83d0e3a Joe Perches 2012-07-30 7
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-08-16 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 1:14 [f2fs-dev] [PATCH 0/1] Add 16K Support for f2fs Daniel Rosenberg via Linux-f2fs-devel
2023-08-16 1:14 ` [f2fs-dev] [PATCH 1/1] ANDROID: f2fs: Support Block Size == Page Size Daniel Rosenberg via Linux-f2fs-devel
2023-08-16 4:11 ` kernel test robot [this message]
2023-08-16 2:34 ` [f2fs-dev] [PATCH 0/1] Add 16K Support for f2fs Eric Biggers
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=202308161231.MjDoxlOG-lkp@intel.com \
--to=lkp@intel.com \
--cc=drosen@google.com \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yuchao0@huawei.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;
as well as URLs for NNTP newsgroup(s).