From: Ricardo Galli <gallir@uib.es>
To: linux-kernel@vger.kernel.org
Subject: BUG: cpufreq_proc_read give prematures eof for /proc/cpufreq (in 2.4.x-ac and 2.5)
Date: Mon, 5 May 2003 02:43:01 +0200 [thread overview]
Message-ID: <200305050243.01922.gallir@uib.es> (raw)
If a process reads from /proc/cpufreq with a small buffer, i.e. count <
len, the function return always eof because len is always zero if the
offset is > 0:
static int cpufreq_proc_read (
char *page,
...
{
char *p = page;
...
if (off != 0)
goto end;
...
end:
len = (p - page);
where p = page.
Is this bug intentional to avoid overload or it's really a mistake?
PS: there is an obvious fix, I didn't attached to avoid you flaming me.
:-)
--
ricardo galli GPG id C8114D34
reply other threads:[~2003-05-05 0:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200305050243.01922.gallir@uib.es \
--to=gallir@uib.es \
--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®