linux-um archives
 help / color / mirror / Atom feed
From: "Peter Teoh" <htmldeveloper@gmail.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: David Shane Holden <dpejesh@yahoo.com>,
	"david.r" <david.r@seznam.cz>,
	uml-devel <user-mode-linux-devel@lists.sourceforge.net>,
	uml-user <user-mode-linux-user@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH] Fix for 2.6.26 ptrace crash
Date: Tue, 22 Jul 2008 16:45:35 +0800	[thread overview]
Message-ID: <804dabb00807220145y375eaaefk5a352046d5e944d7@mail.gmail.com> (raw)
In-Reply-To: <20080721154658.GA6860@c2.user-mode-linux.org>

Thanks, the patch worked for me too.

As an aside, may be u would want to sync with mainline:

http://lkml.org/lkml/2007/5/3/460

which would solve the problem Boaz posed as well?

(the patch above seemed to indicate a problem of post-3.4 vs pre-3.4 GCC:

http://www.gnu.org/software/gcc/gcc-3.4/changes.html

but your patch indicated something to do with 4.x GCC vs pre-3.4 GCC?)

Sorry if I don't get it correctly :-).

On Mon, Jul 21, 2008 at 11:46 PM, Jeff Dike <jdike@addtoit.com> wrote:
> I believe I figured out the ptrace crash that showed up with 2.6.26,
> thanks to Toralf Förster.
>
> The patch is below.
>
> I have one confirmation that this fixes the problem - I'd like a few
> more just to be sure.
>
>                        Jeff
>
> --
> Work email - jdike at linux dot intel dot com
>
> Index: linux-2.6.22/arch/um/include/init.h
> ===================================================================
> --- linux-2.6.22.orig/arch/um/include/init.h    2008-02-18 11:53:50.000000000 -0500
> +++ linux-2.6.22/arch/um/include/init.h 2008-07-20 18:06:35.000000000 -0400
> @@ -45,6 +45,8 @@ typedef void (*exitcall_t)(void);
>  # define __section(S) __attribute__ ((__section__(#S)))
>  #endif
>
> +#if __GNUC__ == 3
> +
>  #if __GNUC_MINOR__ >= 3
>  # define __used                        __attribute__((__used__))
>  #else
> @@ -52,6 +54,12 @@ typedef void (*exitcall_t)(void);
>  #endif
>
>  #else
> +#if __GNUC__ == 4
> +# define __used                        __attribute__((__used__))
> +#endif
> +#endif
> +
> +#else
>  #include <linux/compiler.h>
>  #endif
>  /* These are for everybody (although not all archs will actually
>



-- 
Regards,
Peter Teoh

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2008-07-22  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 15:46 [uml-devel] [PATCH] Fix for 2.6.26 ptrace crash Jeff Dike
2008-07-21 20:24 ` [uml-devel] [uml-user] " vincent-perrier
2008-07-22  8:45 ` Peter Teoh [this message]
     [not found] ` <488599E1.50402@panasas.com>
2008-07-23 16:14   ` [uml-devel] " Jeff Dike

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=804dabb00807220145y375eaaefk5a352046d5e944d7@mail.gmail.com \
    --to=htmldeveloper@gmail.com \
    --cc=david.r@seznam.cz \
    --cc=dpejesh@yahoo.com \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@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