From: "Gustavo Fernando Padovan" <gustavo@las.ic.unicamp.br>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] kernel/signal.c: change vars pid and tgid types to pid_t
Date: Wed, 11 Jun 2008 20:11:01 -0300 [thread overview]
Message-ID: <6b53b1990806111611g1e9550d3q5abe1fe96b8ea99b@mail.gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 2162 bytes --]
Change the type of pid and tgid variables from int to the POSIX type pid_t.
Signed-off-by: Gustavo F. Padovan <gustavo@las.ic.unicamp.br>
--- a/kernel/signal.c 2008-06-09 23:45:49.000000000 -0300+++ b/kernel/signal.c 2008-06-09 23:52:36.000000000 -0300@@ -1120,7 +1120,7 @@ * is probably wrong. Should make it like BSD or SYSV. */
-static int kill_something_info(int sig, struct siginfo *info, int pid)+static int kill_something_info(int sig, struct siginfo *info, pid_t pid) { int ret;
@@ -2228,7 +2228,7 @@ }
asmlinkage long-sys_kill(int pid, int sig)+sys_kill(pid_t pid, int sig) { struct siginfo info;
@@ -2241,7 +2241,7 @@ return kill_something_info(sig, &info, pid); }
-static int do_tkill(int tgid, int pid, int sig)+static int do_tkill(pid_t tgid, pid_t pid, int sig) { int error; struct siginfo info;@@ -2284,7 +2284,7 @@ * exists but it's not belonging to the target process anymore. This * method solves the problem of threads exiting and PIDs getting reused. */-asmlinkage long sys_tgkill(int tgid, int pid, int sig)+asmlinkage long sys_tgkill(pid_t tgid, pid_t pid, int sig) { /* This is only valid for single tasks */ if (pid <= 0 || tgid <= 0)@@ -2297,7 +2297,7 @@ * Send a signal to only one task, even if it's a CLONE_THREAD task. */ asmlinkage long-sys_tkill(int pid, int sig)+sys_tkill(pid_t pid, int sig) { /* This is only valid for single tasks */ if (pid <= 0)@@ -2307,7 +2307,7 @@ }
asmlinkage long-sys_rt_sigqueueinfo(int pid, int sig, siginfo_t __user *uinfo)+sys_rt_sigqueueinfo(pid_t pid, int sig, siginfo_t __user *uinfo) { siginfo_t info;
-- ----------------------------------------------Gustavo Fernando PadovanEngenharia de Computação 2006LAS - Laboratório de Administração e Segurança de SistemasInstituto de Computação - UNICAMP
gfpadovan@gmail.comra061316@students.ic.unicamp.brpao@jabber.org-------------------------------------------
Seja Livre, use Software Livreÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2008-06-11 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 23:11 Gustavo Fernando Padovan [this message]
2008-06-25 7:07 Gustavo Fernando Padovan
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=6b53b1990806111611g1e9550d3q5abe1fe96b8ea99b@mail.gmail.com \
--to=gustavo@las.ic.unicamp.br \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®