From: David Woodhouse <dwmw2@infradead.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: marcelo@conectiva.com.br, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Shared crc32 for 2.4.
Date: Fri, 23 May 2003 10:28:03 +0100 [thread overview]
Message-ID: <1053682083.3402.69.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <1053637864.21582.700.camel@imladris.demon.co.uk>
On Thu, 2003-05-22 at 22:11, David Woodhouse wrote:
> On Thu, 2003-05-22 at 00:50, J.A. Magallon wrote:
> > This works if crc32.o is compiled as a module, but does not work if it is
> > built into the kernel. For example, crc32_le symbol does not appear
> > in System.map nor vmlinux.
>
> Oh bollocks; sorry I'd forgotten about that.
>
> Added to the tree from which Marcelo will pull for 2.4.22-pre1...
I hereby declare myself to be Today's Official Mr Fuck All Good.
On top of that patch which fixes CONFIG_CRC32=y, you'll need this patch
which fixes CONFIG_CRC32=m, newly broken (at least with new modutils) by
the removal of the EXPORT_SYMBOL()s from crc32.o...·
Full patch against 2.4.21-rc3 is in
ftp://ftp.??.kernel.org/pub/linux/kernel/people/dwmw2/crc32/
(and in master.kernel.org:~dwmw2/BK/crc32-2.4 still)
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.1216 -> 1.1217
# lib/crc32.c 1.2 -> 1.3
# lib/Makefile 1.11 -> 1.12
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/05/23 dwmw2@infradead.org 1.1217
# Fix CONFIG_CRC32=m by make crc32.o export its own symbols again in that case.
# --------------------------------------------
#
diff -Nru a/lib/Makefile b/lib/Makefile
--- a/lib/Makefile Fri May 23 10:09:17 2003
+++ b/lib/Makefile Fri May 23 10:09:17 2003
@@ -8,7 +8,8 @@
L_TARGET := lib.a
-export-objs := cmdline.o dec_and_lock.o rwsem-spinlock.o rwsem.o rbtree.o
+export-objs := cmdline.o dec_and_lock.o rwsem-spinlock.o rwsem.o \
+ rbtree.o crc32.o
obj-y := errno.o ctype.o string.o vsprintf.o brlock.o cmdline.o \
bust_spinlocks.o rbtree.o dump_stack.o
diff -Nru a/lib/crc32.c b/lib/crc32.c
--- a/lib/crc32.c Fri May 23 10:09:17 2003
+++ b/lib/crc32.c Fri May 23 10:09:17 2003
@@ -266,6 +266,13 @@
return x;
}
+#ifdef MODULE /* These are exported from kernel/ksyms.c in the non-module
+ case, to ensure that this file is pulled in from lib/lib.a */
+EXPORT_SYMBOL(crc32_le);
+EXPORT_SYMBOL(crc32_be);
+EXPORT_SYMBOL(bitreverse);
+#endif
+
/*
* A brief CRC tutorial.
*
--
dwmw2
next prev parent reply other threads:[~2003-05-23 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 17:43 David Woodhouse
2003-05-19 7:24 ` Duncan Sands
2003-05-19 15:06 ` David Woodhouse
2003-05-21 23:50 ` J.A. Magallon
2003-05-22 21:11 ` David Woodhouse
2003-05-23 9:28 ` David Woodhouse [this message]
2003-05-22 20:23 ` Marcelo Tosatti
2003-05-23 6:44 ` David Woodhouse
[not found] <03ee01c320b4$c3040ad0$020120b0@jockeXP>
2003-05-27 11:26 ` David Woodhouse
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=1053682083.3402.69.camel@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®