Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>,
	stable@vger.kernel.org, Frederik Himpe <fhimpe@ai.vub.ac.be>
Subject: Re: 5.0.7: WARNING: CPU: 1 PID: 169 at net/netfilter/nft_compat.c:82 and genreal protection fault
Date: Tue, 9 Apr 2019 11:27:51 -0400	[thread overview]
Message-ID: <20190409152751.GL4689@sasha-vm> (raw)
In-Reply-To: <20190409102110.zct4uqax3pq3n2as@salvia>

On Tue, Apr 09, 2019 at 12:21:10PM +0200, Pablo Neira Ayuso wrote:
>On Tue, Apr 09, 2019 at 12:19:06PM +0200, Florian Westphal wrote:
>> Hello -stable team,
>>
>> Frederik Himpe <fhimpe@ai.vub.ac.be> wrote:
>> > On Mon, 2019-04-08 at 22:19 +0200, Florian Westphal wrote:
>> > > Frederik Himpe <fhimpe@ai.vub.ac.be> wrote:
>> > > > [   29.015565] general protection fault: 0000 [#1] SMP PTI
>> > > > [   29.015574] CPU: 3 PID: 2069 Comm: ip6tables-resto Tainted:
>> > >
>> > > 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
>> >
>> > Indeed, the problem does not happen any more with this patch applied to
>> > 5.0.7. Thanks!
>>
>> Could you please pick up following patches for 5.0.y?
>> Fix tested by Frederik:
>>
>> b8e204006340b7aaf32bd2b9806c692f6e0cb38a
>> netfilter: nft_compat: use .release_ops and remove list of extension
>>
>> Two followup-ups:
>> 3f3a390dbd59d236f62cff8e8b20355ef7069e3d
>> netfilter: nf_tables: use-after-free in dynamic operations
>>
>> b25a31bf0ca091aa8bdb9ab329b0226257568bbe
>> netfilter: nf_tables: add missing ->release_ops() in error path of newrule()
>>
>> These are clean cherry-picks.
>
>Oh, clash :-)

I've queued all 3 for 5.0, thanks!

--
Thanks,
Sasha

      reply	other threads:[~2019-04-09 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <306bc8c0e81422a73ccfcd0ac3ea2d79fc1df0b0.camel@ai.vub.ac.be>
     [not found] ` <20190408201909.6mcgobkdnswyikfv@breakpoint.cc>
     [not found]   ` <f90ffd6e6f0ebd1f9e99a3d01f526bb92da97b2a.camel@ai.vub.ac.be>
2019-04-09 10:19     ` 5.0.7: WARNING: CPU: 1 PID: 169 at net/netfilter/nft_compat.c:82 and genreal protection fault Florian Westphal
2019-04-09 10:21       ` Pablo Neira Ayuso
2019-04-09 15:27         ` Sasha Levin [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=20190409152751.GL4689@sasha-vm \
    --to=sashal@kernel.org \
    --cc=fhimpe@ai.vub.ac.be \
    --cc=fw@strlen.de \
    --cc=pablo@netfilter.org \
    --cc=stable@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