sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

ipfrag: remove assert for actual product reasons

Browse Source 
If the device's CPU resources are scarce and unable to execute the
ip_fragin_timerwork callback in a timely manner, this assert will
be triggered. This is a normal scenario that can occur. The logic
should be modified to wait for the ip_fragin_timerwork to be
executed if it has not been executed yet.

Signed-off-by: zhanghongyu <zhanghongyu@xiaomi.com>
This commit is contained in:
zhanghongyu 2024-04-09 14:22:59 +08:00 committed by Xiang Xiao
parent fcb3e84c24
commit 5c271198a9
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
net/ipfrag/ipfrag.c
View File

@ -171,8 +171,10 @@ ip_fragout_allocfragbuf(FAR struct iob_queue_s *fragq);
static void ip_fragin_timerout_expiry(wdparm_t arg)
{
ASSERT(g_wkfragtimeout.worker == NULL);
work_queue(IPFRAGWORK, &g_wkfragtimeout, ip_fragin_timerwork, NULL, 0);
if (g_wkfragtimeout.worker == NULL)
{
work_queue(IPFRAGWORK, &g_wkfragtimeout, ip_fragin_timerwork, NULL, 0);
}
}
/****************************************************************************