attachment
0001-Ticket-601-multi-master-replication-allows-schema-vi.patch

{{{

299                         slapi_pblock_get(pb, SLAPI_MODIFY_MODS, &lmods); 
300                         slapi_mods_init_passin(&smods, mods); 
301                         slapi_mods_add_string (&smods, LDAP_MOD_ADD, ATTR_NSDS5_REPLCONFLICT, "Schema violation"); 
302                         lmods = slapi_mods_get_ldapmods_passout(&smods); 
303                         slapi_pblock_set(pb, SLAPI_MODIFY_MODS, lmods); 
304

}}}

Does this leak lmods? lmods is not freed, and it is overwritten.

good catch, it should have been:

slapi_mods_init_passin(&smods, lmods);

There is a problem with this solution. In fractional replication it might be accepted that on the consumer side entries can violate the schema because required attributes are not replicated.
This is itself problematic for fractional replication between masters, so I am not sure how to procede.

I verified that with the change in comment#8 there is no memory leak. lmods is taken from the pblock, slapimods_add_string it is reallocated an then set back to the pblock. The test was also run with valgrind and didn't show a leak.

After some discussion we cam to the conclusion that fractional replication should not be used to allow schema violations, so it is ok to check the schema for replicated mods.

Is it ok now to commit ?

$git merge ticket601
Updating 36f506d..d9f25b7
Fast-forward
ldap/servers/slapd/back-ldbm/ldbm_modify.c | 47 +++++++++++++++++++++++++++++++++++++++--------
ldap/servers/slapd/schema.c | 13 +++++++++++--
ldap/servers/slapd/slapi-plugin.h | 10 ++++++++++
3 files changed, 60 insertions(+), 10 deletions(-)
$ git push origin master
Counting objects: 17, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 2.21 KiB, done.
Total 9 (delta 7), reused 0 (delta 0)
To ssh://git.fedorahosted.org/git/389/ds.git
36f506d..d9f25b7 master -> master

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1044154

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/601

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.