Skip to content

Conversation

@pcmoore
Copy link
Member

@pcmoore pcmoore commented Nov 11, 2024

This is a backport of #435 with the syscall table generated specifically for the release-2.5 branch.

xen0n and others added 3 commits November 11, 2024 13:23
Apart from de-duplication of logic, this refactor is also going to help
syncing to the Linux 6.11+ definitions, where all architectures are
converted to source their syscall definitions from syscall.tbl files.

The change is tested on Linux 6.2 sources to not affect the generated
syscalls.csv apart from timestamp changes.

Signed-off-by: WANG Xuerui <git@xen0n.name>
Signed-off-by: Paul Moore <paul@paul-moore.com>
(imported from commit cfce7b0)
The aarch64, loongarch64 and riscv64 architectures have their syscall
table sources changed to scripts/syscall.tbl, from the original
inclusion of asm-generic/unistd.h. Make the script recognize the new
format for these architectures.

Signed-off-by: WANG Xuerui <git@xen0n.name>
Signed-off-by: Paul Moore <paul@paul-moore.com>
(imported from commit 26e2b31)
No direct cherry-pick from main due to supported architectures and
other changes.

Signed-off-by: Paul Moore <paul@paul-moore.com>
@coveralls
Copy link

Coverage Status

coverage: 89.523%. remained the same
when pulling 4830edc on pcmoore:working-release_25
into f0b04ab on seccomp:release-2.5.

Copy link
Contributor

@xen0n xen0n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the backport!

@UnconnectedBedna
Copy link

UnconnectedBedna commented Nov 27, 2024

GitHub milestones are used to track development and manage new releases. We do not currently follow a regular, calendar based release schedule; the libseccomp releases are determined by the number of outstanding issues and pull-requests assigned to the related GitHub milestone, when all of the outstanding items in the milestone have been closed, we create a new release.

https://github.com/seccomp/libseccomp/milestone/16
Does this mean this will not be in a release for a long time?
I have been waiting for a few weeks for a fix for my computer locking up 1min every time at boot.
Since yesterday, I can no longer even see what is going on at boot, it freezes immediately.

Everything seems to point towards libseccomp being the culprit.
I'm just a normal user, but I would like to know because if it will be longer (last release was in 2023 it seems? Version 2.5.5 - December 1, 2023) I have to uninstall software like opensnitch.

@drakenclimber
Copy link
Member

GitHub milestones are used to track development and manage new releases. We do not currently follow a regular, calendar based release schedule; the libseccomp releases are determined by the number of outstanding issues and pull-requests assigned to the related GitHub milestone, when all of the outstanding items in the milestone have been closed, we create a new release.

https://github.com/seccomp/libseccomp/milestone/16 Does this mean this will not be in a release for a long time?

Not necessarily. libseccomp is just one of many things that @pcmoore and I work on. Unfortunately for me (and likely @pcmoore as well), I have had higher priority tasks lately.

With that said, I think I can carve out some time over the next month or so, and I'm really hoping to make some progress on libseccomp issues. 🤞

@drakenclimber
Copy link
Member

Pushed to the release-2.5 branch. Thanks, @xen0n and @pcmoore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants