From owner-freebsd-current@FreeBSD.ORG Wed Jun 16 13:03:47 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 7B15B16A4CE for ; Wed, 16 Jun 2004 13:03:47 +0000 (GMT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 045B143D5D for ; Wed, 16 Jun 2004 13:03:47 +0000 (GMT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Wed, 16 Jun 2004 09:03:39 -0400 Message-ID: From: Don Bowman To: 'Simon Barner' , current@freebsd.org Date: Wed, 16 Jun 2004 09:03:28 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Bogus signal handler causes kernel panic (5.2.1-p8/i386) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 16 Jun 2004 13:03:47 -0000 From: Simon Barner [mailto:barner@in.tum.de] > Hi, > > I tried the local denial of service attack described in [1], that was > reported for Linux 2.4 and 2.6 some days ago (see [2] for the original > thread in linux.kernel) on my FreeBSD 5.2.1-p8 system. > > The result is a kernel panic (back trace attached). > > Since des@ told me in a private mail, that he could not reprocduce the > panic on -CURRENT, I'd like to ask how to proceed from here. > > Is the problem known to be fixed in current? > Is somebody able to reproduce this on FreeBSD 5.2.1 (I am sorry, > upgrading to -CURRENT is out of question for me)? > > Please note, that the problem does not exist on FreeBSD 4.9 (the test > program simply dumps core (bt attached)). > > Thanks in advance for your hints, > Simon On current, this doesn't seem to do anything bad for me. --don