Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1084532
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Description of problem: We get segmentation faults like: Apr 2 08:09:38 sg001874 kernel: sssd_sudo[29215]: segfault at 751c3480 ip 000000365122730e sp 00007fffcc399638 error 4 in libdbus-1.so.3.4.0[3651200000+40000] Version-Release number of selected component (if applicable): libsss_sudo-1.9.2-129.el6_5.4.x86_64 sudo-1.8.6p3-12.el6.x86_64 How reproducible: Frequently on customer environment (after some minutes). Steps to Reproduce: Not clear Actual results: sssd_sudo segfaults Expected results: Normal operation Additional info:
Fields changed
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => owner: somebody => pbrezina review: True => 0 selected: => testsupdated: => 0
Colin Walters wrote:
Just how many entries are we expecting in "num_rules" here?
If for example it's over 255 or so, we're asking DBus to create an invalid message, because signatures (argument lists) can only have 255 elements. See: http://dbus.freedesktop.org/doc/dbus-specification.html
This is analogous to having a C function with 255 arguments.
What sssd should really be doing here is creating an "as" - an array of strings.
Good job tracking this down!
patch: 0 => 1
_comment0: * master: * dfef1d0 * sssd-1-11: * dfef1d0 => 1406203251674181 resolution: => fixed status: new => closed
Metadata Update from @lslebodn: - Issue assigned to pbrezina - Issue set to the milestone: NEEDS_TRIAGE
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3429
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.