Re: [PATCH 1/2] VFS: Make d_materialise_unique() enforce directory uniqueness

> From: Trond Myklebust <[email protected]>
> 
> If the caller tries to instantiate a directory using an inode that already
> has a dentry alias, then we attempt to rename the existing dentry instead
> of instantiating a new one. Fail with an ELOOP error if the rename would
> affect one of our parent directories.
> 
> This behaviour is needed in order to avoid issues such as
> 
>   http://bugzilla.kernel.org/show_bug.cgi?id=7178
>

This looks like a stale patch.  You posted one on -fsdevel that did
i_mutex locking as well.

Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 1/2] VFS: Make d_materialise_unique() enforce directory uniqueness
    • From: Trond Myklebust <[email protected]>

• References:
  • [PATCH 1/2] VFS: Make d_materialise_unique() enforce directory uniqueness
    • From: Trond Myklebust <[email protected]>

• Prev by Date: RE: Inspiron 6000 and CPU power saving
• Next by Date: Re: [PATCH 0/7] KVM: Kernel-based Virtual Machine
• Previous by thread: [PATCH 2/2] NFS: Cache invalidation fixup
• Next by thread: Re: [PATCH 1/2] VFS: Make d_materialise_unique() enforce directory uniqueness
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]