"David S. Miller" wrote:
> Date: Thu, 07 Sep 2000 14:36:02 -0700
> From: Jun Sun <email@example.com>
> Here is a small patch which is needed on non-i386 platforms.
> The layout of this structure is exported to userspace
> applications, thus you cannot simply just change the
> type in this structure to get the change you need.
> This change thus cannot be made as-is.
> You must find some other way, let me give you one example
> of a potentially acceptable solution:
> 1) Add new member to union inside of ifreq where ifmap
> currently lives. Add new member, perhaps called ifmap2
> which uses more appropriate types for base_addr member.
> 2) Add new ifreq call which looks at ifmap2 instead of ifmap.
> This way, existing userland applications still work as they
> did before hand, and new ones can be written to use the ifmap2
> version of the interface.
> Also be sure that the glibc maintainers get this change once it
> is in the kernel.
> David S. Miller
Hmm, that is a whole lot more complicated than I thought.
Do we know exactly what userland apps/libs use ifmap? Maybe the damage
is not so bad, so that we can fix this problem without making it look
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Sep 07 2000 - 21:00:32 EST