From: William Lee Irwin III <wli@holomorphy.com>
To: Rudmer van Dijk <rudmer@legolas.dynup.net>
Cc: Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.69-mm7
Date: Mon, 19 May 2003 03:38:26 -0700 [thread overview]
Message-ID: <20030519103826.GC8978@holomorphy.com> (raw)
In-Reply-To: <200305191230.06092.rudmer@legolas.dynup.net>
On Monday 19 May 2003 10:23, Andrew Morton wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.69/2.5.69
>>-mm7/
>> . Included most of the new AIO code which has been floating about. This
>> all still needs considerable thought and review, but we may as well get
>> it under test immediately.
>> . Lots of little fixes, as usual.
On Mon, May 19, 2003 at 12:30:05PM +0200, Rudmer van Dijk wrote:
> and this became broken:
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.5.69-mm7; fi
> WARNING: /lib/modules/2.5.69-mm7/kernel/fs/ext2/ext2.ko needs unknown symbol
> __bread_wq
> __bread_wq is introduced in -mm7, someone forgot to export it?
Try this patch please.
-- wli
diff -prauN mm7-2.5.69-1/fs/buffer.c mm7-2.5.69-2A/fs/buffer.c
--- mm7-2.5.69-1/fs/buffer.c 2003-05-19 01:18:03.000000000 -0700
+++ mm7-2.5.69-2A/fs/buffer.c 2003-05-19 03:14:27.000000000 -0700
@@ -1490,6 +1490,7 @@ __bread(struct block_device *bdev, secto
bh = __bread_slow(bh);
return bh;
}
+EXPORT_SYMBOL(__bread);
struct buffer_head *
@@ -1502,7 +1503,7 @@ __bread_wq(struct block_device *bdev, se
bh = __bread_slow_wq(bh, wait);
return bh;
}
-EXPORT_SYMBOL(__bread);
+EXPORT_SYMBOL(__bread_wq);
/*
* invalidate_bh_lrus() is called rarely - at unmount. Because it is only for
diff -prauN mm7-2.5.69-1/kernel/ksyms.c mm7-2.5.69-2A/kernel/ksyms.c
--- mm7-2.5.69-1/kernel/ksyms.c 2003-05-19 01:18:08.000000000 -0700
+++ mm7-2.5.69-2A/kernel/ksyms.c 2003-05-19 03:17:20.000000000 -0700
@@ -123,6 +123,7 @@ EXPORT_SYMBOL(get_unmapped_area);
EXPORT_SYMBOL(init_mm);
EXPORT_SYMBOL(blk_queue_bounce);
EXPORT_SYMBOL(blk_congestion_wait);
+EXPORT_SYMBOL(blk_congestion_wait_wq);
#ifdef CONFIG_HIGHMEM
EXPORT_SYMBOL(kmap_high);
EXPORT_SYMBOL(kunmap_high);
@@ -216,6 +217,7 @@ EXPORT_SYMBOL(sync_dirty_buffer);
EXPORT_SYMBOL(submit_bh);
EXPORT_SYMBOL(unlock_buffer);
EXPORT_SYMBOL(__wait_on_buffer);
+EXPORT_SYMBOL(__wait_on_buffer_wq);
EXPORT_SYMBOL(blockdev_direct_IO);
EXPORT_SYMBOL(block_write_full_page);
EXPORT_SYMBOL(block_read_full_page);
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-19 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 8:23 2.5.69-mm7 Andrew Morton
2003-05-19 10:30 ` 2.5.69-mm7 Rudmer van Dijk
2003-05-19 10:38 ` William Lee Irwin III [this message]
2003-05-19 13:19 ` 2.5.69-mm7 Rudmer van Dijk
2003-05-19 10:58 ` 2.5.69-mm7 Alexander Hoogerhuis
2003-05-20 19:52 ` 2.5.69-mm7 Andy Whitcroft
2003-05-20 20:01 ` 2.5.69-mm7 Eric W. Biederman
2003-05-21 12:13 ` 2.5.69-mm7 Ivan Kokshaysky
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=20030519103826.GC8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rudmer@legolas.dynup.net \
/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