linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: post-2.6.3 build error
Date: Thu, 26 Feb 2004 20:30:56 +0100	[thread overview]
Message-ID: <200402262030.56198.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <87smgyamnx.fsf@bytesex.org>

Alle 22:12, mercoledì 25 febbraio 2004, Gerd Knorr ha scritto:
> BlaisorBlade <blaisorblade_spam@yahoo.it> writes:
> > __NR_sched_yield ] = (syscall_handler_t *) yield
> >
> > It should refer to sys_sched_yield. yield() is not even asmlinkage, so
> > this could case serious problems, and it is commented as "for kernel
> > usage". Also I checked i386 syscall table, and it uses sys_sched_yield.
>
> There is another related one (asmlinkage where it shouldn't be) in
> mprotect.c.

Good catch.

> With the new CONFIG_REGPARM config option it becomes
> really important to get that right ...

Yes, however I think that one asmlinkage more is not very bad (old convention 
used where the call can be optimized), but that a missing asmlinkage could be 
crashy. At least until the prototype is correct; I just noticed that 
do_mprotect is protoized without asmlinkage - and this can be actually 
crashy. Luckily CONFIG_REGPARM is not in the stock kernel.

If it were, that could have explained some Skas-2.6 crashes which can be seen 
here (there is already one BUG hit which explains it in part, see here: "Host 
2.6.2/3 + CFQ + BlaisorBlade patches"... but on one kernel it Oopsed and on 
another it crashed, so there could be something else).

-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&opÌk
_______________________________________________
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:[~2004-02-26 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 17:20 [uml-devel] post-2.6.3 build error Gerd Knorr
2004-02-25 19:47 ` BlaisorBlade
2004-02-25 21:12   ` [uml-devel] " Gerd Knorr
2004-02-26 19:30     ` BlaisorBlade [this message]
2004-02-26 21:10       ` Gerd Knorr

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=200402262030.56198.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --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