From: Paul Moore <pmoore@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [fs] swapper/0: page allocation failure: order:0, mode:0x50
Date: Tue, 27 Jan 2015 11:13:16 -0500 [thread overview]
Message-ID: <3589184.gcKqz6adq7@sifl> (raw)
In-Reply-To: <1422341985.24875.42.camel@intel.com>
On Tuesday, January 27, 2015 02:59:45 PM Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 6aaca9bab6116a2b392e7a07b5ff209741bc248f ("fs: create proper filename
> objects using getname_kernel()")
>
> There are new kernel message as follow, that may have relationship with your
> patch.
>
> [ 4.798286] uvesafb: failed to execute /sbin/v86d
> [ 4.799010] uvesafb: make sure that the v86d helper is installed and
> executable
Why are you applying this patch to 3.16? It is currently in vfs#for-next and
not marked for -stable?
Do you see the same problem when you test linux-next? Although you may want
to wait for today's linux-next release.
--
paul moore
security @ redhat
prev parent reply other threads:[~2015-01-27 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 6:59 Huang Ying
2015-01-27 16:13 ` Paul Moore [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=3589184.gcKqz6adq7@sifl \
--to=pmoore@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@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
Powered by JetHome