pppd unaligned trap on Sparc/LEON3

Cudmore, Alan P. (GSFC-5820) alan.p.cudmore at nasa.gov
Thu Mar 7 14:55:24 UTC 2019

Hi Gedare,
I have a fix for the GetMask function. I will have to open a ticket and submit a patch.

I think the VxWorks BSP for the LEON processors provides a trap-and-emulate solution. While I hope that we can eliminate all possible unaligned traps, this would probably be worth adding to the Sparc/LEON BSPs as a safety net. Do any other architectures have this characteristic? RISC-V perhaps?


From: Gedare Bloom <gedare at rtems.org>
Date: Thursday, March 7, 2019 at 9:34 AM
To: Alan Cudmore <alan.p.cudmore at nasa.gov>
Cc: "rtems-devel at rtems.org" <devel at rtems.org>
Subject: Re: pppd unaligned trap on Sparc/LEON3

Hi Alan,

On Mon, Mar 4, 2019 at 2:34 PM Cudmore, Alan P. (GSFC-5820) <alan.p.cudmore at nasa.gov<mailto:alan.p.cudmore at nasa.gov>> wrote:
I’m trying to get PPP working on SPARC/LEON3. I’m currently using RTEMS 4.11, but plan on switching to 5.x soon.

While handshaking with a Linux PPP client, the LEON3 gets an unaligned memory trap in the GetMask function:
The second network interface returned by the ioctl(SIOGIFCONF) call is not aligned on a 4 byte boundary, so the pointer de-reference causes the trap.

It looks like this was referenced in ticket 1401:
NOTE: the caller, when unpacking the
sequence of ifreqs is likely to encounter
the same problem (see separate bug report
filed for pppd)

I could not find that ticket for pppd. Did anyone try to create a fix for this?
Is the best approach to try to fix the pppd GetMask function to avoid unaligned accesses?

Yes, the best approach would seem to be coercing the value into an aligned reference and then extracting the bits you want to get.

A general solution could also be to implement trap-and-emulate for unaligned data accesses. I started writing code like this (about 5 years ago!), it is about 20-30 hours of coding/testing to be confident about the result.  Existing code is available in netbsd for deriving the exception handler, so most of the effort is to extract, simplify, refactor, and test that code in rtems-sparc.



devel mailing list
devel at rtems.org<mailto:devel at rtems.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190307/363aef48/attachment-0002.html>

More information about the devel mailing list