Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: backport the transaction fixes to release-2.5 #442

Closed
wants to merge 2 commits into from

Conversation

pcmoore
Copy link
Member

@pcmoore pcmoore commented Dec 16, 2024

See the discussion in #415.

It turns out we don't properly handle transaction aborts as we should,
this likely broke when we implemented the shadow snapshots but as the
transaction concept was not exported via the API, and callers most
likely abandoned the filter on error this went unnoticed.

This patch ensures that transaction aborts are handled properly by
correctly managing the filter's transaction stack.

Signed-off-by: Paul Moore <paul@paul-moore.com>
Signed-off-by: Tom Hromatka <tom.hromatka@oracle.com>
(imported from commit 38c8670)
Signed-off-by: Paul Moore <paul@paul-moore.com>
Fix an off-by-one error that was causing us to leak a db_filter struct
at transaction commit time when we removed an arch/ABI in a transaction.

Reported-by: Tom Hromatka <tom.hromatka@oracle.com>
Signed-off-by: Paul Moore <paul@paul-moore.com>
Signed-off-by: Tom Hromatka <tom.hromatka@oracle.com>
(imported from commit 557a788)
Signed-off-by: Paul Moore <paul@paul-moore.com>
@pcmoore pcmoore added the bug label Dec 16, 2024
@pcmoore pcmoore added this to the v2.5.6 milestone Dec 16, 2024
@coveralls
Copy link

Coverage Status

coverage: 89.402% (-0.1%) from 89.523%
when pulling 33676bc on pcmoore:gh-415_backport
into 91d0fa0 on seccomp:release-2.5.

@drakenclimber
Copy link
Member

Pushed to release-2.5 branch in commits 424ee9a and 2fdc8dc. Thanks, @pcmoore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants