From: Theodore Ts'o <tytso@mit.edu>
To: Wang Shilong <wshilong@ddn.com>
Cc: "miaoxie@huawei.com" <miaoxie@huawei.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Li Xi <lixi@ddn.com>, "yi.zhang@huawei.com" <yi.zhang@huawei.com>,
"adilger@dilger.ca" <adilger@dilger.ca>,
Shuichi Ihara <sihara@ddn.com>
Subject: Re: [PATCH 1/4] ext4: fix forgetten xattr lock protection in ext4_expand_extra_isize
Date: Thu, 13 Jul 2017 12:47:00 -0400 [thread overview]
Message-ID: <20170713164700.idfwntrzy2rvaagt@thunk.org> (raw)
In-Reply-To: <3ED34739A4E85E4F894367D57617CDEFE1DD2EEC@LAX-EX-MB2.datadirect.datadirectnet.com>
On Thu, Jul 13, 2017 at 01:04:08PM +0000, Wang Shilong wrote:
> I guess Maintainer will reply you when development cycle is ready for this.
> Please be patient Miao!, let's play Glory of the king.^^^_^^^
Sorry, this come in too late for it be included in the merge window,
since at that time I Was trying to do final regression testing before
sending a pull request to Linus.
I'm also currently on travel (attending Usenix ATC and visiting $WORK
in the Bay Area). I will start accumulating fixes soon, probably
shortly after 4.13-rc1 comes out. It *would* be helpful if other ext4
developers could review the patches while on travel (hint, hint).
Otherwise, I'll start reviewing patches in a week or two.
Cheers,
- Ted
next prev parent reply other threads:[~2017-07-13 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 17:09 [PATCH 1/4] ext4: fix forgetten xattr lock protection in ext4_expand_extra_isize Miao Xie
2017-07-06 17:09 ` [PATCH 2/4] ext4: restructure ext4_expand_extra_isize Miao Xie
2017-08-06 4:47 ` Theodore Ts'o
2017-07-06 17:09 ` [PATCH 3/4] ext4: cleanup ext4_expand_extra_isize_ea() Miao Xie
2017-08-06 4:56 ` Theodore Ts'o
2017-07-06 17:09 ` [PATCH 4/4] ext4, project: expand inode extra size if possible Miao Xie
2017-08-06 5:05 ` Theodore Ts'o
2017-07-13 12:55 ` [PATCH 1/4] ext4: fix forgetten xattr lock protection in ext4_expand_extra_isize Miao Xie
2017-07-13 13:04 ` Wang Shilong
2017-07-13 16:47 ` Theodore Ts'o [this message]
2017-08-06 4:28 ` Theodore Ts'o
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=20170713164700.idfwntrzy2rvaagt@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=lixi@ddn.com \
--cc=miaoxie@huawei.com \
--cc=sihara@ddn.com \
--cc=wshilong@ddn.com \
--cc=yi.zhang@huawei.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