Bugtraq mailing list archives
Re: local users can panic linux kernel (was: SuSE syslogdadvisory)
From: mouse () RODENTS MONTREAL QC CA (der Mouse)
Date: Wed, 24 Nov 1999 12:53:28 -0500
As long as syslog uses a connected socket (which it does), and doesn't flag MSG_NOWAIT (which it doesn't), there isn't anything in the kernel source that looks like the code will fail under cpu/memory/whatever contention.
That's *heavily* OS-dependent. Not all implementations of AF_LOCAL sockets work the same.
Just because UDP datagrams are unreliable that doesn't mean that UNIX datagrams are too.
True. But don't forget either that just because one implementation of AF_LOCAL actually is reliable doesn't mean that they all are. (Though if AF_LOCAL sockets are reliable, they should be SOCK_RDM rather than SOCK_DGRAM, I think.) der Mouse mouse () rodents montreal qc ca 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Current thread:
- Re: local users can panic linux kernel (was: SuSE syslogdadvisory) A. Steinmetz (Nov 24)
- Re: local users can panic linux kernel (was: SuSE syslogdadvisory) Paul Boyer (Nov 24)
- [w00giving '99 #7]: UnixWare 7's xlock Matt Conover (Nov 25)
- <Possible follow-ups>
- Re: local users can panic linux kernel (was: SuSE syslogdadvisory) der Mouse (Nov 24)
- Re: local users can panic linux kernel (was: SuSE syslogdadvisory) Alessandro Rubini (Nov 26)