From: Mingming Cao <cmm@us.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-fsdevel@vger.kernel.org, Duane Griffin <duaneg@dghda.com>
Subject: Re: [PATCH] fix up thinko in jbd2 revoke code
Date: Mon, 31 Mar 2008 11:30:58 -0700 [thread overview]
Message-ID: <1206988258.3653.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1206979062.3192.26.camel@localhost.localdomain>
On Mon, 2008-03-31 at 10:57 -0500, James Bottomley wrote:
> This commit:
>
> commit e898f3154d78d1520265aade0992981866d827fb
> Author: Duane Griffin <duaneg@dghda.com>
> Date: Tue Mar 25 19:47:39 2008 -0400
>
> jbd2: tidy up revoke cache initialisation and destruction
>
> Introduced a thinko (it doesn't check whether jbd2_revoke_record cache
> is null, it checks jbd2_revoke_table_cache twice).
>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
>
Signed-off-by: Mingming Cao <cmm@us.ibm.com>
Thanks, I picked this up in ext4 patch queue.
Mingming
> ---
>
> diff --git a/fs/jbd2/revoke.c b/fs/jbd2/revoke.c
> index e13584a..4dc5b85 100644
> --- a/fs/jbd2/revoke.c
> +++ b/fs/jbd2/revoke.c
> @@ -192,7 +192,7 @@ int __init jbd2_journal_init_revoke_caches(void)
> jbd2_revoke_table_cache = kmem_cache_create("jbd2_revoke_table",
> sizeof(struct jbd2_revoke_table_s),
> 0, SLAB_TEMPORARY, NULL);
> - if (jbd2_revoke_table_cache && jbd2_revoke_table_cache) {
> + if (jbd2_revoke_record_cache && jbd2_revoke_table_cache) {
> return 0;
> } else {
> jbd2_journal_destroy_revoke_caches();
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-31 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 15:57 [PATCH] fix up thinko in jbd2 revoke code James Bottomley
2008-03-31 18:30 ` Mingming Cao [this message]
2008-04-03 16:17 ` Christoph Hellwig
2008-04-21 9:54 ` Aneesh Kumar K.V
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=1206988258.3653.2.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=duaneg@dghda.com \
--cc=linux-fsdevel@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).