From: George Beshers <gbeshers@sgi.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevd on very large systems: again
Date: Thu, 03 May 2007 19:49:18 +0000 [thread overview]
Message-ID: <463A3CBE.7050408@sgi.com> (raw)
In-Reply-To: <4637D051.7060103@sgi.com>
Yes your right --- I am guilty of not reading the source
in sufficient detail.
The patch you proposed works fine, may it appear soon :-).
George
Kay Sievers wrote:
> On Wed, 2007-05-02 at 17:26 -0400, George Beshers wrote:
>
>
>
> Looking at the seq_file code, calling lseek() causes the buffer to be
> repopulated:
> seq_lseek() -> traverse() -> m->op->show()
> while show() is the method of the "stat" file that fills the buffer.
>
> A simple read() should not do that, and just copy the content (up to
> 128kB) of the kernel seq_file file buffer to the user-process:
> seq_read() -> copy_to_user(buf, m->buf + m->from, n)
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-05-03 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 23:42 udevd on very large systems: again George Beshers
2007-05-02 19:37 ` Kay Sievers
2007-05-02 21:11 ` Kay Sievers
2007-05-02 21:26 ` George Beshers
2007-05-02 21:39 ` George Beshers
2007-05-02 23:42 ` Kay Sievers
2007-05-02 23:51 ` Kay Sievers
2007-05-03 19:49 ` George Beshers [this message]
2007-05-03 21:12 ` Kay Sievers
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=463A3CBE.7050408@sgi.com \
--to=gbeshers@sgi.com \
--cc=linux-hotplug@vger.kernel.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.