From: kernel test robot <lkp@intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [mcgrof-next:large-block-20230617-hacks 44/45] block/bdev.c:140:47: error: 'struct block_device' has no member named 'bd_buffer_head_mounted'
Date: Sat, 17 Jun 2023 23:43:31 +0800 [thread overview]
Message-ID: <202306172356.7Ap7UmF6-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git large-block-20230617-hacks
head: 87ea751f68b5bc03c4c3491b5cab898765002565
commit: b1bd39924b170a4c910626be18f732385e206f2a [44/45] bdev: make iomap aops default and allow to switch
config: powerpc-allnoconfig (https://download.01.org/0day-ci/archive/20230617/202306172356.7Ap7UmF6-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230617/202306172356.7Ap7UmF6-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/202306172356.7Ap7UmF6-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/powerpc/include/asm/bug.h:159,
from include/linux/bug.h:5,
from include/linux/mmdebug.h:5,
from include/linux/mm.h:6,
from block/bdev.c:9:
block/bdev.c: In function 'set_init_blocksize':
>> block/bdev.c:140:47: error: 'struct block_device' has no member named 'bd_buffer_head_mounted'
140 | WARN_ON_ONCE(atomic_read(&bdev->bd_buffer_head_mounted) != 0);
| ^~
include/asm-generic/bug.h:111:32: note: in definition of macro 'WARN_ON_ONCE'
111 | int __ret_warn_on = !!(condition); \
| ^~~~~~~~~
vim +140 block/bdev.c
124
125 static void set_init_blocksize(struct block_device *bdev)
126 {
127 unsigned int bsize = bdev_logical_block_size(bdev);
128 loff_t size = i_size_read(bdev->bd_inode);
129 int order, folio_order;
130
131 while (bsize < PAGE_SIZE) {
132 if (size & bsize)
133 break;
134 bsize <<= 1;
135 }
136 bdev->bd_inode->i_blkbits = blksize_bits(bsize);
137 order = bdev->bd_inode->i_blkbits - PAGE_SHIFT;
138 folio_order = mapping_min_folio_order(bdev->bd_inode->i_mapping);
139 if (order > 0 && folio_order == 0) {
> 140 WARN_ON_ONCE(atomic_read(&bdev->bd_buffer_head_mounted) != 0);
141 mapping_set_min_folio_order(bdev->bd_inode->i_mapping, order);
142 bdev->bd_inode->i_data.a_ops = &def_blk_aops_iomap;
143 }
144 }
145
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-17 15:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202306172356.7Ap7UmF6-lkp@intel.com \
--to=lkp@intel.com \
--cc=mcgrof@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.