Amerigo Wang [xiyou.wangcong@xxxxxxxxx] wrote:
| On Wed, Jun 03, 2009 at 11:07:40PM -0400, Oren Laadan wrote:
| >On Tue, 2 Jun 2009, Sukadev Bhattiprolu wrote:
| >
| >> | >diff --git a/include/linux/types.h b/include/linux/types.h
| >> | >index 5abe354..17ec186 100644
| >> | >--- a/include/linux/types.h
| >> | >+++ b/include/linux/types.h
| >> | >@@ -204,6 +204,11 @@ struct ustat {
| >> | > char f_fpack[6];
| >> | > };
| >> | >
| >> | >+struct target_pid_set {
| >> | >+ int num_pids;
| >> | >+ pid_t *target_pids;
| >> | >+};
| >> | >+
| >> |
| >> | A quick question: why not putting this definition into
| >> | include/linux/pid.h?
| >>
| >> Well, the data structure needs to be visible to applications so I
| >> chose types.h since its already listed in fork(2) man page and the
| >> related type, 'pid_t' is defined there.
| >
| >I don't recall linux/types.h mentioned in the manpage.
|
| In fact, linux/types.h for userspace only has a few types
| for endians...
Hmm, user space's <linux/types.h> does not seem to be restricted to endianess.
On both RHEL5.2 and Ubuntu 7.10, I see fd_set, dev_t, ino_t etc. Lot of these
definitions correspond to what is in the kernel source's include/linux/types.h,
One difference though is in the kernel source tree, they are under
#ifdef __KERNEL__ while in user's linux/include, they are under
#ifndef __KERNEL_STRICT_NAMES.
I am trying to find out how new stuff in kernel's include/linux/types.h
ends up in user's <linux/types.h>. It may require a separate patch to
the kernel headers package.
|
| >
| >And, heh, it ended up within #ifdef __KERNEL__ there...
| >In fact, the types defined in that header are for kernel use.
|
| Yup, I believe Sukadev put it in a wrong position.
|
| Thanks.
_______________________________________________
Containers mailing list
Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/containers
