Tomasz Bursztyka 675277e28d net: nbuf: Initialize nbuf memory area after allocation ... After commit 71c7c01819 about buf pool, we started to get spurious behaviors on various places of the code on different boards (a101, frdm...) BUT on qemu. Basically, outgoing ip/udp packets were full of garbage. Or sometimes it was the abilitty to parse incoming packet that was happening. The difference between qemu and actualy boards is - afaik, at least, let me know if I am wrong - that qemu provide initialized memory (full of 0s). Following this asssumption, this patch just reset the nbuf right after it got allocated. And all started to work again as thought. It's in fact a good thing to reset nbuf memory. Even before the above commit: after being used more than once, a buffer would have ended up with old content, and this could have been generating a bug. So let's be on the safe side and always intialize nbuf content. Change-Id: I50647d9e9b82a4ed340a5ceb0d69409b0194dddd Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>		2016-12-16 19:14:56 +01:00
..
bluetooth	Bluetooth: Remove unnecessary runtime kernel object initialization	2016-12-16 10:27:48 +02:00
fs	fs/disk: Improve code readability	2016-12-05 02:46:52 +00:00
net	net: nbuf: Initialize nbuf memory area after allocation	2016-12-16 19:14:56 +01:00
usb	usb :mass_storage: correct the license details	2016-12-02 02:11:34 +00:00
Kconfig	net: Moved net/ to subsys/net	2016-12-02 12:41:20 +02:00
Makefile	net: Moved net/ to subsys/net	2016-12-02 12:41:20 +02:00