public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug McNaught <doug@mcnaught.org>
To: "David D. Hagood" <wowbagger@sktc.net>
Cc: Valdis.Kletnieks@vt.edu, Michael Frank <mhf@linuxmail.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Dumb question: Why are exceptions such as SIGSEGV not logged
Date: 16 Aug 2003 19:17:29 -0400	[thread overview]
Message-ID: <m3oeypb3au.fsf@varsoon.wireboard.com> (raw)
In-Reply-To: "David D. Hagood"'s message of "Sat, 16 Aug 2003 18:06:34 -0500"

"David D. Hagood" <wowbagger@sktc.net> writes:

> Valdis.Kletnieks@vt.edu wrote:
> 
> > Consider this code:
> > 	char *foo = 0;
> > 	sigset(SIGSEGV,SIG_IGNORE);
> > 	for(;;) { *foo = '\5'; }
> > Your logfiles just got DoS'ed....
> 
> 
> Why not then just log uncaught exceptions?

You can still DoS by forking repeatedly and having the child die with
SEGV...

-Doug

  reply	other threads:[~2003-08-16 23:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-16 20:10 Dumb question: Why are exceptions such as SIGSEGV not logged Michael Frank
2003-08-16 20:49 ` Valdis.Kletnieks
2003-08-16 21:42   ` Jamie Lokier
2003-08-16 23:06   ` David D. Hagood
2003-08-16 23:17     ` Doug McNaught [this message]
2003-08-16 23:41       ` Dr. David Alan Gilbert
2003-08-17  8:17         ` Russell King
2003-08-16 23:49     ` Alan Cox
2003-08-17 20:54     ` Jakob Oestergaard
2003-08-18  4:28       ` Michael Frank
2003-08-18  9:15     ` David Schwartz
2003-08-19  2:43       ` H. Peter Anvin
2003-08-19 13:27         ` Jesse Pollard
2003-08-19 19:28         ` David Schwartz
2003-08-19 19:34           ` H. Peter Anvin
2003-08-19 20:01             ` David Schwartz
2003-08-18 14:31 ` William Lee Irwin III
2003-08-18 17:52   ` Michael Frank
     [not found] <lv8Y.2XU.9@gated-at.bofh.it>
     [not found] ` <lv8Y.2XU.11@gated-at.bofh.it>
     [not found]   ` <lv8Y.2XU.13@gated-at.bofh.it>
     [not found]     ` <lviD.35d.3@gated-at.bofh.it>
     [not found]       ` <lviD.35d.1@gated-at.bofh.it>
     [not found]         ` <lvC1.3p9.11@gated-at.bofh.it>
2003-08-17 14:29           ` Ihar 'Philips' Filipau
  -- strict thread matches above, loose matches on Subject: below --
2003-08-18  1:56 Hank Leininger
     [not found] <lg0i.6yo.11@gated-at.bofh.it>
     [not found] ` <lgjJ.6Oo.5@gated-at.bofh.it>
     [not found]   ` <lilr.p2.7@gated-at.bofh.it>
     [not found]     ` <livc.wX.17@gated-at.bofh.it>
2003-08-17 12:43       ` Ihar 'Philips' Filipau
     [not found]     ` <lj7O.14a.1@gated-at.bofh.it>
2003-08-17 12:52       ` Ihar 'Philips' Filipau
2003-08-17 13:09         ` Alan Cox
     [not found]     ` <lOll.3Jp.19@gated-at.bofh.it>
2003-08-18  9:34       ` Ihar 'Philips' Filipau
2003-08-18 17:26         ` David Schwartz
2003-08-18 20:50 Hank Leininger
2003-08-18 21:02 ` Mike Fedyk
2003-08-18 21:18   ` Hank Leininger
2003-08-18 21:25     ` Mike Fedyk
2003-08-18 22:12   ` William Lee Irwin III
2003-08-18 22:39   ` David Schwartz
2003-08-18 22:44     ` Mike Fedyk
2003-08-18 22:53       ` David Schwartz
2003-08-19  6:54     ` Denis Vlasenko
2003-08-19 14:52       ` Valdis.Kletnieks
2003-08-19 18:51       ` David Schwartz

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=m3oeypb3au.fsf@varsoon.wireboard.com \
    --to=doug@mcnaught.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@linuxmail.org \
    --cc=wowbagger@sktc.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