From: Gerard J Snitselaar <snits@snitselaar.org>
To: Amnon Shiloh <amnons@cs.huji.ac.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug report: mem_write
Date: Thu, 24 Aug 2006 03:35:29 -0700 [thread overview]
Message-ID: <20060824103529.GA19854@snitselaar.org> (raw)
In-Reply-To: <E1GGAWv-0001uP-Mu@lucifer.cs.huji.ac.il>
On 0, Amnon Shiloh <amnons@cs.huji.ac.il> wrote:
> Hi,
>
> Alright, I know that "mem_write" (fs/proc/base.c) is a "security hazard",
> but I need to use it anyway (as super-user only), and find it broken,
> somewhere between Linux-2.6.17 and Linux-2.6.18-rc4.
>
> The point is that in the beginning of the routine, "copied" is set to 0,
> but it is no good because in lines 805 and 812 it is set to other values.
> Finally, the routine returns as if it copied 12 (=ENOMEM) bytes less than
> it actually did.
>
Is there any reason copied shouldn't get set to 0 just prior to entering
the while loop?
> Amnon.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2006-08-24 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 8:25 bug report: mem_write Amnon Shiloh
2006-08-24 10:35 ` Gerard J Snitselaar [this message]
2006-08-24 14:00 ` [2.6.18 patch] fix mem_write return value (was: Re: bug report: mem_write) Frederik Deweerdt
2006-08-24 16:33 ` Eric W. Biederman
2006-08-24 22:07 ` Frederik Deweerdt
2006-08-25 1:05 ` Amnon Shiloh
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=20060824103529.GA19854@snitselaar.org \
--to=snits@snitselaar.org \
--cc=amnons@cs.huji.ac.il \
--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