linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jan Kara <jack@suse.cz>
Cc: Georg Ottinger <g.ottinger@gmx.at>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the ext3 tree
Date: Wed, 16 Aug 2023 10:37:51 +1000	[thread overview]
Message-ID: <20230816103751.13f217a8@canb.auug.org.au> (raw)

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

Hi all,

After merging the ext3 tree, today's linux-next build (x86_64
allmodconfig) failed like this:

In file included from include/linux/kernel.h:30,
                 from arch/x86/include/asm/percpu.h:27,
                 from arch/x86/include/asm/preempt.h:6,
                 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 include/linux/highmem.h:5,
                 from include/linux/bvec.h:10,
                 from include/linux/blk_types.h:10,
                 from include/linux/buffer_head.h:12,
                 from fs/ext2/xattr.c:57:
fs/ext2/xattr.c: In function 'ext2_xattr_set2':
fs/ext2/xattr.c:748:42: error: format '%d' expects argument of type 'int', but argument 2 has type 'ext2_fsblk_t' {aka 'long unsigned int'} [-Werror=format=]
  748 |                         ea_idebug(inode, "creating block %d", block);
      |                                          ^~~~~~~~~~~~~~~~~~~  ~~~~~
      |                                                               |
      |                                                               ext2_fsblk_t {aka long unsigned int}
include/linux/printk.h:427:25: note: in definition of macro 'printk_index_wrap'
  427 |                 _p_func(_fmt, ##__VA_ARGS__);                           \
      |                         ^~~~
include/linux/printk.h:129:17: note: in expansion of macro 'printk'
  129 |                 printk(fmt, ##__VA_ARGS__);             \
      |                 ^~~~~~
fs/ext2/xattr.c:88:33: note: in expansion of macro 'no_printk'
   88 | # define ea_idebug(inode, f...) no_printk(f)
      |                                 ^~~~~~~~~
fs/ext2/xattr.c:748:25: note: in expansion of macro 'ea_idebug'
  748 |                         ea_idebug(inode, "creating block %d", block);
      |                         ^~~~~~~~~
fs/ext2/xattr.c:748:59: note: format string is defined here
  748 |                         ea_idebug(inode, "creating block %d", block);
      |                                                          ~^
      |                                                           |
      |                                                           int
      |                                                          %ld

Caused by commit

  38e38567c5bd ("ext2: fix datatype of block number in ext2_xattr_set2()")

I have used the ext3 tree from next-20230815 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-08-16  0:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  0:37 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-07  0:07 linux-next: build failure after merge of the ext3 tree Stephen Rothwell
2024-03-07  6:18 ` Winston Wen
2024-03-07 12:03   ` Jan Kara
2020-11-12 23:47 Stephen Rothwell
2020-11-13 10:33 ` Jan Kara
2019-01-31  4:14 Stephen Rothwell
2019-01-31 10:11 ` Jan Kara
2019-01-31 22:09   ` Stephen Rothwell
2014-08-08  1:52 Stephen Rothwell
2014-08-08  9:22 ` Jan Kara
2011-12-28  0:22 Stephen Rothwell
2012-01-02 22:40 ` Jan Kara
2010-03-02  0:36 Stephen Rothwell
2010-03-02  9:07 ` Christoph Hellwig
2010-03-02 17:27 ` Jan Kara
2010-03-03  0:42   ` Stephen Rothwell

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=20230816103751.13f217a8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=g.ottinger@gmx.at \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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).