active locks in released memory

Bug #782431 reported by Vladislav Vaintroub
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MariaDB
Fix Released
Medium
Vladislav Vaintroub
PBXT
Fix Committed
Undecided
Vladimir Kolesnikov

Bug Description

Found during MariaDB tests with application verifier:

xt_ind_exit() frees memory block pointed to by ind_cac_globals.cg_blocks, but does not free page locks in it, that are initialized using XT_IPAGE_INIT_LOCK(self, &block->cb_lock) in xt_ind_init().

This makes application verifier unhappy on 64 bit Windows.

  XTIndBlockPtr block = ind_cac_globals.cg_blocks;
  for (u_int i=0; i<ind_cac_globals.cg_block_count; i++) {
   XT_IPAGE_FREE_LOCK(self, &block->cb_lock);
   block++;
  }

Related branches

Revision history for this message
Vladislav Vaintroub (wlad-montyprogram) wrote :

the code at the end of bug report is meant to be the fix for it

Revision history for this message
Vladislav Vaintroub (wlad-montyprogram) wrote :

Fixed in MariaDB 5.2.7

Changed in maria:
assignee: nobody → Vladislav Vaintroub (wlad-montyprogram)
importance: Undecided → Medium
milestone: none → 5.2
status: New → Fix Released
Changed in pbxt:
assignee: nobody → Vladimir Kolesnikov (vkolesnikov)
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.