All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tommy Reynolds <reynolds@redhat.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: seq_open, et. al. are not exported for modules
Date: Thu, 29 Nov 2001 13:39:11 -0600	[thread overview]
Message-ID: <20011129133911.4816fe2b.reynolds@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

Alex,

The patch below, relative to 2.4.16, exports the seq_FOO symbols so they can be
used from a loadable kernel module.

BTW: could the "kmalloc()" calls be safely changed to "vmalloc()"?

--- linux/kernel/ksyms.c.orig	Thu Nov 29 13:14:10 2001
+++ linux/kernel/ksyms.c	Thu Nov 29 13:15:29 2001
@@ -46,6 +46,7 @@
 #include <linux/tty.h>
 #include <linux/in6.h>
 #include <linux/completion.h>
+#include <linux/seq_file.h>
 #include <asm/checksum.h>
 
 #if defined(CONFIG_PROC_FS)
@@ -559,3 +560,11 @@ EXPORT_SYMBOL(init_task_union);
 
 EXPORT_SYMBOL(tasklist_lock);
 EXPORT_SYMBOL(pidhash);
+
+/* Sequential file systems */
+
+EXPORT_SYMBOL(seq_open);
+EXPORT_SYMBOL(seq_read);
+EXPORT_SYMBOL(seq_lseek);
+EXPORT_SYMBOL(seq_release);
+EXPORT_SYMBOL(seq_escape);


---------------------------------------------+-----------------------------
Tommy Reynolds                               | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone:  +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA  | FAX:    +1.256.837.3839
Senior Software Developer                    | Mobile: +1.919.641.2923

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2001-11-29 19:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29 19:39 Tommy Reynolds [this message]
2001-11-29 20:08 ` seq_open, et. al. are not exported for modules Tommy Reynolds

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=20011129133911.4816fe2b.reynolds@redhat.com \
    --to=reynolds@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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.