It allows tools like sparse to tell kernel developers that they’re possibly using an untrusted pointer (or a pointer that may be invalid in the current virtual address mapping) improperly.
More Related Contents:
- What’s the use of do while(0) when we define a macro? [duplicate]
- What is “:-!!” in C code?
- What are vdso and vsyscall?
- Is there a macro definition to check the Linux kernel version?
- Why my kernel log is not showing the latest output?
- addr2line on kernel module
- How to use lockdep feature in linux kernel for deadlock detection
- Passing values to macros by for loop
- The need for parentheses in macros in C [duplicate]
- Read/write files within a Linux kernel module
- Real-world use of X-Macros
- C multi-line macro: do/while(0) vs scope block [duplicate]
- __FILE__ macro shows full path
- What exactly do C include guards do?
- Understanding container_of macro in the Linux kernel
- Measure time in Linux – time vs clock vs getrusage vs clock_gettime vs gettimeofday vs timespec_get?
- Whole one core dedicated to single process
- Building a kernel module from several source files which one of them has the same name as the module
- Macro expansion and stringification: How to get the macro name (not its value) stringified using another macro?
- Keyboard IRQ within an x86 kernel
- Incompatible pointer types passing in _Generic macro
- How to call exported kernel module functions from another module?
- Print TCP Packet Data
- How to pass macro definition from “make” command line arguments (-D) to C source code?
- How to flush the CPU cache for a region of address space in Linux?
- Inline function v. Macro in C — What’s the Overhead (Memory/Speed)?
- How to create a new Linux kernel scheduler
- What is ‘:-!!’ in C?
- Efficient way to find task_struct by pid
- Where can I find system call source code?