public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] sys_clone() related info/help/pointer needed
Date: Fri, 30 May 2003 17:47:17 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723706090@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705986@msgid-missing>

>>>>> On Fri, 30 May 2003 09:21:54 -0700 (PDT), Raj Patil <rpatil0296@yahoo.com> said:

  Raj> Thanks for your comments/info David.  (was out for few days...)

  Raj> One thing I am not clear is why should it be different when
  Raj> sys_clone() is called as part of the regulare syscall and from
  Raj> a module as another syscall. Both of them are going through the
  Raj> same path; sys_clone(), do_fork(), copy_thread(). Am I missing
  Raj> something vey obvious to see the difference?

Modules are a different story: you can't call modules via the syscall
table (because the global pointer will be wrong).  This is actually a
feature since it's almost always either wrong or illegal to install
syscalls from a module.  In fact, in newer kernels, the syscall table
isn't exported to modules anymore.  That's a good thing.

  Raj> BTW: I bought "ia-64 linux kernel design and implementation"
  Raj> book.  It is very well wriiten.

Thanks!

	--david


      parent reply	other threads:[~2003-05-30 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 20:36 [Linux-ia64] sys_clone() related info/help/pointer needed Raj Patil
2003-05-27 16:57 ` David Mosberger
2003-05-30 16:21 ` Raj Patil
2003-05-30 17:47 ` David Mosberger [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=marc-linux-ia64-105590723706090@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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