Date: Wed, 23 Oct 2002 18:00:14 +0200 From: Sheldon Hearn <sheldonh@starjuice.net> To: Vitaly Markitantov <vm@dics.com.ua> Cc: current@FreeBSD.ORG Subject: Re: smbfs broken? Message-ID: <20021023160014.GM661@starjuice.net> In-Reply-To: <20021023152144.GA10351@iron.del.local> References: <3DB664D0.FE0B8018@mindspring.com> <XFMail.20021023105107.jhb@FreeBSD.org> <20021023152144.GA10351@iron.del.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On (2002/10/23 18:21), Vitaly Markitantov wrote:
> > Umm, guys. The code was dereferencing NULL pointers in the mbchain
> > code which was fixed yesterday. Please test it out with the fixed
> > mbchains code.
>
> Yes, it not panics now, but again, when i copy to/from
> smbfs share i get:
>
> cp /share/someFile ./
> cp: ./someFile: Bad address
Confirmed with rev 1.9 of subr_mchain.c.
However, I notice that this only happens with files of 8145 bytes size
or larger.
[server]
# for i in `jot 512 7680`; do
dd if=/dev/zero of=$i bs=$i count=1
done 2>/dev/null
[client]
$ for i in `jot 512 7680`; do
cp /smb/urchin/pub/bytes/$i . || break;
done
cp: ./8145: Bad address
If I truss the cp process, I get this:
[...]
open("/smb/urchin/pub/bytes/8145",0x0,00) = 3 (0x3)
open("./8145",0x401,00) = 4 (0x4)
mmap(0x0,8145,0x1,0x1,3,0x0) = 671461376 (0x2805b000)
I don't have my laptop set up as a serial debugging client now, so
that's as far as I can go. :-(
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021023160014.GM661>