From owner-svn-src-head@FreeBSD.ORG Mon Apr 16 21:29:41 2012 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 158331065672; Mon, 16 Apr 2012 21:29:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id C7D6D8FC12; Mon, 16 Apr 2012 21:29:40 +0000 (UTC) Received: by dadz14 with SMTP id z14so25028126dad.17 for ; Mon, 16 Apr 2012 14:29:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=1S/c8x13R0trSl964ZV5Zv5iU8CCHFlXYqVJZjkasfw=; b=du6a9vLampuejXN7Ul8romNJHMASY+PPnjhWoc0wpTr9rczH2Y6EicsCP4JtFzBHA7 lk1g9WDmfGh06FxQUlAtyByM7UPMdAoq9HBjvyi4kaChrdG97tj3wHJdlQ3+yIFghjUn N9T6+0XGy7TZiQ5wkmY29O2fKw46q2zUKwF7OteLwTTOm884JsWV7UmYiPm2znI/O+hi A71e+B0TunXvTyG/Lv0KIOXXksyPRn4CZeG/IsW7tKpoOnK3rIMFrRul29nwCAgEtkJV qkT8DmaFRGQcnaI+YcexBNvma/BB3kPs7Uj6vOxoypWWD4SwXzZdzNXl93mau2W7CW5H HFKg== MIME-Version: 1.0 Received: by 10.68.202.168 with SMTP id kj8mr30783615pbc.86.1334611780650; Mon, 16 Apr 2012 14:29:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.142.101.9 with HTTP; Mon, 16 Apr 2012 14:29:40 -0700 (PDT) In-Reply-To: <4F8BBD4E.1040106@FreeBSD.org> References: <201204060653.q366rwLa096182@svn.freebsd.org> <4F7E9413.20602@FreeBSD.org> <4F8BBD4E.1040106@FreeBSD.org> Date: Mon, 16 Apr 2012 14:29:40 -0700 X-Google-Sender-Auth: nBBpe069Sf7q0Mpb9opgifHk294 Message-ID: From: Adrian Chadd To: "Alexander V. Chernikov" Content-Type: text/plain; charset=ISO-8859-1 Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r233937 - in head/sys: kern net security/mac X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2012 21:29:41 -0000 On 15 April 2012 23:33, Alexander V. Chernikov wrote: > On 16.04.2012 01:17, Adrian Chadd wrote: >> >> Hi, >> >> This has broken (at least) net80211 and bpf, with LOR: > > Yes, it is. Please try the attached patch Hi, This seems like a very, very complicated diff. * You've removed BPF_LOCK_ASSERT() inside bpf_detachd_locked() - why'd you do that? * You removed a comment ("We're already protected by the global lock") which is still relevant/valid * There are lots of modifications to the read/write locks here - I'm not sure whether they're at all relevant to my immediate problem and may belong in separate commits Is there a document somewhere which describes what the "new" style BPF locking should be? I "just" added BPF_LOCK() / BPF_UNLOCK() around all the calls to bpf_detachd() which weren't locked (there were a few.) One final question - should the BPF global lock be recursive? thanks, Adrian