From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH]bisected:fs:anon_inodes.c one processor core reads full throttle.
Date: Tue, 25 May 2010 07:24:36 -0700 [thread overview]
Message-ID: <4BFBDDA4.6040802@gmail.com> (raw)
In-Reply-To: <1274795592.2810.67.camel@localhost>
On 05/25/2010 06:53 AM, Eric Paris wrote:
> On Mon, 2010-05-24 at 19:54 -0700, Justin P. Mattock wrote:
>
>> I have no idea why this is doing this., but when doing
>> watch cat /proc/cpuinfo I see one of my cores reading
>> full throttle.
>>
> Check out:
> http://lkml.org/lkml/2010/5/22/150
> and
> http://lkml.org/lkml/2010/5/25/159
>
> Sorry, but this patch isn't right (S_IFMNT shouldn't be used like that)
>
> -Eric
>
>
>
ahh.. so udev is getting crapped out..
alright I'll revert this for now..
Justin P. Mattock
prev parent reply other threads:[~2010-05-25 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 2:54 [PATCH]bisected:fs:anon_inodes.c one processor core reads full throttle Justin P. Mattock
2010-05-25 13:53 ` Eric Paris
2010-05-25 14:24 ` Justin P. Mattock [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=4BFBDDA4.6040802@gmail.com \
--to=justinmattock@gmail.com \
--cc=eparis@redhat.com \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).