mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: don-temp5298413@isis.cs3-inc.com (Don Cohen)
To: linux-kernel@vger.kernel.org
Subject: reading /proc files larger than one buffer
Date: Sat, 28 Sep 2002 13:10:28 -0700	[thread overview]
Message-ID: <200209282010.g8SKASL01208@isis.cs3-inc.com> (raw)


If you follow the directions in Documentation/DocBook/procfs-guide.tmpl
then your file read will not work correctly unless the whole file is
read in one call.

After examining (and experimenting with) fs/proc/generic.c I now see
what you have to do: in addition to writing bytes in the page
parameter, setting eof as appropriate and returning the number of
bytes written, you also need to do:
 *start = page;
At minimum the documentation should be corrected.

Actually I think this is a bug in proc_file_read.
The problem seems to be in this code, executed after the read function:

               if (!start) {
                        /*
                         * For proc files that are less than 4k
                         */
                        start = page + *ppos;
                        n -= *ppos;
                        if (n <= 0)
                                break;
                        if (n > count)
                                n = count;
                }
 
Can anyone explain what it's supposed to do?
What does it have to do with files < 4k ?

The addition of "*start = page;" both sets start to the correct value
and avoids executing the problematic code above.
[Note: The "start" in your read function is actually the address of
the "start" in proc_file_read.]

Therefore I think that code should be

               if (!start) start=page;

The current code normally works for the first read because *ppos is 0.
Otherwise:
- start is given the wrong value (should be page)
- n is the number of bytes read, and it makes no sense to reduce that
 by ppos, which is the file position at which you were supposed to
 start reading.  

The behavior I saw was that on the second buffer count and ppos were 
both 512 (asked to read bytes 512-1023).  My function returned 512,
so n was set to 0, which was then interpreted as eof.

Please cc me on replies.

             reply	other threads:[~2002-09-28 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-28 20:10 Don Cohen [this message]
2002-09-28 20:31 ` Jeff Garzik
2002-09-28 21:05   ` Don Cohen

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=200209282010.g8SKASL01208@isis.cs3-inc.com \
    --to=don-temp5298413@isis.cs3-inc.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®