summaryrefslogtreecommitdiff
path: root/bpf_comp.c
diff options
context:
space:
mode:
authorVadim Kochan <vadim4j@gmail.com>2017-06-12 23:55:37 +0300
committerTobias Klauser <tklauser@distanz.ch>2017-06-19 11:05:42 +0200
commit6e3a87093dfcd8b4b62685e67b565d842c631da1 (patch)
tree5b6b1c93d8ed4bc8c2804ccccedfd5dac584378a /bpf_comp.c
parent78c13b71e196a107eaa4ec00bb40b062929a6a88 (diff)
trafgen: Fix output pcap file name length trimming
Trim output name to IFNAMSIZ only if the output is a networking device, otherwise the following error occured if output name is greater then IFNAMSIZ: $ trafgen -n 1 '{ udp() }' -o /tmp/xxxxxxxxxxxxxx.pcap No networking device or pcap file: /tmp/xxxxxxxxxx Failed to open output device Signed-off-by: Vadim Kochan <vadim4j@gmail.com> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'bpf_comp.c')
0 files changed, 0 insertions, 0 deletions
front changed() > Connect() > Set blkback to XenbusStateConnected blkback_changed() > Skip talk_to_blkback() because frontstate == XenbusStateInitialised > blkfront_connect() > Set blkfront to XenbusStateConnected ----- And here we get another XenbusStateConnected notification leading to: ----- blkback_changed() > because now frontstate != XenbusStateInitialised talk_to_blkback() is also called again > blkfront state changed from XenbusStateConnected to XenbusStateInitialised (Which is not correct!) front_changed(): > Do nothing because blkback already in XenbusStateConnected Now blkback is in XenbusStateConnected but blkfront is still in XenbusStateInitialised - leading to no disks. Poking of the XenbusStateConnected state is allowed (to deal with block disk change) and has to be dealt with. The most likely cause of this bug are custom udev scripts hooking up the disks and then validating the size. Signed-off-by: Bob Liu <bob.liu@oracle.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'Documentation/devicetree/bindings/mfd')