On Fri, 22 Sep 2000, Andi Kleen wrote:
>
> The problem is that the !SI_FROMUSER check in bad_signal() does not work
> properly, because SI_FROMUSER does not match the defined SI_* codes (it returns
> true for kernel generated signals). The result is that it always looks at
> current and what happens depends on the credentials of the current process
> (= random)
No. The current process is always the same one we send the signal to, so
that test ends up being irrelevant.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
- [PATCH] 2.4.0 i386 watchpoint problems James Cownie
- Re: [PATCH] 2.4.0 i386 watchpoint problems Linus Torvalds
- Re: [PATCH] 2.4.0 i386 watchpoint problems Linus Torvalds
- Re: [PATCH] 2.4.0 i386 watchpoint problems H. Peter Anvin
- Re: [PATCH] 2.4.0 i386 watchpoint problems James Cownie
- Re: [PATCH] 2.4.0 i386 watchpoint problems Linus Torvalds
- Re: [PATCH] 2.4.0 i386 watchpoint pro... Andi Kleen
- Re: [PATCH] 2.4.0 i386 watchpoint... Linus Torvalds
- Re: [PATCH] 2.4.0 i386 watchp... Andi Kleen
- Re: [PATCH] 2.4.0 i386 watchp... Linus Torvalds
- Re: [PATCH] 2.4.0 i386 watchp... Andi Kleen
- [ANOTHER PATCH] Re: [PATCH] 2... Andi Kleen
- Re: [ANOTHER PATCH] Re: [PATC... Linus Torvalds
- Re: [PATCH] 2.4.0 i386 watchp... Linus Torvalds
- Re: [PATCH] 2.4.0 i386 watchp... H. Peter Anvin
- Re: [PATCH] 2.4.0 i386 watchpoint pro... James Cownie

