All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Paolo Giarrusso <blaisorblade@yahoo.it>
Cc: Rob Landley <rob@landley.net>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] Ok, I build x86-64 -skas0, and it still segfaults.
Date: Tue, 15 Nov 2005 19:57:10 -0500	[thread overview]
Message-ID: <20051116005710.GA11520@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20051115220903.73648.qmail@web25208.mail.ukl.yahoo.com>

On Tue, Nov 15, 2005 at 11:09:03PM +0100, Paolo Giarrusso wrote:
> I've come to a (possible) conclusion - probably we could try to adapt
> and reuse the batching syscall stub to do everything. With the
> original single-syscall stub it didn't make sense, with this one it
> could do. 

What would that look like?  An array of numbers representing register
values to be given to the batch syscall stub?  Or the syscall_stub* macros
would fill in an array?

> Or anyway, it's possibly becoming harder to write all this in C with
> assembly inserts rather than directly in assembly. It also does not
> work well on some strange compilers (aka Hardened GCC, as reported by
> Antoine Martin).

I'm wondering about this as well.  I'm unsure whether we are mopping up the
last few problems, or whether we will just be seeing misassembly after
misassembly.

At least this patch is a clear bug fix.

> > -/*	__asm__("movl %0, %%eax ; int $0x80": : "g" (__NR_getpid));
> > -	__asm__("movl %%eax, %%ebx ; movl %0, %%eax ; movl %1, %%ecx ;"
> > -		"int $0x80": : "g" (__NR_kill), "g" (SIGUSR1)); */
> 
> Where does this commented getpid + kill comes from? It seems to come
> from rubbish in some patch.

This patch was at the end of my series - the current version doesn't have
this.

> The idea would be nice, but I am reluctant in trusting GCC to leave
> %esp unaltered; also, without volatile, GCC feels probably allowed to
> move this instruction anywhere in the code.

OK, I changed it back.

> Actually, I start feeling this could be moved to assembly.

Maybe.  I prefer C as long as that is viable, though.

				Jeff


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2005-11-16  0:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-13  1:36 [uml-devel] [PATCH] Ok, I build x86-64 -skas0, and it still segfaults Rob Landley
2005-11-13 17:54 ` Blaisorblade
2005-11-13 23:26   ` Rob Landley
2005-11-14 19:40     ` Blaisorblade
2005-11-16  3:09       ` Rob Landley
2005-11-18  7:43         ` Blaisorblade
2005-11-18  7:36           ` Rob Landley
2005-11-18  7:58             ` Blaisorblade
2005-11-18  8:58               ` Rob Landley
2005-11-19  0:11               ` [uml-devel] [PATCH] UML x86-64 build fix Rob Landley
2005-11-13 19:32 ` [uml-devel] [PATCH] Ok, I build x86-64 -skas0, and it still segfaults Jeff Dike
2005-11-13 19:20   ` Blaisorblade
2005-11-13 23:32     ` Rob Landley
2005-11-14 15:33       ` Jeff Dike
2005-11-14 21:55       ` Jeff Dike
2005-11-14 23:24         ` Rob Landley
2005-11-14 23:45           ` Rob Landley
2005-11-15  1:38             ` Jeff Dike
2005-11-15  2:18               ` Rob Landley
2005-11-15 22:09         ` Paolo Giarrusso
2005-11-16  0:57           ` Jeff Dike [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=20051116005710.GA11520@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade@yahoo.it \
    --cc=rob@landley.net \
    --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 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.