From: Christoph Hellwig <hch@infradead.org>
To: Eric Paris <eparis@redhat.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Kay Sievers <kay.sievers@suse.de>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: udev loops eating 100 % CPU [mmotm 2010-05-21-16-05]
Date: Tue, 25 May 2010 08:28:27 -0400 [thread overview]
Message-ID: <20100525122827.GA21596@infradead.org> (raw)
In-Reply-To: <1274790132.2810.65.camel@localhost>
On Tue, May 25, 2010 at 08:22:12AM -0400, Eric Paris wrote:
> On Tue, 2010-05-25 at 14:12 +0200, Jiri Slaby wrote:
>
> thanks for the report, it's a known problem:
>
> http://lkml.org/lkml/2010/5/22/150
>
> Not sure yet how we are going to fix it. You can either just revert or
> you could run this patch which I am using on my box. Not sure which Al
> is going to want to do......
>
> commit 6e066d6c0c70e2032b5fd2b5c6375e66a0f547f9
> Author: Eric Paris <eparis@redhat.com>
> Date: Tue May 25 07:55:46 2010 -0400
>
> anon_inode/ioctl: push FIONREAD for anon_inode to the file handler
>
> FIONREAD for all S_IFREG files is handled by file_ioctl but the
> anon_inode_inode is a magic special beast since the inode is shared between
> lots of users. Thus ioctl calls on anon_inode_inode needs to go through
> vfs_inode() instead of trying to shortcut some calls through file_ioctl().
>
> Signed-off-by: Eric Paris <eparis@redhat.com>
This one is defintively far too disgusting.
next prev parent reply other threads:[~2010-05-25 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 12:12 udev loops eating 100 % CPU [mmotm 2010-05-21-16-05] Jiri Slaby
2010-05-25 12:22 ` Eric Paris
2010-05-25 12:28 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-26 9:18 Sedat Dilek
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=20100525122827.GA21596@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=jirislaby@gmail.com \
--cc=kay.sievers@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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.