All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Andreas Dilger <adilger@sun.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/2] ext4: journal all modifications in ext4_xattr_set_handle
Date: Fri, 6 Nov 2009 21:33:41 -0500	[thread overview]
Message-ID: <20091107023341.GF26342@mit.edu> (raw)
In-Reply-To: <55C0D494-12AD-4EF7-8C35-411B2B5151EF@sun.com>

On Fri, Nov 06, 2009 at 05:22:51PM -0700, Andreas Dilger wrote:
> On 2009-11-06, at 15:35, Eric Sandeen wrote:
>> 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.
>>
>> Oh, and for those who haven't been following the bug, big
>> thanks to Chris Mason for helping to look into this and coming
>> up with the debugging patch that made it obvious...
>
> It would be great, IMHO, to have this debugging patch submitted to
> the kernel also, and enabled under a CONFIG option.

The debugging patch is only safe when the file system's block size ==
page size.  I suppose we could leave a warning in Kconfig that the
debugging option is only safe to be used when all of the file systems
in the system have a 4k (or whatever the page size happens to be)
block size, but it's probably better to clean up the patch so that
it's only enabled on a mount option, and then only if the file system
block size is the same as the page size.

> I'd also be interested to see the "write shadow buffer to journal"
> one-line patch that was discussed in the bug.

Which patch are you referring to?

					- Ted

  reply	other threads:[~2009-11-07  2:33 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 [this message]
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
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=20091107023341.GF26342@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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.