Re: Panic: Memory modified after free

On Tue, Feb 01, 2005 at 04:06:13PM -0800, Kris Kennaway wrote:
> On Sun, Jan 30, 2005 at 10:46:16AM +0100, Peter Holm wrote:
> > With GENERIC HEAD from Jan 28 20:19 UTC +  mpsafe_vfs = 1 I got:
> > 
> > Memory modified after free 0xc1d7c100(124) val=c23fa000 _at_ 0xc1d7c164
> > 
> > panic(c083d005,c083b16e,c083cfd6,c1d7c100,7c) at panic+0xef
> > mtrash_ctor(c1d7c100,80,0,402) at mtrash_ctor+0x4d
> > uma_zalloc_arg(c10526e0,0,402) at uma_zalloc_arg+0x14c
> > malloc(68,c08bcd60,402,c094f0c0,0) at malloc+0xae
> > inodedep_lookup(c167a000,193a1,1,cf261be0,c094f0c0) at inodedep_lookup+0xa7
> > softdep_change_linkcnt(c213b578,c6bc54f0,c65f3f88,c213b578,c1c39270) at softdep_change_linkcnt+0x31
> > ufs_dirremove(c17d83a8,c213b578,100800c,0,cf261c48) at ufs_dirremove+0x12d
> > ufs_remove(cf261c4c) at ufs_remove+0x4b
> > VOP_REMOVE_AP(cf261c4c) at VOP_REMOVE_AP+0x62
> > kern_unlink(c1add2e0,bfbfe940,0,cf261d40,c07bd6c3) at kern_unlink+0x167
> > unlink(c1add2e0,cf261d14,1,28,292) at unlink+0x12
> > syscall(2804002f,bfbf002f,bfbf002f,2804f6c0,bfbfeb14) at syscall+0x213
> > 
> > More info at http://www.holm.cc/stress/log/cons112.html
> 
> > panic: Most recently used by inodedep
> 
> You can try to use DEBUG_MEMGUARD with M_INODEDEP to find this.  I'll
> add that to my SMP package machines to see if I can trigger it too.

Well, that didn't work:

panic: MEMGUARD: Cannot handle objects > PAGE_SIZE

CC'ing Bosko, the memguard author.

Kris