mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Ivan Delalande <colona@arista.com>
Cc: kbuild-all@01.org, David Miller <davem@davemloft.net>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ivan Delalande <colona@arista.com>
Subject: Re: [PATCH 2/2] tcp: md5: export all configured signature keys in /proc/net
Date: Sun, 25 Jun 2017 09:38:30 +0800	[thread overview]
Message-ID: <201706250911.wgoDe4j2%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170623014028.28257-2-colona@arista.com>

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

Hi Ivan,

[auto build test ERROR on net/master]
[also build test ERROR on v4.12-rc6 next-20170623]
[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/Ivan-Delalande/tcp-add-mode-parameter-to-tcp_proc_register/20170625-070707
config: x86_64-randconfig-x019-06250446 (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/ipv4/tcp.c: In function 'do_md5_seq_print_key':
   net/ipv4/tcp.c:3300:53: error: 'const struct tcp_md5sig_key' has no member named 'prefixlen'
      seq_printf(seq, "%39pI4/%-3u ", &key->addr.a4, key->prefixlen);
                                                        ^~
>> net/ipv4/tcp.c:3302:46: error: 'const union tcp_md5_addr' has no member named 'a6'; did you mean 'a4'?
      seq_printf(seq, "%39pI6c/%-3u ", &key->addr.a6, key->prefixlen);
                                                 ^
   net/ipv4/tcp.c:3302:54: error: 'const struct tcp_md5sig_key' has no member named 'prefixlen'
      seq_printf(seq, "%39pI6c/%-3u ", &key->addr.a6, key->prefixlen);
                                                         ^~

vim +3302 net/ipv4/tcp.c

  3294	{
  3295		if (key->keylen == 0)
  3296			return;
  3297	
  3298		seq_printf(seq, "%4d: %6lu ", st->num, ino);
  3299		if (key->family == AF_INET)
> 3300			seq_printf(seq, "%39pI4/%-3u ", &key->addr.a4, key->prefixlen);
  3301		else
> 3302			seq_printf(seq, "%39pI6c/%-3u ", &key->addr.a6, key->prefixlen);
  3303		seq_printf(seq, "%*pE\n", key->keylen, key->key);
  3304	}
  3305	

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

  reply	other threads:[~2017-06-25  1:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23  1:40 [PATCH 1/2] tcp: add mode parameter to tcp_proc_register Ivan Delalande
2017-06-23  1:40 ` [PATCH 2/2] tcp: md5: export all configured signature keys in /proc/net Ivan Delalande
2017-06-25  1:38   ` kbuild test robot [this message]
2017-06-23  4:27 ` [PATCH 1/2] tcp: add mode parameter to tcp_proc_register David Miller

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=201706250911.wgoDe4j2%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=colona@arista.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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 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®