From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753965AbdKJTQ5 (ORCPT <rfc822;w@1wt.eu>);
        Fri, 10 Nov 2017 14:16:57 -0500
Received: from mail-pg0-f48.google.com ([74.125.83.48]:52108 "EHLO
        mail-pg0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753689AbdKJTQz (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 10 Nov 2017 14:16:55 -0500
X-Google-Smtp-Source: AGs4zMaLSgzZ5djQ2Oc4b0ykFJrVWI8m7CvJCPhfGkzX138uoi8aS0OeZXDkwfQ/2t/cGO/7eS0hK2nNX/+dR2IAOoI=
MIME-Version: 1.0
In-Reply-To: <CAEeGbKME2ngYXZOFbPxjCkwu-hsooZZ4J3iHapgAZrFm3+AsMA@mail.gmail.com>
References: <CAM_iQpXa+orUek72UQ7OM9NiP0uvj_KKBunX7=SSNVrB+i_yEA@mail.gmail.com>
 <CA+55aFwVgYmfe6fFHxEnoAjKrFsDC357PmQ+qE2U2E7wDhgG7Q@mail.gmail.com>
 <CA+55aFzFgomi=xWUxkGxLyU0n1gWQQ+SzvqHUjnAi-8aRPB7Bg@mail.gmail.com>
 <CAM_iQpXEHsc+Yu9UDMmKBgx+fdF9ZNHLrmNrtZ5L0ypFgwr-Zw@mail.gmail.com>
 <CA+55aFypnFvxdZbaqwyZmV_1QzgHE92zu7xsMqAwJ+u-vR=01g@mail.gmail.com>
 <CAM_iQpWFGsXdC2qHfMLHy_0y3jEZxToxkSWYhj2_uQpTurPvdQ@mail.gmail.com> <CAEeGbKME2ngYXZOFbPxjCkwu-hsooZZ4J3iHapgAZrFm3+AsMA@mail.gmail.com>
From: Cong Wang <xiyou.wangcong@gmail.com>
Date: Fri, 10 Nov 2017 11:16:34 -0800
Message-ID: <CAM_iQpVKwMHkAQ_vOfNJnxWzf1EQC-QgiWOGZNjMjjuEuCAhhw@mail.gmail.com>
Subject: Re: Kernel crash in free_pipe_info()
To: Simon Brewer <sbrunau@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
        Al Viro <viro@zeniv.linux.org.uk>,
        Andrew Morton <akpm@linux-foundation.org>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi, Simon

On Thu, Nov 9, 2017 at 10:07 PM, Simon Brewer <sbrunau@gmail.com> wrote:
> This looks familiar...
>
> https://github.com/moby/moby/issues/34472
>
> From the bug report:
> "In particular, it looks like either docker-containerd or
> docker-containerd-shim (the log is cut off) has a pipe open that is
> causing a kernel BUG when attempting to kill the process. Fun times."

Yeah, looks nearly the same.

If you know how to reproduce it reliably, that would help a lot.

Also, as suggested by Linus, turning on slub debug would also help.
Or enable kdump to get a core dump.

Thanks!