NetBSD Problem Report #29527
From sjamaan@frohike.nvie.com Fri Feb 25 12:12:49 2005
Return-Path: <sjamaan@frohike.nvie.com>
Received: from hermes.uci.kun.nl (hermes.uci.kun.nl [131.174.93.58])
by narn.netbsd.org (Postfix) with ESMTP id 83CB363B400
for <gnats-bugs@gnats.NetBSD.org>; Fri, 25 Feb 2005 12:12:43 +0000 (UTC)
Message-Id: <20050225121109.7D0976B343@frohike.nvie.com>
Date: Fri, 25 Feb 2005 13:11:09 +0100 (CET)
From: Peter.Bex@student.kun.nl
Reply-To: Peter.Bex@student.kun.nl
To: gnats-bugs@netbsd.org
Subject: kern/uipc_socket2.c's sbdrop() panics
X-Send-Pr-Version: 3.95
>Number: 29527
>Category: kern
>Synopsis: sbdrop()'s code incorrect if len > 0, m == 0
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Feb 25 12:13:00 +0000 2005
>Originator: Peter Bex
>Release: NetBSD 2.0
>Organization:
>Environment:
System: NetBSD frohike.nvie.com 2.0 NetBSD 2.0 (FROHIKE) #0: Wed Dec 22 10:00:59 CET 2004 sjamaan@frohike.nvie.com:/usr/src/sys/arch/i386/compile/FROHIKE i386
Architecture: i386
Machine: i386
>Description:
My kernel panicked one day in sbdrop() from kern/uipc_socket2.c.
Looking at the code quickly (even though I don't _really_ understand
it) it looks like the function gets a len > 0 and sb of which
sb->sb_mb == 0 In this case we clearly get a panic.
Unfortunately, my sync request for ddb failed, causing another
problem, so I did another sync. This screwed up my core dump.
If necessary, I can provide it, though.
>How-To-Repeat:
Unknown. At the time two rather heavy bittorrent processes were
running, so I suspect it can occur on very heavy network load.
I had INET6 disabled, if it matters.
>Fix:
N/A
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.