All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 2/6] fs: ext4: move fstrim to file_operation
Date: Tue, 22 Jun 2021 23:34:13 +0800	[thread overview]
Message-ID: <202106222354.D0G3bGS6-lkp@intel.com> (raw)
In-Reply-To: <20210622121136.4394-3-info@metux.net>

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

Hi "Enrico,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on kdave/for-next]
[also build test ERROR on linux/master linus/master v5.13-rc7]
[cannot apply to ext4/dev next-20210622]
[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/Enrico-Weigelt-metux-IT-consult/fs-generic-file-operation-for-fstrim/20210622-211217
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
config: um-x86_64_defconfig (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/2f26b6809e1541cf945da594ef5251e51ba73d3b
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Enrico-Weigelt-metux-IT-consult/fs-generic-file-operation-for-fstrim/20210622-211217
        git checkout 2f26b6809e1541cf945da594ef5251e51ba73d3b
        # save the attached .config to linux build tree
        make W=1 ARCH=um SUBARCH=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/ext4/file.c:930:3: error: 'const struct file_operations' has no member named 'fitrim'; did you mean 'fstrim'?
     930 |  .fitrim  = ext4_fitrim,
         |   ^~~~~~
         |   fstrim
>> fs/ext4/file.c:930:13: error: positional initialization of field in 'struct' declared with 'designated_init' attribute [-Werror=designated-init]
     930 |  .fitrim  = ext4_fitrim,
         |             ^~~~~~~~~~~
   fs/ext4/file.c:930:13: note: (near initialization for 'ext4_file_operations')
>> fs/ext4/file.c:930:13: error: initialization of 'void (*)(struct seq_file *, struct file *)' from incompatible pointer type 'long int (*)(struct file *, struct fstrim_range *)' [-Werror=incompatible-pointer-types]
   fs/ext4/file.c:930:13: note: (near initialization for 'ext4_file_operations.show_fdinfo')
   cc1: some warnings being treated as errors
--
   fs/ext4/ioctl.c: In function 'ext4_fitrim':
>> fs/ext4/ioctl.c:805:43: error: 'sb' undeclared (first use in this function); did you mean 's8'?
     805 |  struct request_queue *q = bdev_get_queue(sb->s_bdev);
         |                                           ^~
         |                                           s8
   fs/ext4/ioctl.c:805:43: note: each undeclared identifier is reported only once for each function it appears in


vim +930 fs/ext4/file.c

   911	
   912	const struct file_operations ext4_file_operations = {
   913		.llseek		= ext4_llseek,
   914		.read_iter	= ext4_file_read_iter,
   915		.write_iter	= ext4_file_write_iter,
   916		.iopoll		= iomap_dio_iopoll,
   917		.unlocked_ioctl = ext4_ioctl,
   918	#ifdef CONFIG_COMPAT
   919		.compat_ioctl	= ext4_compat_ioctl,
   920	#endif
   921		.mmap		= ext4_file_mmap,
   922		.mmap_supported_flags = MAP_SYNC,
   923		.open		= ext4_file_open,
   924		.release	= ext4_release_file,
   925		.fsync		= ext4_sync_file,
   926		.get_unmapped_area = thp_get_unmapped_area,
   927		.splice_read	= generic_file_splice_read,
   928		.splice_write	= iter_file_splice_write,
   929		.fallocate	= ext4_fallocate,
 > 930		.fitrim		= ext4_fitrim,
   931	};
   932	

---
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: 8645 bytes --]

  reply	other threads:[~2021-06-22 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 12:11 RFC: generic file operation for fstrim ioctl() Enrico Weigelt, metux IT consult
2021-06-22 12:11 ` [RFC PATCH 1/6] fs: generic file operation for fstrim Enrico Weigelt, metux IT consult
2021-06-22 12:11 ` [RFC PATCH 2/6] fs: ext4: move fstrim to file_operation Enrico Weigelt, metux IT consult
2021-06-22 15:34   ` kernel test robot [this message]
2021-06-22 12:11 ` [RFC PATCH 3/6] fs: hpfs: " Enrico Weigelt, metux IT consult
2021-06-22 12:11 ` [RFC PATCH 4/6] fs: btrfs: " Enrico Weigelt, metux IT consult
2021-06-22 16:55   ` kernel test robot
2021-06-22 12:11 ` [RFC PATCH 5/6] fs: fat: " Enrico Weigelt, metux IT consult
2021-06-22 12:11 ` [RFC PATCH 6/6] fs: f2fs: " Enrico Weigelt, metux IT consult
2021-06-22 17:48   ` kernel test robot

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=202106222354.D0G3bGS6-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.