From: Rusty Russell <rusty@rustcorp.com.au>
To: nagendra_tomar@adaptec.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG in fs/proc/generic.c:proc_file_read
Date: Sun, 10 Aug 2003 15:07:42 +1000 [thread overview]
Message-ID: <20030811205149.E1AE92C37D@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 07 Aug 2003 23:59:00 +0530." <Pine.LNX.4.44.0308072346020.3811-100000@localhost.localdomain>
In message <Pine.LNX.4.44.0308072346020.3811-100000@localhost.localdomain> you write:
> In short:
> The hack used to be able to read proc files larger than 4k, breaks if the
> caller does lseek() after read()
Hmm, my more(1) does this too. What a PITA. less(1) does not.
I've never noticed it before, though. I certainly didn't notice it
when I implemented the hack.
Of course, converting to seq_file is probably the nicest solution
these days.
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
prev parent reply other threads:[~2003-08-11 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 18:29 Nagendra Singh Tomar
2003-08-08 6:53 ` Zwane Mwaikambo
2003-08-08 6:54 ` Zwane Mwaikambo
2003-08-10 5:07 ` Rusty Russell [this message]
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=20030811205149.E1AE92C37D@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=nagendra_tomar@adaptec.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 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®