[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1447779716.22599.123.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Tue, 17 Nov 2015 09:01:56 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Will Deacon <will.deacon@....com>
Cc: Arnd Bergmann <arnd@...db.de>,
Catalin Marinas <catalin.marinas@....com>,
kernel-build-reports@...ts.linaro.org, olof@...om.net,
David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: next build: 235 warnings 3 failures (next/next-20151117)
On Tue, 2015-11-17 at 16:44 +0000, Will Deacon wrote:
> Do you know the usage in the kernel causing this warning?
/**
* sk_state_load - read sk->sk_state for lockless contexts
* @sk: socket pointer
*
* Paired with sk_state_store(). Used in places we do not hold socket lock :
* tcp_diag_get_info(), tcp_get_info(), tcp_poll(), get_tcp4_sock() ...
*/
static inline int sk_state_load(const struct sock *sk)
{
return smp_load_acquire(&sk->sk_state);
}
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists