From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Andrew <nitr0@seti.kr.ua>
Cc: netfilter@vger.kernel.org
Subject: Re: Kernel panic in 4.1.6 in nf_nat_redirect
Date: Wed, 14 Oct 2015 19:58:59 +0200 [thread overview]
Message-ID: <20151014175859.GA3415@salvia> (raw)
In-Reply-To: <5613A136.7010203@seti.kr.ua>
On Tue, Oct 06, 2015 at 01:23:50PM +0300, Andrew wrote:
> Maybe crash happens when packet comes to interface without assigned IP?
Do this resolved the problem for you?
Not telling here this is enough, obviously we shouldn't crash here.
> 06.10.2015 13:11, Andrew wrote:
> >Hi.
> >
> >I recompiled kernel with debug info enabled; here's gdb output:
> >
> >(gdb) list *nf_nat_redirect_ipv4+0x24
> >0x24 is in nf_nat_redirect_ipv4 (/var/testpoint/LEAF/source/i486-unknown-linux-uclibc/linux/linux-4.1/net/netfilter/nf_nat_redirect.c:60).
> >55
> >56 rcu_read_lock();
> >57 indev = __in_dev_get_rcu(skb->dev);
> >58 if (indev != NULL) {
> >59 ifa = indev->ifa_list;
> >60 newdst = ifa->ifa_local;
> >61 }
> >62 rcu_read_unlock();
> >63
> >64 if (!newdst)
> >
> >
> >04.10.2015 22:05, Pablo Neira Ayuso wrote:
> >>Could you please do the following?
> >>
> >>$ gdb net/netfilter/nf_nat_redirect.o
> >>$ list *nf_nat_redirect_ipv4+0x24
> >>
> >>And post the result, thanks.
> >
> >--
> >To unsubscribe from this list: send the line "unsubscribe netfilter" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-10-14 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 20:55 Kernel panic in 4.1.6 in nf_nat_redirect Andrew
2015-10-04 19:05 ` Pablo Neira Ayuso
2015-10-04 19:46 ` Andrew
2015-10-06 10:11 ` Andrew
2015-10-06 10:23 ` Andrew
2015-10-14 17:58 ` Pablo Neira Ayuso [this message]
2015-10-14 18:45 ` Andrew
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=20151014175859.GA3415@salvia \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=nitr0@seti.kr.ua \
/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