Opened 11 years ago
Closed 11 years ago
#10226 closed bug (fixed)
Fixed resource leak and possible strings without null-termiator
Reported by: | Ezodev | Owned by: | bonefish |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | System/Kernel | Version: | R1/Development |
Keywords: | gci2013 | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
Found in coverity, CIDs: 605891, 990975
Attachments (2)
Change History (6)
by , 11 years ago
Attachment: | 0001-Fixed-resource-leak-and-possible-strings-without-nul.patch added |
---|
comment:1 by , 11 years ago
patch: | 0 → 1 |
---|
comment:2 by , 11 years ago
Component: | - General → System/Kernel |
---|---|
Owner: | changed from | to
Status: | new → assigned |
by , 11 years ago
Attachment: | 0001-Fixed-resource-leak-and-possible-strings-corruption.patch added |
---|
comment:4 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Thanks, applied in hrev46410.
Note:
See TracTickets
for help on using tickets.
The resource leak could be fixed more simply by just moving the first call to
unload_driver_settings()
down two lines (just before the closing curly brace for if (settings != NULL)). That would render both the boolean flag and consequent additional calls tounload_driver_settings()
entirely unnecessary.