From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Subject: Re: [RFC][PATCH 0/3] Process events biarch bug: Intro
Date: Tue, 27 Jun 2006 11:23:44 -0700 [thread overview]
Message-ID: <1151432624.1412.3.camel@linuxchandra> (raw)
In-Reply-To: <1151408822.21787.1807.camel@stark>
On Tue, 2006-06-27 at 04:47 -0700, Matt Helsley wrote:
> The events sent by Process Events from a 64-bit kernel are not binary compatible
> with what a 32-bit userspace program would expect to recieve because the timespec
> struct (used to send a timestamp) is not the same. This means that fields stored
> after the timestamp are offset and programs that don't take this into account
> break under these circumstances.
>
> This is a problem for 32-bit userspace programs running with 64-bit kernels on
> ppc64, s390, x86-64.. any "biarch" system.
>
> This series:
>
> 1 - Gives a name to the union of the process events structure so it may be used
> to work around the problem from userspace.
> 2 - Comments on the bug and describes a userspace workaround in
> Documentation/connector/process_events.txt
Above two options need the user space program to workaround the issue,
while assuming that the size of the data structure will never change (if
it ever changes, you break compatibility), which IMO is not very
appealing.
> 3 - Implements a second connector interface without the problem
> (Removing the old interface or changing the definition would break
> binary compatibility)
I think this is a better option if we want to fix the problem while
maintaining compatibility.
>
> Compiled, booted, and lightly tested.
>
> Comments or suggestions on alternate approaches would be appreciated.
>
> Cheers,
> -Matt Helsley
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------
prev parent reply other threads:[~2006-06-27 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 11:47 [RFC][PATCH 0/3] Process events biarch bug: Intro Matt Helsley
2006-06-27 12:33 ` Evgeniy Polyakov
2006-06-27 21:39 ` Matt Helsley
2006-06-28 5:49 ` Evgeniy Polyakov
2006-06-27 18:23 ` Chandra Seetharaman [this message]
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=1151432624.1412.3.camel@linuxchandra \
--to=sekharan@us.ibm.com \
--cc=guillaume.thouvenin@bull.net \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.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