From: Oleg Nesterov <oleg@redhat.com>
To: Tycho Andersen <tycho@tycho.pizza>
Cc: coverity-bot <keescook@chromium.org>,
Christian Brauner <brauner@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Peng Zhang <zhangpeng.00@bytedance.com>,
Ard Biesheuvel <ardb@kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Suren Baghdasaryan <surenb@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mateusz Guzik <mjguzik@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Tycho Andersen <tandersen@netflix.com>,
Mike Christie <michael.christie@oracle.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: Coverity: __do_sys_pidfd_send_signal(): UNINIT
Date: Wed, 14 Feb 2024 10:03:33 +0100 [thread overview]
Message-ID: <20240214090332.GA14017@redhat.com> (raw)
In-Reply-To: <ZcwGua3a9Z8nJXVq@tycho.pizza>
On 02/13, Tycho Andersen wrote:
>
> I think this is a false positive, we have:
Agreed,
> That said, a default case wouldn't hurt, and we should fix the first
> comment anyways, since now we have extensions.
>
> I'm happy to send a patch or maybe it's better for Christian to fix it
> in-tree.
I leave this to you and Christian, whatever you prefer. But perhaps we
can simplify these checks? Something like below.
Oleg.
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -3876,10 +3876,6 @@ static struct pid *pidfd_to_pid(const struct file *file)
return tgid_pidfd_to_pid(file);
}
-#define PIDFD_SEND_SIGNAL_FLAGS \
- (PIDFD_SIGNAL_THREAD | PIDFD_SIGNAL_THREAD_GROUP | \
- PIDFD_SIGNAL_PROCESS_GROUP)
-
/**
* sys_pidfd_send_signal - Signal a process through a pidfd
* @pidfd: file descriptor of the process
@@ -3903,13 +3899,21 @@ SYSCALL_DEFINE4(pidfd_send_signal, int, pidfd, int, sig,
kernel_siginfo_t kinfo;
enum pid_type type;
- /* Enforce flags be set to 0 until we add an extension. */
- if (flags & ~PIDFD_SEND_SIGNAL_FLAGS)
- return -EINVAL;
-
- /* Ensure that only a single signal scope determining flag is set. */
- if (hweight32(flags & PIDFD_SEND_SIGNAL_FLAGS) > 1)
- return -EINVAL;
+ switch (flags) {
+ case 0:
+ /* but see the PIDFD_THREAD check below */
+ type = PIDTYPE_TGID;
+ break;
+ case PIDFD_SIGNAL_THREAD:
+ type = PIDTYPE_PID;
+ break;
+ case PIDFD_SIGNAL_THREAD_GROUP:
+ type = PIDTYPE_TGID;
+ break;
+ case PIDFD_SIGNAL_PROCESS_GROUP:
+ type = PIDTYPE_PGID;
+ break;
+ }
f = fdget(pidfd);
if (!f.file)
@@ -3926,24 +3930,8 @@ SYSCALL_DEFINE4(pidfd_send_signal, int, pidfd, int, sig,
if (!access_pidfd_pidns(pid))
goto err;
- switch (flags) {
- case 0:
- /* Infer scope from the type of pidfd. */
- if (f.file->f_flags & PIDFD_THREAD)
- type = PIDTYPE_PID;
- else
- type = PIDTYPE_TGID;
- break;
- case PIDFD_SIGNAL_THREAD:
+ if (!flags && (f.file->f_flags & PIDFD_THREAD))
type = PIDTYPE_PID;
- break;
- case PIDFD_SIGNAL_THREAD_GROUP:
- type = PIDTYPE_TGID;
- break;
- case PIDFD_SIGNAL_PROCESS_GROUP:
- type = PIDTYPE_PGID;
- break;
- }
if (info) {
ret = copy_siginfo_from_user_any(&kinfo, info);
next prev parent reply other threads:[~2024-02-14 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 23:59 Coverity: __do_sys_pidfd_send_signal(): UNINIT coverity-bot
2024-02-14 0:18 ` Tycho Andersen
2024-02-14 9:03 ` Oleg Nesterov [this message]
2024-02-14 9:06 ` Oleg Nesterov
2024-02-14 14:18 ` Tycho Andersen
2024-02-14 17:55 ` Oleg Nesterov
2024-02-14 18:11 ` Tycho Andersen
2024-02-14 19:18 ` Oleg Nesterov
2024-02-16 12:37 ` Christian Brauner
2024-02-14 18:51 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240214090332.GA14017@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=brauner@kernel.org \
--cc=dvyukov@google.com \
--cc=gustavo@embeddedor.com \
--cc=hca@linux.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=michael.christie@oracle.com \
--cc=mjguzik@gmail.com \
--cc=npiggin@gmail.com \
--cc=paulmck@kernel.org \
--cc=surenb@google.com \
--cc=tandersen@netflix.com \
--cc=tglx@linutronix.de \
--cc=tycho@tycho.pizza \
--cc=zhangpeng.00@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).