From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>
Subject: [brauner-vfs:b4/vfs-bdev-file 41/42] fs/nilfs2/mdt.c:93:21: error: no member named 'f_s_bdev' in 'struct super_block'
Date: Thu, 4 Jan 2024 05:14:46 +0800 [thread overview]
Message-ID: <202401040559.LWerfZTh-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git b4/vfs-bdev-file
head: 81a0b5d317a5188e7e8aaf68adf070d44c7a3eea
commit: 6d26064a464a6f8ace90a2176a17bd6f853825e0 [41/42] [DRAFT] buffer: port block device access to files and get rid of bd_inode access
config: i386-buildonly-randconfig-001-20240103 (https://download.01.org/0day-ci/archive/20240104/202401040559.LWerfZTh-lkp@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240104/202401040559.LWerfZTh-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/202401040559.LWerfZTh-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/nilfs2/mdt.c:93:21: error: no member named 'f_s_bdev' in 'struct super_block'
93 | bh->f_b_bdev = sb->f_s_bdev;
| ~~ ^
1 error generated.
--
>> fs/nilfs2/btnode.c:63:30: error: no member named 'f_s_bdev' in 'struct super_block'
63 | bh->f_b_bdev = inode->i_sb->f_s_bdev;
| ~~~~~~~~~~~ ^
fs/nilfs2/btnode.c:123:30: error: no member named 'f_s_bdev' in 'struct super_block'
123 | bh->f_b_bdev = inode->i_sb->f_s_bdev;
| ~~~~~~~~~~~ ^
2 errors generated.
--
>> fs/nilfs2/the_nilfs.c:66:9: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
66 | nilfs->ns_f_bdev = sb->s_f_bdev;
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
1 error generated.
--
>> fs/nilfs2/recovery.c:110:24: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
110 | bh = __bread(nilfs->ns_f_bdev, ++start, blocksize);
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
fs/nilfs2/recovery.c:139:25: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
139 | bh_sr = __bread(nilfs->ns_f_bdev, sr_block, nilfs->ns_blocksize);
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
fs/nilfs2/recovery.c:186:26: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
186 | bh_sum = __bread(nilfs->ns_f_bdev, start_blocknr, nilfs->ns_blocksize);
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
fs/nilfs2/recovery.c:253:25: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
253 | *pbh = __bread(nilfs->ns_f_bdev, blocknr + 1,
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
fs/nilfs2/recovery.c:292:25: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
292 | *pbh = __bread(nilfs->ns_f_bdev, blocknr + bcnt,
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
fs/nilfs2/recovery.c:321:22: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
321 | bh = __bread(nilfs->ns_f_bdev, start_blocknr, nilfs->ns_blocksize);
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
fs/nilfs2/recovery.c:480:26: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
480 | bh_org = __bread(nilfs->ns_f_bdev, rb->blocknr, nilfs->ns_blocksize);
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
fs/nilfs2/recovery.c:699:23: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
699 | bh = __getblk(nilfs->ns_f_bdev, ri->ri_lsegs_start, nilfs->ns_blocksize);
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
fs/nilfs2/recovery.c:825:23: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
825 | __breadahead(nilfs->ns_f_bdev, b++, nilfs->ns_blocksize);
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
fs/nilfs2/recovery.c:871:25: error: no member named 'ns_f_bdev' in 'struct the_nilfs'; did you mean 'ns_bdev'?
871 | __breadahead(nilfs->ns_f_bdev, b++,
| ^~~~~~~~~
| ns_bdev
fs/nilfs2/the_nilfs.h:100:26: note: 'ns_bdev' declared here
100 | struct block_device *ns_bdev;
| ^
10 errors generated.
--
>> fs/nilfs2/gcinode.c:88:31: error: no member named 'f_s_bdev' in 'struct super_block'
88 | bh->f_b_bdev = inode->i_sb->f_s_bdev;
| ~~~~~~~~~~~ ^
1 error generated.
vim +93 fs/nilfs2/mdt.c
65
66 static int nilfs_mdt_create_block(struct inode *inode, unsigned long block,
67 struct buffer_head **out_bh,
68 void (*init_block)(struct inode *,
69 struct buffer_head *,
70 void *))
71 {
72 struct super_block *sb = inode->i_sb;
73 struct nilfs_transaction_info ti;
74 struct buffer_head *bh;
75 int err;
76
77 nilfs_transaction_begin(sb, &ti, 0);
78
79 err = -ENOMEM;
80 bh = nilfs_grab_buffer(inode, inode->i_mapping, block, 0);
81 if (unlikely(!bh))
82 goto failed_unlock;
83
84 err = -EEXIST;
85 if (buffer_uptodate(bh))
86 goto failed_bh;
87
88 wait_on_buffer(bh);
89 if (buffer_uptodate(bh))
90 goto failed_bh;
91
92 bh->b_bdev = sb->s_bdev;
> 93 bh->f_b_bdev = sb->f_s_bdev;
94 err = nilfs_mdt_insert_new_block(inode, block, bh, init_block);
95 if (likely(!err)) {
96 get_bh(bh);
97 *out_bh = bh;
98 }
99
100 failed_bh:
101 unlock_page(bh->b_page);
102 put_page(bh->b_page);
103 brelse(bh);
104
105 failed_unlock:
106 if (likely(!err))
107 err = nilfs_transaction_commit(sb);
108 else
109 nilfs_transaction_abort(sb);
110
111 return err;
112 }
113
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-03 21:15 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=202401040559.LWerfZTh-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--cc=llvm@lists.linux.dev \
--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.