Linux Kernel Quotes

But you weren’t born,” I tell him. “I wrote an algorithm based on the Linux operating kernel. You’re an open-source search engine married to a dialog bot and a video compiler. The program scrubs the Web and archives a person’s images and videos and data—everything you say, you’ve said before.” For

SHORT NOTE ABOUT SHA-1 A lot of people become concerned at some point that they will, by random happenstance, have two objects in their repository that hash to the same SHA-1 value. What then? If you do happen to commit an object that hashes to the same SHA-1 value as a previous object in your repository, Git will see the previous object already in your Git database and assume it was already written. If you try to check out that object again at some point, you’ll always get the data of the first object. However, you should be aware of how ridiculously unlikely this scenario is. The SHA-1 digest is 20 bytes or 160 bits. The number of randomly hashed objects needed to ensure a 50% probability of a single collision is about 280 (the formula for determining collision probability is p = (n(n-1)/2) * (1/2^160)). 280 is 1.2 x 10^24 or 1 million billion billion. That’s 1,200 times the number of grains of sand on the earth. Here’s an example to give you an idea of what it would take to get a SHA-1 collision. If all 6.5 billion humans on Earth were programming, and every second, each one was producing code that was the equivalent of the entire Linux kernel history (3.6 million Git objects) and pushing it into one enormous Git repository, it would take roughly 2 years until that repository contained enough objects to have a 50% probability of a single SHA-1 object collision. A higher probability exists that every member of your programming team will be attacked and killed by wolves in unrelated incidents on the same night.

When a process is rescheduled to run on a multiprocessor system, it doesn’t necessarily run on the same CPU on which it last executed. The usual reason it may run on another CPU is that the original CPU is already busy. When a process changes CPUs, there is a performance impact: in order for a line of the process’s data to be loaded into the cache of the new CPU, it must first be invalidated (i.e., either discarded if it is unmodified, or flushed to main memory if it was modified), if present in the cache of the old CPU. (To prevent cache inconsistencies, multiprocessor architectures allow data to be kept in only one CPU cache at a time.) This invalidation costs execution time. Because of this performance impact, the Linux (2.6) kernel tries to ensure soft CPU affinity for a process — wherever possible, the process is rescheduled to run on the same CPU.

