From owner-freebsd-current Wed Oct 15 13:20:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA24224 for current-outgoing; Wed, 15 Oct 1997 13:20:50 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA24197 for ; Wed, 15 Oct 1997 13:20:43 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA05596 for freebsd-current@FreeBSD.ORG; Wed, 15 Oct 1997 22:20:40 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id WAA13656; Wed, 15 Oct 1997 22:07:29 +0200 (MET DST) Message-ID: <19971015220729.AJ14379@uriah.heep.sax.de> Date: Wed, 15 Oct 1997 22:07:29 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG (FreeBSD-current users) Subject: Re: lockmgr panic References: <19971013230818.ZB55478@uriah.heep.sax.de> <1631.876811195@critter.freebsd.dk> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <1631.876811195@critter.freebsd.dk>; from Poul-Henning Kamp on Oct 14, 1997 08:39:55 +0200 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Poul-Henning Kamp wrote: > Joerg, I spent all of 30 minutes on this ting, and I just hacked it > together for a particular experiment, OK ? :-) Ja. Understood... but well, i don't mind seeing it becoming a real driver once it's a little more flexible. > I offered it here as a bandaid if release building was in trouble, > not as a solution for world poverty... :-) Speaking of bandaids, would anybody mind me committing Mr. KATO's fix/hack? (Of course, unless he's going to commit it himself.) The patch seems to solve the vn(4) lockmgr problem. I haven't made a release on a 2.2.5-BETA system lately. If the problem there is the same, i would vote for moving the fix there as well. It's only affecting to vn.c, so i figure it can't do much harm outside the vn driver (which is apparently broken enough anyway). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)