From: ebiederm@xmission.com (Eric W. Biederman)
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>, LKP <lkp@01.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [vfs mnt_set_mountpoint] invalid opcode: 0000 [#1] DEBUG_PAGEALLOC
Date: Tue, 19 Aug 2014 20:52:06 -0700 [thread overview]
Message-ID: <878umju8bd.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20140819114738.GB18960@localhost> (Fengguang Wu's message of "Tue, 19 Aug 2014 19:47:38 +0800")
Fengguang Wu <fengguang.wu@intel.com> writes:
> // Fix email address for Eric and add another oops message.
> // This commit seem to generate all kinds of oops.
My apologies about the email. This patch has taken so long to get
somewhere that email address has bit-rotted.
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 89f7ca1af15bdfe7a6aed343032a84af2a69f736
> Author: Eric W. Biederman <ebiederman@twitter.com>
> AuthorDate: Sun Sep 22 19:37:01 2013 -0700
> Commit: Al Viro <viro@zeniv.linux.org.uk>
> CommitDate: Sun Aug 17 07:02:00 2014 -0400
>
> vfs: Keep a list of mounts on a mount point
>
> To spot any possible problems call BUG if a mountpoint
> is put when it's list of mounts is not empty.
>
> AV: use hlist instead of list_head
Hugh Dickins has a fix for an unitialized field he has sent to Stephen
Rothwell.
> Reviewed-by: Miklos Szeredi <miklos@szeredi.hu>
> Signed-off-by: Eric W. Biederman <ebiederman@twitter.com>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
I expect Al will sort things out when he get home from kernel summit.
Eric
prev parent reply other threads:[~2014-08-20 3:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 11:40 [vfs mnt_set_mountpoint] BUG: unable to handle kernel paging request at 5a5a5a5e Fengguang Wu
2014-08-19 11:47 ` [vfs mnt_set_mountpoint] invalid opcode: 0000 [#1] DEBUG_PAGEALLOC Fengguang Wu
2014-08-20 3:52 ` Eric W. Biederman [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=878umju8bd.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=fengguang.wu@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=viro@zeniv.linux.org.uk \
/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