nx_ip_status_check() blocks forever even if timeout is specified

Licio MAPELLI 51

The nx_ip_status_check(, , NX_IP_INITIALIZE_DONE | NX_IP_LINK_ENABLED | NX_IP_INTERFACE_LINK_ENABLED, timeout) internally calls tx_mutex_get(&(ip_ptr -> nx_ip_protection), TX_WAIT_FOREVER); that blocks forever in case the requested conditions are not meet.

Shouldn't be tx_mutex_get(&(ip_ptr -> nx_ip_protection), timeout) ?

Thanks

LeelaRajeshSayana-MSFT 13,966 Reputation points

2023-07-11T23:42:04.7533333+00:00

Hi @Licio MAPELLI Greetings! Thank you for posting this question here. Our Community SMEs will review this issue and get back to you as soon as possible. Please stay tuned for updates.
Licio MAPELLI 51 Reputation points

2023-07-12T06:56:19.0166667+00:00

Thanks for your answer, in fact also here https://github.com/azure-rtos/netxduo/issues/184 its me, however is not yet clear to me if it will be fixed or not. Thanks
Tiejun Zhou 1,126 Reputation points Microsoft Employee

2023-07-14T06:50:05.7166667+00:00

I don't think this is a bug in nx_ip_status_check. It should be fixed in the network driver.
Licio MAPELLI 51 Reputation points

2023-07-14T08:32:26.3566667+00:00

Thanks for your suggestion, however the nx_ip_status_check() could become blocking, regardless of the timeout passed in the arguments, depending by the subtending driver behavior (buggy or not). I believe this possible deviation from the expected API behavior should be fixed to make it consistent with the documentation and predictable. Thanks

1 answer

Tiejun Zhou 1,126 Reputation points Microsoft Employee

2023-07-12T05:11:06.9+00:00

This issue is duplicated with https://github.com/azure-rtos/netxduo/issues/184
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

nx_ip_status_check() blocks forever even if timeout is specified

1 answer