(skb_cow(skb,

neigh_blackhole(struct

ARP protocol implementation, it is time to move on to IPv6 NDISC protocol implementation. You

When the registered netfilter hook returns NF_STOLEN, it means that the packet was taken over by the netfilter subsystem,

linux is my kernel programming is my bus

The kernel schedules individual threads, not processes.

The Linux world behaves in many respects like a free market or an ecology, a collection of selfish agents attempting to maximize utility which in the process produces a self-correcting spontaneous order more elaborate and efficient than any amount of central planning could have achieved. Here, then, is the place to seek the “principle of understanding”. The “utility function” Linux hackers are maximizing is not classically economic, but is the intangible of their own ego satisfaction and reputation among other hackers. (One may call their motivation “altruistic”, but this ignores the fact that altruism is itself a form of ego satisfaction for the altruist). Voluntary cultures that work this way are not actually uncommon; one other in which I have long participated is science fiction fandom, which unlike hackerdom has long explicitly recognized “egoboo” (ego-boosting, or the enhancement of one’s reputation among other fans) as the basic drive behind volunteer activity. Linus, by successfully positioning himself as the gatekeeper of a project in which the development is mostly done by others, and nurturing interest in the project until it became self-sustaining, has shown an acute grasp of Kropotkin’s “principle of shared understanding”. This quasi-economic view of the Linux world enables us to see how that understanding is applied. We may view Linus’s method as a way to create an efficient market in “egoboo” — to connect the selfishness of individual hackers as firmly as possible to difficult ends that can only be achieved by sustained cooperation. With the fetchmail project I have shown (albeit on a smaller scale) that his methods can be duplicated with good results. Perhaps I have even done it a bit more consciously and systematically than he. Many people (especially those who politically distrust free markets) would expect a culture of self-directed egoists to be fragmented, territorial, wasteful, secretive, and hostile. But this expectation is clearly falsified by (to give just one example) the stunning variety, quality, and depth of Linux documentation. It is a hallowed given that programmers hate documenting; how is it, then, that Linux hackers generate so much documentation? Evidently Linux’s free market in egoboo works better to produce virtuous, other-directed behavior than the massively-funded documentation shops of commercial software producers. Both the fetchmail and Linux kernel projects show that by properly rewarding the egos of many other hackers, a strong developer/coordinator can use the Internet to capture the benefits of having lots of co-developers without having a project collapse into a chaotic mess. So to Brooks’s Law I counter-propose the following: Provided the development coordinator has a communications medium at least as good as the Internet, and knows how to lead without coercion, many heads are inevitably better than one.

sudo apt install git fakeroot build-essential tar ncurses-dev tar xz-utils libssl-dev bc stress python3-distutils libelf-dev linux-headers-$(uname -r) bison flex libncurses5-dev util-linux net-tools linux-tools-$(uname -r) exuberant-ctags cscope sysfsutils gnome-system-monitor curl perf-tools-unstable gnuplot rt-tests indent tree pstree smem libnuma-dev numactl hwloc bpfcc-tools sparse flawfinder cppcheck tuna hexdump openjdk-14-jre trace-cmd virt-what

For less than the cost of a standard Windows license, you can download GNU tools and a fresh Linux kernel or good free software which you will enjoy much more.

For example, consider the leap second on June 30, 2012, that caused many applications to hang simultaneously due to a bug in the Linux kernel

1.1M    ./scripts 58M     ./cloud9 74M     . You can also use tee to write the output to several files at the same time, as shown in this example: root@beaglebone:/opt# du ‐d1 ‐h | tee /tmp/1.txt /tmp/2.txt /tmp/3.txt Filter Commands (from sort to xargs) There are filtering commands, each of which provides a useful function: sort: This command has several options, including (‐r) sorts in reverse; (‐f) ignores case; (‐d) uses dictionary sorting, ignoring punctuation; (‐n) numeric sort; (‐b) ignores blank space; (‐i) ignores control characters; (‐u) displays duplicate lines only once; and (‐m) merges multiple inputs into a single output. wc (word count): This can be used to calculate the number of words, lines, or characters in a stream. For example: root@beaglebone:/tmp# wc < animals.txt  4  4 18 This has returned that there are 4 lines, 4 words, and 18 characters. You can select the values independently by using (‐l) for line count; (‐w) for word count; (‐m) for character count; and (‐c) for the byte count (which would also be 18 in this case). head: Displays the first lines of the input. This is useful if you have a very long file or stream of information and you want to examine only the first few lines. By default it will display the first 10 lines. You can specify the number of lines using the ‐n option. For example, to get the first five lines of output of the dmesg command (display message or driver message), which displays the message buffer of the kernel, you can use the following: root@beaglebone:/tmp# dmesg | head ‐n5   [    0.000000] Booting Linux on physical CPU 0x0   [    0.000000] Initializing cgroup subsys cpuset   [    0.000000] Initializing cgroup subsys cpu   [    0.000000] Initializing cgroup subsys cpuacct   [    0.000000] Linux version 3.13.4-bone5(root@imx6q-sabrelite-1gb-0) tail: This is just like head except that it displays the last lines of a file or stream. Using it in combination with dmesg provides useful output, as shown here: root@beaglebone:/tmp# dmesg | tail ‐n2   [   36.123251] libphy: 4a101000.mdio:00 - Link is Up - 100/Full   [   36.123421] IPv6:ADDRCONF(NETDEV_CHANGE): eth0:link becomes ready grep: A very powerful filter command that can parse lines using text and regular expressions. You can use this command to filter output with options, including (‐i) ignore case; (‐m 5) stop after five matches; (‐q) silent, will exit with return status 0 if any matches are found; (‐e) specify a pattern; (‐c) print a count of matches; (‐o) print only the matching text; and (‐l) list the filename of the file containing the match. For example, the following examines the dmesg output for the first three occurrences of the string “usb,” using ‐i to ignore case: root@beaglebone:/tmp# dmesg |grep ‐i ‐m3 usb   [    1.948582] usbcore: registered new interface driver usbfs   [    1.948637] usbcore: registered new interface driver hub   [    1.948795] usbcore: registered new device driver usb You can combine pipes together. For example, you get the exact same output by using head and displaying only the first three lines of the grep output: root@beaglebone:/tmp# dmesg |grep ‐i usb |head ‐n3   [    1.948582] usbcore: registered new interface driver usbfs   [    1.948637] usbcore: registered new interface driver hub   [    1.948795] usbcore: registered new device driver usb xargs: This is a very powerful filter command that enables you to construct an argument list that you use to call another command or tool. In the following example, a text file args.txt that contains three strings is used to create three new files. The output of cat is piped to xargs, where it passes the three strings as arguments to the touch command, creating three new files a.txt, b.txt,

Note from the authors: Yes, we have lost our minds. Be forewarned: You will lose yours too.

UNIX. Understanding the meagerly documented, demanding, and complex sources of

Sladkey recalls the first time he found and sent a bug to Linus: "My first contribution was in porting some program, probably one of my smaller personal projects. I discovered a bug. Since Linux came with source, my first inclination as a hacker was to take a look under the hood and see if I could fix the problem. I found that although I had never done any kernel work, that I was able to navigate around the code pretty easily and provide a small patch to correct the problem. "With my heart beating and my palms sweating, I composed the most professional message I could muster and sent it off to linus.torvalds@cs.helsinki.fi describing the bug and including my proposed fix. Minutes later he replied something like, 'Yup, that's a bug. Nice investigation. Thanks. Fixed,' and I was hooked.