From: Al Viro <viro@ZenIV.linux.org.uk>
To: Am??rico Wang <xiyou.wangcong@gmail.com>
Cc: Toralf F??rster <toralf.foerster@gmx.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: Re: kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null'
Date: Fri, 29 Jan 2010 13:38:16 +0000 [thread overview]
Message-ID: <20100129133816.GQ19799@ZenIV.linux.org.uk> (raw)
In-Reply-To: <2375c9f91001272051x3d2e89r24133c42f52082ea@mail.gmail.com>
On Thu, Jan 28, 2010 at 12:51:02PM +0800, Am??rico Wang wrote:
> 2010/1/22 Toralf F??rster <toralf.foerster@gmx.de>:
> > I was inspired by http://article.gmane.org/gmane.linux.kernel/941115 .
> >
> > Running the command (se subject) as a normal user at a 2.6.32.4 kernel
> > gives this in /var/log/messages:
> >
> > 2010-01-21T20:11:39.171+01:00 n22 kernel: head: page allocation failure. order:9, mode:0xd0
>
>
> Hmm, it is suspecious that we need 2^9 pages for seq_file...
Something's using single_open() and obscene amounts of output; should
switch to real iterator... Which file it is?
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Am??rico Wang <xiyou.wangcong@gmail.com>
Cc: Toralf F??rster <toralf.foerster@gmx.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: Re: kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null'
Date: Fri, 29 Jan 2010 13:38:16 +0000 [thread overview]
Message-ID: <20100129133816.GQ19799@ZenIV.linux.org.uk> (raw)
In-Reply-To: <2375c9f91001272051x3d2e89r24133c42f52082ea@mail.gmail.com>
On Thu, Jan 28, 2010 at 12:51:02PM +0800, Am??rico Wang wrote:
> 2010/1/22 Toralf F??rster <toralf.foerster@gmx.de>:
> > I was inspired by http://article.gmane.org/gmane.linux.kernel/941115 .
> >
> > Running the command (se subject) as a normal user at a 2.6.32.4 kernel
> > gives this in /var/log/messages:
> >
> > 2010-01-21T20:11:39.171+01:00 n22 kernel: head: page allocation failure. order:9, mode:0xd0
>
>
> Hmm, it is suspecious that we need 2^9 pages for seq_file...
Something's using single_open() and obscene amounts of output; should
switch to real iterator... Which file it is?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-01-29 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 19:16 kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null' Toralf Förster
2010-01-21 20:35 ` Alexey Dobriyan
2010-01-21 21:19 ` Toralf Förster
2010-01-26 13:17 ` Jiri Kosina
2010-01-26 13:17 ` Jiri Kosina
2010-01-28 1:39 ` Zhang Rui
2010-01-28 1:39 ` Zhang Rui
2010-01-29 13:45 ` Al Viro
2010-01-28 4:51 ` Américo Wang
2010-01-28 4:51 ` Américo Wang
2010-01-29 13:38 ` Al Viro [this message]
2010-01-29 13:38 ` Al Viro
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=20100129133816.GQ19799@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=toralf.foerster@gmx.de \
--cc=xiyou.wangcong@gmail.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 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.