From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: add reserved blocks for root user
Date: Wed, 3 Jan 2018 14:46:27 +0800 [thread overview]
Message-ID: <b91cc440-0401-9818-4e37-2ef6d6cf602a@huawei.com> (raw)
In-Reply-To: <20180102192456.GA474@jaegeuk-macbookpro.roam.corp.google.com>
On 2018/1/3 3:24, Jaegeuk Kim wrote:
>> How about adding uid & gid verification also like ext4?
>
> Again, that's another feature which requires a mount option. I think it'd be
> better to add that, once we have a use-case.
That's OK. ;)
Thanks,
next prev parent reply other threads:[~2018-01-03 6:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 2:19 [PATCH] " Jaegeuk Kim
2017-12-29 7:55 ` Chao Yu
2018-01-01 1:24 ` [PATCH v2] " Jaegeuk Kim
2018-01-01 1:29 ` [PATCH v3] " Jaegeuk Kim
2018-01-02 6:25 ` [f2fs-dev] " Chao Yu
2018-01-02 19:24 ` Jaegeuk Kim
2018-01-03 6:46 ` Chao Yu [this message]
2018-01-02 19:27 ` [PATCH v4] " Jaegeuk Kim
2018-01-03 2:21 ` [PATCH v5] " Jaegeuk Kim
2018-01-03 6:45 ` [f2fs-dev] " Chao Yu
2018-01-03 19:06 ` Jaegeuk Kim
2018-01-04 1:16 ` Chao Yu
2018-01-04 6:02 ` Jaegeuk Kim
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=b91cc440-0401-9818-4e37-2ef6d6cf602a@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®