From: Christoph Hellwig <hch@infradead.org>
To: lkp@lists.01.org
Subject: Re: [fs] BUG: unable to handle kernel NULL pointer dereference at 00000104
Date: Wed, 30 Jul 2014 04:14:20 -0700 [thread overview]
Message-ID: <20140730111420.GA759@infradead.org> (raw)
In-Reply-To: <20140730041235.GJ16537@localhost>
[-- Attachment #1: Type: text/plain, Size: 271 bytes --]
On Wed, Jul 30, 2014 at 12:12:35PM +0800, Fengguang Wu wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
Where is this coming from? Bloating struct file for device specific
stuff really isn't acceptable anyway.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: David Herrmann <dh.herrmann@gmail.com>,
Jet Chen <jet.chen@intel.com>, Su Tao <tao.su@intel.com>,
Yuanhan Liu <yuanhan.liu@intel.com>, LKP <lkp@01.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [fs] BUG: unable to handle kernel NULL pointer dereference at 00000104
Date: Wed, 30 Jul 2014 04:14:20 -0700 [thread overview]
Message-ID: <20140730111420.GA759@infradead.org> (raw)
In-Reply-To: <20140730041235.GJ16537@localhost>
On Wed, Jul 30, 2014 at 12:12:35PM +0800, Fengguang Wu wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
Where is this coming from? Bloating struct file for device specific
stuff really isn't acceptable anyway.
next prev parent reply other threads:[~2014-07-30 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 4:12 [fs] BUG: unable to handle kernel NULL pointer dereference at 00000104 Fengguang Wu
2014-07-30 4:12 ` Fengguang Wu
2014-07-30 11:14 ` Christoph Hellwig [this message]
2014-07-30 11:14 ` Christoph Hellwig
2014-07-30 12:39 ` Fengguang Wu
2014-07-30 12:39 ` Fengguang Wu
2014-07-30 14:49 ` Christoph Hellwig
2014-07-30 14:49 ` Christoph Hellwig
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=20140730111420.GA759@infradead.org \
--to=hch@infradead.org \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.