From: Mingming Cao <cmm@us.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] clear extents flag on inodes created in ext4_mknod
Date: Mon, 18 Feb 2008 21:22:42 -0800 [thread overview]
Message-ID: <1203398562.3612.3.camel@localhost.localdomain> (raw)
In-Reply-To: <47B9F1F1.30604@redhat.com>
Acked and added to the patch queue.
On Mon, 2008-02-18 at 15:00 -0600, Eric Sandeen wrote:
> e2fsck doesn't expect to find char, block, fifo, or socket
> files with the extent flag set, so clear that in ext4_mknod.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> Index: linux-2.6.24/fs/ext4/namei.c
> ===================================================================
> --- linux-2.6.24.orig/fs/ext4/namei.c
> +++ linux-2.6.24/fs/ext4/namei.c
> @@ -1766,6 +1766,7 @@ retry:
> #ifdef CONFIG_EXT4DEV_FS_XATTR
> inode->i_op = &ext4_special_inode_operations;
> #endif
> + EXT4_I(inode)->i_flags &= ~EXT4_EXTENTS_FL;
> err = ext4_add_nondir(handle, dentry, inode);
> }
> ext4_journal_stop(handle);
>
>
> -
> 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
next prev parent reply other threads:[~2008-02-19 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 21:00 [PATCH] clear extents flag on inodes created in ext4_mknod Eric Sandeen
2008-02-19 5:22 ` Mingming Cao [this message]
2008-02-19 16:39 ` Eric Sandeen
2008-02-19 16:49 ` Aneesh Kumar K.V
2008-02-19 16:54 ` Eric Sandeen
2008-02-19 17:05 ` Aneesh Kumar K.V
2008-02-19 17:15 ` 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=1203398562.3612.3.camel@localhost.localdomain \
--to=cmm@us.ibm.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.