From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Girish Shilamkar <girish@linsyssoft.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: Tue, 26 Jun 2007 09:13:57 -0500 [thread overview]
Message-ID: <1182867237.11569.2.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <1182854850.3041.16.camel@dhcp7.linsyssoft.com>
On Tue, 2007-06-26 at 16:17 +0530, Girish Shilamkar wrote:
> On Fri, 2007-06-22 at 15:06 +0530, Girish Shilamkar wrote:
> > Hi,
> > The previous patch was an old one. Hence I am sending the latest patch
> > rebased to 2.6.22-rc5. I have also fixed few coding style issues in both
> > the patches.
> >
> > Regards,
> > Girish
> This patch had a bug. Thanks to Valerie for pointing it out.
I updated the patch queue with the updated patch and this fix.
Thanks,
Shaggy
> Regards,
> Girish.
>
> Index: linux-2.6.22-rc5/fs/jbd2/commit.c
> ===================================================================
> --- linux-2.6.22-rc5.orig/fs/jbd2/commit.c
> +++ linux-2.6.22-rc5/fs/jbd2/commit.c
> @@ -121,8 +121,8 @@ static int journal_submit_commit_record(
> bh = jh2bh(descriptor);
>
> for (i = 0; i < bh->b_size; i += 512) {
> - struct commit_header *tmp = (struct commit_header *)bh->b_data +
> - i;
> + struct commit_header *tmp = (struct commit_header *)(bh->b_data+
> + i);
> tmp->h_magic = cpu_to_be32(JBD2_MAGIC_NUMBER);
> tmp->h_blocktype = cpu_to_be32(JBD2_COMMIT_BLOCK);
> tmp->h_sequence = cpu_to_be32(commit_transaction->t_tid);
>
>
--
David Kleikamp
IBM Linux Technology Center
prev parent reply other threads:[~2007-06-26 14:14 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
2007-06-23 5:43 ` Girish Shilamkar
2007-06-26 10:47 ` Girish Shilamkar
2007-06-26 14:13 ` Dave Kleikamp [this message]
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=1182867237.11569.2.camel@kleikamp.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=adilger@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=girish@linsyssoft.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