| commit | d6d511ecff241d459a70e270ac98d107faffdd45 | |
| author | Tobias Klauser <tklauser@distanz.ch> | |
| Thu, 15 Dec 2016 17:00:04 +0000 (15 18:00 +0100) | ||
| committer | Tobias Klauser <tklauser@distanz.ch> | |
| Thu, 15 Dec 2016 17:00:04 +0000 (15 18:00 +0100) | ||
| tree | f996436bd0b6c7d5b84966b7667d28a6cc31fecd | treesnapshot (tar.gz zip) |
| parent | 57739dfaa8bd88160fadcb34cea543c832a3b265 | commitdiff |
trafgen: proto: Zero out newly allocated struct packet
When allocating a new struct packet, the headers and headers_count
fields are not zeroed and retain whatever value the allocator returned.
Incidentally, this usually seems to have been zero. But on some systems
(e.g. Ubuntu 16.04 with a self-compiled 4.9) it is not and we hit the
following bug_on:
trafgen: trafgen_proto.c:135: proto_header_push: Assertion `!(pkt->headers_count >= 16)' failed.
Fix this by properly zeroing the entire struct packet.
Fixes: e7dd63060e44 ("trafgen: proto: Update field value at runtime")
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
When allocating a new struct packet, the headers and headers_count
fields are not zeroed and retain whatever value the allocator returned.
Incidentally, this usually seems to have been zero. But on some systems
(e.g. Ubuntu 16.04 with a self-compiled 4.9) it is not and we hit the
following bug_on:
trafgen: trafgen_proto.c:135: proto_header_push: Assertion `!(pkt->headers_count >= 16)' failed.
Fix this by properly zeroing the entire struct packet.
Fixes: e7dd63060e44 ("trafgen: proto: Update field value at runtime")
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
| trafgen_parser.y | diffblobblamehistory |