From: kbuild test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, dhowells@redhat.com,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 8/9] rxrpc: Reduce the number of PING ACKs sent
Date: Thu, 22 Sep 2016 09:25:19 +0800 [thread overview]
Message-ID: <201609220902.7f1IrDr7%fengguang.wu@intel.com> (raw)
In-Reply-To: <147450480416.14691.2181748630440433933.stgit@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Hi David,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/David-Howells/rxrpc-Preparation-for-slow-start-algorithm/20160922-085242
config: i386-randconfig-x009-201638 (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=i386
Note: the linux-review/David-Howells/rxrpc-Preparation-for-slow-start-algorithm/20160922-085242 HEAD f739ad653a9471b67eb8fc01185c01c2ca1dcb4b builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
net/rxrpc/input.c: In function 'rxrpc_send_ping':
>> net/rxrpc/input.c:50:42: error: 'struct rxrpc_peer' has no member named 'rtt_last_req'; did you mean 'rtt_cache'?
ktime_before(ktime_add_ms(call->peer->rtt_last_req, 1000), now))
^~
vim +50 net/rxrpc/input.c
44 int skew)
45 {
46 struct rxrpc_skb_priv *sp = rxrpc_skb(skb);
47 ktime_t now = skb->tstamp;
48
49 if (call->peer->rtt_usage < 3 ||
> 50 ktime_before(ktime_add_ms(call->peer->rtt_last_req, 1000), now))
51 rxrpc_propose_ACK(call, RXRPC_ACK_PING, skew, sp->hdr.serial,
52 true, true);
53 }
---
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: 28961 bytes --]
next prev parent reply other threads:[~2016-09-22 1:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 0:39 [PATCH net-next 0/9] rxrpc: Preparation for slow-start algorithm David Howells
2016-09-22 0:39 ` [PATCH net-next 1/9] rxrpc: Don't store the rxrpc header in the Tx queue sk_buffs David Howells
2016-09-22 0:39 ` [PATCH net-next 2/9] rxrpc: Add re-sent Tx annotation David Howells
2016-09-22 0:39 ` [PATCH net-next 3/9] rxrpc: Add per-peer RTT tracker David Howells
2016-09-22 4:34 ` kbuild test robot
2016-09-22 4:56 ` kbuild test robot
2016-09-22 0:39 ` [PATCH net-next 4/9] rxrpc: Send pings to get RTT data David Howells
2016-09-22 0:39 ` [PATCH net-next 5/9] rxrpc: Expedite ping response transmission David Howells
2016-09-22 0:39 ` [PATCH net-next 6/9] rxrpc: Add ktime_sub_ms() David Howells
2016-09-22 0:39 ` [PATCH net-next 7/9] rxrpc: Obtain RTT data by requesting ACKs on DATA packets David Howells
2016-09-22 0:40 ` [PATCH net-next 8/9] rxrpc: Reduce the number of PING ACKs sent David Howells
2016-09-22 1:25 ` kbuild test robot [this message]
2016-09-22 0:40 ` [PATCH net-next 9/9] rxrpc: Reduce the number of ACK-Requests sent David Howells
2016-09-22 5:24 ` kbuild test robot
2016-09-22 8:10 ` [PATCH net-next 0/9] rxrpc: Preparation for slow-start algorithm David Howells
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=201609220902.7f1IrDr7%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-afs@lists.infradead.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®