public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: KaiGai Kohei <kaigai@ak.jp.nec.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 ACL problem.
Date: Fri, 14 Sep 2007 08:40:50 +0200	[thread overview]
Message-ID: <1189752050.3241.16.camel@shinybook.infradead.org> (raw)
In-Reply-To: <46EA2743.3090107@ak.jp.nec.com>

On Fri, 2007-09-14 at 15:16 +0900, KaiGai Kohei wrote:
> 
> The attached patch separate jffs2_init_acl() into two parts.
> 
> The one is jffs2_init_acl_pre() called from jffs2_new_inode().
> It compute ACL oriented inode->i_mode bits, and allocate in-memory ACL
> objects associated with the new inode just before when inode meta
> infomation is written to the medium.
> 
> The other is jffs2_init_acl_post() called from jffs2_symlink(),
> jffs2_mkdir(), jffs2_mknod() and jffs2_do_create().
> It actually writes in-memory ACL objects into the medium next to
> the success of writing meta-information.
> 
> In the current implementation, we have to write a same inode meta
> infomation twice when inode->i_mode is updated by the default ACL.
> However, we can avoid the behavior by putting an updated i_mode
> before it is written at first, as jffs2_init_acl_pre() doing.
> 
> Please review this patch.

At first glance, that looks much nicer than what I did -- thanks.

I should hopefully have some time later today to take a closer look and
merge it.

-- 
dwmw2

      reply	other threads:[~2007-09-14  6:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1186676611.7282.47.camel@shinybook.infradead.org>
     [not found] ` <46C9783D.4000503@ak.jp.nec.com>
     [not found]   ` <1187782861.22432.81.camel@pmac.infradead.org>
     [not found]     ` <46D25ECF.8090409@ak.jp.nec.com>
2007-09-14  6:16       ` JFFS2 ACL problem KaiGai Kohei
2007-09-14  6:40         ` David Woodhouse [this message]

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=1189752050.3241.16.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=kaigai@ak.jp.nec.com \
    --cc=linux-mtd@lists.infradead.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