Date: Sun, 11 May 2003 01:20:11 -0700 (PDT) From: Valentin Nechayev <netch@segfault.kiev.ua> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/51016: kernel panic: ufsdirhash_lookup: bad offset in hash array Message-ID: <200305110820.h4B8KBgB024958@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/51016; it has been noted by GNATS. From: Valentin Nechayev <netch@segfault.kiev.ua> To: Ted Mittelstaedt <tedm@toybox.placo.com> Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/51016: kernel panic: ufsdirhash_lookup: bad offset in hash array Date: Sun, 11 May 2003 11:13:49 +0300 Sat, May 10, 2003 at 11:50:12, tedm (Ted Mittelstaedt) wrote about "RE: kern/51016: kernel panic: ufsdirhash_lookup: bad offset in hash array": >>If some port can cause a system crash it's probably a kernel >>security bug and >>it's have to be fixed imho. In any case it can't be classified as port bug, as you suggested in previous letter, unless program has direct access to kernel memory or raw disks. I don't believe he run leafnode as root. TM> This is true if the port crashes on every FreeBSD system it TM> is tried on. Totally wrong. Problem can be triggered with specific config or specific running history. It even can be irreproduceable, if it can be diagnosed. If it is reproduceable, it can be diagnosed much easier. TM> However if your system is the only one that is TM> crashing then it's most likely something specific to your TM> system. This is also possible but you haven't *any* real arguments "pro" it. -netch-
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305110820.h4B8KBgB024958>