From: Russell King <rmk@arm.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Matthew Wilcox <matthew@wil.cx>,
linux-arch@vger.kernel.org, ralf@linux-mips.org
Subject: Re: [PATCH] consolidate shmat usage
Date: Mon, 11 Apr 2005 21:29:34 +0100 [thread overview]
Message-ID: <20050411212934.C5070@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050407010501.1631e14f.sfr@canb.auug.org.au>; from sfr@canb.auug.org.au on Thu, Apr 07, 2005 at 01:05:01AM +1000
On Thu, Apr 07, 2005 at 01:05:01AM +1000, Stephen Rothwell wrote:
> On Tue, 5 Apr 2005 14:03:12 +0100 Matthew Wilcox <matthew@wil.cx> wrote:
> >
> > Umm. I think you've just discovered a bug in ARM and MIPS. I don't see
> > any code in glibc for handling the 4-argument version of sys_shmat.
> > Russell, Ralf, could you comment?
>
> OK, assuming that using the 4 argument version of sys_shmat as a system
> call, here is another version of the patch (not tested) for comment.
I suspect you mean "assuming that using the 4 argument version of
sys_shmat as a system call is wrong" because that seems to be what
you've implemented.
This patch converts ARM sys_shmat from the 4 arg to the 3 arg version.
I'm mostly happy with that, except for one exception - the effect of
running a glibc with sys_shmat support against an older kernel with
the 4 argument version will be inherently problematic - the system
call will appear to succeed, but not as one would expect.
Since sys_shmat was added to ARM on 2 March 2005, it means that the 4
argument version is in both 2.6.12-rc1 and 2.6.12-rc2, but not 2.6.11.
I guess that means we can fix the API now, before 2.6.12 happens. This
would mean that we don't expect the kernel API to be stable for new
features until the following non-rc release?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-04-11 20:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 4:01 [PATCH] consolidate asm/ipc.h Stephen Rothwell
2005-03-23 4:12 ` David S. Miller
2005-03-23 6:48 ` [PATCH] consolidate shmat usage Stephen Rothwell
2005-03-23 10:54 ` David Howells
2005-04-05 8:02 ` Stephen Rothwell
2005-03-23 14:51 ` Matthew Wilcox
2005-04-05 8:01 ` Stephen Rothwell
2005-04-05 13:03 ` Matthew Wilcox
2005-04-05 20:00 ` Ralf Baechle
2005-04-05 20:16 ` Russell King
2005-04-05 20:20 ` Ralf Baechle
2005-04-06 15:05 ` Stephen Rothwell
2005-04-07 5:14 ` Stephen Rothwell
2005-04-11 20:29 ` Russell King [this message]
2005-04-27 6:27 ` [PATCH] consolidate sys_shmat Stephen Rothwell
2005-04-27 12:50 ` Ralf Baechle
2005-04-27 14:36 ` Stephen Rothwell
2005-04-05 8:05 ` [PATCH] consolidate shmat usage Stephen Rothwell
2005-03-23 8:06 ` [PATCH] consolidate asm/ipc.h Andi Kleen
2005-03-24 0:30 ` Stephen Rothwell
2005-03-23 10:49 ` 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=20050411212934.C5070@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-arch@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
/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