The new issue was discussed upstream already [1] and has a PR [2] this is targetted at v2.5, but we might pick just the fix [3] for now.
[1]: https://github.com/seccomp/libseccomp/issues/184 [2]: https://github.com/seccomp/libseccomp/pull/182 [3]: https://github.com/seccomp/libseccomp/pull/182/commits/35803ceb43c453762a3ab5177c5f8d5dbb813478
The new issue was discussed upstream already [1] and has a PR [2] this is targetted at v2.5, but we might pick just the fix [3] for now.
[1]: https:/ /github. com/seccomp/ libseccomp/ issues/ 184 /github. com/seccomp/ libseccomp/ pull/182 /github. com/seccomp/ libseccomp/ pull/182/ commits/ 35803ceb43c4537 62a3ab5177c5f8d 5dbb813478
[2]: https:/
[3]: https:/