-
Notifications
You must be signed in to change notification settings - Fork 243
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
sssd_flush_cache() errors ignored #1221
Comments
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 21, 2025
All callers ignore it. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 21, 2025
All callers ignore it. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 21, 2025
All callers ignore it. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 21, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 21, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 21, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 21, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 22, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 22, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 22, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 23, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 23, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 23, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 23, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 23, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Feb 23, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Mar 3, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Mar 4, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this issue
Mar 4, 2025
Being a macro, the unused return value triggers a diagnostic. This probably needs further investigation, but we have the issue linked below for that. Link: <shadow-maint#1221> Signed-off-by: Alejandro Colomar <alx@kernel.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
shadow/lib/sssd.c
Line 41 in 40bb89b
shadow/lib/sssd.h
Line 13 in 40bb89b
This function (actually the macro when it's not being compiled) triggered an error while enabling
-Werror=all
, due to (all) callers ignoring the return value. Do we need to care about that return value when this function fails?Cc: @jhrozek
The text was updated successfully, but these errors were encountered: