From: Al Viro <viro@ftp.linux.org.uk>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
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 [thread overview]
Message-ID: <20060302115422.GY27946@ftp.linux.org.uk> (raw)
In-Reply-To: <b6fcc0a0603020347r32567ae9l1fe4495059149449@mail.gmail.com>
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.
prev parent reply other threads:[~2006-03-02 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 11:47 s_vfs_rename_sem and cifs (was Re: Possible deadlock in vfs layer, namei.c) Alexey Dobriyan
2006-03-02 11:54 ` Al Viro [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=20060302115422.GY27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).