public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Constantine Gavrilov <constg@qlusters.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: bugs@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: Calling syscalls from x86-64 kernel results in a crash on Opteron machines
Date: Mon, 13 Sep 2004 18:05:52 +0300	[thread overview]
Message-ID: <4145B750.6060900@qlusters.com> (raw)
In-Reply-To: <20040913153803.A27282@infradead.org>

Christoph Hellwig wrote:

>On Mon, Sep 13, 2004 at 05:04:17PM +0300, Constantine Gavrilov wrote:
>  
>
>>Hello:
>>
>>We have a piece of kernel code that calls some system calls in kernel 
>>context (
>>    
>>
>
>Which you shouldn't do in the first place.
>  
>

Function kernel_thread() on i386 is implemented by putting the args to 
appropriate regs and calling int 0x80, resulting in a system call 
clone() on i386.

I have also found the "syscall" instruction in x86-64 kernel specific 
code (it does not call _syscall() macros directly, though). So, 
"shouldn't do" is a bit too strong.

What I am writing is an application, and not interface. As such, it is 
not much different from its requierements from a user-space application. 
If user-space application may call system calls, why a kernel space 
application cannot?

And BTW, kernel-space applications have their own place even if the 
concept seems foreign to you.

-- 
----------------------------------------
Constantine Gavrilov
Kernel Developer
Qlusters Software Ltd
1 Azrieli Center, Tel-Aviv
Phone: +972-3-6081977
Fax:   +972-3-6081841
----------------------------------------



  reply	other threads:[~2004-09-13 15:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13 14:04 Calling syscalls from x86-64 kernel results in a crash on Opteron machines Constantine Gavrilov
2004-09-13 14:38 ` Christoph Hellwig
2004-09-13 15:05   ` Constantine Gavrilov [this message]
2004-09-13 16:17     ` Andrea Arcangeli
2004-09-13 16:41       ` Stephen Hemminger
2004-09-13 20:08         ` Andrea Arcangeli
2004-09-13 16:42     ` Greg KH
2004-09-13 17:21     ` Brian Gerst
2004-09-14  2:04     ` William Lee Irwin III
2004-09-13 14:44 ` Arnd Bergmann
2004-09-13 15:18   ` Constantine Gavrilov
2004-09-13 19:39     ` H. Peter Anvin
2004-09-13 15:00 ` Brian Gerst
2004-09-13 15:26   ` Constantine Gavrilov
     [not found] <2DZQy-7TB-7@gated-at.bofh.it>
2004-09-13 14:31 ` Andi Kleen
2004-09-13 15:28   ` Constantine Gavrilov

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=4145B750.6060900@qlusters.com \
    --to=constg@qlusters.com \
    --cc=bugs@x86-64.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@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