synchronous signal in the blocked signal context

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: synchronous signal in the blocked signal context
  - From: Linus Torvalds <[email protected]>

Prev by Date: Re: let md auto-detect 128+ raid members, fix potential race condition
Next by Date: + espfix-code-cleanup.patch added to -mm tree
Previous by thread: [PATCH] AUX_DEVICE_INFO is one byte long, use 'movb'
Next by thread: Re: synchronous signal in the blocked signal context
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]