All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android-4.9-p 3/4] net/netfilter/xt_quota2.c:346:4: error: 'struct xt_match' has no member named 'usersize'
Date: Tue, 02 Nov 2021 12:00:44 +0800	[thread overview]
Message-ID: <202111021237.EiWiS8xY-lkp@intel.com> (raw)

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

tree:   https://android.googlesource.com/kernel/common android-4.9-p
head:   a38021a717a62118df7f0a536694943050ec2af5
commit: 9e8a7105d57ec295f2c32067de0b7ed2f7565d67 [3/4] ANDROID: xt_quota2: set usersize in xt_match registration object
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
        git remote add android-common https://android.googlesource.com/kernel/common
        git fetch --no-tags android-common android-4.9-p
        git checkout 9e8a7105d57ec295f2c32067de0b7ed2f7565d67
        # save the attached .config to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash net/netfilter/

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 >>):

   In file included from include/linux/kasan.h:4:0,
                    from include/linux/slab.h:118,
                    from include/linux/textsearch.h:8,
                    from include/linux/skbuff.h:30,
                    from net/netfilter/xt_quota2.c:17:
   include/linux/sched.h:1261:1: warning: type qualifiers ignored on function return type [-Wignored-qualifiers]
    const struct sched_group_energy * const(*sched_domain_energy_f)(int cpu);
    ^~~~~
>> net/netfilter/xt_quota2.c:346:4: error: 'struct xt_match' has no member named 'usersize'
      .usersize   = offsetof(struct xt_quota_mtinfo2, master),
       ^~~~~~~~
   net/netfilter/xt_quota2.c:357:4: error: 'struct xt_match' has no member named 'usersize'
      .usersize   = offsetof(struct xt_quota_mtinfo2, master),
       ^~~~~~~~


vim +346 net/netfilter/xt_quota2.c

   336	
   337	static struct xt_match quota_mt2_reg[] __read_mostly = {
   338		{
   339			.name       = "quota2",
   340			.revision   = 3,
   341			.family     = NFPROTO_IPV4,
   342			.checkentry = quota_mt2_check,
   343			.match      = quota_mt2,
   344			.destroy    = quota_mt2_destroy,
   345			.matchsize  = sizeof(struct xt_quota_mtinfo2),
 > 346			.usersize   = offsetof(struct xt_quota_mtinfo2, master),
   347			.me         = THIS_MODULE,
   348		},
   349		{
   350			.name       = "quota2",
   351			.revision   = 3,
   352			.family     = NFPROTO_IPV6,
   353			.checkentry = quota_mt2_check,
   354			.match      = quota_mt2,
   355			.destroy    = quota_mt2_destroy,
   356			.matchsize  = sizeof(struct xt_quota_mtinfo2),
   357			.usersize   = offsetof(struct xt_quota_mtinfo2, master),
   358			.me         = THIS_MODULE,
   359		},
   360	};
   361	

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

                 reply	other threads:[~2021-11-02  4:00 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=202111021237.EiWiS8xY-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.