From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] missing exports of __strlen_user(), __strncpy_from_user()?
Date: Tue, 05 Dec 2000 22:18:21 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205791@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205789@msgid-missing>
__copy_user and __do_clear_user were already in the current kernel
sources but I added the other three now.
Thanks,
--david
>>>>> On Tue, 5 Dec 2000 17:04:06 -0500 (EST), John Kohl <jtk@rational.com> said:
John> i386 kernels export strnlen_user() and strncpy_from_user();
John> the former is referenced by the macro for strlen_user().
John> ia64 does not export either __strlen_user() or
John> __strncpy_from_user() (referenced by strlen_user() and
John> strncpy_from_user() macros functions). We need these symbols
John> to implement some code in our kernel module (ClearCase MVFS).
John> I presume this is just an oversight, and they should be added
John> to arch/ia64/kernel/ia64_ksyms.c? I'd suggest adding these,
John> as similar to exported symbols in i386, to make
John> copy_{from,to}_user(), strncpy_from_user(), and clear_user()
John> usable by modules.
John> EXPORT_SYMBOL(__strncpy_from_user);
John> EXPORT_SYMBOL(__do_clear_user); EXPORT_SYMBOL(__strlen_user);
John> EXPORT_SYMBOL(__strnlen_user); EXPORT_SYMBOL(__copy_user);
John> -- =John Kohl <jtk@rational.com>, Software Engineer Rational
John> Software, Configuration Management Business Unit Mark your
John> calendars! Rational User Conference 2001, July 22-26, 2001 in
John> beautiful Denver, Colorado
John> _______________________________________________ Linux-IA64
John> mailing list Linux-IA64@linuxia64.org
John> http://lists.linuxia64.org/lists/listinfo/linux-ia64
prev parent reply other threads:[~2000-12-05 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 22:04 [Linux-ia64] missing exports of __strlen_user(), __strncpy_from_user()? John Kohl
2000-12-05 22:18 ` 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-105590678205791@msgid-missing \
--to=davidm@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