From owner-freebsd-current  Wed Oct 23  6: 9:11 2002
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 B15D037B401; Wed, 23 Oct 2002 06:09:10 -0700 (PDT)
Received: from MX3.estpak.ee (ld1.estpak.ee [194.126.101.98])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7066843E91; Wed, 23 Oct 2002 06:09:08 -0700 (PDT)
	(envelope-from kalts@estpak.ee)
Received: from tiiu.internal (adsl7332.estpak.ee [213.219.75.84])
	by MX3.estpak.ee (Postfix) with ESMTP
	id 7E0558802E; Wed, 23 Oct 2002 16:08:55 +0300 (EEST)
Received: from tiiu.internal (localhost [127.0.0.1])
	by tiiu.internal (8.12.6/8.12.6) with ESMTP id g9ND8ibj002522;
	Wed, 23 Oct 2002 16:08:44 +0300 (EEST)
	(envelope-from vallo@tiiu.internal)
Received: (from vallo@localhost)
	by tiiu.internal (8.12.6/8.12.6/Submit) id g9ND8b98002521;
	Wed, 23 Oct 2002 16:08:37 +0300 (EEST)
Date: Wed, 23 Oct 2002 16:08:37 +0300
From: Vallo Kallaste <kalts@estpak.ee>
To: John Baldwin <jhb@FreeBSD.org>
Cc: Maxime Henrion <mux@FreeBSD.org>,
	Vitaly Markitantov <vm@dics.com.ua>, current@FreeBSD.org
Subject: Re: smbfs broken?
Message-ID: <20021023130837.GA2504@tiiu.internal>
Reply-To: kalts@estpak.ee
References: <20021022180527.GA4048@tiiu.internal> <XFMail.20021022145143.jhb@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <XFMail.20021022145143.jhb@FreeBSD.org>
User-Agent: Mutt/1.5.1i-ja.1
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On Tue, Oct 22, 2002 at 02:51:43PM -0400, John Baldwin <jhb@FreeBSD.org> wrote:

[snip]
> As someone else has pointed out, it is executing at a garbage
> address which is why it panic'd.  My guess is that smb_smb_readx()
> called some function which had a buffer overflow of a variable on
> the stack and trashed the return address.
> 
> Actually, there are some bugs in the mbchains code.  I've just
> committed a possible fix.  Can you cvsup and try out revision
> 1.9 of subr_mchain.c and see if it works better?  Thanks.

The crash is gone, thanks.
-- 

Vallo Kallaste
kalts@estpak.ee

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message