Here are my latest logs. I don't include the verbatim output, just the
distilled version. First the lists split by local port, then the list in
order. Moving the whole stuff into libports added only 70s and 72s, it
seems.
TABLE BY LOCAL PORT
===
local port 311:
order bits
On Sun, Apr 01, 2001 at 06:14:27PM -0400, Roland McGrath wrote:
> > Ok. I put it in proc's demuxer, so we miss out anything that is processed
> > earlier. I will move the code into libproc before I do another test (and
> > increase the buffer a bit).
>
> That will have a better chance of catching
> > I gather from your data that what you mean is a buffer of the last 16
> > messages handled by proc's demuxer? In the general case one would would
> > want to track the reply messages too, and see if there is interleaving of
> > the RPCs, i.e. a second RPC beginning processing before another h
On Sun, Apr 01, 2001 at 03:46:03AM -0400, Roland McGrath wrote:
> > I have reproduced exactly the crash Jeff reported. I have collected the data.
> > I used a ring buffer of 16 entries (can increase if needed), and the full
>
> I gather from your data that what you mean is a buffer of the last 16
> Ok. I put it in proc's demuxer, so we miss out anything that is processed
> earlier. I will move the code into libproc before I do another test (and
> increase the buffer a bit).
That will have a better chance of catching the crash location, but
it still could easily be obscured if the corrupt
> I have added several convenience function and revised the source
> appropriately. It also uses a new calling convention making
> not checking for errors difficult, however, this is at the cost
> of ABI incompatibility, however, I feel that this is worth it.
I don't think this is a useful inter
> In io-revoke.c, we iterate over the protid class yet we inhibit
> all RPCs on the bucket. Why do we not just inhibit the class?
Inhibiting the bucket also prevents any other RPCs that might result in
creating a protid. Inhibiting the protid class would prevents RPCs made on
protid ports, but
In io-revoke.c, we iterate over the protid class yet we inhibit
all RPCs on the bucket. Why do we not just inhibit the class?
PGP signature
libdiskfs/io-interrupt.c is a dead file. It is still being compiled
into the library, thus:
Index: Makefile
===
RCS file: /cvs/hurd/libdiskfs/Makefile,v
retrieving revision 1.66
diff -u -r1.66 Makefile
--- Makefile2001/02/26 04:
On Sat, Mar 31, 2001 at 11:56:43PM -0500, Roland McGrath wrote:
> Thanks, I've applied these changes.
Sorry about that, you need this one also:
Index: Makefile
===
RCS file: /cvs/hurd/libnetfs/Makefile,v
retrieving revision 1.19
dif
On Sat, Mar 31, 2001 at 11:46:45PM -0500, Roland McGrath wrote:
> I don't understand what your option is supposed to do.
After looking at the code some more, my code adds nothing.
PGP signature
> Perhaps iohelp should have a convenience function to create an iouser
> for root, or any one-uid, one-gid iouser. Then those two places you
> mention would just have iohelp_create_iouser_oneid (0, 0) in their call
> to make_protid.
I have added several convenience function and revised the sour
> Anyway, I think the abstractions are bad. Basically, you separated the
> code by what was convienient to do.
I seperated the code by what was arch specific. I feel this is in
keeping with other projects namely libc.
> I think we should do something similar to the way disk.c and disk_*.c work
On Sun, Apr 01, 2001 at 03:46:03AM -0400, Roland McGrath wrote:
> > I have reproduced exactly the crash Jeff reported. I have collected the data.
> > I used a ring buffer of 16 entries (can increase if needed), and the full
>
> I gather from your data that what you mean is a buffer of the last 16
14 matches
Mail list logo
