> I haven't checked your code, but make sure you call mach_msg_destroy
> on the bogon so that ports and ool memory get freed.
We do not need to; the message is not (yet) considered bogus.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org
I haven't checked your code, but make sure you call mach_msg_destroy
on the bogon so that ports and ool memory get freed.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Roland McGrath <[EMAIL PROTECTED]> writes:
> I haven't checked your code, but make sure you call mach_msg_destroy
> on the bogon so that ports and ool memory get freed.
No, that would be a mistake. The caller is responsible for doing that
if the message is not recognized by any demuxer. Since
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> I remember reading about this in the TODO list etc. Are there any concrete
> other unrobustnesses you remember?
There are a jillion. The filesystem basically assumes that it's
talking to the kernel. If it's not, then the user could be bollixing
t
On Thu, Jan 17, 2002 at 10:01:47AM -0800, Thomas Bushnell, BSG wrote:
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> > Neal reported this bug to me a while ago. If you send an invalid message (a
> > message with an unhandled msgid) to a pager, it will miss out on this msg id
> > and the seqno s
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> Neal reported this bug to me a while ago. If you send an invalid message (a
> message with an unhandled msgid) to a pager, it will miss out on this msg id
> and the seqno stuff doesn't catch up anymore. The result is a deadlock
> waiting for this m
Package: hurd
Version: n/a
Hi,
Neal reported this bug to me a while ago. If you send an invalid message (a
message with an unhandled msgid) to a pager, it will miss out on this msg id
and the seqno stuff doesn't catch up anymore. The result is a deadlock
waiting for this msg id when the next v
