From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 11:42:06 2005 Return-Path: X-Original-To: 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 A1CE216A420; Mon, 31 Oct 2005 11:42:06 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0833F43D45; Mon, 31 Oct 2005 11:42:05 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.13.3/8.13.3) with ESMTP id j9VBg35h092456; Mon, 31 Oct 2005 14:42:03 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Mon, 31 Oct 2005 14:42:03 +0300 (MSK) From: Maxim Konovalov To: "Cai, Quanqing" In-Reply-To: <2b22951e0510302128q571a3c1se111262e88ae19bb@mail.gmail.com> Message-ID: <20051031144056.A92356@mp2.macomnet.net> References: <2b22951e0510302128q571a3c1se111262e88ae19bb@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Igor Sysoev , Edwin Groothuis , freebsd-current@freebsd.org, Uwe Doering , bug-followup@freebsd.org Subject: Re: kern/67919: Why nobody take serious to fix this bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 11:42:06 -0000 On Sun, 30 Oct 2005, 21:28-0800, Cai, Quanqing wrote: > Today I happened to read this message on freebsd-stable: > http://lists.freebsd.org/pipermail/freebsd-stable/2005-October/019086.html > > After I read all messages and related links, I feel so frustrating, > why nobody take serious to fix this bug even we have a patch for it? > I can repeat this bug on 7.0-CURRENT and 6.0-RC1 easily as a normal > user! System goes no response so I have to power cycle it. The patch > made by Uwe Doering actually works well. This bug looks like a > security hole to me:( If you guys don't like this patch, please give > out a reason and come out a better patch or solution. I was told the patch is incorrect. It works in certain cases but incorrect in general. -- Maxim Konovalov