From: Mike Frysinger <vapier.adi@gmail.com>
To: Johannes Weiner <jw@emlix.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
Russell King <rmk@arm.linux.org.uk>,
Bryan Wu <cooloney@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Paul Mundt <lethal@linux-sh.org>, Greg Ungerer <gerg@uclinux.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch -v2] flat: fix data sections alignment
Date: Wed, 4 Mar 2009 16:48:04 -0500 [thread overview]
Message-ID: <8bd0f97a0903041348i2c88343fvbc7a1b6d428c7e7a@mail.gmail.com> (raw)
In-Reply-To: <E1LerUo-0000NE-Q3@mailer.emlix.com>
On Wed, Mar 4, 2009 at 08:51, Johannes Weiner wrote:
> --- a/fs/binfmt_flat.c
> +++ b/fs/binfmt_flat.c
> +#ifdef ARCH_SLAB_MINALIGN
> +#define FLAT_DATA_ALIGN (ARCH_SLAB_MINALIGN)
> +#else
> +#define FLAT_DATA_ALIGN (sizeof(void *))
> +#endif
> ...
> + sp = (unsigned long *) ((unsigned long)sp & -FLAT_DATA_ALIGN);
> ...
> - datapos = realdatastart + MAX_SHARED_LIBS * sizeof(unsigned long);
> + datapos = ALIGN(realdatastart + MAX_SHARED_LIBS * sizeof(unsigned long),
> + FLAT_DATA_ALIGN);
> ...
> - datapos = realdatastart + MAX_SHARED_LIBS * sizeof(unsigned long);
> + datapos = ALIGN(realdatastart + MAX_SHARED_LIBS * sizeof(unsigned long),
> + FLAT_DATA_ALIGN);
why not make FLAT_DATA_ALIGN into a macro ? then it'd naturally
follow the existing ALIGN() behavior.
> - sp = (unsigned long *) ((-(unsigned long)sizeof(char *))&(unsigned long) p);
> -
> - sp -= envc+1;
> - envp = sp;
> - sp -= argc+1;
> - argv = sp;
> + sp = (unsigned long *)p;
> + sp -= (envc + argc + 2) + 1 + (flat_argvp_envp_on_stack() ? 2 : 0);
> + sp = (unsigned long *) ((unsigned long)sp & -FLAT_DATA_ALIGN);
> + argv = sp + 1 + (flat_argvp_envp_on_stack() ? 2 : 0);
> + envp = argv + (argc + 1);
can this be cleaned up a bit so that the argv/envp assignment happens
by using sp before aligning sp ? that would be defensive coding wrt
preventing sp adjustment falling out of line with argv initialization,
and cut down on duplicated code.
> - put_user(argc,--sp);
> + put_user(argc,sp);
might as well fix the style issues here while you're changing code ...
stick a space after the comma
> @@ -854,7 +861,7 @@ static int load_flat_binary(struct linux
> stack_len = TOP_OF_ARGS - bprm->p; /* the strings */
> stack_len += (bprm->argc + 1) * sizeof(char *); /* the argv array */
> stack_len += (bprm->envc + 1) * sizeof(char *); /* the envp array */
> -
> + stack_len += FLAT_DATA_ALIGN;
this seems weird. alignment is for aligning data, not padding it out
some value ...
-mike
next prev parent reply other threads:[~2009-03-04 21:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 13:51 Johannes Weiner
2009-03-04 18:04 ` Mike Frysinger
2009-03-04 19:33 ` Johannes Weiner
2009-03-04 20:00 ` Mike Frysinger
2009-03-04 20:13 ` Johannes Weiner
2009-03-04 21:48 ` Mike Frysinger [this message]
2009-03-05 10:53 ` Johannes Weiner
2009-03-05 16:40 ` Oskar Schirmer
2009-03-05 8:43 ` Paul Mundt
2009-05-29 0:01 ` John Williams
2009-05-29 3:58 ` Paul Mundt
2009-05-29 5:11 ` John Williams
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=8bd0f97a0903041348i2c88343fvbc7a1b6d428c7e7a@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cooloney@kernel.org \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=jw@emlix.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.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®