The case of the prematurely freed SKB
The case of the prematurely freed SKB
Posted Mar 2, 2017 8:25 UTC (Thu) by wsa (guest, #52415)In reply to: The case of the prematurely freed SKB by marcH
Parent article: The case of the prematurely freed SKB
I used to do that. When I received a bugfix in my subsystem which looked like a generic issue to me, I wrote a coccinelle script to see how widespread it was. However, fixing it automatically was seldomly possible. Usually, the coccinelle generated patches needed manual changes and a really careful review in order to avoid regressions. The code in question was often not touched for a while, so getting it upstream without being able to test it was slow (rightfully, I'd say).
That all easily exceeded the free-time capacity I had for hacking such stuff. I tried to get funding for it but failed ("no predictable deliverables"). So, I stopped writing cocci scripts because knowing where mushrooms are and then not being able to pick them gets frustrating.
Posted Mar 3, 2017 15:48 UTC (Fri)
by grmd (guest, #4391)
[Link] (3 responses)
Would it have been possible to identify likely errors and raise them for others to consider?
Posted Mar 3, 2017 17:23 UTC (Fri)
by wsa (guest, #52415)
[Link] (2 responses)
Posted Mar 3, 2017 18:15 UTC (Fri)
by marcH (subscriber, #57642)
[Link] (1 responses)
Lists not. Maintainers why not?
Posted Mar 3, 2017 19:34 UTC (Fri)
by wsa (guest, #52415)
[Link]
The case of the prematurely freed SKB
The case of the prematurely freed SKB
The case of the prematurely freed SKB
The case of the prematurely freed SKB
