Date: Sun, 6 Oct 1996 13:16:08 -0400 (EDT) From: Gene Stark <gene@starkhome.cs.sunysb.edu> To: freebsd-bugs@freefall.freebsd.org Subject: Re: active bugs Message-ID: <199610061716.NAA22755@starkhome.cs.sunysb.edu>
next in thread | raw e-mail | index | archive | help
>Whatever happened to the service where I got sent a list of just those >bugs assigned to me? That was much more practical since I tend not to >be all that motivated to look over this list of 400+ problems when >it gets posted once a week - it's just too much. Also, for the rest of us "outsiders" without accounts on freefall, it would be helpful to be able to obtain the text of problem reports (this has come up before, but I haven't heard of a facility for this). Occasionally I have to fix some bug that is getting in the way of my getting something done, and I would like to know if the problem I am having is the same as one that has already been reported by somebody else, who maybe already fixed it but it didn't get committed. For example, a few weeks ago I posted a report about a hanging problem with the ft driver, together with a fix for that problem. That fix has just sat there, where it is pretty much unavailable to anybody else with the same problem. As another example, on my 2.1.5 systems I have experienced problems with crashes due to page faults in kernel mode from within getinoquota(). My latest information is that these get exercised by the popper port, which (at least under NFS) seems to create files with garbage UID's perhaps triggering the crash due to going out of bounds of an mmap()'ed quota file (pure speculation). If I got psyched to track this down in more detail, I would want to be able to scan the other reports of page faults in kernel mode to see if they might be related. How about it? - Gene Stark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610061716.NAA22755>