From: Christoph Hellwig <hch@infradead.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
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 07:49:18 -0700 [thread overview]
Message-ID: <20140730144918.GA32728@infradead.org> (raw)
In-Reply-To: <20140730123933.GA7717@localhost>
On Wed, Jul 30, 2014 at 08:39:33PM +0800, Fengguang Wu wrote:
> It's from this git tree:
>
> git://people.freedesktop.org/~dvdhrm/linux fops
David, please make sure things touching VFS code go through
linux-fsdevel and the proper trees. In the current form this gets a
strong NAK.
prev parent reply other threads:[~2014-07-30 14:49 UTC|newest]
Thread overview: 4+ 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 11:14 ` Christoph Hellwig
2014-07-30 12:39 ` Fengguang Wu
2014-07-30 14:49 ` Christoph Hellwig [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=20140730144918.GA32728@infradead.org \
--to=hch@infradead.org \
--cc=dh.herrmann@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=tao.su@intel.com \
--cc=yuanhan.liu@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;
as well as URLs for NNTP newsgroup(s).