From: "Xin Zhao" <uszhaoxin@gmail.com>
To: "Oleg Verych" <olecom@flower.upol.cz>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [newbie] Re: Is it possible to directly call do_path_lookup() in kernel?
Date: Wed, 24 Jan 2007 02:59:45 -0500 [thread overview]
Message-ID: <4ae3c140701232359o50e9c27ahe30d441b8083a7ae@mail.gmail.com> (raw)
In-Reply-To: <slrnere41b.e7s.olecom@flower.upol.cz>
Thanks for your reply.
But more details are appreciated. Actually I checked linkage.h before
I sent last email. Looks like "fastcall" is used to direct the
compiler to put the first 3 parameters into registers instead of
stack. But I just don't understand why that causes "general protection
fault".
I am writing a new file system on Linux platform. So I thought this is
the right email list where I can discuss Linux kernel developing
questions. Is this email list only used to post patches and report
bugs? If so, I will stay away.
-x
On 1/24/07, Oleg Verych <olecom@flower.upol.cz> wrote:
>
> On 2007-01-24, Xin Zhao wrote:
> > Archived-At: <http://permalink.gmane.org/gmane.linux.kernel/485775>
>
> Hallo.
>
> > I just successfully called do_path_lookup() in my kernel module. I
> > just removed the "fastcall" from the declaration of do_path_lookup(),
> > then the problem disappeared. I don't quite understand "fastcall"
> > though.
>
> In linkage.h header near you.
>
> > Can someone explain it?
>
> Please use appropriate mailing list:
>
> Kernelnewbies: Help each other learn about the Linux kernel.
> Archive: http://mail.nl.linux.org/kernelnewbies/
> FAQ: http://kernelnewbies.org/faq/
>
> > Thanks,
> > -x
> >
> ____
>
prev parent reply other threads:[~2007-01-24 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 18:32 Xin Zhao
2007-01-24 7:33 ` Xin Zhao
2007-01-24 7:43 ` [newbie] " Oleg Verych
2007-01-24 7:59 ` Xin Zhao [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=4ae3c140701232359o50e9c27ahe30d441b8083a7ae@mail.gmail.com \
--to=uszhaoxin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
/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
all inboxes | Powered by JetHome®