From: "David S. Miller" <davem@redhat.com>
To: macro@ds2.pg.gda.pl
Cc: dizzy@roedu.net, linux-kernel@vger.kernel.org
Subject: Re: mmap, SIGBUS, and handling it
Date: Fri, 10 May 2002 09:56:00 -0700 (PDT) [thread overview]
Message-ID: <20020510.095600.90795538.davem@redhat.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1020510183538.13449A-100000@delta.ds2.pg.gda.pl>
From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Date: Fri, 10 May 2002 19:03:19 +0200 (MET DST)
On Fri, 10 May 2002, David S. Miller wrote:
> If we reexecute the instruction it will take the signal endlessly,
> forever. That makes no sense.
It depends on an application. It certainly shouldn't be the default, but
a user may choose such an option for some reason. E.g. for debugging a
system with an ICE or a similar tool.
He's talking about how SIG_IGN should behave.
If you want non-default behavior, specify a signal handler instead
of SIG_IGN.
> So my original point I was trying to make, which still stands, is that
> what is being requested is totally rediculious behavior, trying to
> ignore a page fault that can't be serviced.
Why should we enforce policy on a user? If one wants to ignore such
signals for whatever reason, let him do that.
We don't specify any policy other than the behavior of SIG_IGN which
is to kill off the process for SIGBUS.
If you specify a handler you can have SIGBUS do whatever you want it
to. There are no enforced limitations, only a specified behavior
for SIG_IGN when used for SIGBUS.
The original poster has solved his problem, yet you continue to argue
one and on and on.
next prev parent reply other threads:[~2002-05-10 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 15:37 Mihai RUSU
2002-05-10 15:30 ` David S. Miller
2002-05-10 15:53 ` Maciej W. Rozycki
2002-05-10 15:47 ` David S. Miller
2002-05-10 17:03 ` Maciej W. Rozycki
2002-05-10 16:56 ` David S. Miller [this message]
2002-05-10 19:54 ` Maciej W. Rozycki
2002-05-10 15:56 ` Dave Gilbert (Home)
2002-05-10 15:48 ` David S. Miller
2002-05-10 16:04 ` Mihai RUSU
2002-05-11 13:27 ` Alex Riesen
2002-05-10 16:27 ` Alan Cox
2002-05-10 16:40 ` Mihai RUSU
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=20020510.095600.90795538.davem@redhat.com \
--to=davem@redhat.com \
--cc=dizzy@roedu.net \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
/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
all inboxes | Powered by JetHome®