fix errors in sigqueue (potential information leak, wrong behavior)
fix errors in sigqueue (potential information leak, wrong behavior)

1. any padding in the siginfo struct was not necessarily zero-filled,
so it might have contained private data off the caller's stack.

2. the uid and pid must be filled in from userspace. the previous
rsyscall fix broke rsyscalls because the values were always incorrect.

chardi/musl,chardi/musl,davidlazar/musl,rofl0r/musl-old,chneukirchen/musl-chris2,chneukirchen/musl-chris2,davidlazar/musl,rofl0r/musl-old,chardi/musl