Date: Fri, 13 Nov 2015 07:08:15 -0600
From: Seth Forshee <seth.forshee@canonical.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: kernel test robot <ying.huang@linux.intel.com>, lkp@01.org,
        LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lkp] [loop] 1d5ab0e98c: BUG: unable to handle kernel NULL
 pointer dereference at 0000000000000008
Message-ID: <20151113130815.GA136440@ubuntu-hedt>
References: <87oaeyl8m5.fsf@yhuang-dev.intel.com>
 <20151113080632.GA7889@infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20151113080632.GA7889@infradead.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 757
Lines: 16

On Fri, Nov 13, 2015 at 12:06:32AM -0800, Christoph Hellwig wrote:
> Err, where the heck is a loop file system coming from?

I've been working on code to let some regular filesystems be mounted in
user namespace containers, and loopfs is an idea I'm playing with to
allow those containers to allocate and use loop devices (since they
can't mknod and devtmpfs isn't namepace aware). I'm not sure how I ended
up with the kbuild bot testing this code though, my tree doesn't feed
into linux-next or anything.

Seth
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/