From: kbuild test robot <lkp@intel.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: kbuild-all@01.org, kernel test robot <fengguang.wu@intel.com>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 net] tcp/dccp: fix other lockdep splats accessing ireq_opt
Date: Tue, 24 Oct 2017 20:17:52 +0800 [thread overview]
Message-ID: <201710242026.bCICiPKA%fengguang.wu@intel.com> (raw)
In-Reply-To: <1508800508.30291.104.camel@edumazet-glaptop3.roam.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 2033 bytes --]
Hi Eric,
[auto build test ERROR on net/master]
url: https://github.com/0day-ci/linux/commits/Eric-Dumazet/tcp-dccp-fix-other-lockdep-splats-accessing-ireq_opt/20171024-200038
config: i386-randconfig-x003-201743 (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
All error/warnings (new ones prefixed by >>):
In file included from include/linux/srcu.h:33:0,
from include/linux/notifier.h:15,
from include/linux/memory_hotplug.h:6,
from include/linux/mmzone.h:779,
from include/linux/gfp.h:5,
from include/linux/mm.h:9,
from net/socket.c:61:
include/net/inet_sock.h: In function 'ireq_opt_deref':
>> include/net/inet_sock.h:138:29: error: 'ireq' is a pointer; did you mean to use '->'?
refcount_read(&ireq.req->rsk_refcnt) > 0);
^
->
include/linux/rcupdate.h:292:52: note: in definition of macro 'RCU_LOCKDEP_WARN'
if (debug_lockdep_rcu_enabled() && !__warned && (c)) { \
^
include/linux/rcupdate.h:486:2: note: in expansion of macro '__rcu_dereference_check'
__rcu_dereference_check((p), (c) || rcu_read_lock_held(), __rcu)
^~~~~~~~~~~~~~~~~~~~~~~
>> include/net/inet_sock.h:137:9: note: in expansion of macro 'rcu_dereference_check'
return rcu_dereference_check(ireq->ireq_opt,
^~~~~~~~~~~~~~~~~~~~~
vim +138 include/net/inet_sock.h
134
135 static inline struct ip_options_rcu *ireq_opt_deref(const struct inet_request_sock *ireq)
136 {
> 137 return rcu_dereference_check(ireq->ireq_opt,
> 138 refcount_read(&ireq.req->rsk_refcnt) > 0);
139 }
140
---
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: 29923 bytes --]
next prev parent reply other threads:[~2017-10-24 12:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 19:33 [PATCH net] tcp/dccp: fix lockdep splat in inet_csk_route_req() Eric Dumazet
2017-10-23 4:46 ` David Miller
2017-10-23 9:56 ` [tcp/dccp] 81e5391ca7: WARNING:suspicious_RCU_usage kernel test robot
2017-10-23 15:02 ` [PATCH net] tcp/dccp: fix again lockdep splat in inet_csk_route_req() Eric Dumazet
2017-10-23 22:46 ` Eric Dumazet
2017-10-23 23:15 ` [PATCH v2 net] tcp/dccp: fix other lockdep splats accessing ireq_opt Eric Dumazet
2017-10-24 9:56 ` David Miller
2017-10-24 15:18 ` Eric Dumazet
2017-10-24 12:17 ` kbuild test robot [this message]
2017-10-24 12:27 ` kbuild test robot
2017-10-24 15:20 ` [PATCH v3 " Eric Dumazet
2017-10-26 8:42 ` 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=201710242026.bCICiPKA%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.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;
as well as URLs for NNTP newsgroup(s).