From: Rusty Lynch <rusty@linux.co.intel.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Revision 30 fails to insmod
Date: Tue Feb 10 18:28:29 2004 [thread overview]
Message-ID: <20040211002621.GA16362@penguin.co.intel.com> (raw)
In-Reply-To: <50D19C3AC815734C9E19FE4C4F6128A617802E@orsmsx403.jf.intel.com>
On Tue, Feb 10, 2004 at 04:07:26PM -0800, Villalovos, John L wrote:
> Just did a sync with revision 30 from the repository.
>
> It fails to insmod.
>
> /lib/modules/2.4.22-1.2149.nptl/unsupported/fs/ocfs2.o: unresolved
> symbol OCFS_SB_GET_KDEV
>
> It looks like the latest revision removed the definition of
> OCFS_SB_GET_KDEV in src/inc/ocfs.h but is still using the macro :(
Here is a fix
--rusty
Index: src/inc/ocfs.h
===================================================================
--- src/inc/ocfs.h (revision 30)
+++ src/inc/ocfs.h (working copy)
@@ -1107,7 +1107,7 @@
typedef long sector_t;
#define map_bh(bh, sb, blk) \
({ \
- bh->b_dev = OCFS_SB_GET_KDEV(sb); \
+ bh->b_dev = sb->s_dev; \
bh->b_blocknr = blk; \
bh->b_state |= (1UL << BH_Mapped); \
})
next prev parent reply other threads:[~2004-02-10 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 18:07 [Ocfs2-devel] Revision 30 fails to insmod Villalovos, John L
2004-02-10 18:28 ` Rusty Lynch [this message]
2004-02-10 19:10 ` Manish Singh
-- strict thread matches above, loose matches on Subject: below --
2004-02-10 18:36 Villalovos, John L
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=20040211002621.GA16362@penguin.co.intel.com \
--to=rusty@linux.co.intel.com \
--cc=ocfs2-devel@oss.oracle.com \
/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.