From: Coywolf Qi Hunt <coywolf@greatcn.org>
To: David Weinehall <david@southpole.se>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: [PATCH 2.0.40] Fix comment error of prepare_binprm() in exec.c
Date: Wed, 03 Mar 2004 21:38:09 +0800 [thread overview]
Message-ID: <4045DFC1.2010904@greatcn.org> (raw)
In-Reply-To: <20040128033755.GC16675@khan.acc.umu.se>
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
David Weinehall wrote:
> My aim for 2.0.41 is to make it a cleanup-release; remove warnings, tidy
> up a little source-code mess, kill dead code, fix typos etc.
>
>
> Regards: David Weinehall
Hello, David
In the comment of prepare_binprm() in fs/exec.c, 512 bytes should be 128
bytes.
Coywolf
--
Coywolf Qi Hunt
Admin of http://GreatCN.org and http://LoveCN.org
[-- Attachment #2: patch-cy0403030-2.0.40 --]
[-- Type: text/plain, Size: 364 bytes --]
--- linux-2.0.40/fs/exec.c 2004-02-27 11:48:20.000000000 +0800
+++ linux-2.0.40-cy/fs/exec.c 2004-03-03 21:14:28.000000000 +0800
@@ -528,7 +528,7 @@
/*
* Fill the binprm structure from the inode.
- * Check permissions, then read the first 512 bytes
+ * Check permissions, then read the first 128 bytes
*/
int prepare_binprm(struct linux_binprm *bprm)
{
next prev parent reply other threads:[~2004-03-03 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 19:23 [PATCH 2.0.39] put_last_free() defined, but not used Coywolf Qi Hunt
2004-01-25 22:29 ` David Weinehall
2004-01-25 23:43 ` Jens Axboe
2004-01-26 2:01 ` David Weinehall
2004-01-27 17:10 ` [2.0.40-rc8] Works well Markus Hästbacka
2004-01-27 17:38 ` David Weinehall
2004-01-28 3:28 ` Coywolf Qi Hunt
2004-01-28 3:37 ` David Weinehall
2004-01-28 6:13 ` Markus Hästbacka
2004-01-28 15:17 ` David Weinehall
2004-01-28 23:37 ` Markus Hästbacka
2004-01-28 23:50 ` David Weinehall
2004-02-23 6:28 ` about 2.0 cleanup or adaption Coywolf Qi Hunt
2004-03-03 13:38 ` Coywolf Qi Hunt [this message]
2004-03-03 13:51 ` [PATCH 2.0.40] Fix comment error of prepare_binprm() in exec.c David Weinehall
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=4045DFC1.2010904@greatcn.org \
--to=coywolf@greatcn.org \
--cc=david@southpole.se \
--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