From owner-freebsd-current@FreeBSD.ORG Thu Jul 1 11:04:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDE3616A4CE for ; Thu, 1 Jul 2004 11:04:10 +0000 (GMT) Received: from smtp004.bizmail.sc5.yahoo.com (smtp004.bizmail.sc5.yahoo.com [66.163.175.81]) by mx1.FreeBSD.org (Postfix) with SMTP id BE80143D1D for ; Thu, 1 Jul 2004 11:04:10 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@70.240.179.20 with login) by smtp004.bizmail.sc5.yahoo.com with SMTP; 1 Jul 2004 11:02:34 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id A543F6247; Thu, 1 Jul 2004 06:02:33 -0500 (CDT) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 12229-06-2; Thu, 1 Jul 2004 06:02:32 -0500 (CDT) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id 03336624A; Thu, 1 Jul 2004 06:02:32 -0500 (CDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by compgeek.noacks.org (8.12.11/8.12.11) with ESMTP id i61B2VkU085451; Thu, 1 Jul 2004 06:02:31 -0500 (CDT) (envelope-from noackjr@alumni.rice.edu) Message-ID: <40E3EF47.5090007@alumni.rice.edu> Date: Thu, 01 Jul 2004 06:02:31 -0500 From: Jon Noack User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040629) X-Accept-Language: en-us, en MIME-Version: 1.0 To: noackjr@alumni.rice.edu References: <20040701061818.GA80579@lucky.net> <20040701063105.GA20785@xor.obsecurity.org> <200407011617.03053.doconnor@gsoft.com.au> <20040701083434.GA83951@atrbg11.informatik.tu-muenchen.de> <40E3DE2D.3020204@alumni.rice.edu> <20040701103535.GA84499@atrbg11.informatik.tu-muenchen.de> <40E3EBD2.2020106@alumni.rice.edu> In-Reply-To: <40E3EBD2.2020106@alumni.rice.edu> Content-Type: multipart/mixed; boundary="------------070209030904030509090107" X-Virus-Scanned: by amavisd-new at noacks.org cc: "Bjoern A. Zeeb" cc: FreeBSD current mailing list cc: Daniel Lang Subject: Re: LOR (vm object - swap_pager swhash) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2004 11:04:11 -0000 This is a multi-part message in MIME format. --------------070209030904030509090107 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit On 07/01/04 05:47, Jon Noack wrote: > On 07/01/04 05:35, Daniel Lang wrote: >> Jon Noack wrote on Thu, Jul 01, 2004 at 04:49:33AM -0500: >> [..] >> >>> Yes, but I think the idea was to get it put on the FreeBSD web site >>> first (Bjoern's been doing a great job, but it simplifies things a >>> lot to have it on the FreeBSD web site). I started working on this, >>> but [1]. >> [..] >> >> How about just creating a redirect from the FreeBSD.org website? >> >> So that in the lor-code the message will refer to s.th. like >> >> http://www.freebsd.org/doc/bla/blubb/lor.html >> >> and lor.html just contains a META redirect tag to Bjoern's site? >> >> So the message can be included right now, without mentioning >> Bjoern's site in the code. If Bjoern's page (or the content) >> is actually moved to the FreeBSD webserver, the redirect >> can simply be removed. > > > *banging head on wall* Perhaps when this infernal banging stops I'll be > able to come up with great ideas like this. > > Perhaps the best bet is to add a FAQ. The FAQ would point to Bjoern's > site and the LOR-message would point to the FAQ entry. Again, my docproj foo is weak, but see the attached FAQ. Jon --------------070209030904030509090107 Content-Type: text/plain; name="lor-faq.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="lor-faq.diff" Index: book.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/faq/book.sgml,v retrieving revision 1.626 diff -r1.626 book.sgml 4381a4382,4426 > > > > What is a lock order reversal? > > > > &a.rwatson; answered this question very succinctly on > the freebsd-current list in a thread entitled url="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=65165+0+/usr/local/www/db/text/2003/freebsd-current/20031221.freebsd-current">lock > order reversals - what do they mean? > >
> &a.rwatson; on freebsd-current, December 14, > 2003 > > These warnings are generated by Witness, a run-time lock > diagnostic system found in FreeBSD 5-CURRENT kernels (but > removed in releases). You can read more about Witness in the > WITNESS(4) man page, which talks about its capabilities. Among > other things, Witness performs run-time lock order verification > using a combination of hard coded lock orders, and run-time > detected lock orders, and generates console warnings when lock > orders are violated. The intent of this is to detect the > potential for deadlocks due to lock order violations; it's worth > observing that Witness is actually slightly conservative, and so > it's possible to get false positives. In the event that Witness > is accurately reporting a lock order problem, it's basically > saying "If you were unlucky, a deadlock would have happened > here". There are a couple of "well known" false positives, > which we need to do a better job of documenting to prevent > spurious reports. The non-well-known ones typically correspond > to bugs in newly added locking, as lock order reversals usually > get fixed pretty quickly because Witness is busy generating > warnings :-). > > > See url="http://sources.zabbadoz.net/freebsd/lor.html">Bjoern > Zeeb's lock order reversal page for the status of > known lock order reversals. > >
> > --------------070209030904030509090107--