mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Joe Stringer <joestringer@nicira.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, pshelar@nicira.com,
	linux-kernel@vger.kernel.org, jesse@nicira.com
Subject: Re: [PATCHv2 1/7] openvswitch: Rename LABEL->LABELS
Date: Fri, 2 Oct 2015 05:13:49 +0800	[thread overview]
Message-ID: <201510020526.yYUtAeEs%fengguang.wu@intel.com> (raw)
In-Reply-To: <1443732810-38746-2-git-send-email-joestringer@nicira.com>

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

Hi Joe,

[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]

config: i386-randconfig-s0-201539 (attached as .config)
reproduce:
        git checkout eed31e9f7806b78678a47676a8b841831cbdd582
        # save the attached .config to linux build tree
        make ARCH=i386 

All error/warnings (new ones prefixed by >>):

   In file included from arch/x86/include/asm/string.h:2:0,
                    from include/linux/string.h:17,
                    from include/linux/dynamic_debug.h:111,
                    from include/linux/printk.h:277,
                    from include/linux/kernel.h:13,
                    from include/linux/skbuff.h:17,
                    from net/openvswitch/actions.c:21:
   net/openvswitch/conntrack.h: In function 'ovs_ct_fill_key':
>> net/openvswitch/conntrack.h:75:17: error: 'struct <anonymous>' has no member named 'label'
     memset(&key->ct.label, 0, sizeof(key->ct.label));
                    ^
   arch/x86/include/asm/string_32.h:325:46: note: in definition of macro 'memset'
    #define memset(s, c, count) __builtin_memset(s, c, count)
                                                 ^
   net/openvswitch/conntrack.h:75:42: error: 'struct <anonymous>' has no member named 'label'
     memset(&key->ct.label, 0, sizeof(key->ct.label));
                                             ^
   arch/x86/include/asm/string_32.h:325:52: note: in definition of macro 'memset'
    #define memset(s, c, count) __builtin_memset(s, c, count)
                                                       ^

vim +75 net/openvswitch/conntrack.h

7f8a436e Joe Stringer 2015-08-26  59  	return -ENOTSUPP;
7f8a436e Joe Stringer 2015-08-26  60  }
7f8a436e Joe Stringer 2015-08-26  61  
7f8a436e Joe Stringer 2015-08-26  62  static inline int ovs_ct_execute(struct net *net, struct sk_buff *skb,
7f8a436e Joe Stringer 2015-08-26  63  				 struct sw_flow_key *key,
7f8a436e Joe Stringer 2015-08-26  64  				 const struct ovs_conntrack_info *info)
7f8a436e Joe Stringer 2015-08-26  65  {
7f8a436e Joe Stringer 2015-08-26  66  	return -ENOTSUPP;
7f8a436e Joe Stringer 2015-08-26  67  }
7f8a436e Joe Stringer 2015-08-26  68  
7f8a436e Joe Stringer 2015-08-26  69  static inline void ovs_ct_fill_key(const struct sk_buff *skb,
7f8a436e Joe Stringer 2015-08-26  70  				   struct sw_flow_key *key)
7f8a436e Joe Stringer 2015-08-26  71  {
7f8a436e Joe Stringer 2015-08-26  72  	key->ct.state = 0;
7f8a436e Joe Stringer 2015-08-26  73  	key->ct.zone = 0;
182e3042 Joe Stringer 2015-08-26  74  	key->ct.mark = 0;
c2ac6673 Joe Stringer 2015-08-26 @75  	memset(&key->ct.label, 0, sizeof(key->ct.label));
7f8a436e Joe Stringer 2015-08-26  76  }
7f8a436e Joe Stringer 2015-08-26  77  
7f8a436e Joe Stringer 2015-08-26  78  static inline int ovs_ct_put_key(const struct sw_flow_key *key,
7f8a436e Joe Stringer 2015-08-26  79  				 struct sk_buff *skb)
7f8a436e Joe Stringer 2015-08-26  80  {
7f8a436e Joe Stringer 2015-08-26  81  	return 0;
7f8a436e Joe Stringer 2015-08-26  82  }
7f8a436e Joe Stringer 2015-08-26  83  

:::::: The code at line 75 was first introduced by commit
:::::: c2ac667358708d7cce64c78f58af6adf4c1e848b openvswitch: Allow matching on conntrack label

:::::: TO: Joe Stringer <joestringer@nicira.com>
:::::: CC: David S. Miller <davem@davemloft.net>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 25092 bytes --]

  reply	other threads:[~2015-10-01 21:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 20:53 [PATCHv2 0/7] OVS conntrack fixes for net Joe Stringer
2015-10-01 20:53 ` [PATCHv2 1/7] openvswitch: Rename LABEL->LABELS Joe Stringer
2015-10-01 21:13   ` kbuild test robot [this message]
2015-10-01 22:00     ` [PATCHv3] " Joe Stringer
2015-10-01 22:23       ` Pravin Shelar
2015-10-05 13:34       ` David Miller
2015-10-01 20:53 ` [PATCHv2 2/7] openvswitch: Fix typos in CT headers Joe Stringer
2015-10-01 20:53 ` [PATCHv2 3/7] openvswitch: Fix skb leak in ovs_fragment() Joe Stringer
2015-10-01 22:25   ` Pravin Shelar
2015-10-01 20:53 ` [PATCHv2 4/7] openvswitch: Ensure flow is valid before executing ct Joe Stringer
2015-10-01 20:53 ` [PATCHv2 5/7] openvswitch: Reject ct_state unsupported bits Joe Stringer
2015-10-01 20:53 ` [PATCHv2 6/7] openvswitch: Extend ct_state match field to 32 bits Joe Stringer
2015-10-01 20:53 ` [PATCHv2 7/7] openvswitch: Change CT_ATTR_FLAGS to CT_ATTR_COMMIT Joe Stringer
2015-10-01 22:26   ` Pravin Shelar

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=201510020526.yYUtAeEs%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=jesse@nicira.com \
    --cc=joestringer@nicira.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®