Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Sat, 9 Mar 2019 00:35:34 +0300
From:   Dmitrii Tcvetkov <demfloro@demfloro.ru>
To:     Florian Westphal <fw@strlen.de>
Cc:     netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: NULL pointer dereference in nft_set_elem_destroy()
Message-ID: <20190309003534.4f114b38@fire.localdomain>
In-Reply-To: <20190308105039.xmf3ho3nixhfnnmh@breakpoint.cc>
References: <20190308131746.5899877a@fire.localdomain>
        <20190308105039.xmf3ho3nixhfnnmh@breakpoint.cc>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, 8 Mar 2019 11:50:39 +0100
Florian Westphal <fw@strlen.de> wrote:

> Dmitrii Tcvetkov <demfloro@demfloro.ru> wrote:
> > After upgrade to 5.0 on XPS 13 9360 I get NULL pointer dereference
> > in dmesg (attached). Distro is Arch Linux, kernel is built with
> > custom config (attached), but distro kernel[1] reproduces the issue
> > on the laptop as well.
> > 
> > Bisect led me to commit f6ac858589768 (netfilter: nf_tables: unbind
> > set in rule from commit path), bisect log attached. The commit
> > doesn't revert cleanly on top of v5.0, and conflicts aren't trivial
> > for me to resolve.
> 
> Please see
> https://patchwork.ozlabs.org/patch/1053232/
> 
> this probably resolves this crash as well.

Thank you! With the patch nft loads ruleset fine.