From: Jan Kara <jack@suse.cz>
To: linux-ext4@vger.kernel.org
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] ext3 in-inode xattr handling fix for reserved inodes
Date: Tue, 14 Sep 2010 14:32:44 +0200 [thread overview]
Message-ID: <1284467566-12661-1-git-send-email-jack@suse.cz> (raw)
Hi,
the first patch in this series fixes a bug where we could lose extended
attributes for ino 11 if lost+found was deleted and inode used again.
The second patch makes kernel accept in-inode xattrs even for reserved
inodes if they look sane as Andreas suggested. This way we could in theory
remove the special casing sometime in future. I'm personally not convinced
this is worth the effort since the time when we could remove the special
casing is at least several years in future (for example I switch to 2.6.16
or even older kernels on our test machines) but I'm throwing the patch
in so that people can express their opinions...
Honza
next reply other threads:[~2010-09-14 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 12:32 Jan Kara [this message]
2010-09-14 12:32 ` [PATCH 1/2] ext3: Fix lost extented attributes for inode with ino == 11 Jan Kara
2010-09-14 21:36 ` Andreas Dilger
2010-09-14 12:32 ` [PATCH 2/2] ext3: Accept in-inode xattrs for reserved inodes Jan Kara
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=1284467566-12661-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox