All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/2] ext4: journal all modifications in ext4_xattr_set_handle
Date: Fri, 06 Nov 2009 19:00:48 -0600	[thread overview]
Message-ID: <4AF4C6C0.5080305@redhat.com> (raw)
In-Reply-To: <A7C68A34-99A5-4476-8545-10FA95E32EAD@sun.com>

Andreas Dilger wrote:
> On 2009-11-06, at 15:29, Eric Sandeen wrote:
>> ext4_xattr_set_handle() was modifying s_inode_size outside
>> of journaling constraints; this is one of the accesses that
>> was causing the crc errors in journal replay as seen in
>> kernel.org bugzilla #14354.
> 
> Is this description accurate?  It doesn't seem to be modifying 
> s_inode_size, per-se, but rather zeroing the whole inode if it is a new 
> inode that was never read from disk.

Doh, skimmed too fast, you're right. I'll resend a V2 w/ the proper 
description, sorry about that.  :)

-eric

> Other than the above description the patch looks correct.
> 
> Reviewed-by: Andreas Dilger <adilger@sun.com>
> 
>> @@ -988,6 +988,10 @@ ext4_xattr_set_handle(handle_t *handle, struct 
>> inode *inode, int name_index,
>>     if (error)
>>         goto cleanup;
>> +    error = ext4_journal_get_write_access(handle, is.iloc.bh);
>> +    if (error)
>> +        goto cleanup;
>> +
>>     if (EXT4_I(inode)->i_state & EXT4_STATE_NEW) {
>>         struct ext4_inode *raw_inode = ext4_raw_inode(&is.iloc);
>>         memset(raw_inode, 0, EXT4_SB(inode->i_sb)->s_inode_size);
>> @@ -1013,9 +1017,6 @@ ext4_xattr_set_handle(handle_t *handle, struct 
>> inode *inode, int name_index,
>>         if (flags & XATTR_CREATE)
>>             goto cleanup;
>>     }
>> -    error = ext4_journal_get_write_access(handle, is.iloc.bh);
>> -    if (error)
>> -        goto cleanup;
>>     if (!value) {
>>         if (!is.s.not_found)
>>             error = ext4_xattr_ibody_set(handle, inode, &i, &is);
>>
>> -- 
>> 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
> 
> 
> Cheers, Andreas
> -- 
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.
> 


  reply	other threads:[~2009-11-07  1:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06 22:29 [PATCH 1/2] ext4: journal all modifications in ext4_xattr_set_handle Eric Sandeen
2009-11-06 22:35 ` Eric Sandeen
2009-11-07  0:22   ` Andreas Dilger
2009-11-07  2:33     ` Theodore Tso
2009-11-07 19:22       ` Andreas Dilger
2009-11-07 19:31         ` Eric Sandeen
2009-11-07  0:18 ` Andreas Dilger
2009-11-07  1:00   ` Eric Sandeen [this message]
2009-11-07  1:03 ` [PATCH 1/2 V2] " Eric Sandeen

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=4AF4C6C0.5080305@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.