cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH] [GFS2] Fix format string bug
Date: Fri, 13 Jun 2008 12:37:39 +0100	[thread overview]
Message-ID: <1213357059.4011.8.camel@quoit> (raw)
In-Reply-To: <1213246215-9685-1-git-send-email-max@stro.at>

Hi,

On Thu, 2008-06-12 at 06:50 +0200, maximilian attems wrote:
> similar to 326f6a5c9c9e1a62aec37bdc0c3f8d53adabe77b,
> only writable by root but worth fixing.
> 
> Signed-off-by: maximilian attems <max@stro.at>
> ---
>  fs/gfs2/locking.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/gfs2/locking.c b/fs/gfs2/locking.c
> index 663fee7..4857024 100644
> --- a/fs/gfs2/locking.c
> +++ b/fs/gfs2/locking.c
> @@ -131,7 +131,7 @@ retry:
>  		if (!try && capable(CAP_SYS_MODULE)) {
>  			try = 1;
>  			mutex_unlock(&lmh_lock);
> -			request_module(proto_name);
> +			request_module("%s", proto_name);
>  			goto retry;
>  		}
>  		printk(KERN_INFO "GFS2: can't find protocol %s\n", proto_name);

I'm not quite sure whats wrong with the original here, but I'm currently
working upon a patch to remove the lock_dlm module (the lock_nolock
module is already gone) by merging it into the core of GFS2. So that
this module loading code will be disappearing very shortly.

So on that basis, I don't feel that its worth applying this patch at the
moment anyway,

Steve.




           reply	other threads:[~2008-06-13 11:37 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1213246215-9685-1-git-send-email-max@stro.at>]

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=1213357059.4011.8.camel@quoit \
    --to=swhiteho@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).