From: Al Viro <viro@ZenIV.linux.org.uk>
To: lkp@lists.01.org
Subject: Re: [vfs] BUG: sleeping function called from invalid context at arch/x86/mm/fault.c:1191
Date: Thu, 19 Nov 2015 11:39:47 +0000 [thread overview]
Message-ID: <20151119113947.GH22011@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20151119094214.GB18875@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
On Thu, Nov 19, 2015 at 05:42:14PM +0800, Fengguang Wu wrote:
> Hi Al,
>
> Here is another bisect result.
Umm... Looks like bisect hazard - the chunk that should've gone into
ebd0bb376 went into 31d49afa22 instead. Namely, this
- struct pid_namespace *ns = dentry->d_sb->s_fs_info;
+ struct pid_namespace *ns = inode->i_sb->s_fs_info;
in proc_self_get_link()... And similar in proc_thread_self_get_link(),
apparently.
Fixed (by moving these chunks into the previous commit, the final tree is
unchanged) and force-pushed...
prev parent reply other threads:[~2015-11-19 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 9:41 [vfs] BUG: unable to handle kernel NULL pointer dereference at 00000090 Fengguang Wu
2015-11-19 9:42 ` [vfs] BUG: sleeping function called from invalid context at arch/x86/mm/fault.c:1191 Fengguang Wu
2015-11-19 11:39 ` Al Viro [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=20151119113947.GH22011@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--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.