-
Notifications
You must be signed in to change notification settings - Fork 360
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
Sanitizer test #321
base: main
Are you sure you want to change the base?
Sanitizer test #321
Conversation
/cc @evverx |
@cgzones Looks like Regarding memory leaks, unfortunately there're a lot of them in the tests themselves so I think until they're fixed they probably shouldn't be reported so as not to clutter the output of the tests. |
Having said that, looking at the "raw" logs of the action I think it's more or less manageable so I'm going to have to take that back. |
b5471f7
to
5261491
Compare
844fb24
to
829f618
Compare
@cgzones I noticed that you sent the patches where all the issues found by ASan/UBsan were fixed to the mailing list. Are you planning to send the other commits later or should I just cherry-pick the two commits you added related to GHActions on top of my PR and send it myself? |
I'd appreciate if you could send them yourself. |
I'll squash the commits into one and send it to the mailing list once https://lore.kernel.org/selinux/[email protected]/T/#t is merged to keep the GHActions workflow green. Thanks! |
libsemanage/tests/test_ibendport.c
Outdated
@@ -362,6 +373,8 @@ void test_ibendport_modify_del_query_local(void) | |||
&ibendport_local) < 0); | |||
|
|||
/* cleanup */ | |||
semanage_ibendport_key_free(key); | |||
semanage_ibendport_free(ibendport_local); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cgzones This semanage_ibendport_free(ibendport_local);
should probably be moved after CU_ASSERT_PTR_NOT_NULL_FATAL(ibendport_local);
(a few lines up), as the variable is then used again in the test which checks that semanage_ibendport_query_local
fails,
CU_ASSERT(semanage_ibendport_query_local(sh, key,
&ibendport_local) < 0);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
true, I'll reorder this and the other affected free calls
libsemanage/tests/test_user.c
Outdated
@@ -577,6 +590,8 @@ void test_user_modify_del_query_local(void) | |||
CU_ASSERT(semanage_user_query_local(sh, key, &user_local) < 0); | |||
|
|||
/* cleanup */ | |||
semanage_user_key_free(key); | |||
semanage_user_free(user_local); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as 322243e#r730306247 here: semanage_user_free(user_local);
should be moved up a few lines, before CU_ASSERT(semanage_user_query_local(sh, key, &user_local) < 0);
libsemanage/tests/test_iface.c
Outdated
@@ -546,6 +567,8 @@ void test_iface_modify_del_query_local(void) | |||
CU_ASSERT(semanage_iface_query_local(sh, key, &iface_local) < 0); | |||
|
|||
/* cleanup */ | |||
semanage_iface_key_free(key); | |||
semanage_iface_free(iface_local); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as 322243e#r730306247 here: semanage_iface_free(iface_local);
should be moved up a few lines, before CU_ASSERT(semanage_iface_query_local(sh, key, &iface_local) < 0);
It was tested in SELinuxProject#321 and SELinuxProject#320. In the process it discovered a few issues all of which were fixed in SELinuxProject@b98d3c4 SELinuxProject@ea53901 SELinuxProject@fe01a91 SELinuxProject@f95dbf2 Now that all the issues are gone it should be safe to turn it on to make it easier to automatically catch bugs like that almost as soon as they end up in the repository. Signed-off-by: Evgeny Vereshchagin <[email protected]>
It was tested in SELinuxProject#321 and SELinuxProject#320. In the process it discovered a few issues all of which were fixed in SELinuxProject@b98d3c4 SELinuxProject@ea53901 SELinuxProject@fe01a91 SELinuxProject@f95dbf2 Now that all the issues are gone it should be safe to turn it on to make it easier to automatically catch bugs like that almost as soon as they end up in the repository. Signed-off-by: Evgeny Vereshchagin <[email protected]>
It was tested in #321 and #320. In the process it discovered a few issues all of which were fixed in b98d3c4 ea53901 fe01a91 f95dbf2 Now that all the issues are gone it should be safe to turn it on to make it easier to automatically catch bugs like that almost as soon as they end up in the repository. Signed-off-by: Evgeny Vereshchagin <[email protected]>
829f618
to
54c3dde
Compare
f557dab
to
a89dad1
Compare
a89dad1
to
3fc0f42
Compare
3fc0f42
to
7065496
Compare
It was tested in SELinuxProject/selinux#321 and SELinuxProject/selinux#320. In the process it discovered a few issues all of which were fixed in SELinuxProject/selinux@b98d3c4 SELinuxProject/selinux@ea53901 SELinuxProject/selinux@fe01a91 SELinuxProject/selinux@f95dbf2 Now that all the issues are gone it should be safe to turn it on to make it easier to automatically catch bugs like that almost as soon as they end up in the repository. Signed-off-by: Evgeny VereshchaGin <[email protected]>
343d13a
to
dc85199
Compare
Signed-off-by: Christian Göttsche <[email protected]>
Signed-off-by: Christian Göttsche <[email protected]>
Signed-off-by: Christian Göttsche <[email protected]>
Signed-off-by: Christian Göttsche <[email protected]>
Signed-off-by: Christian Göttsche <[email protected]>
Signed-off-by: Christian Göttsche <[email protected]>
Signed-off-by: Christian Göttsche <[email protected]>
Signed-off-by: Christian Göttsche <[email protected]>
dc85199
to
10de147
Compare
No description provided.