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
Internal range searches using OP_FLAG_REVERSE_CANDIDATE_ORDER can crash the server #1189
Comments
Comment from mreynolds (@mreynolds389) at 2014-07-14 21:00:31 attachment |
Comment from mreynolds (@mreynolds389) at 2014-07-14 21:57:13 git merge ticket47858 git push origin master commit e6cee31 |
Comment from nhosoi (@nhosoi) at 2014-07-14 22:25:49 Hi Mark, Is this bug introduced with 47767, where OP_FLAG_REVERSE_CANDIDATE_ORDER flag is newly defined? |
Comment from mreynolds (@mreynolds389) at 2014-07-14 22:51:36 Replying to [comment:4 nhosoi]:
Yes it was. I only found the crash when I created an internal range search for ticket 47819. So there is no "real" regression at this point in time. As this was committed before ticket 47819 was - so no one is doing internal range searches (with reverse candidate ordering). The only way to verify this fix is to run the ticket47819_test.py script. |
Comment from mreynolds (@mreynolds389) at 2014-07-15 02:25:49 88aa59f..da318fa 389-ds-base-1.3.2 -> 389-ds-base-1.3.2 45dcda2..722117e 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 1dbf87a..7dc69db 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 |
Comment from spichugi (@droideck) at 2016-12-14 17:46:58 attachment |
Comment from firstyear (@Firstyear) at 2016-12-15 05:17:50 The code looks good and has my ack. I want to confirm that "without" the patch this causes the crash 100% of the time, and that with the patch this test passes? If that is the case, ack and commit! |
Comment from spichugi (@droideck) at 2016-12-16 11:41:53 By Mark information, it is enough to check a tombstone purge operation, because during this the internal search with OP_FLAG_REVERSE_CANDIDATE_ORDER flag happens. P.S. I've checked 6.9 with an old build (72), but no crash has happened. Maybe it is not 100% reproducible... |
Comment from spichugi (@droideck) at 2016-12-16 14:27:09 I've pushed it for now, because it is basic tombstone test suite functionality. We always can add more test cases. To ssh://git.fedorahosted.org/git/389/ds.git |
Comment from nhosoi (@nhosoi) at 2017-02-11 23:07:08 Metadata Update from @nhosoi:
|
Comment from mreynolds (@mreynolds389) at 2017-03-06 17:55:58 Simon can this be closed? |
Comment from mreynolds (@mreynolds389) at 2017-03-06 17:56:12 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2017-04-20 16:33:07 Metadata Update from @mreynolds389:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47858
Internal range searches using OP_FLAG_REVERSE_CANDIDATE_ORDER, that do not find any entries, can crash the server in ldbm_search().
This crash can not be reproduced externally. It was discovered while working on ticket 47819 which added an internal range search using the reverse candidates flag.
The text was updated successfully, but these errors were encountered: