Custom Query (33 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (4 - 6 of 33)

1 2 3 4 5 6 7 8 9 10 11
Ticket Owner Reporter Resolution Summary
#33 jsoumagne jsoumagne fixed Add callback version of HG API
Description

Switch mercury to callback model.

#31 jsoumagne anonymous fixed Addr uninitialized
Description

After calling NA_Addr_lookup_wait to fill an address, the function returns successfully (HG_SUCCESS), but on usage of the returned addr, it is uninitialized memory.

Addr lookup returns:

na_ssm_addr_lookup:695: Enter (in_name: tcp://localhost:10000).

na_ssm_addr_lookup:793: Exit (Addr: 0x59f6a10, Status: 0).

Further usage of that addr results in: ==2916== Use of uninitialised value of size 8 ==2916== at 0x40C1A0: NA_Addr_is_self (na.c:582) ==2916== by 0x402CB1: HG_Forward (mercury.c:836) ==2916== by 0x4020D0: main (ping_server.c:173) ==2916== ==2916== Jump to the invalid address stated on the next line ==2916== at 0x0: ??? ==2916== by 0x402CB1: HG_Forward (mercury.c:836) ==2916== by 0x4020D0: main (ping_server.c:173) ==2916== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==2916== ==2916== ==2916== Process terminating with default action of signal 11 (SIGSEGV) ==2916== Bad permissions for mapped region at address 0x0 ==2916== at 0x0: ??? ==2916== by 0x402CB1: HG_Forward (mercury.c:836) ==2916== by 0x4020D0: main (ping_server.c:173)

#30 jsoumagne carns fixed race condition in na_bmi put
Description

The na_bmi put operation stores the BMI operation ID for two BMI operations that are posted back to back. Later on in na_bmi_progress_expected() it compares them to completed operations IDs to determine how to make progress on the put operation.

If another thread is being used to drive progress, however, then BMI may actually complete the first operation before the second one is issued. In that case they can both be assigned the same operation ID. This causes the put to hang because the operation is mis-identified in na_bmi_progress_expected().

I can easily reproduce this issue and will be happy to test possible fixes.

1 2 3 4 5 6 7 8 9 10 11
Note: See TracQuery for help on using queries.