mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Fredrik Markstrom <fredrik.markstrom@gmail.com>
Cc: kbuild-all@01.org, "Eric Dumazet" <eric.dumazet@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	bridge@lists.linux-foundation.org,
	"Fredrik Markström" <fredrik.markstrom@gmail.com>
Subject: Re: [PATCH 1/2] net: Added mtu parameter to dev_forward_skb calls
Date: Wed, 10 May 2017 19:47:04 +0800	[thread overview]
Message-ID: <201705101953.bufW4IP0%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170509124439.45674-2-fredrik.markstrom@gmail.com>

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

Hi Fredrik,

[auto build test ERROR on net/master]
[also build test ERROR on v4.11 next-20170510]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Fredrik-Markstrom/net-Added-mtu-parameter-to-dev_forward_skb-calls/20170509-231142
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   net//bridge/br_forward.c: In function '__br_forward':
>> net//bridge/br_forward.c:99:46: error: 'struct sk_buff' has no member named 'dev_mtu'
       if (!is_skb_forwardable(skb->dev, skb, skb->dev_mtu)) {
                                                 ^~

vim +99 net//bridge/br_forward.c

    93			}
    94			br_hook = NF_BR_FORWARD;
    95			skb_forward_csum(skb);
    96			net = dev_net(indev);
    97		} else {
    98			if (unlikely(netpoll_tx_running(to->br->dev))) {
  > 99				if (!is_skb_forwardable(skb->dev, skb, skb->dev_mtu)) {
   100					kfree_skb(skb);
   101				} else {
   102					skb_push(skb, ETH_HLEN);

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 39200 bytes --]

  reply	other threads:[~2017-05-10 11:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 12:44 [PATCH 0/2] net: Set maximum receive packet size on veth interfaces Fredrik Markstrom
2017-05-09 12:44 ` [PATCH 1/2] net: Added mtu parameter to dev_forward_skb calls Fredrik Markstrom
2017-05-10 11:47   ` kbuild test robot [this message]
2017-05-09 12:44 ` [PATCH 2/2] veth: Added attribute to set maximum receive size on veth interfaces Fredrik Markstrom
2017-05-09 12:44 ` Support for VETH_MRU in libnl Fredrik Markstrom
2017-05-09 15:49 ` [PATCH 0/2] net: Set maximum receive packet size on veth interfaces Stephen Hemminger
2017-05-09 17:48 ` David Miller
2017-05-10  0:42   ` Fredrik Markström
2017-05-12  3:27     ` Cong Wang

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=201705101953.bufW4IP0%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=ast@kernel.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=fredrik.markstrom@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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 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®