diff options
| author | Chandra Seetharaman <sekharan@us.ibm.com> | 2006-07-30 03:03:04 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-07-31 13:28:36 -0700 |
| commit | 822cfbff2ef49a08d1b9618d50f81b475d4f936c (patch) | |
| tree | 9b8bd37b3940410a13d0c439cc585d5aea1147ac /drivers/char/pc8736x_gpio.c | |
| parent | 2ccb48ebb4de139eef4fcefd5f2bb823cb0d81b9 (diff) | |
| download | kernel_samsung_smdk4412-822cfbff2ef49a08d1b9618d50f81b475d4f936c.tar.gz kernel_samsung_smdk4412-822cfbff2ef49a08d1b9618d50f81b475d4f936c.tar.bz2 kernel_samsung_smdk4412-822cfbff2ef49a08d1b9618d50f81b475d4f936c.zip | |
[PATCH] Process Events: Fix biarch compatibility issue. use __u64 timestamp
Events sent by Process Events Connector from a 64-bit kernel are not binary
compatible with a 32-bit userspace program because the "timestamp" field
(struct timespec) is not arch independent. This affects the fields that
follow "timestamp" as they will be be off by 8 bytes.
This is a problem for 32-bit userspace programs running with 64-bit kernels
on ppc64, s390, x86-64.. any "biarch" system.
Matt had submitted a different solution to lkml as an RFC earlier. We have
since switched to a solution recommended by Evgeniy Polyakov.
This patch fixes the problem by changing the timestamp to be a __u64, which
stores the number of nanoseconds.
Tested on a x86_64 system with both 32 bit application and 64 bit
application and on a i386 system.
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Matt Helsley <matthltc@us.ibm.com>
Cc: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'drivers/char/pc8736x_gpio.c')
0 files changed, 0 insertions, 0 deletions