netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@bytheb.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Netdev list <netdev@vger.kernel.org>,
	pablo@netfilter.org
Subject: Re: 4.9-rc0: nf_hooks_ingress missing, breaking compilation
Date: Thu, 06 Oct 2016 09:54:15 -0400	[thread overview]
Message-ID: <f7ttwcpy454.fsf@redhat.com> (raw)
In-Reply-To: <20161006065844.GA27024@amd> (Pavel Machek's message of "Thu, 6 Oct 2016 08:58:44 +0200")

Pavel Machek <pavel@ucw.cz> writes:

> Hi!

Hi Pavel,

> In kernel based on edadd0e, I get plenty of errors such as:

In this case, I screwed up - sincere apologies.

Enabling CONFIG_NETFILTER_INGRESS will work around this error for the
time being, while the fix makes it way through the various trees.

> net/netfilter/core.c:96:3: note: in expansion of macro ‘rcu_assign_pointer’
>    rcu_assign_pointer(reg->dev->nf_hooks_ingress, entry);
>    ^
> In file included from ./include/linux/linkage.h:4:0,
>                  from ./include/linux/kernel.h:6,
>                  from net/netfilter/core.c:10:
> net/netfilter/core.c:96:30: error: ‘struct net_device’ has no member named ‘nf_hooks_ingress’
>    rcu_assign_pointer(reg->dev->nf_hooks_ingress, entry);
>                               ^
>
> Config is attached.
>
> [Ok, I guess testing -rc0 is "a bit too brave" :-)]
>
> Best regards,
> 									Pavel

      reply	other threads:[~2016-10-06 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06  6:58 4.9-rc0: nf_hooks_ingress missing, breaking compilation Pavel Machek
2016-10-06 13:54 ` Aaron Conole [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=f7ttwcpy454.fsf@redhat.com \
    --to=aconole@bytheb.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=pavel@ucw.cz \
    /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).