)]}'
{"neutron/plugins/ml2/drivers/linuxbridge/agent/arp_protect.py":[{"author":{"_account_id":8655,"name":"Jakub Libosvar","email":"libosvar@redhat.com","username":"jlibosva"},"change_message_id":"69bc8f6f9a11b87ca59893b79b2f091ec4cec1fb","unresolved":false,"context_lines":[{"line_number":43,"context_line":"    _setup_arp_spoofing_protection(vif, port_details)"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"@lockutils.synchronized(\u0027ebtables\u0027)"},{"line_number":47,"context_line":"def _setup_arp_spoofing_protection(vif, port_details):"},{"line_number":48,"context_line":"    current_rules \u003d ebtables([\u0027-L\u0027]).splitlines()"},{"line_number":49,"context_line":"    _install_mac_spoofing_protection(vif, port_details, current_rules)"}],"source_content_type":"text/x-python","patch_set":3,"id":"7f231b9d_856133d6","line":46,"range":{"start_line":46,"start_character":11,"end_line":46,"end_character":23},"updated":"2017-06-15 09:21:40.000000000","message":"Is the in-memory lock enough for functional tests? Do we always run ebtables in isolation in namespaces?\n\nIf not then we should consider adding a hack to add an external\u003dTrue parameter for functional job to use file-lock.","commit_id":"6451e0750356b600ac01c13ac86eb556b2a616ee"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"d2372cc02d5d109d5beffc9862f467f6ea7e58f9","unresolved":false,"context_lines":[{"line_number":43,"context_line":"    _setup_arp_spoofing_protection(vif, port_details)"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"@lockutils.synchronized(\u0027ebtables\u0027)"},{"line_number":47,"context_line":"def _setup_arp_spoofing_protection(vif, port_details):"},{"line_number":48,"context_line":"    current_rules \u003d ebtables([\u0027-L\u0027]).splitlines()"},{"line_number":49,"context_line":"    _install_mac_spoofing_protection(vif, port_details, current_rules)"}],"source_content_type":"text/x-python","patch_set":3,"id":"7f231b9d_41cf7a55","line":46,"range":{"start_line":46,"start_character":11,"end_line":46,"end_character":23},"in_reply_to":"7f231b9d_856133d6","updated":"2017-06-15 20:42:28.000000000","message":"I guess the in-memory lock won\u0027t save them from each other, but the --concurrent should protect them from clobber other rules.\n\nMaybe the functional tests are fine since they are using unique vifs?","commit_id":"6451e0750356b600ac01c13ac86eb556b2a616ee"}]}
