From owner-freebsd-bugs Sun Dec 5 18:10: 6 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 86CF814F1F for ; Sun, 5 Dec 1999 18:10:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id SAA44886; Sun, 5 Dec 1999 18:10:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 5 Dec 1999 18:10:01 -0800 (PST) Message-Id: <199912060210.SAA44886@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bosko Milekic Subject: Re: kern/10872: Panic in sorecieve() due to NULL mbuf pointer Reply-To: Bosko Milekic Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/10872; it has been noted by GNATS. From: Bosko Milekic To: freebsd-gnats-submit@freebsd.org Cc: Subject: Re: kern/10872: Panic in sorecieve() due to NULL mbuf pointer Date: Sun, 5 Dec 1999 21:00:43 -0500 (EST) (Appologies for the double-post... I don't believe the first post ended up in the correct place.) Bob, I'm looking through some related PRs, and I happened to stumble upon this one. It's certainly been a while since this was originally filed. Are you still experiencing this problem? I haven't been able to reproduce it on 4.0-CURRENT as of today (using the shell script you had originally provided). I'm thinking that initially, the problem could have been related to tacking something onto the sb in a fashion where the involved code in soreceive doesn't necessarily "notice" it, due to it running at a given priority level, where it can potentially be interrupted. This is a real shot in the dark and shouldn't be considered if you're no longer experiencing this problem. If, on the other hand, you are and are still willing to contribute to solving it, can you please acknowledge, and I would be interested in taking a shot at it as well. Later, Bosko. -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message