Date: Wed, 25 Apr 2007 21:05:34 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Oleg Derevenetz <oleg@vsi.ru> Cc: freebsd-stable@freebsd.org, LI Xin <delphij@delphij.net>, Kris Kennaway <kris@obsecurity.org> Subject: Re: How to report bugs (Re: 6.2-STABLE deadlock?) Message-ID: <20070426010534.GA79851@xor.obsecurity.org> In-Reply-To: <1177525225.462f9be9adad8@webmail.vsi.ru> References: <20070313140848.GA89182@steerpike.hanley.stade.co.uk> <20070423025631.GA33256@steerpike.hanley.stade.co.uk> <20070423113912.GE2052@deviant.kiev.zoral.com.ua> <462DDB4D.8080507@delphij.net> <1177442585.462e5919c71f0@webmail.vsi.ru> <462EC294.3040001@delphij.net> <20070425035316.GB44054@xor.obsecurity.org> <1177488860.462f0ddc6ce8c@webmail.vsi.ru> <20070425180843.GA72881@xor.obsecurity.org> <1177525225.462f9be9adad8@webmail.vsi.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 25, 2007 at 10:20:25PM +0400, Oleg Derevenetz wrote: > ??????? Kris Kennaway <kris@obsecurity.org>: >=20 > > On Wed, Apr 25, 2007 at 12:14:20PM +0400, Oleg Derevenetz wrote: > >=20 > > > > Until you (or a developer) have analyzed the resulting information, > > > > you cannot definitively determine whether or not your problem is > > the > > > > same as a given random other problem, and you may just confuse the > > > > issue by making claims of similarity when you are really reporting > > a > > > > completely separate problem. > > >=20 > > > Not all people can do deadlock debugging, though. In my case turning > > on=20 > > > INVARIANTS and WITNESS leads to unacceptable performance penalty due > > to heavily=20 > > > loaded server. So I can only describe my case, actions and result > > without=20 > > > providing any debug information. > >=20 > > But you can still do *some* things, e.g. backtraces and/or a coredump: > > every little bit helps. > >=20 > > Ultimately, though, you have to understand and accept that the less > > information you provide, the less chance there is that a developer > > will be able to track down your problem. In fact a developer may have > > to effectively ignore your problem report altogether, because of what > > I explained about "symptoms" usually not being enough to tell one bug > > from another. > >=20 > > In general, when you encounter a bug in FreeBSD, you have a little bit > > of work to do on your side before we can start doing the rest. I > > understand that you may not be in a position to do that work, but that > > means you also need to understand that we can't do it either. >=20 > In fact, I solved (or workarounded) this problem for me, so in this threa= d I=20 > provide my workaround as possible workaround for users that experiences t= he=20 > same problem. This only hint for them, and not a bugreport for you. I cou= ld not=20 > provide a full (or only partial) debug information because I will not bac= k out=20 > cvsuped sources, will not replace unionfs with nullfs again and will not = wait=20 > week or more for another stuck. OK. FYI I use nullfs on a few dozen heavily loaded machines without issue for the past year or so, so if you are seeing a nullfs issue it is probably an obscure one. Kris --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGL/reWry0BWjoQKURAulrAJ0dXyqN7XjbNLhdmqcVEyx4Q6tGNgCeL5Ob G4zIz5oDfPypSKTkxKdBSDA= =UNHB -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070426010534.GA79851>