Date: Thu, 2 Jun 2005 19:38:11 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Derek Kuli?ski <takeda@takeda.tk> Cc: freebsd-stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: stack backtrace Message-ID: <20050602233811.GE20397@xor.obsecurity.org> In-Reply-To: <1056775349.20050602162730@takeda.tk> References: <8910581751.20050529112956@takeda.tk> <20050602073739.GB2756@xor.obsecurity.org> <5010392255.20050602091123@takeda.tk> <20050602180654.GA59076@xor.obsecurity.org> <1056775349.20050602162730@takeda.tk>
next in thread | previous in thread | raw e-mail | index | archive | help
--k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 02, 2005 at 04:27:30PM -0700, Derek Kuli?ski wrote: > Hello Kris, >=20 > Thursday, June 2, 2005, 11:06:54 AM, you wrote: >=20 > >> > in 1.141 of ffs_softdep.c you added a call to backtrace() if bp->b_vp > >> > =3D=3D NULL..you removed it in current in 1.166, but some people are > >> > seeing it trigger on 5.x > >> So it's harmless? > > I don't know, but I presume the debugging code was added for debugging > > reasons :-) >=20 > Sorry, I didn't stated precise what I meant. > Since this code was triggered it means something went wrong, the > system didn't crash but I'm just wonder if something else could be > damaged. For me it looks like the problem was somewhere in the disk > writing code. It is clearly a condition the original author thought important to examine when it occurs, since he added the debugging code. Whether or not it indicates a problem I do not know. Kris --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCn5hjWry0BWjoQKURAuhXAJ96CvYDA2wBPcWszt6yRinjjl2mFACgg71T KL7BZg38y7lHs5HGjpCSSjo= =fr1Q -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050602233811.GE20397>