From owner-freebsd-bugs@FreeBSD.ORG Mon Oct 31 11:50:17 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BCD716A41F for ; Mon, 31 Oct 2005 11:50:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B1D943D4C for ; Mon, 31 Oct 2005 11:50:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j9VBoHJ0019833 for ; Mon, 31 Oct 2005 11:50:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j9VBoHNT019832; Mon, 31 Oct 2005 11:50:17 GMT (envelope-from gnats) Date: Mon, 31 Oct 2005 11:50:17 GMT Message-Id: <200510311150.j9VBoHNT019832@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Maxim Konovalov Cc: Subject: Re: kern/67919: Why nobody take serious to fix this bug? X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Maxim Konovalov List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 11:50:17 -0000 The following reply was made to PR kern/67919; it has been noted by GNATS. From: Maxim Konovalov To: "Cai, Quanqing" Cc: freebsd-current@freebsd.org, bug-followup@freebsd.org, Edwin Groothuis , Igor Sysoev , Uwe Doering Subject: Re: kern/67919: Why nobody take serious to fix this bug? Date: Mon, 31 Oct 2005 14:42:03 +0300 (MSK) 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