From owner-freebsd-current@FreeBSD.ORG  Thu Jul  1 12:17:48 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 5B89216A4CE
	for <current@freebsd.org>; Thu,  1 Jul 2004 12:17:48 +0000 (GMT)
Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3FB9B43D1F
	for <current@freebsd.org>; Thu,  1 Jul 2004 12:17:45 +0000 (GMT)
	(envelope-from rik@cronyx.ru)
Received: (from root@localhost) by hanoi.cronyx.ru
  id i61CE4Ek021506 for current@freebsd.org.checked; (8.12.8/vak/2.1)
  Thu, 1 Jul 2004 16:14:04 +0400 (MSD) (envelope-from rik@cronyx.ru)
Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru
	with ESMTP  id i61CBQNM021403; (8.12.8/vak/2.1)
	Thu, 1 Jul 2004 16:11:26 +0400 (MSD) (envelope-from rik@cronyx.ru)
Message-ID: <40E3FF50.5050909@cronyx.ru>
Date: Thu, 01 Jul 2004 16:10:56 +0400
From: Roman Kurakin <rik@cronyx.ru>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.6b) Gecko/20031208
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Lang <dl@leo.org>
References: <20040701061818.GA80579@lucky.net>
	<20040701063105.GA20785@xor.obsecurity.org>
	<200407011617.03053.doconnor@gsoft.com.au>
	<Pine.BSF.4.53.0407010706370.28103@e0-0.zab2.int.zabbadoz.net>
	<20040701083434.GA83951@atrbg11.informatik.tu-muenchen.de>
	<40E3DE2D.3020204@alumni.rice.edu>
	<20040701103535.GA84499@atrbg11.informatik.tu-muenchen.de>
In-Reply-To: <20040701103535.GA84499@atrbg11.informatik.tu-muenchen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
cc: FreeBSD current mailing list <current@freebsd.org>
Subject: Re: LOR (vm object - swap_pager swhash)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2004 12:17:48 -0000

Daniel Lang wrote:

>Hi,
>
>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 
>><insert lame excuse> [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
>  
>
I came to the same idea while reading current. But my idea is more concrete:

--- subr_witness.c.orig Thu Jul  1 08:41:54 2004
+++ subr_witness.c      Thu Jul  1 09:12:31 2004
@@ -853,6 +853,8 @@ witness_checkorder(struct lock_object *l
                         * Ok, yell about it.
                         */
                        printf("lock order reversal\n");
+                       printf("before reporting please examine http://"
+                               "http://www.freebsd.org/doc/en_US.ISO8859-1/"
+				"books/faq/book.html#LOCK-ORDER-REVERSAL\n");
                        /*
                         * Try to locate an earlier lock with
                         * witness w in our list.

rik

>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.
>  
>
>Cheers,
> Daniel
>  
>