All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Tondellier <tondellier+ml.nfdev@dosisoft.fr>
To: netfilter-devel@vger.kernel.org
Subject: Re: OOPS NULL pointer dereference in nf_nat_setup_info+0x471 (reproductible, 3.14.4)
Date: Fri, 30 May 2014 02:06:13 +0200	[thread overview]
Message-ID: <9348748.0ZqBPE68XC@quad> (raw)
In-Reply-To: <20140529183253.GA16912@breakpoint.cc>

Hi, 

Florian Westphal wrote :
> Vincent Tondellier <tondellier+ml.nfdev@dosisoft.fr> wrote:
> > sysctl -w net.ipv4.ip_forward=1
> > sysctl -w net.netfilter.nf_conntrack_helper=0
> > sysctl -w net.netfilter.nf_conntrack_acct=1
> > 
> > And try to connect the pptp client. Instant oops.
> 
> Q: does it not oops with _acct=0?

No oops when _acct == 0, and I can't reproduce it with the ftp helper, or 
without the iptables helpers (_helper=0 is not needed, only the iptables 
rules)

> If that fixes it, and you have lockdep enabled in kernel
> config 

# grep LOCKDEP /boot/config-3.14.4
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_LOCKDEP=y
CONFIG_DEBUG_LOCKDEP=y

> -- can you check if
> 
> commit 223b02d923ecd7c84cf9780bb3686f455d279279
> netfilter: nf_conntrack: reserve two bytes for nf_ct_ext->len
> 
> helps?

yes, no oops. Seems to be scheduled for 3.14.5

and 3.15-rc7 works too

I will ask the debian bug [1] reporter if it fixes his problem

Thanks


[1] https://bugs.debian.org/741667


      reply	other threads:[~2014-05-30  0:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 16:59 OOPS NULL pointer dereference in nf_nat_setup_info+0x471 (reproductible, 3.14.4) Vincent Tondellier
2014-05-27  9:12 ` Vincent Tondellier
2014-05-29 16:41 ` Vincent Tondellier
2014-05-29 18:32   ` Florian Westphal
2014-05-30  0:06     ` Vincent Tondellier [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=9348748.0ZqBPE68XC@quad \
    --to=tondellier+ml.nfdev@dosisoft.fr \
    --cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.