All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Ryan Murray <rmurray@debian.org>,
	linux-mips@linux-mips.org, libc-alpha@sources.redhat.com
Subject: Re: [patch] userspace mcontext_t doesn't match what kernel returns
Date: Sun, 15 Sep 2002 15:16:13 -0400	[thread overview]
Message-ID: <20020915191613.GA21794@nevyn.them.org> (raw)
In-Reply-To: <20020915210601.A24588@linux-mips.org>

On Sun, Sep 15, 2002 at 09:06:01PM +0200, Ralf Baechle wrote:
> On Tue, Sep 10, 2002 at 08:28:32PM -0700, Ryan Murray wrote:
> 
> > The definition of mcontext_t in sysdeps/unix/sysv/linux/mips/sys/ucontext.h
> > does not match what the kernel copies to userspace (struct sigcontext).
> > alpha, ia64, and hppa have fixed this by typedefing one to the other in
> > sys/ucontext.h  The following patch accomplishes the same thing for mips.
> 
> I choose to fix the kernel instead which will keep as closer to the MIPS
> ABI and also prevent having to recompile zillions of user apps.  Below my
> working version of <asm/ucontext.h>.

What are the gregset_t/fpregset_t types in your working tree?  There
aren't any definitions of them in the only copy of the MIPS code that I
have here, and they've had various bad definitions in glibc until
recently.  They also recently changed...

[Although I think your kernel change is the right way to go, here. 
Just being cautious.]

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2002-09-15 19:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11  3:28 [patch] userspace mcontext_t doesn't match what kernel returns Ryan Murray
2002-09-15 19:06 ` Ralf Baechle
2002-09-15 19:16   ` Daniel Jacobowitz [this message]
2002-09-15 23:08     ` Ralf Baechle

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=20020915191613.GA21794@nevyn.them.org \
    --to=dan@debian.org \
    --cc=libc-alpha@sources.redhat.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=rmurray@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.