linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Yin, Kangkai" <kangkai.yin@intel.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] jbd: jbd-debug and jbd2-debug should be writable.
Date: Fri, 4 Dec 2009 15:19:32 +0530	[thread overview]
Message-ID: <20091204094932.GC4272@skywalker.linux.vnet.ibm.com> (raw)
In-Reply-To: <20091204031735.GN19635@kai-debian>

On Fri, Dec 04, 2009 at 11:17:35AM +0800, Yin, Kangkai wrote:
> Hi,
> 
> Re-send since seems my mail was dropped by vger, because of my wrong
> envelope_from..
> 
> ----
> I was trying to enable the jbd debug option, and found that jbd-debug
> in debugfs is read-only, shouldn't that be writable?
> 
> Found in both .31 stable kernel and .32 one.
> 
> Thanks,
> Kangkai
> 
> From 492ec0453ca3458c68deaa6e308ca01acc0eca1f Mon Sep 17 00:00:00 2001
> From: Yin Kangkai <kangkai.yin@intel.com>
> Date: Thu, 3 Dec 2009 18:01:38 +0800
> Subject: [PATCH] jbd: jbd-debug and jbd2-debug should be writable.
> 
> jbd-debug and jbd2-debug is currently read-only (S_IRUGO), which is not
> correct. Make it writable so that we can start debuging.
> 
> Signed-off-by: Yin Kangkai <kangkai.yin@intel.com>

Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>

> ---
>  fs/jbd/journal.c  |    2 +-
>  fs/jbd2/journal.c |    3 ++-
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/jbd/journal.c b/fs/jbd/journal.c
> index 4160afa..bd224ee 100644
> --- a/fs/jbd/journal.c
> +++ b/fs/jbd/journal.c
> @@ -1913,7 +1913,7 @@ static void __init jbd_create_debugfs_entry(void)
>  {
>  	jbd_debugfs_dir = debugfs_create_dir("jbd", NULL);
>  	if (jbd_debugfs_dir)
> -		jbd_debug = debugfs_create_u8("jbd-debug", S_IRUGO,
> +		jbd_debug = debugfs_create_u8("jbd-debug", S_IRUGO | S_IWUSR,
>  					       jbd_debugfs_dir,
>  					       &journal_enable_debug);
>  }
> diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
> index fed8538..3c41c5a 100644
> --- a/fs/jbd2/journal.c
> +++ b/fs/jbd2/journal.c
> @@ -2103,7 +2103,8 @@ static void __init jbd2_create_debugfs_entry(void)
>  {
>  	jbd2_debugfs_dir = debugfs_create_dir("jbd2", NULL);
>  	if (jbd2_debugfs_dir)
> -		jbd2_debug = debugfs_create_u8(JBD2_DEBUG_NAME, S_IRUGO,
> +		jbd2_debug = debugfs_create_u8(JBD2_DEBUG_NAME,
> +					       S_IRUGO | S_IWUSR,
>  					       jbd2_debugfs_dir,
>  					       &jbd2_journal_enable_debug);
>  }
> -- 
> 1.6.5
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-12-04  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04  3:17 [PATCH] jbd: jbd-debug and jbd2-debug should be writable Yin, Kangkai
2009-12-04  9:49 ` Aneesh Kumar K.V [this message]
2009-12-25 20:48   ` tytso
2010-01-04 22:26     ` Jan Kara
2010-01-05 16:35       ` tytso

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=20091204094932.GC4272@skywalker.linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=kangkai.yin@intel.com \
    --cc=linux-ext4@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).