On Tuesday, June 03, 2014 07:20:52 PM Marcin Juszkiewicz wrote: > W dniu 02.06.2014 22:57, Paul Moore pisze: > > Thanks for posting this patch. If AArch64 is implemented properly in > > libseccomp the use of the open() syscall in the libseccomp tests would not > > cause an error. See the "__PNR_*" macros in libseccomp, aka our "pseudo- > > syscalls", for hints. > > So if architecture does not support syscall then table is populated with > __PNR_ macro (like "oldolduname" for example which is only on x86)?
Yes. > And for all syscalls which are missing (like "open" on AArch64) I should > create entries in syscalls table pointing entries to __PNR_ macros and > create new macros for those syscalls which do not have one defined. > > Am I right? Yes. You'll also need to make sure that any new syscalls introduced with AArch64 are also added to the other architectures as well, using the appropriate __PNR_* value. -- paul moore security and virtualization @ redhat ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ libseccomp-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libseccomp-discuss
