* [PATCH] Allow rt_sigqueueinfo and rt_tgsigqueueinfo to use si_code == SI_ASYNCIO
@ 2011-03-28 18:24 Roland Dreier
2011-03-28 17:42 ` Oleg Nesterov
0 siblings, 1 reply; 3+ messages in thread
From: Roland Dreier @ 2011-03-28 18:24 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, Oleg Nesterov, Julien Tinnes, Klaus Dittrich
From: Roland Dreier <roland@purestorage.com>
Commit da48524eb206 ("Prevent rt_sigqueueinfo and rt_tgsigqueueinfo
from spoofing the signal code") made the check on si_code too strict:
glibc's aio implementation wants to queue signals with SI_ASYNCIO, and
indeed glibc's tst-aio4 fails with the patched kernel.
Fix this by loosening the new check to allow SI_ASYNCIO as well.
Reported-by: Klaus Dittrich <kladit@arcor.de>
Signed-off-by: Roland Dreier <roland@purestorage.com>
---
kernel/signal.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index 324eff5..b2bfa3a 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -2437,7 +2437,7 @@ SYSCALL_DEFINE3(rt_sigqueueinfo, pid_t, pid, int, sig,
/* Not even root can pretend to send signals from the kernel.
* Nor can they impersonate a kill()/tgkill(), which adds source info.
*/
- if (info.si_code != SI_QUEUE) {
+ if (info.si_code != SI_QUEUE && info.si_code != SI_ASYNCIO) {
/* We used to allow any < 0 si_code */
WARN_ON_ONCE(info.si_code < 0);
return -EPERM;
@@ -2457,7 +2457,7 @@ long do_rt_tgsigqueueinfo(pid_t tgid, pid_t pid, int sig, siginfo_t *info)
/* Not even root can pretend to send signals from the kernel.
* Nor can they impersonate a kill()/tgkill(), which adds source info.
*/
- if (info->si_code != SI_QUEUE) {
+ if (info->si_code != SI_QUEUE && info->si_code != SI_ASYNCIO) {
/* We used to allow any < 0 si_code */
WARN_ON_ONCE(info->si_code < 0);
return -EPERM;
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH] Allow rt_sigqueueinfo and rt_tgsigqueueinfo to use si_code == SI_ASYNCIO
2011-03-28 18:24 [PATCH] Allow rt_sigqueueinfo and rt_tgsigqueueinfo to use si_code == SI_ASYNCIO Roland Dreier
@ 2011-03-28 17:42 ` Oleg Nesterov
2011-03-28 20:27 ` Roland Dreier
0 siblings, 1 reply; 3+ messages in thread
From: Oleg Nesterov @ 2011-03-28 17:42 UTC (permalink / raw)
To: Roland Dreier; +Cc: Linus Torvalds, linux-kernel, Julien Tinnes, Klaus Dittrich
On 03/28, Roland Dreier wrote:
>
> Commit da48524eb206 ("Prevent rt_sigqueueinfo and rt_tgsigqueueinfo
> from spoofing the signal code") made the check on si_code too strict:
> glibc's aio implementation wants to queue signals with SI_ASYNCIO, and
> indeed glibc's tst-aio4 fails with the patched kernel.
>
> Fix this by loosening the new check to allow SI_ASYNCIO as well.
Heh.
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2437,7 +2437,7 @@ SYSCALL_DEFINE3(rt_sigqueueinfo, pid_t, pid, int, sig,
> /* Not even root can pretend to send signals from the kernel.
> * Nor can they impersonate a kill()/tgkill(), which adds source info.
> */
> - if (info.si_code != SI_QUEUE) {
> + if (info.si_code != SI_QUEUE && info.si_code != SI_ASYNCIO) {
I am starting to think that "plan B" was better.
if (info.si_code >= 0 || info.si_code == SI_TKILL)
return -EPERM;
Although we should probably keep WARN_ON_ONCE() anyway.
Oleg.
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH] Allow rt_sigqueueinfo and rt_tgsigqueueinfo to use si_code == SI_ASYNCIO
2011-03-28 17:42 ` Oleg Nesterov
@ 2011-03-28 20:27 ` Roland Dreier
0 siblings, 0 replies; 3+ messages in thread
From: Roland Dreier @ 2011-03-28 20:27 UTC (permalink / raw)
To: Oleg Nesterov; +Cc: Linus Torvalds, linux-kernel, Julien Tinnes, Klaus Dittrich
On Mon, Mar 28, 2011 at 10:42 AM, Oleg Nesterov <oleg@redhat.com> wrote:
> I am starting to think that "plan B" was better.
>
> if (info.si_code >= 0 || info.si_code == SI_TKILL)
> return -EPERM;
Indeed. Grepping further in glibc finds sysdeps/unix/sysv/linux/aio_sigqueue.c:
/* We must pass the information about the data in a siginfo_t
value. */
info.si_signo = timer->event.sigev_signo;
info.si_code = SI_TIMER;
info.si_pid = timer->creator_pid;
info.si_uid = getuid ();
info.si_value = timer->event.sigev_value;
INLINE_SYSCALL (rt_sigqueueinfo, 3, info.si_pid, info.si_signo, &info);
and sysdeps/unix/sysv/linux/gai_sigqueue.c:
/* We must pass the information about the data in a siginfo_t value. */
info.si_signo = sig;
info.si_code = SI_ASYNCNL;
info.si_pid = caller_pid;
info.si_uid = __getuid ();
info.si_value = val;
return INLINE_SYSCALL (rt_sigqueueinfo, 3, info.si_pid,
sig, __ptrvalue (&info));
where SI_ASYNCNL is -60, which the kernel doesn't know about.
Updated patch coming in a minute.
Thanks,
Roland
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-03-28 20:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-28 18:24 [PATCH] Allow rt_sigqueueinfo and rt_tgsigqueueinfo to use si_code == SI_ASYNCIO Roland Dreier
2011-03-28 17:42 ` Oleg Nesterov
2011-03-28 20:27 ` Roland Dreier
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox