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
Date: Fri, 13 Nov 2015 07:08:15 -0600 [thread overview]
Message-ID: <20151113130815.GA136440@ubuntu-hedt> (raw)
In-Reply-To: <20151113080632.GA7889@infradead.org>
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
prev parent reply other threads:[~2015-11-13 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 6:24 [lkp] [loop] 1d5ab0e98c: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 kernel test robot
2015-11-13 8:06 ` Christoph Hellwig
2015-11-13 13:08 ` Seth Forshee [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=20151113130815.GA136440@ubuntu-hedt \
--to=seth.forshee@canonical.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@linux.intel.com \
/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