diff options
| author | avg <avg@FreeBSD.org> | 2011-07-25 09:12:48 +0000 |
|---|---|---|
| committer | avg <avg@FreeBSD.org> | 2011-07-25 09:12:48 +0000 |
| commit | 50b05401d3190631fb48430b4c0b48789f259b8d (patch) | |
| tree | ff97ee9903ea140928fcd9303e0d93873d3c2d2e /sys/netgraph/ng_ether.c | |
| parent | ffeefed9fc8fa85d3fcbd19640ba38e51e2ff4da (diff) | |
| download | FreeBSD-src-50b05401d3190631fb48430b4c0b48789f259b8d.zip FreeBSD-src-50b05401d3190631fb48430b4c0b48789f259b8d.tar.gz | |
remove RESTARTABLE_PANICS option
This is done per request/suggestion from John Baldwin
who introduced the option. Trying to resume normal
system operation after a panic is very unpredictable
and dangerous. It will become even more dangerous
when we allow a thread in panic(9) to penetrate all
lock contexts.
I understand that the only purpose of this option was
for testing scenarios potentially resulting in panic.
Suggested by: jhb
Reviewed by: attilio, jhb
X-MFC-After: never
Approved by: re (kib)
Diffstat (limited to 'sys/netgraph/ng_ether.c')
| -rw-r--r-- | sys/netgraph/ng_ether.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/sys/netgraph/ng_ether.c b/sys/netgraph/ng_ether.c index afedaa3..15e8b2d 100644 --- a/sys/netgraph/ng_ether.c +++ b/sys/netgraph/ng_ether.c @@ -604,9 +604,6 @@ ng_ether_rcvdata(hook_p hook, item_p item) NG_FREE_ITEM(item); panic("%s: weird hook", __func__); -#ifdef RESTARTABLE_PANICS /* so we don't get an error msg in LINT */ - return (0); -#endif } /* |
