public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Girish Shilamkar <girish@clusterfs.com>
Cc: Ext4 Mailing List <linux-ext4@vger.kernel.org>,
	Andreas Dilger <adilger@clusterfs.com>,
	Theodore Tso <tytso@mit.edu>, Mingming Cao <cmm@us.ibm.com>
Subject: Re: [PATCH] Journal Checksum - rebased to 2.6.22-rc5
Date: Fri, 22 Jun 2007 11:05:06 -0500	[thread overview]
Message-ID: <1182528306.10740.7.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <1182504986.3788.18.camel@dhcp7.linsyssoft.com>

On Fri, 2007-06-22 at 15:06 +0530, Girish Shilamkar wrote:
> --- linux-2.6.22-rc5.orig/fs/jbd2/journal.c
> +++ linux-2.6.22-rc5/fs/jbd2/journal.c
> @@ -1272,6 +1272,33 @@ int jbd2_journal_set_features (journal_t
>         return 1;
>  }
> 
> +/**
> + * int jbd2_journal_clear_features () - Clear a given journal feature
> in the superblock
> + * @journal: Journal to act on.
> + * @compat: bitmask of compatible features
> + * @ro: bitmask of features that force read-only mount
> + * @incompat: bitmask of incompatible features
> + *
> + * Clear a given journal feature as present on the
> + * superblock.  Returns true if the requested features could be
> reset.
> + *
> + */
> +int jbd2_journal_clear_features (journal_t *journal, unsigned long
> compat,
> +                         unsigned long ro, unsigned long incompat)
> +{
> +       journal_superblock_t *sb;
> +
> +       jbd_debug(1, "Clear features 0x%lx/0x%lx/0x%lx\n",
> +                 compat, ro, incompat);
> +
> +       sb = journal->j_superblock;
> +
> +       sb->s_feature_compat    &= ~cpu_to_be32(compat);
> +       sb->s_feature_ro_compat &= ~cpu_to_be32(ro);
> +       sb->s_feature_incompat  &= ~cpu_to_be32(incompat);
> +
> +       return 1;
> +} 

This needs an EXPORT_SYMBOL(jbd2_journal_clear_features).  Otherwise,
ext4 can't be built as a module.
-- 
David Kleikamp
IBM Linux Technology Center

  reply	other threads:[~2007-06-22 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22  9:36 [PATCH] Journal Checksum - rebased to 2.6.22-rc5 Girish Shilamkar
2007-06-22 16:05 ` Dave Kleikamp [this message]
2007-06-23  5:43   ` Girish Shilamkar
2007-06-26 10:47 ` Girish Shilamkar
2007-06-26 14:13   ` Dave Kleikamp

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=1182528306.10740.7.camel@kleikamp.austin.ibm.com \
    --to=shaggy@linux.vnet.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=cmm@us.ibm.com \
    --cc=girish@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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