synchronous signal in the blocked signal context

[Siddha, Suresh B]

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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/