Re: [PATCH] fs:lock_rename()/unlock_rename() can lead to deadlock in distributed fs.

On Mon, Jun 27, 2005 at 11:24:49AM +0200, Zuzana Petrova wrote:
> When lock_rename(new_dir, old_dir) is called, the dentries don't match, so we  
> end up in a code path that tries to acquire the inode i_sem of both the  
> old_dir and new_dir, but since they point to the same inode, the second  
> attempt to acquire the same i_sem results in a deadlock.  
>   
> A fix would be to compare the dentries ->d_inode field instead.  Patch for  
> kernel 2.6.12.1 attached.

No, that's bogus.  Make sure the filesystem never has multiple dentries
for the same directory inode.  
-
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/

---

• References:
  • [PATCH] fs:lock_rename()/unlock_rename() can lead to deadlock in distributed fs.
    • From: Zuzana Petrova <[email protected]>

• Prev by Date: Re: 2.6.12-mm2
• Next by Date: Re: reiser4 plugins
• Previous by thread: [PATCH] fs:lock_rename()/unlock_rename() can lead to deadlock in distributed fs.
• Next by thread: Re: [PATCH] fs:lock_rename()/unlock_rename() can lead to deadlock in distributed fs.
• 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]