From: kernel test robot <lkp@intel.com>
To: Boris Burkov <boris@bur.io>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com,
linux-fscrypt@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH v3 2/5] btrfs: initial fsverity support
Date: Fri, 9 Apr 2021 07:19:17 +0800 [thread overview]
Message-ID: <202104090656.T2kv4QCd-lkp@intel.com> (raw)
In-Reply-To: <c9335d862ee4ddc1f7193bbb06ca7313d9ff1b30.1617900170.git.boris@bur.io>
[-- Attachment #1: Type: text/plain, Size: 3177 bytes --]
Hi Boris,
I love your patch! Yet something to improve:
[auto build test ERROR on kdave/for-next]
[also build test ERROR on next-20210408]
[cannot apply to v5.12-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Boris-Burkov/btrfs-support-fsverity/20210409-023606
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
config: x86_64-randconfig-a005-20210408 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/dd118218fea47389631a62ec533207ba39e69b41
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Boris-Burkov/btrfs-support-fsverity/20210409-023606
git checkout dd118218fea47389631a62ec533207ba39e69b41
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
fs/btrfs/super.c: In function 'btrfs_fill_super':
>> fs/btrfs/super.c:1368:6: error: 'struct super_block' has no member named 's_vop'; did you mean 's_op'?
1368 | sb->s_vop = &btrfs_verityops;
| ^~~~~
| s_op
vim +1368 fs/btrfs/super.c
1354
1355 static int btrfs_fill_super(struct super_block *sb,
1356 struct btrfs_fs_devices *fs_devices,
1357 void *data)
1358 {
1359 struct inode *inode;
1360 struct btrfs_fs_info *fs_info = btrfs_sb(sb);
1361 int err;
1362
1363 sb->s_maxbytes = MAX_LFS_FILESIZE;
1364 sb->s_magic = BTRFS_SUPER_MAGIC;
1365 sb->s_op = &btrfs_super_ops;
1366 sb->s_d_op = &btrfs_dentry_operations;
1367 sb->s_export_op = &btrfs_export_ops;
> 1368 sb->s_vop = &btrfs_verityops;
1369 sb->s_xattr = btrfs_xattr_handlers;
1370 sb->s_time_gran = 1;
1371 #ifdef CONFIG_BTRFS_FS_POSIX_ACL
1372 sb->s_flags |= SB_POSIXACL;
1373 #endif
1374 sb->s_flags |= SB_I_VERSION;
1375 sb->s_iflags |= SB_I_CGROUPWB;
1376
1377 err = super_setup_bdi(sb);
1378 if (err) {
1379 btrfs_err(fs_info, "super_setup_bdi failed");
1380 return err;
1381 }
1382
1383 err = open_ctree(sb, fs_devices, (char *)data);
1384 if (err) {
1385 btrfs_err(fs_info, "open_ctree failed");
1386 return err;
1387 }
1388
1389 inode = btrfs_iget(sb, BTRFS_FIRST_FREE_OBJECTID, fs_info->fs_root);
1390 if (IS_ERR(inode)) {
1391 err = PTR_ERR(inode);
1392 goto fail_close;
1393 }
1394
1395 sb->s_root = d_make_root(inode);
1396 if (!sb->s_root) {
1397 err = -ENOMEM;
1398 goto fail_close;
1399 }
1400
1401 cleancache_init_fs(sb);
1402 sb->s_flags |= SB_ACTIVE;
1403 return 0;
1404
1405 fail_close:
1406 close_ctree(fs_info);
1407 return err;
1408 }
1409
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3 2/5] btrfs: initial fsverity support
Date: Fri, 09 Apr 2021 07:19:17 +0800 [thread overview]
Message-ID: <202104090656.T2kv4QCd-lkp@intel.com> (raw)
In-Reply-To: <c9335d862ee4ddc1f7193bbb06ca7313d9ff1b30.1617900170.git.boris@bur.io>
[-- Attachment #1: Type: text/plain, Size: 3276 bytes --]
Hi Boris,
I love your patch! Yet something to improve:
[auto build test ERROR on kdave/for-next]
[also build test ERROR on next-20210408]
[cannot apply to v5.12-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Boris-Burkov/btrfs-support-fsverity/20210409-023606
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
config: x86_64-randconfig-a005-20210408 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/dd118218fea47389631a62ec533207ba39e69b41
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Boris-Burkov/btrfs-support-fsverity/20210409-023606
git checkout dd118218fea47389631a62ec533207ba39e69b41
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
fs/btrfs/super.c: In function 'btrfs_fill_super':
>> fs/btrfs/super.c:1368:6: error: 'struct super_block' has no member named 's_vop'; did you mean 's_op'?
1368 | sb->s_vop = &btrfs_verityops;
| ^~~~~
| s_op
vim +1368 fs/btrfs/super.c
1354
1355 static int btrfs_fill_super(struct super_block *sb,
1356 struct btrfs_fs_devices *fs_devices,
1357 void *data)
1358 {
1359 struct inode *inode;
1360 struct btrfs_fs_info *fs_info = btrfs_sb(sb);
1361 int err;
1362
1363 sb->s_maxbytes = MAX_LFS_FILESIZE;
1364 sb->s_magic = BTRFS_SUPER_MAGIC;
1365 sb->s_op = &btrfs_super_ops;
1366 sb->s_d_op = &btrfs_dentry_operations;
1367 sb->s_export_op = &btrfs_export_ops;
> 1368 sb->s_vop = &btrfs_verityops;
1369 sb->s_xattr = btrfs_xattr_handlers;
1370 sb->s_time_gran = 1;
1371 #ifdef CONFIG_BTRFS_FS_POSIX_ACL
1372 sb->s_flags |= SB_POSIXACL;
1373 #endif
1374 sb->s_flags |= SB_I_VERSION;
1375 sb->s_iflags |= SB_I_CGROUPWB;
1376
1377 err = super_setup_bdi(sb);
1378 if (err) {
1379 btrfs_err(fs_info, "super_setup_bdi failed");
1380 return err;
1381 }
1382
1383 err = open_ctree(sb, fs_devices, (char *)data);
1384 if (err) {
1385 btrfs_err(fs_info, "open_ctree failed");
1386 return err;
1387 }
1388
1389 inode = btrfs_iget(sb, BTRFS_FIRST_FREE_OBJECTID, fs_info->fs_root);
1390 if (IS_ERR(inode)) {
1391 err = PTR_ERR(inode);
1392 goto fail_close;
1393 }
1394
1395 sb->s_root = d_make_root(inode);
1396 if (!sb->s_root) {
1397 err = -ENOMEM;
1398 goto fail_close;
1399 }
1400
1401 cleancache_init_fs(sb);
1402 sb->s_flags |= SB_ACTIVE;
1403 return 0;
1404
1405 fail_close:
1406 close_ctree(fs_info);
1407 return err;
1408 }
1409
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 34228 bytes --]
next prev parent reply other threads:[~2021-04-08 23:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 18:33 [PATCH v3 0/5] btrfs: support fsverity Boris Burkov
2021-04-08 18:33 ` [PATCH v3 1/5] btrfs: add compat_flags to btrfs_inode_item Boris Burkov
2021-04-08 23:40 ` Anand Jain
2021-04-09 18:20 ` Boris Burkov
2021-05-13 17:21 ` David Sterba
2021-04-08 18:33 ` [PATCH v3 2/5] btrfs: initial fsverity support Boris Burkov
2021-04-08 22:38 ` kernel test robot
2021-04-08 22:38 ` kernel test robot
2021-04-08 22:50 ` Eric Biggers
2021-04-09 18:05 ` Boris Burkov
2021-04-09 23:25 ` Eric Biggers
2021-04-09 22:45 ` Boris Burkov
2021-04-09 23:32 ` Eric Biggers
2021-05-03 18:46 ` Boris Burkov
2021-04-08 22:56 ` kernel test robot
2021-04-08 22:56 ` kernel test robot
2021-04-08 23:19 ` kernel test robot [this message]
2021-04-08 23:19 ` kernel test robot
2021-04-08 18:33 ` [PATCH v3 3/5] btrfs: check verity for reads of inline extents and holes Boris Burkov
2021-04-08 18:33 ` [PATCH v3 4/5] btrfs: fallback to buffered io for verity files Boris Burkov
2021-04-08 18:33 ` [PATCH v3 5/5] btrfs: verity metadata orphan items Boris Burkov
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=202104090656.T2kv4QCd-lkp@intel.com \
--to=lkp@intel.com \
--cc=boris@bur.io \
--cc=kbuild-all@lists.01.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fscrypt@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 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.