Re: [RFC PATCH] vfs: make rename_lock per-sb

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Miklos Szeredi <miklos@xxxxxxxxxx>
Subject: Re: [RFC PATCH] vfs: make rename_lock per-sb
From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Date: Sun, 8 Dec 2019 05:54:11 +0000
Cc: linux-fsdevel@xxxxxxxxxxxxxxx
In-reply-to: <20191128154858.GA16668@miu.piliscsaba.redhat.com>
User-agent: Mutt/1.12.1 (2019-06-15)

On Thu, Nov 28, 2019 at 04:48:58PM +0100, Miklos Szeredi wrote:

> Turning rename_lock into a per-sb lock mitigates the above issues.

... and completely fucks d_lookup(), since false negative can be
caused by rename of *ANYTHING* you've encountered while walking
a hash chain.

NAK.

Follow-Ups:
- Re: [RFC PATCH] vfs: make rename_lock per-sb
  - From: Miklos Szeredi

References:
- [RFC PATCH] vfs: make rename_lock per-sb
  - From: Miklos Szeredi

Prev by Date: Re: memory leak in fasync_helper
Next by Date: Re: [RFC] Thing 1: Shardmap fox Ext4
Previous by thread: [RFC PATCH] vfs: make rename_lock per-sb
Next by thread: Re: [RFC PATCH] vfs: make rename_lock per-sb
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux