linux-um archives
 help / color / mirror / Atom feed
From: Andree Leidenfrost <aleidenf@bigpond.net.au>
To: Alexander Nyberg <alexn@dsv.su.se>
Cc: blaisorblade@yahoo.it, akpm@osdl.org, jdike@addtoit.com,
	bstroesser@fujitsu-siemens.com, linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [patch 1/1] uml: fix handling of no fpx_regs [critical, for 2.6.12]
Date: Tue, 26 Apr 2005 19:44:15 +1000	[thread overview]
Message-ID: <1114508655.7716.28.camel@aurich.ostfriesland> (raw)
In-Reply-To: <1114459067.983.22.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1965 bytes --]

Hi Alexander

On Mon, 2005-04-25 at 21:57 +0200, Alexander Nyberg wrote:
> mån 2005-04-25 klockan 21:12 +0200 skrev blaisorblade@yahoo.it:
> > From: Andree Leidenfrost <aleidenf@bigpond.net.au>, Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
> > 
> > Fix the error path, which is triggered when the processor misses the fpx regs
> > (i.e. the "fxsr" cpuinfo feature). For instance by VIA C3 Samuel2. Tested and
> > obvious, please merge ASAP.
> > 
> > Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
> > ---
> > 
> >  linux-2.6.12-paolo/arch/um/os-Linux/sys-i386/registers.c |    7 ++++---
> >  1 files changed, 4 insertions(+), 3 deletions(-)
> > 
> > diff -puN arch/um/os-Linux/sys-i386/registers.c~uml-fix-no_fpx_regs_handling arch/um/os-Linux/sys-i386/registers.c
> > --- linux-2.6.12/arch/um/os-Linux/sys-i386/registers.c~uml-fix-no_fpx_regs_handling	2005-04-25 21:03:11.000000000 +0200
> > +++ linux-2.6.12-paolo/arch/um/os-Linux/sys-i386/registers.c	2005-04-25 21:08:07.000000000 +0200
> > @@ -105,14 +105,15 @@ void init_registers(int pid)
> >  		panic("check_ptrace : PTRACE_GETREGS failed, errno = %d",
> >  		      err);
> >  
> > +	errno = 0;
> >  	err = ptrace(PTRACE_GETFPXREGS, pid, 0, exec_fpx_regs);
> >  	if(!err)
> >  		return;
> > +	if(errno != EIO)
> > +		panic("check_ptrace : PTRACE_GETFPXREGS failed, errno = %d",
> > +		      errno);
> 
> Looks like you mean "if (err != EIO)" here

No. The patch is correct.

ptrace will always return -1 in case of an error. The actual error code
is in errno, hence this is what needs to be compared to EIO. Please also
see the ptrace manpage.

> >  	have_fpx_regs = 0;
> > -	if(err != EIO)
> > -		panic("check_ptrace : PTRACE_GETFPXREGS failed, errno = %d",
> > -		      err);
> >  
> >  	err = ptrace(PTRACE_GETFPREGS, pid, 0, exec_fp_regs);
> >  	if(err)

Best regards
Andree
-- 
Andree Leidenfrost
Sydney - Australia


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-04-26  9:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 19:12 [uml-devel] [patch 1/1] uml: fix handling of no fpx_regs [critical, for 2.6.12] blaisorblade
2005-04-25 19:57 ` [uml-devel] " Alexander Nyberg
2005-04-26  9:44   ` Andree Leidenfrost [this message]

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=1114508655.7716.28.camel@aurich.ostfriesland \
    --to=aleidenf@bigpond.net.au \
    --cc=akpm@osdl.org \
    --cc=alexn@dsv.su.se \
    --cc=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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