lwIP - A Lightweight TCP/IP stack - Bugs: bug #37955, LWIP_ERROR fails with...
You are not allowed to post comments on this tracker with your current authentication level.
bug #37955: LWIP_ERROR fails with "message", doesn't call "handler"
Submitter: | Valery Ushakov <uwe> | ||
Submitted: | Wed 19 Dec 2012 04:44:00 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Invalid |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | CVS Head |
Thu 20 Dec 2012 07:44:39 AM UTC, comment #1: |
Simon Goldschmidt <goldsimon> |
Wed 19 Dec 2012 04:44:00 AM UTC, original submission:
LWIP_ERROR calls LWIP_PLATFORM_ASSERT(message) which is fatal.
|
Valery Ushakov <uwe> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2012-12-20 | goldsimon | Status | None | Invalid | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-d3ae.
Corresponding source code
This is intended behaviour. The default should be assert but anyone not wanting this can disable the assert and define LWIP_ERROR to execute the handler instead. This is rather an advanced option. We could discuss whether we just use ASSERT, but some vote against it some years ago...
Anyway, the actual bug is that incoming packet handling should not fail on malicious packets. I've added a task to check this.