On Fri, Jan 31, 2025 at 10:07:59AM +0000, Lorenzo Stoakes wrote: > On Fri, Jan 31, 2025 at 05:43:28PM +0800, kernel test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable > > head: f5604ad70091eabe663ea7106ced99449d653320 > > commit: 951452b2ec82d352a69f14cfffdeb7c08461eefb [106/111] mm: further refactor commit_merge() > > config: x86_64-buildonly-randconfig-001-20250131 (https://download.01.org/0day-ci/archive/20250131/202501311708.dRI35epU-lkp@xxxxxxxxx/config) > > compiler: gcc-11 (Debian 11.3.0-12) 11.3.0 > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250131/202501311708.dRI35epU-lkp@xxxxxxxxx/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@xxxxxxxxx> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202501311708.dRI35epU-lkp@xxxxxxxxx/ > > > > All warnings (new ones prefixed by >>): > > > > In file included from include/linux/kernel.h:31, > > from mm/debug.c:9: > > mm/debug.c: In function 'dump_vmg': > > >> include/linux/kern_levels.h:5:25: warning: unknown conversion type character 'b' in format [-Wformat=] > > 5 | #define KERN_SOH "\001" /* ASCII Start Of Header */ > > Well that'll teach me for assuming a compiler with CONFIG_WERROR on will > actually... report warnings as errors. Apparently not. > > Will send a follow up fix-patch... > Even a W=1 build doesn't pick this up, so I'm thinking this might be a compiler version thing. Am doing a respin as that'll be easier.
