From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: David Howells <dhowells@redhat.com>,
torvalds@osdl.org, bernds_cb1@t-online.de, sam@ravnborg.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] FDPIC: Add coredump capability for the ELF-FDPIC binfmt [try #3]
Date: Thu, 06 Jul 2006 19:38:49 +0100 [thread overview]
Message-ID: <26133.1152211129@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20060706105223.97b9a531.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
> llseek takes a loff_t and file->f_pos is loff_t. I guess it's a bit moot
> on such a CPU. Was it deliberate?
It compiles with no error and no warning, so I haven't noticed. This is as
binfmt_elf.c is, I believe, so that is probably wrong too.
> (how come the kernel doesn't have a SEEK_SET #define?)
I don't know. It probably should.
> Three callsites - seems too large to inline.
Again taken from binfmt_elf.c, although I added the debugging stuff. It
shouldn't matter as the compiler will make its own decision (or does "inline"
get #defined to always-inline nowadays?).
> Which seems reasonable to me. I'll steal it from them.
Okay.
> Embedding returns and gotos in macros is evil. For new code it's worth
> doing it vaguely tastefully.
Again, stolen verbatim from binfmt_elf.c. I'd prefer to keep it comparable by
the blink-comparator method if possible.
> Does this need locking?
It shouldn't do; we own our own vma chain, and because we're part of exec, we
have a fresh mm_struct to play with. The VMAs themselves aren't allowed to
change, not even on NOMMU.
David
next prev parent reply other threads:[~2006-07-06 18:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 12:47 [PATCH 0/6] Fix FRV, ELF-FDPIC and NOMMU stuff [try #3] David Howells
2006-07-06 12:47 ` [PATCH 1/6] FDPIC: Fix FDPIC compile errors " David Howells
2006-07-06 13:40 ` David Woodhouse
2006-07-07 9:41 ` David Howells
2006-07-06 12:47 ` [PATCH 2/6] FRV: Fix FRV arch " David Howells
2006-07-06 17:31 ` Andrew Morton
2006-07-06 18:25 ` David Howells
2006-07-06 18:39 ` Andrew Morton
2006-07-06 19:02 ` David Howells
2006-07-06 17:36 ` Andrew Morton
2006-07-06 18:29 ` David Howells
2006-07-06 12:47 ` [PATCH 3/6] NOMMU: Fix execution off of ramfs with mmap() " David Howells
2006-07-06 12:47 ` [PATCH 4/6] FDPIC: Adjust the ELF-FDPIC driver to conform more to the CodingStyle " David Howells
2006-07-06 12:47 ` [PATCH 5/6] FDPIC: Add coredump capability for the ELF-FDPIC binfmt " David Howells
2006-07-06 17:52 ` Andrew Morton
2006-07-06 18:38 ` David Howells [this message]
2006-07-06 23:27 ` Andrew Morton
2006-07-07 9:46 ` David Howells
2006-07-07 10:54 ` David Howells
2006-07-07 11:00 ` David Howells
2006-07-07 11:12 ` Andrew Morton
2006-07-07 9:54 ` David Howells
2006-07-07 10:20 ` Andrew Morton
2006-07-07 10:34 ` David Howells
2006-07-06 12:47 ` [PATCH 6/6] FRV: Introduce asm-offsets for FRV arch " David Howells
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=26133.1152211129@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=bernds_cb1@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.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