From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] multiple pings cause panic
Date: Sun, 18 Apr 2010 20:27:32 -0400 [thread overview]
Message-ID: <ba655f19e2c16143d49aa4aa34cc1b9f@kw.quanstro.net> (raw)
In-Reply-To: <bd3b88825b4af6d308914bfb485c6efc@gmx.de>
> made a patch that changes the panic into a print:
>
> /n/sources/patch/devip-allconvused-panic
i'm not sure that's what one wants, in general.
depending on the protocol and the use case, you may
want to
(a) panic
(b) print (carefully)
(c) wait for the resource to become available.
i'd be afraid of transforming a simple, automaticly
recoverable problem into something that just wedges
the machine with prints to the console and no progress.
i've never seen a machine panic for this reason.
- erik
next prev parent reply other threads:[~2010-04-19 0:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 19:36 James Chapman
2010-04-18 20:32 ` erik quanstrom
2010-04-18 20:54 ` James Chapman
2010-04-18 21:19 ` erik quanstrom
2010-04-18 20:39 ` geoff
2010-04-18 23:52 ` erik quanstrom
2010-04-19 0:23 ` cinap_lenrek
2010-04-19 0:27 ` erik quanstrom [this message]
2010-04-19 1:19 ` cinap_lenrek
2010-04-19 1:27 ` andrey mirtchovski
2010-04-19 2:53 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ba655f19e2c16143d49aa4aa34cc1b9f@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).