From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>, Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT] /proc/uptime fix
Date: Mon, 3 Nov 2008 10:14:16 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0811031000020.3459@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20081103145023.GA3986@x200.localdomain>
On Mon, 3 Nov 2008, Alexey Dobriyan wrote:
>
> Alexey Dobriyan (1):
> proc: revert /proc/uptime to ->read_proc hook
Ok, pulled, but it's a bit sad.
Al: the commit is 6c87df37dcb9c6c33923707fa5191e0a65874d60, and the
message explains it all:
Turned out some VMware userspace does pread(2) on /proc/uptime, but
seqfiles currently don't allow pread() resulting in -ESPIPE.
Seqfiles in theory can do pread(), but this can be a long story,
so revert to ->read_proc until then.
and I bet that the pread() usage is just with a constant loff_t of 0, and
just there to avoid a simple case of "lseek+read".
I wonder how hard it is to make seqfiles support pread. Maybe it's
something as trivial as just flushing the buffer whenever 'pos' doesn't
match f_pos?
ie something like the following (TOTALLY UNTESTED!)
I may be way off base here, Al needs to whack some sense into this.
Linus
---
fs/seq_file.c | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/fs/seq_file.c b/fs/seq_file.c
index eba2eab..eb95ec9 100644
--- a/fs/seq_file.c
+++ b/fs/seq_file.c
@@ -48,8 +48,8 @@ int seq_open(struct file *file, const struct seq_operations *op)
*/
file->f_version = 0;
- /* SEQ files support lseek, but not pread/pwrite */
- file->f_mode &= ~(FMODE_PREAD | FMODE_PWRITE);
+ /* SEQ files support lseek, but not pwrite */
+ file->f_mode &= ~(FMODE_PWRITE);
return 0;
}
EXPORT_SYMBOL(seq_open);
@@ -91,6 +91,8 @@ ssize_t seq_read(struct file *file, char __user *buf, size_t size, loff_t *ppos)
if (!m->buf)
goto Enomem;
}
+ if (pos != file->f_pos)
+ m->count = 0;
/* if not empty - flush it first */
if (m->count) {
n = min(m->count, size);
@@ -175,6 +177,8 @@ Done:
else
*ppos += copied;
file->f_version = m->version;
+ if (pos != file->f_pos)
+ m->count = 0;
mutex_unlock(&m->lock);
return copied;
Enomem:
next prev parent reply other threads:[~2008-11-03 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 14:50 Alexey Dobriyan
2008-11-03 18:14 ` Linus Torvalds [this message]
2008-11-03 20:25 ` Alexey Dobriyan
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=alpine.LFD.2.00.0811031000020.3459@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=adobriyan@gmail.com \
--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 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®