From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: s_vfs_rename_sem and cifs (was Re: Possible deadlock in vfs layer, namei.c) Date: Thu, 2 Mar 2006 11:54:22 +0000 Message-ID: <20060302115422.GY27946@ftp.linux.org.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:37576 "EHLO ZenIV.linux.org.uk") by vger.kernel.org with ESMTP id S1750823AbWCBLyX (ORCPT ); Thu, 2 Mar 2006 06:54:23 -0500 To: Alexey Dobriyan Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Mar 02, 2006 at 03:47:50AM -0800, Alexey Dobriyan wrote: > On Wed, Mar 01, 2006 at 06:46:42PM -0800, Joshua Hudson wrote: > > from namei.c (function: lock_rename), rename takes: > > 1. s_vfs_rename_sem, > > Speaking of s_vfs_rename_sem, does cifs usage of it despite explicit > warning at fs.h > was found to be legal? Legal as in "works until anything changes in VFS-internal locking". Not legal as in "not promised to keep working". Dumb in all respects.