mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	marcello@acc.umu.se, cyeoh@samba.org, anton@samba.org,
	paulus@samba.org, davidm@hpl.hp.com,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: WRT SIGURG incorrectly delivered to process
Date: Wed, 8 May 2002 22:39:28 +0200	[thread overview]
Message-ID: <20020508223928.J9980@khan.acc.umu.se> (raw)

On, or about, April 18, Christopher Yeoh fixed a problem in the
v2.4-kernel where SIGURG got terminated incorrectly, in violation to
SuSv3. I intend to merge this fix into v2.0 as well, unless someone has
any objections.

However, I noticed that kernel/signal.c also contains similar code that
does not contain SIGURG (mangled whitespace):

(on line 1112 or thereabouts)

  if (k->sa.sa_handler == SIG_IGN
                    || (k->sa.sa_handler == SIG_DFL
                        && (sig == SIGCONT ||
                            sig == SIGCHLD ||
                            sig == SIGWINCH))) {
                        spin_lock_irq(&current->sigmask_lock);
                        if (rm_sig_from_queue(sig, current))
                                recalc_sigpending(current);
                        spin_unlock_irq(&current->sigmask_lock);
                }


Is this intentionally left this way, or did it get missed out by
mistake?!


Regards: David Weinehall
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Maintainer of the v2.0 kernel   //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

                 reply	other threads:[~2002-05-08 20:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020508223928.J9980@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=anton@samba.org \
    --cc=cyeoh@samba.org \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcello@acc.umu.se \
    --cc=paulus@samba.org \
    --cc=torvalds@transmeta.com \
    /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®