linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: gaoxiang25@huawei.com (Gao Xiang)
Subject: [PATCH v2 2/2] staging: erofs: complete POSIX ACL support
Date: Tue, 29 Jan 2019 16:03:34 +0800	[thread overview]
Message-ID: <8dbd81b4-48c2-4e0c-85c7-c3bfb12785ba@huawei.com> (raw)
In-Reply-To: <20190128183053.GK1795@kadam>

Hi,

On 2019/1/29 2:30, Dan Carpenter wrote:
> Are you serious?  The standard fault injection doesn't do that???
> 
> Please fix it instead of creating a duplicate better implementation
> which only your filesystem can use.  I would have thought that obviously
> any fault injection framework could at least be configured to test
> specific code...
> 
> regards,
> dan carpenter

Since Chao is now on the short business trip, I will resend v4 and change
erofs_kmalloc into kmalloc temporarily to make sure ACL is usable first
in the staging tree.

As for the EROFS fault injection, let's wait Chao's reply...

Thanks,
Gao Xiang

  reply	other threads:[~2019-01-29  8:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 16:10 [PATCH v2 1/2] staging: erofs: use xattr_prefix to wrap up Gao Xiang
2019-01-25 16:10 ` [PATCH v2 2/2] staging: erofs: complete POSIX ACL support Gao Xiang
2019-01-26  2:48   ` Chao Yu
2019-01-26  3:06     ` Gao Xiang
2019-01-28 13:33     ` Dan Carpenter
2019-01-28 13:48       ` Gao Xiang
2019-01-28 14:28         ` Dan Carpenter
2019-01-28 15:04           ` Gao Xiang
2019-01-28 16:41         ` Chao Yu
2019-01-28 18:30           ` Dan Carpenter
2019-01-29  8:03             ` Gao Xiang [this message]
2019-02-03  2:52             ` Chao Yu
2019-02-15  2:10               ` Chao Yu
2019-02-15  7:36                 ` Dan Carpenter
2019-02-15  9:31                   ` Chao Yu
2019-01-26  2:08 ` [PATCH v2 1/2] staging: erofs: use xattr_prefix to wrap up Chao Yu

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=8dbd81b4-48c2-4e0c-85c7-c3bfb12785ba@huawei.com \
    --to=gaoxiang25@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;
as well as URLs for NNTP newsgroup(s).