-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[all] etharp assert "no packet queues allowed!" (IDFGH-13386) #71
Comments
maybe the assert is supposed to be
If the total len is not the len of the packet or there is another packet attached to this one. |
i added a log this is the crash i get:
this is what happens by changing the assert, but i-m not sure this is a correct fix.
|
any news? |
Hi @KonssnoK, It seems that both logs show: I'm a bit puzzled as to why it would crash. Could you check if there might be any memory corruption issues in your project? Also, could you share a simple code snippet that we can use to reproduce this problem? |
@espressif-abhikroy Sadly i cannot share code snippets cause the crash is happening only when using LTE PPP on our custom board. This is how I understood it: The assert is Did I understood anything wrong? I have to recheck the crashes because few weeks passed and had to work on other stuff. |
@KonssnoK I agree with your understanding. However, I believe this check is primarily for sanitization purposes. To explain the negative scenario: The assertion will fail when both of the following conditions are true:
In this case, the check fails because the code expects that if the packet isn't fragmented (i.e., p->len == p->tot_len), there should be no additional packets queued (i.e., p->next == 0). Having a fully contained pbuf with a non-null p->next suggests an improper packet queue, which could lead to unpredictable behavior. |
@espressif-abhikroy what i can say is that we have devices in the field having the issue, so it's not simply sanitization for us. I agree with your negative scenario, I still have no idea why this was triggering so often on some installations. |
well, i confirm that changing the asset does not solve the issue
I'll go back to checking how we can avoid this |
@KonssnoK, Since you're unable to provide code to reproduce the issue, could you try printing the values of |
from
a45be9e
anybody has idea of what could trigger this issue?
The text was updated successfully, but these errors were encountered: