Date: Mon, 21 Apr 1997 18:20:48 -0700 (PDT) From: Simon Shapiro <Shimon@i-Connect.Net> To: (Joerg Wunsch) <joerg_wunsch@uriah.heep.sax.de> Cc: freebsd-bugs@freebsd.org, (J Wunsch) <j@uriah.heep.sax.de> Subject: Re: Mystery of the X11 Panic... Message-ID: <XFMail.970421215527.Shimon@i-Connect.Net> In-Reply-To: <19970421152036.AM09487@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi J Wunsch; On 21-Apr-97 you wrote: > As David Greenman wrote: > > > >This means that cdevsw[maj]->d_open is bad (probably null) although > > >cdevsw[maj] != NULL. This might be caused by a buggy or stale LKM. > > Nope, Bruce: > > if ( (cdevsw[maj] == NULL) || (cdevsw[maj]->d_open == > NULL)) > ^^^^^^^^^^^^^^^^^^^ > return ENXIO; > > This case is tested, and it's actually this test itself that causes > the panic. > > > ...or it could be caused by the bug in kern_exec.c, which could have > > mangled adjacent buffers or possibly random kernel memory. It seems > > to involve bash and the kern_exec.c bug was triggered when running > small > > shell scripts. > > This seems more reasonable after reading that piece of code. > > Simon didn't tell us the faulting VA, but i bet it's not right NULL. No, i did not, but AFAICR it was not null. These are easier to spot. Even i can track these down ;-) Simon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.970421215527.Shimon>