netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lev Stipakov <lstipakov@gmail.com>
To: linux-audit@redhat.com
Cc: netfilter-devel@vger.kernel.org
Subject: iptables audit target causes kernel panic with iptables-persistent (kernel 3.2.78)
Date: Tue, 26 Apr 2016 11:58:32 +0300	[thread overview]
Message-ID: <nfnajo$4cj$1@ger.gmane.org> (raw)

Hello,

I see kernel panic with iptables-persistent package installed and one 
iptables rule with AUDIT target.

   root@debian7:~# uname -a
   Linux debian7 3.2.0-4-amd64 #1 SMP Debian 3.2.78-1 x86_64 GNU/Linux

   root@debian7:~# dpkg -l | grep iptables
   ii  iptables			1.4.14-3.1
   ii  iptables-persistent	0.5.7+deb7u1

Steps to reproduce:

1) Install Debian 7 and iptables-persistent (see versions above)
2) Add iptables rule (must be OUTPUT chain):

   root@debian7:~# iptables -I OUTPUT -j AUDIT --type ACCEPT

3) Save rule:

   root@debian7:~# iptables-save > /etc/iptables/rules.v4

4) Reboot

5) Kernel panic (screenshot): 
https://www.dropbox.com/s/db40e5kc10e4ddg/kernel_panic2.png?dl=0


I cannot reproduce it on (one of) previous kernel version:

   lev@debi7:~$ uname -a
   Linux debi7 3.2.0-4-amd64 #1 SMP Debian 3.2.73-2+deb7u2 x86_64 GNU/Linux

   lev@debi7:~$ dpkg -l | grep iptables
   ii  iptables                           1.4.14-3.1
   ii  iptables-persistent                0.5.7+deb7u1


-Lev

             reply	other threads:[~2016-04-26  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26  8:58 Lev Stipakov [this message]
2016-04-26 18:54 ` iptables audit target causes kernel panic with iptables-persistent (kernel 3.2.78) Paul Moore
2016-04-26 19:58   ` Lev Stipakov
2016-04-26 20:17     ` Paul Moore
  -- strict thread matches above, loose matches on Subject: below --
2016-04-26  9:25 Lev Stipakov
2016-04-26 12:17 ` Lev Stipakov

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='nfnajo$4cj$1@ger.gmane.org' \
    --to=lstipakov@gmail.com \
    --cc=linux-audit@redhat.com \
    --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 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).