Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 03 Jul 2008 13:30:24 -0700
From:      Doug Barton <dougb@FreeBSD.org>
To:        Kostik Belousov <kostikbel@gmail.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Panic using rsync to msdosfs filesystem
Message-ID:  <486D36E0.6080005@FreeBSD.org>
In-Reply-To: <20080703193856.GS17123@deviant.kiev.zoral.com.ua>
References:  <486BFFE5.1010808@FreeBSD.org> <20080703193856.GS17123@deviant.kiev.zoral.com.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
Kostik Belousov wrote:

> Looks like this is the first casuality of the -fstack-protector.

D'oh! I seem to have a talent for such things. :-/

> Try this:
> 
> diff --git a/sys/fs/msdosfs/msdosfs_vnops.c b/sys/fs/msdosfs/msdosfs_vnops.c
> index 8a1484f..fe673e0 100644
> --- a/sys/fs/msdosfs/msdosfs_vnops.c
> +++ b/sys/fs/msdosfs/msdosfs_vnops.c
> @@ -982,7 +982,7 @@ msdosfs_rename(ap)
>  	struct componentname *tcnp = ap->a_tcnp;
>  	struct componentname *fcnp = ap->a_fcnp;
>  	struct denode *ip, *xp, *dp, *zp;
> -	u_char toname[11], oldname[11];
> +	u_char toname[12], oldname[11];
>  	u_long from_diroffset, to_diroffset;
>  	u_char to_count;
>  	int doingdirectory = 0, newparent = 0;

So far so good! I managed to complete my rsync run with that patch in, 
and now I'm churning the disk with other stuff to make sure. So far so 
good!

Thanks for getting on this one so fast.

Doug

-- 

     This .signature sanitized for your protection




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?486D36E0.6080005>