I solved my problem a few months ago. Here’s the solution I used. The standard packet-sending API (sock_create, connect, …) cannot be used in a few contexts (interruptions). Using it in the wrong place leads to a KP. The netpoll API is more “low-level” and works in every context. However, there are several conditions : … Read more
[*] To enable lockdep feature, edit .config file through menuconfig: make menuconfig And enable following in Hacking Options: 1. [*] Detect Hard and Soft Lockups 2. [*] Detect Hung Tasks 3. [*] RT Mutex debugging, deadlock detection 4. -*- Spinlock and rw-lock debugging: basic checks 5. -*- Mutex debugging: basic checks 6. -*- Lock debugging: … Read more
In Linux host: Run the container in privileged mode (–privileged) Add all capabilities (–cap-add=ALL) mount host /lib/modules into the container (-v /lib/modules:/lib/modules) docker run –name container_name \ –privileged \ –cap-add=ALL -d \ -v /dev:/dev \ -v /lib/modules:/lib/modules \ image_id Caution: Here all Linux capabilities are added so capabilities can be refined. Few words about Linux … Read more
As Dani has already mentioned in the comment: It’s a bug in Windows 7 and likely in Windows Server 2008 (possibly 64bit versions only). It surfaces when you disable Application Experience service. Re-enabling this service has fixed this problem for me. A bit more info here as to why it’s causing a problem. List of … Read more
I suppose the module is built with debug info included. If so, you can use gdb or objdump to find out which source file and line each address belongs to. Something like this: $ gdb “$(modinfo -n my_module)” (gdb) list *(some_function+0x12c) Gdb will now tell the name of the source file and the line in … Read more
ctags enables two features: allowing you to jump from function calls to their definitions, and omni completion. The first means that when you are over a call to a method, hitting g] or CTRL-] will jump to the place where that method is defined or implemented. The second feature means that when you type foo. … Read more
Mark “T” in /proc/kallsyms means that symbol is globally visible, and can be used in other kernel’s code (e.g. by drivers, compiled built-in). But for being usable in kernel module’s code, symbol is needed to be exported using EXPORT_SYMBOL or similar. List of exported symbols is maintained separately from list of all symbols in the … Read more
From Bash FAQ: E10) Why does `cd //’ leave $PWD as `//’? POSIX.2, in its description of `cd’, says that *three* or more leading slashes may be replaced with a single slash when canonicalizing the current working directory. This is, I presume, for historical compatibility. Certain versions of Unix, and early network file systems, used … Read more
The Linux scheduler (on recent Linux kernels, e.g. 3.0 at least) is scheduling schedulable tasks or simply tasks. A task may be : a single-threaded process (e.g. created by fork without any thread library) any thread inside a multi-threaded process (including its main thread), in particular Posix threads (pthreads) kernel tasks, which are started internally … Read more
@paulsm4 I am doubtful about your comment that kernel knows every thing. In this particular context of user level threads, the kernel is unaware of the fact that such a thing is happening. A user level thread’s scheduling is maintained by the user himself (via the interface provided by a library) and the kernel ends … Read more