public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: paulmck@us.ibm.com, torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: synchronous signal in the blocked signal context
Date: Mon, 31 Jul 2006 19:14:49 -0700	[thread overview]
Message-ID: <20060731191449.B4592@unix-os.sc.intel.com> (raw)

This patch (b0423a0d9cc836b2c3d796623cd19236bfedfe63)

[PATCH] Remove duplicate code in signal.c

reverts a patch introduced by Linus long time back.

http://linux.bkbits.net:8080/linux-2.6/gnupatch@3f0621871mAhWfFZzuA74eKKLvE6OQ

Was this intentional?

With the current mainline code, SIGSEGV inside a SIGSEGV handler will endup
in linux handling endless recursive faults.

Just wondering if this has been discussed before and is intentional.

thanks,
suresh

             reply	other threads:[~2006-08-01  2:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01  2:14 Siddha, Suresh B [this message]
2006-08-01  4:54 ` synchronous signal in the blocked signal context Linus Torvalds
2006-08-01 14:44   ` Paul E. McKenney
2006-08-01 15:25     ` Linus Torvalds
2006-08-01 18:01       ` Siddha, Suresh B
2006-08-01 18:13       ` Paul E. McKenney
2006-08-01 18:13         ` Siddha, Suresh B
2006-08-01 19:01           ` Paul E. McKenney

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=20060731191449.B4592@unix-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --cc=torvalds@osdl.org \
    /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