From: Marco Stornelli <marco.stornelli@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Vladimir Davydov <vdavydov@parallels.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 09/19] pramfs: inode operations for dirs
Date: Sat, 07 Sep 2013 18:17:41 +0200 [thread overview]
Message-ID: <522B51A5.4040003@gmail.com> (raw)
In-Reply-To: <20130907150857.GC13318@ZenIV.linux.org.uk>
Il 07/09/2013 17:08, Al Viro ha scritto:
> On Sat, Sep 07, 2013 at 10:23:42AM +0200, Marco Stornelli wrote:
>
>> +static int pram_rmdir(struct inode *dir, struct dentry *dentry)
>> +{
>> + struct inode *inode = dentry->d_inode;
>> + struct pram_inode *pi;
>> + int err = -ENOTEMPTY;
>> +
>> + if (!inode)
>> + return -ENOENT;
>> +
>> + pi = pram_get_inode(dir->i_sb, inode->i_ino);
>> +
>> + /* directory to delete is empty? */
>> + if (pi->i_type.dir.tail == 0) {
>> + inode->i_ctime = dir->i_ctime;
>> + inode->i_size = 0;
>> + clear_nlink(inode);
>> + pram_write_inode(inode, NULL);
>> + pram_dec_count(dir);
>> + err = 0;
>> + } else {
>> + pram_dbg("dir not empty\n");
>> + }
>> +
>> + return err;
>> +}
>
> ... and here you are paying for delayed removal of entries:
> mkdir foo
> touch foo/bar
> rm -rf foo <foo/bar
> will fail, since opened-and-unlinked file in effect keeps the directory
> where it used to be "not empty" from your rmdir (and rename) POV.
>
Yep. Same problem as before. I think I can move the remove link into
pram_dec_count and I have to modify the evict path, it should be easy to
manage.
Thanks for your comments Al!!!!
Marco
prev parent reply other threads:[~2013-09-07 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 8:23 [PATCH 09/19] pramfs: inode operations for dirs Marco Stornelli
2013-09-07 15:08 ` Al Viro
2013-09-07 16:17 ` Marco Stornelli [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=522B51A5.4040003@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vdavydov@parallels.com \
--cc=viro@ZenIV.linux.org.uk \
/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).