netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Easy network (config) breakage with 3.17-rc1: NETFILTER_XT_TARGET_LOG
Date: Fri, 22 Aug 2014 20:01:12 +0200	[thread overview]
Message-ID: <20140822180112.GB3402@salvia> (raw)
In-Reply-To: <CACna6rymZjgex0p1snf3e-GvK2xHrQST3roGiA3F__y3DvYhKw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]

On Thu, Aug 21, 2014 at 12:49:33PM +0200, Rafał Miłecki wrote:
> Few days ago I updated my 3.16 to 3.17-rc1 (both self compiled) and I
> was using it until I noticed my machine doesn't respond to pings. I
> rebooted to 3.16 and it was working again.
> 
> I bisected between 3.16 and 3.17-rc1 but it has failed. After all I
> got 3.16 not working anymore as well.
> 
> It took me few hours to find the one to blame:
> CONFIG_NETFILTER_XT_TARGET_LOG. After moving my config from 3.16 to
> 3.17-rc1 CONFIG_NETFILTER_XT_TARGET_LOG got disabled because of two
> new dependencies: NF_LOG_IPV4 && NF_LOG_IPV6.
> 
> It would be nice if you could try to use "select" instead of "depends
> on" in such cases in the future. I bet fix my problem would be trivial
> since the beginning, but end-users may spent hours or days tracking
> such things :(

Sorry for that Kconfig problem. Please, have a look at the attached
patch and confirm that it fixes the problem. At quick glance I think
it's safe to use select in this case.

> Please, treat it as an advise/request, not a blaming :)

It's good indeed that you have reported this, we're still in -rc1
which means that we can still fix things.

If you have any further problem, please let us know. Thanks.

[-- Attachment #2: x --]
[-- Type: text/plain, Size: 460 bytes --]

diff --git a/net/netfilter/Kconfig b/net/netfilter/Kconfig
index 05eb177..44625d8 100644
--- a/net/netfilter/Kconfig
+++ b/net/netfilter/Kconfig
@@ -747,7 +747,8 @@ config NETFILTER_XT_TARGET_LED
 
 config NETFILTER_XT_TARGET_LOG
 	tristate "LOG target support"
-	depends on NF_LOG_IPV4 && NF_LOG_IPV6
+	select NF_LOG_IPV4
+	select NF_LOG_IPV6
 	default m if NETFILTER_ADVANCED=n
 	help
 	  This option adds a `LOG' target, which allows you to create rules in

  reply	other threads:[~2014-08-22 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21 10:49 Easy network (config) breakage with 3.17-rc1: NETFILTER_XT_TARGET_LOG Rafał Miłecki
2014-08-22 18:01 ` Pablo Neira Ayuso [this message]
2014-08-24 13:28   ` Pablo Neira Ayuso
2014-08-29  7:04     ` Rafał Miłecki

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=20140822180112.GB3402@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /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).