Netdev List
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	joe@wand.net.nz
Subject: Re: linux-next: Tree for Oct 5 (net/core/filter.c)
Date: Fri, 5 Oct 2018 17:51:54 +0200	[thread overview]
Message-ID: <e5a04d2f-df44-4616-5621-23d7738353d6@iogearbox.net> (raw)
In-Reply-To: <51ea61d3-032b-f316-4a61-b63ab208d8d4@infradead.org>

[ +Joe ]

On 10/05/2018 05:42 PM, Randy Dunlap wrote:
> On 10/4/18 11:39 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20181004:
>>
> 
> on i386 or x86_64:
> 
> net/core/filter.o: In function `bpf_sk_release':
> filter.c:(.text+0x3c5c): undefined reference to `sock_gen_put'
> net/core/filter.o: In function `sk_lookup':
> filter.c:(.text+0x79a5): undefined reference to `tcp_hashinfo'
> filter.c:(.text+0x79bc): undefined reference to `__inet_lookup_established'
> filter.c:(.text+0x79eb): undefined reference to `tcp_hashinfo'
> filter.c:(.text+0x79f3): undefined reference to `__inet_lookup_listener'
> filter.c:(.text+0x7a14): undefined reference to `udp_table'
> filter.c:(.text+0x7a26): undefined reference to `__udp4_lib_lookup'
> 
> 
> Full randconfig file is attached.
> 
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> 

      reply	other threads:[~2018-10-05 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181005163943.3f8d4f32@canb.auug.org.au>
2018-10-05 15:42 ` linux-next: Tree for Oct 5 (net/core/filter.c) Randy Dunlap
2018-10-05 15:51   ` Daniel Borkmann [this message]

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=e5a04d2f-df44-4616-5621-23d7738353d6@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=joe@wand.net.nz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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