Should we consider multi syscall tables?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Just one of the recent bug fixes to the Linux Kernel API to keep Linux
user space api kind made me remember the freebsd multi syscall tables.

It was a case that someone developing a user space program had miss
read the api and sent size of data in bits instead of bytes.  Prior
Linux kernels disregarded this defect.  So one day kernel syscall was
fixed and application broke and now we have left overs in the kernel.

Multi syscall tables will allow these bugs to be fixed for all new
applications while allowing backwards support.  Defects become
deprecated functionality.

For containers it will allow emulation of other OS's by using a
syscall table that suits that OS.    This is more a open idea there
many be internal reasons why this is imposable that I cannot see.

Peter Dolding.
_______________________________________________
Containers mailing list
Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/containers

[Index of Archives]     [Cgroups]     [Netdev]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux