From: Frederik Himpe <fhimpe@ai.vub.ac.be>
To: Florian Westphal <fw@strlen.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
netfilter-devel@vger.kernel.org
Subject: Re: 5.0.7: WARNING: CPU: 1 PID: 169 at net/netfilter/nft_compat.c:82 and genreal protection fault
Date: Tue, 09 Apr 2019 11:59:08 +0200 [thread overview]
Message-ID: <f90ffd6e6f0ebd1f9e99a3d01f526bb92da97b2a.camel@ai.vub.ac.be> (raw)
In-Reply-To: <20190408201909.6mcgobkdnswyikfv@breakpoint.cc>
On Mon, 2019-04-08 at 22:19 +0200, Florian Westphal wrote:
> Frederik Himpe <fhimpe@ai.vub.ac.be> wrote:
> > I'm experiencing this reproducible bug every time shorewall6 is
> > restarted:
> > [ 28.932323] WARNING: CPU: 1 PID: 169 at
> > net/netfilter/nft_compat.c:82 nft_xt_put.part.9+0x21/0x30
> > [nft_compat]
> [..]
> > [ 29.015565] general protection fault: 0000 [#1] SMP PTI
> > [ 29.015574] CPU: 3 PID: 2069 Comm: ip6tables-resto Tainted:
> > G W E 5.0.7 #1
>
> Does this problem go away when you apply this commit on top of 5.0.7?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8e204006340b7aaf32bd2b9806c692f6e0cb38a
>
> If not, can you send a minimal reproducer?
Indeed, the problem does not happen any more with this patch applied to
5.0.7. Thanks!
--
Frederik Himpe <fhimpe@ai.vub.ac.be>
Vrije Universiteit Brussel
prev parent reply other threads:[~2019-04-09 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 13:22 5.0.7: WARNING: CPU: 1 PID: 169 at net/netfilter/nft_compat.c:82 and genreal protection fault Frederik Himpe
2019-04-08 20:19 ` Florian Westphal
2019-04-09 9:59 ` Frederik Himpe [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=f90ffd6e6f0ebd1f9e99a3d01f526bb92da97b2a.camel@ai.vub.ac.be \
--to=fhimpe@ai.vub.ac.be \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--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).