NetBSD Problem Report #40313

From www@NetBSD.org  Thu Jan  1 16:42:43 2009
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id BD51A63B8C6
	for <gnats-bugs@gnats.netbsd.org>; Thu,  1 Jan 2009 16:42:43 +0000 (UTC)
Message-Id: <20090101164243.8217763B884@narn.NetBSD.org>
Date: Thu,  1 Jan 2009 16:42:43 +0000 (UTC)
From: pooka@iki.fi
Reply-To: pooka@iki.fi
To: gnats-bugs@NetBSD.org
Subject: puffs rename protocol is broken
X-Send-Pr-Version: www-1.0

>Number:         40313
>Category:       kern
>Synopsis:       puffs rename protocol is broken
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 01 16:45:00 +0000 2009
>Originator:     Antti Kantee
>Release:        
>Organization:
bug cookery inc.
>Environment:
>Description:
puffs file servers currently depend on the kernel vnode locking protocol.
However, rename is special in the sense that it doesn't protect the
source directory since it's not possible to hold two locks in a single
thread at the same time without knowing the directory layout
(i.e. without being the file system).

In case of a multithreaded or blocking (via puffs_cc) file server,
operations on the source directory are not automatically serialized.
>How-To-Repeat:
sauce meditation
>Fix:
Clarify and document the locking necessary in userspace.

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.