From owner-freebsd-bugs  Sun Oct  6 10:16:43 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA00615
          for bugs-outgoing; Sun, 6 Oct 1996 10:16:43 -0700 (PDT)
Received: from bsd7.cs.sunysb.edu (bsd7.cs.sunysb.edu [130.245.1.197])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA00607
          for <freebsd-bugs@freefall.freebsd.org>; Sun, 6 Oct 1996 10:16:35 -0700 (PDT)
Received: (from uucp@localhost) by bsd7.cs.sunysb.edu (8.6.12/8.6.9) with UUCP id NAA15306 for freebsd-bugs@freefall.freebsd.org; Sun, 6 Oct 1996 13:16:27 -0400
Received: (from gene@localhost) by starkhome.cs.sunysb.edu (8.7.5/8.6.9) id NAA22755; Sun, 6 Oct 1996 13:16:08 -0400 (EDT)
Date: Sun, 6 Oct 1996 13:16:08 -0400 (EDT)
From: Gene Stark <gene@starkhome.cs.sunysb.edu>
Message-Id: <199610061716.NAA22755@starkhome.cs.sunysb.edu>
To: freebsd-bugs@freefall.freebsd.org
Subject: Re: active bugs
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>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