From owner-freebsd-current  Wed May  7 20:31:39 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id UAA04965
          for current-outgoing; Wed, 7 May 1997 20:31:39 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA04954;
          Wed, 7 May 1997 20:31:29 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id NAA01676; Thu, 8 May 1997 13:30:16 +1000
Date: Thu, 8 May 1997 13:30:16 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199705080330.NAA01676@godzilla.zeta.org.au>
To: current@FreeBSD.ORG, gena@NetVision.net.il
Subject: Re: Another panic
Cc: phk@FreeBSD.ORG
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I reported a panic problem a few days ago (see below). After some investigation
>i find out that i have a file with a very long filename (~220 characters). An
>attempt to "stat" this file caused the panic (and this is reproducible).
>I loaded old kernel and removed it. Anyway, i think it's a bug and it should be
>fixed.
>
>Stopped at _generic_bcopy+0x41:  repe movsl (%esi),%es:(%edi)
>-------------------trace--------------
>_generic_bcopy(f0797b80,f08f4680,f4145ed4,f06f40d8,f0797b80)

[cache_enter]

>_ufs_lookup+0xccc

It seems to be a classic sign extension bug.  nc_nlen has type char, so
it is unsuitable for storing name lengths longer than 127.  This probably
didn't matter until recently because NCHNAMLEN limited the lengths.  The
casts to (u_int) may have helped hide the problem.

Bruce