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:   Tue, 7 Apr 2020 04:13:18 +0100
From:   Al Viro <viro@zeniv.linux.org.uk>
To:     Levi <ppbuk5246@gmail.com>
Cc:     davem@davemloft.net, kuba@kernel.org, gnault@redhat.com,
        nicolas.dichtel@6wind.com, edumazet@google.com,
        lirongqing@baidu.com, tglx@linutronix.de, johannes.berg@intel.com,
        dhowells@redhat.com, daniel@iogearbox.net,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        netdev@vger.kernel.org
Subject: Re: [PATCH] netns: dangling pointer on netns bind mount point.
Message-ID: <20200407031318.GY23230@ZenIV.linux.org.uk>
References: <20200407023512.GA25005@ubuntu>
 <20200407030504.GX23230@ZenIV.linux.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200407030504.GX23230@ZenIV.linux.org.uk>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Apr 07, 2020 at 04:05:04AM +0100, Al Viro wrote:

> Could you post a reproducer, preferably one that would trigger an oops
> on mainline?

BTW, just to make sure - are we talking about analysis of existing
oops, or is it "never seen it happen, but looks like it should be
triggerable" kind of situation?