On Tue, Feb 12, 2013 at 11:18:45AM +0100, Pau Koning wrote:
An entry in DAT with the hashed position of 0 can cause a NULL pointer dereference when the first entry is checked by batadv_choose_next_candidate. This first candidate automatically has the max value of 0 and the max_orig_node of NULL. Not checking max_orig_node for NULL in batadv_is_orig_node_eligible will lead to a NULL pointer dereference when checking for the lowest address.
This problem was added in 785ea1144182c341b8b85b0f8180291839d176a8 ("batman-adv: Distributed ARP Table - create DHT helper functions").
Signed-off-by: Pau Koning paukoning@gmail.com
Hello Pau,
thank you very much for this fix, this was not an easy one!
However, next time please CC our mailing list as well (get_maintainer.pl will give you all the needed addresses), otherwise it may be the case that we overlook such patches and: 1) we don't review it 2) we don't merge it into our repository (which is where the real development goes on).
Both 1) and 2) happened with this patch and, in my humble opinion, it is not a good idea to merge such delicate fixes without having a reply from the maintainers.
Therefore, please keep us in the loop when sending patches. It would be really appreciated.
Regards,