From: "Walter Harms" <Walter.Harms@Informatik.Uni-Oldenburg.DE>
To: linux-kernel@vger.kernel.org
Cc: danielebellucci@libero.it
Subject: inconsistant use of pid_t and patches
Date: Fri, 2 May 2003 22:03:05 +0200 (MEST) [thread overview]
Message-ID: <E19BgkL-000Lzp-00@grossglockner.Informatik.Uni-Oldenburg.DE> (raw)
hi list,
we noticed that kernel_thread() returned diffent types. A quick
"grep -r kernel_thread() arch " will show pid_t, long and int
(for 2.4.20). So we started to clean up.
Everyone interessted can download the patches for 2.4.20 from
www.getenv.de/~walter
contact:
danielebellucci@libero.it
These are several patches. i dont want to bomb the ML so
no attachment to this mail.
As a first step we cleaned the definition in several architectures.
The changes are small as possible. Some architectures use pure asm
no understanding -> no changes
The following architectures have changed:
sh i386 mips mips64 s390x s390 ia64 m68k
changes occur in:
arch/<ARCH>/kernel/process.c
< change return type kernel_thread() to pid_t kernel_thread() >
include/asm-<ARCH>/processor.h
< add linux/types.h for pid_t >
< definiton change return type kernel_thread() to pid_t kernel_thread() >
additionaly we started to clean the kernel
rch/i386/kernel/ptrace.c:
changed type of sys_ptrace pid argument from to pid_t (original: long)
include/linux/fs.h:
changed type of pid member of struct fown_struct to pid_t (original: int)
fs/proc/base.c:
change type of pid variable in proc_pid_lookup to pid_t (original: unsigned int) [See Above]
include/linux/sched.h:
change type of find_task_by_pid argument (pid) from to pid_t (original: int)
kernel/capability.c:
in sys_capget: change type of pid variable to pid_t (original: int)
in sys_capset: change type of pid variable to pid_t (original: int)
kernel/signal.c:
in sys_tkill: changed type of pid argument to pid_t (original: int)
--
reply other threads:[~2003-05-02 19:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E19BgkL-000Lzp-00@grossglockner.Informatik.Uni-Oldenburg.DE \
--to=walter.harms@informatik.uni-oldenburg.de \
--cc=danielebellucci@libero.it \
--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;
as well as URLs for NNTP newsgroup(s).