[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] no version for "gfs2_unmount_lockproto"

Bob Peterson <rpeterso redhat com>:
> Hi Wagner,
> The HEAD / RHEL5 / (similar) versions of GFS use part of gfs2's
> locking infrastructure.  For RHEL5, we did a patch to export
> those symbols from GFS2.  The patch looks like the one I have
> below.  So the GFS2 module has to be loaded for GFS to work
> and that's just so GFS and GFS2 share the same locking protocol.
> (i.e. people can mount both gfs and gfs2 at the same time and
> go through the same dlm).  The exporting of those symbols did
> not get pushed into upstream GFS2 because it's only needed for
> GFS(1), which itself isn't part of the upstream kernel.
> If you add these symbol exports to GFS2 it should allow GFS
> to mount properly.
> Regards,
> Bob Peterson
> Red Hat GFS
> --
> --- a/fs/gfs2/locking.c	2008-02-11 11:10:57.000000000 -0600
> +++ b/fs/gfs2/locking.c	2008-02-08 14:10:36.000000000 -0600
> @@ -181,4 +181,6 @@ void gfs2_withdraw_lockproto(struct lm_l
>  EXPORT_SYMBOL_GPL(gfs2_register_lockproto);
>  EXPORT_SYMBOL_GPL(gfs2_unregister_lockproto);
> -
> +EXPORT_SYMBOL_GPL(gfs2_withdraw_lockproto);
> +EXPORT_SYMBOL_GPL(gfs2_mount_lockproto);
> +EXPORT_SYMBOL_GPL(gfs2_unmount_lockproto);

I'm curious.  Are there plans to include this patch in the mainline?  Any
reasons why or why not?


Attachment: smime.p7s
Description: S/MIME cryptographic signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]