[En-Nut-Discussion] Freeing NETBUFs on error

[Michael Jones]

Cheers!

I totally agree! Also because the "upstream" code that must cope with this
fluke gets a bit sensitive.

The only thing that has been stopping me and as I guess a few others of
changing this is the amount of testing that would follow to ensure that all
other modules continue to work - including modules not in the cvs written
and maintained privately by others.

Cu,
Michael

-----Original Message-----
From: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] On Behalf Of Michal 'Khorne'
Rzechonek
Sent: Wednesday, February 22, 2006 1:08 PM
To: en-nut-discussion at egnite.de
Subject: [En-Nut-Discussion] Freeing NETBUFs on error

Hello,

Could anyone explain to me why NutEtherOutput() frees passed
NETBUF on errors?

In my opinion this seriously violates object/memory ownership
rules...

regards
-- 
Michał 'Khorne' Rzechonek, research & development
Xylab Sp.z o.o, Karmelicka 45/8 Kraków, Poland
tel: +48 12 423 45 55 url: http://www.xylab.com



_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion