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
>
____
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 <[email protected]> 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
> >
> ____
>