linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: antoine <antoine@nagafix.co.uk>
Subject: Re: [uml-devel] Re: SKAS0 test tree against 2.6.12
Date: Sat, 9 Jul 2005 12:40:46 +0200	[thread overview]
Message-ID: <200507091240.46934.blaisorblade@yahoo.it> (raw)
In-Reply-To: <1120818569.2940.6.camel@172.16.1.47>

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

On Friday 08 July 2005 12:29, antoine wrote:
> > Ok, it's there. I've simply adapted the two SKAS0 patches for 2.6.12
> > (backporting a cleanup and fixing some trivial rejects). More info at the
> > web page.
> >
> > Testing is welcome. In particular, any regression in SKAS3 mode should be
> > prompty reported to me and Jeff, because they are not expected at all.
> >
> > I'll add a simplified "proc_mm=0" switch (it's not the Bodo's patch
> > because that is more intrusive and splits that further into proc_mm and
> > faultinfo switches).

> Don't know if you're interested in this report but it does not build for
> x86_64:
>   SYMLINK arch/um/sys-x86_64/semaphore.c
>   CC      arch/um/sys-x86_64/semaphore.o
>   CC      arch/um/sys-x86_64/sigcontext.o
>   CC      arch/um/sys-x86_64/signal.o
> arch/um/sys-x86_64/signal.c: In function ‘setup_signal_stack_si’:
> arch/um/sys-x86_64/signal.c:171: error: invalid lvalue in assignment
> make[1]: *** [arch/um/sys-x86_64/signal.o] Error 1
> make: *** [arch/um/sys-x86_64] Error 2
I remember this report, only I just suggested the fix and didn't post it (was 
busy at that time). It's SKAS0 - unrelated I think (I may be wrong, but the 
whole patchset does not include it) but triggered by GCC4.

> Could you include the pcap patch in bb?
Yes, I'll do.
> Thanks
> Antoine

-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

[-- Attachment #2: uml-fix-for-gcc4-lvalue.patch --]
[-- Type: text/x-diff, Size: 847 bytes --]


This is refused by GCC 4, so here's the fix.

Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
---

 vanilla-linux-2.6.12-paolo/arch/um/sys-x86_64/signal.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN arch/um/sys-x86_64/signal.c~uml-fix-for-gcc4-lvalue arch/um/sys-x86_64/signal.c
--- vanilla-linux-2.6.12/arch/um/sys-x86_64/signal.c~uml-fix-for-gcc4-lvalue	2005-07-09 12:02:27.000000000 +0200
+++ vanilla-linux-2.6.12-paolo/arch/um/sys-x86_64/signal.c	2005-07-09 12:02:51.000000000 +0200
@@ -168,7 +168,7 @@ int setup_signal_stack_si(unsigned long 
 
 	frame = (struct rt_sigframe __user *)
 		round_down(stack_top - sizeof(struct rt_sigframe), 16) - 8;
-	((unsigned char *) frame) -= 128;
+	frame -= 128 / sizeof(frame);
 
 	if (!access_ok(VERIFY_WRITE, fp, sizeof(struct _fpstate)))
 		goto out;
_

  reply	other threads:[~2005-07-09 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050707182817.9601389260@sc8-sf-spam1.sourceforge.net>
2005-07-08 10:29 ` [uml-devel] Re: SKAS0 test tree against 2.6.12 antoine
2005-07-09 10:40   ` Blaisorblade [this message]
2005-07-11 21:46     ` Blaisorblade
2005-07-11 22:04       ` Blaisorblade

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=200507091240.46934.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=antoine@nagafix.co.uk \
    --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