From: ebiederm@xmission.com (Eric W. Biederman)
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@osdl.org>, Michael Tokarev <mjt@tls.msk.ru>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bug reading /proc/sys/kernel/*: only first byte read.
Date: Tue, 30 Jan 2007 08:07:51 -0700 [thread overview]
Message-ID: <m1y7nkh7so.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070130140015.GA123@tv-sign.ru> (Oleg Nesterov's message of "Tue, 30 Jan 2007 17:00:15 +0300")
Oleg Nesterov <oleg@tv-sign.ru> writes:
> On 01/30, Oleg Nesterov wrote:
>>
>> On 01/30, Andrew Morton wrote:
>> >
>> > + if (len + pos < maxlen) {
>> ^^^^^^^^^^^^^^^^^^^^^^^
>> Shouldn't this be
>> if (len < *lenp)
>>
>> ?
>
> On the other hand. If we may assume that original code was correct,
> we can make a simpler patch?
I think there is an issue worth fixing her.
However as far as I can tell the code has this limitation
deliberately for simplicity.
Getting the string side of this fixed even by itself is
worthwhile, although it might be worth teach people
about sys_uname and /bin/uname. It seems is the biggest thing
people look at /proc/sys/ for...
For the non-string data the only way we can do this is to
generate it into a temporary buffer and the read out the
part of the buffer the user is requesting. Isn't there
something in seq_file that will do this?
On the other side I'm fairly certain we can't support
short writes to magic sysctl files on the write side of things.
I do have to say I like Oleg short version of this patch.
Eric
next prev parent reply other threads:[~2007-01-30 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 12:43 Michael Tokarev
2007-01-30 10:24 ` Andrew Morton
2007-01-30 13:25 ` Oleg Nesterov
2007-01-30 14:00 ` Oleg Nesterov
2007-01-30 15:07 ` Eric W. Biederman [this message]
2007-01-30 15:57 ` Michael Tokarev
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=m1y7nkh7so.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=oleg@tv-sign.ru \
/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
Powered by JetHome