Opened 12 years ago

Closed 12 years ago

#8839 closed bug (fixed)

[tcpdump] is broken

Reported by: diver Owned by: mmlr
Priority: normal Milestone: R1
Component: Applications/Command Line Tools Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

This is hrev44478

tcpdump -i /dev/net/attansic_l2/0 -vvv doesn't output anything.

Change History (6)

comment:1 by siarzhuk, 12 years ago

According to the GCI 2012 task (​http://google-melange.appspot.com/gci/task/view/google/gci2012/7980210) investigations the tcpdump breakage occured between hrev42711 and hrev43638.

comment:2 by siarzhuk, 12 years ago

Hm... tcpdump bombs standard output with packets info in hrev43045 but keep silence in hrev43046. I wonder, how hrev43046 changes can affect the tcpdump at all? :-|

comment:3 by axeld, 12 years ago

The kernel is currently compiled with PARANOID_KERNEL_FREE by default, so the changes in hrev43046 actually affect the kernel. Apparently, the network stack does not like memory initialized with 0xcc somewhere affecting tcpdump.

comment:4 by siarzhuk, 12 years ago

yep, compiling with KERNEL_DEBUG_LEVEL 0 "fixes" this issue and tcpdump works in such build.

comment:5 by diver, 12 years ago

Owner: changed from nobody to mmlr
Status: new → assigned

comment:6 by siarzhuk, 12 years ago

Resolution: → fixed
Status: assigned → closed

Fixed in hrev45062. Final investigations where done by Evgeny Abdraimov. Thanks to all who participated!

Note: See TracTickets for help on using tickets.