From: Steven Whitehouse <swhiteho@redhat.com>
To: Chris Zubrzycki <chris@middle--earth.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19.1 GFS2_FS_LOCKING_DLM bug still lurking
Date: Tue, 12 Dec 2006 09:59:26 +0000 [thread overview]
Message-ID: <1165917566.3752.1056.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <FCD18869-724B-4E5B-B682-2E39578C36B4@middle--earth.org>
Hi,
On Tue, 2006-12-12 at 00:10 -0500, Chris Zubrzycki wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I tried building the new kernel and ran into this bug:
>
> WARNING: "kernel_sendmsg" [fs/dlm/dlm.ko] undefined!
> WARNING: "sock_release" [fs/dlm/dlm.ko] undefined!
> WARNING: "config_item_put" [fs/dlm/dlm.ko] undefined!
> WARNING: "sock_create_kern" [fs/dlm/dlm.ko] undefined!
> WARNING: "config_item_init_type_name" [fs/dlm/dlm.ko] undefined!
> WARNING: "config_group_init_type_name" [fs/dlm/dlm.ko] undefined!
> WARNING: "configfs_register_subsystem" [fs/dlm/dlm.ko] undefined!
> WARNING: "config_group_find_obj" [fs/dlm/dlm.ko] undefined!
> WARNING: "configfs_unregister_subsystem" [fs/dlm/dlm.ko] undefined!
> WARNING: "kernel_recvmsg" [fs/dlm/dlm.ko] undefined!
> WARNING: "config_item_get" [fs/dlm/dlm.ko] undefined!
> WARNING: "config_group_init" [fs/dlm/dlm.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
>
>
> I found the solution here: http://www.spinics.net/lists/kernel/
> msg535532.html
> I only changed the one file, fs/gfs2/Kconfig, and added
>
> + depends on GFS2_FS && INET && (IPV6 || IPV6=n)
> + select IP_SCTP if DLM_SCTP
> + select CONFIGFS_FS
>
> It seems to work fine now. Please CC me on any replies, thank you.
>
Ok. I'll make a proper patch now and get that added to the git tree.
Thanks,
Steve.
prev parent reply other threads:[~2006-12-12 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 5:10 Chris Zubrzycki
2006-12-12 9:59 ` Steven Whitehouse [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=1165917566.3752.1056.camel@quoit.chygwyn.com \
--to=swhiteho@redhat.com \
--cc=chris@middle--earth.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®