After a long time searching keywords on Google and sending several e-mails to mailing lists, I finally found how to test a tx_timeout function of a network kernel module.
First, lets do a simple overview about this function. This is not an essential function to a network kernel module. Some drivers does not implement this operation. Is it really necessary? No, if you have ways to prevent this kind of exception, you don’t need to spend your time.
What is the purpose of this function? This function is thrown when the driver fails to transmit a packet. So, this functions is responsible to act to reset or interrupt the driver. Sometimes, it is hard to simulate this scenario. If you want to do a stress test to you will waste so many time waiting for an exception. To avoid it, we will use Netem feature.
Netem is a Network Emulation. He is part of the Linux Kernel and it has many capabilities to test the network and traffic control. To enable this feature you need to recompile your kernel setting up the option:
Networking -->; Networking Options -->; QoS and/or fair queuing -->; Network emulator
If you recompile your kernel and reinstall it, you will be able to use Netem features and controlling them using the command tc.
Obviously, you need to implement a tx_timeout function and set up a time for watchdog_timeo. After that, you can simulate an exception considering that it will throw only when the tx buffer will be overflowed.
So, we can set a high delay for our packets.
# tc qdisc add dev eth0 root netem delay 9s
See that we need to identify the interface: eth0, eth1, wlan0, etc. For me 9 seconds is enough to test without changes other advanced settings on my system.
After, I will using a ping command to cause an exception.
# ping www.google.com -i 0.1 -s 2048
I’m using a small interval (-i) between the ping’s and I’m sending a packet with a greater size (-s) than the default one to have an exception quickly.
If your tx_timeout function is showing a log message, you can check it using a dmesg command or opening the kernel log into /var/log/.
I wish I can help many people with this article.