Re: stability problems

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Wed, Mar 16, 2011 at 02:34:32PM +0100, Thomas Klausner wrote:
> I've now got a reproducible case where it does that: When I'm running
> the tests for m4-1.4.16 in my bulk build tmpfs sandbox.
> 
> Since after two times I was expecting it, I got a (handcopied)
> backtrace now:
> 
> vmem_alloc() at netbsd:vmem_alloc+0x38
> tmpfs_alloc_node() at netbsd:tmpfs_alloc_node+0x232
> tmpfs_alloc_file() at netbsd:tmpfs_alloc_file+0xb0
> VOP_SYMLINK() at netbsd:VOP_SYMLINK+0x71
> do_sys_symlink() at netbsd:do_sys_symlink+0x16a
> syscall() at netbsd:syscall+0xaa

pooka pointed out to me that this might be the bug reported in
kern/43843 (tests/fs/vfs/t_vnops:symlink_zerolen) last year.

With a workaround patch by him, the problem disappears. Let's see how
this helps with the stability issues I was seeing (i.e. if this was
the reason for the other problems as well -- probably not, since the
issue is older.)
 Thomas