From: Andi Kleen <ak@muc.de>
To: john@stebbins.name
Cc: linux-kernel@vger.kernel.org
Subject: Re: sys_close undefined on x86_64
Date: Sun, 13 Jun 2004 02:38:09 +0200 [thread overview]
Message-ID: <m3acz8nvgu.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <26qTc-8ok-3@gated-at.bofh.it> (John Stebbins's message of "Sun, 13 Jun 2004 02:20:06 +0200")
John Stebbins <john@stebbins.name> writes:
> Can someone tell me if this is a kernel bug or a problem with the module
> I'm trying to compile?
>
> I'm attempting to compile an external module for the PVR-250 mpeg-2
> capture card (ivtv module). The driver is a little behind the times,
> but various people have persuaded it to compile and load on 2.6
> systems. I had it running on i386 arch 2.6 kernel earlier. But I've
> since upgraded to x86_64.
>
> insmod fails with sys_close undefined message when attempting to load
> the module.
>
> The other sys_ functions seem to be there.
>
> If the use of sys_close has been deprecated or something, could someone
> please give me a pointer to the right way to do syscalls in the 2.6
> kernels. I've done some digging and just can't find any useful
> information.
It's just not exported and x86-64 unlike i386 calls in kernel system
calls directly. In theory it could be exported (stick a
EXPORT_SYMBOL(sys_close) somewhere in the main kernel), however it
would be better to change the driver to not use it and use a private
file or no file at all.
-Andi
next parent reply other threads:[~2004-06-13 0:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26qTc-8ok-3@gated-at.bofh.it>
2004-06-13 0:38 ` Andi Kleen [this message]
2004-06-13 0:11 sys_close undefined on x86_64 John Stebbins
2004-06-13 0:28 ` Greg KH
2004-06-13 20:42 ` John Stebbins
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=m3acz8nvgu.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=john@stebbins.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.