From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 18 15:38:35 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB175106567A for ; Mon, 18 Aug 2008 15:38:35 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-gx0-f17.google.com (mail-gx0-f17.google.com [209.85.217.17]) by mx1.freebsd.org (Postfix) with ESMTP id 71BAC8FC08 for ; Mon, 18 Aug 2008 15:38:35 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by gxk10 with SMTP id 10so4298999gxk.19 for ; Mon, 18 Aug 2008 08:38:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=ka2yECww3vQ724PSKUitMl0MyWa+41xB+xF8q/gVfiY=; b=LKOp/qTVAY+8hrm4CxFBwaNKC0J9i9NLSosIn9D8VZ5ut0NN+Phk18QagoFbajylWX ao/hdv9G2G33C5bnradJ+m311KnP1tuchV2Yu7H7IYsq2mQH3s23wTgphoPrsVv2fplq U0YCxXwbX/NlVDhy3U6Q97tGOi9tOiNX5R54I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=TAuFK99J1rCEC9T2zt+I3/dVaTrUAhWfzz4adZBYurCmLodCOfLZmkuTeLjPKWBuBp hvaUZy3c+5pNAopymyYhiPR7CvN3MU6FhMIyiCt39KFcuBOvcRJGMVz2fecOK1EgxJ/D 1VH6f5Dn4ZGaGjOjnqdlUGBYCFo2jdCvof35s= Received: by 10.151.103.11 with SMTP id f11mr9868315ybm.190.1219072449218; Mon, 18 Aug 2008 08:14:09 -0700 (PDT) Received: by 10.150.225.21 with HTTP; Mon, 18 Aug 2008 08:14:01 -0700 (PDT) Message-ID: Date: Mon, 18 Aug 2008 11:14:01 -0400 From: "Ryan Stone" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 18 Aug 2008 15:50:00 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Acquiring a mtx after an sx lock X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2008 15:38:35 -0000 Are there any problems acquiring a sleep mutex after acquiring an sx lock? man 9 locking says that you can't, but doesn't provide any reasons. Obviously while you're holding the mutex you have to abide by the rules applying to mutexes, but as long as you do that, I can't see why acquiring a mutex after an sx lock would cause an issue. Is the locking man page wrong about this? Ryan Stone