From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: make xattr extension work with new local alloc reservation.
Date: Fri, 09 Jul 2010 11:38:33 +0800 [thread overview]
Message-ID: <4C3699B9.3010204@oracle.com> (raw)
In-Reply-To: <20100708185134.GD17445@mail.oracle.com>
On 07/09/2010 02:51 AM, Joel Becker wrote:
> On Fri, Jun 18, 2010 at 11:02:50AM +0800, Tao Ma wrote:
>> @@ -735,8 +736,9 @@ static int ocfs2_xattr_extend_allocation(struct inode *inode,
>> ctxt->data_ac,
>> ctxt->meta_ac,
>> &why);
>
> Btw, this code was already buggy.
> ocfs2_xattr_extend_allocation() calls ocfs2_add_clusters_in_btree(),
> which can return with RESTART_TRANS just because the filesystem is
> fragmented. We would just fail with EAGAIN in that case, which makes no
> sense to a user.
> So this fix actually matters to older kernels and non-reflink
> operations too. Would you agree it should go to the stable tree? If
> so, add the Cc: to your commit message.
yes, the old kernel should be affected by this and we should have it in
stable tree.
But I just have one concern: should I add stable to cc list the first
time I create the patch? I am afraid not since it may be changed may
times and have many revisions.
So my suggestion is that we go on the normal process, and when my patch
get acked, I will resend it, add your ack and cc to stable. Agree? The
same goes to other's patches.
Regards,
Tao
next prev parent reply other threads:[~2010-07-09 3:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 3:00 [Ocfs2-devel] [PATCH 0/2] ocfs2: make xattr work with new local alloc reservation Tao Ma
2010-06-18 3:02 ` [Ocfs2-devel] [PATCH] ocfs2: make xattr extension " Tao Ma
2010-07-08 18:36 ` Joel Becker
2010-07-08 18:51 ` Joel Becker
2010-07-09 3:38 ` Tao Ma [this message]
2010-07-09 8:01 ` Joel Becker
2010-06-18 3:02 ` [Ocfs2-devel] [PATCH] ocfs2: Make xattr reflink " Tao Ma
2010-06-18 3:29 ` [Ocfs2-devel] [PATCH v2] " Tao Ma
2010-07-08 19:42 ` [Ocfs2-devel] [PATCH] " Joel Becker
2010-07-09 4:03 ` Tao Ma
2010-07-08 18:27 ` [Ocfs2-devel] [PATCH 0/2] ocfs2: make xattr " Joel Becker
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=4C3699B9.3010204@oracle.com \
--to=tao.ma@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).