Understanding container_of macro in the Linux kernel

by

Your usage example container_of(dev, struct wifi_device, dev); might be a bit misleading as you are mixing two namespaces there.

While the first dev in your example refers to the name of pointer the second dev refers to the name of a structure member.

Most probably this mix up is provoking all that headache. In fact the member parameter in your quote refers to the name given to that member in the container structure.

Taking this container for example:

struct container {
  int some_other_data;
  int this_data;
}

And a pointer int *my_ptr to the this_data member you’d use the macro to get a pointer to struct container *my_container by using:

struct container *my_container;
my_container = container_of(my_ptr, struct container, this_data);

Taking the offset of this_data to the beginning of the struct into account is essential to getting the correct pointer location.

Effectively you just have to subtract the offset of the member this_data from your pointer my_ptr to get the correct location.

That’s exactly what the last line of the macro does.

More Related Contents:

  1. #pragma pack effect
  2. Real-world use of X-Macros
  3. Easy way to use variables of enum types as string in C?
  4. How do I check OS with a preprocessor directive?
  5. What are the applications of the ## preprocessor operator and gotchas to consider?
  6. Stringification of a macro value
  7. What is the meaning of lines starting with a hash sign and number like ‘# 1 “a.c”‘ in the gcc preprocessor output?
  8. Are typedef and #define the same in c?
  9. Linux Kernel: System call hooking example
  10. Measure time in Linux – time vs clock vs getrusage vs clock_gettime vs gettimeofday vs timespec_get?
  11. What are vdso and vsyscall?
  12. What does ## mean for the C(C++) preprocessor?
  13. Whole one core dedicated to single process
  14. Building a kernel module from several source files which one of them has the same name as the module
  15. Type of #define variables
  16. #ifdef inside #define
  17. Is there a good reason for always enclosing a define in parentheses in C?
  18. Rationale behind the container_of macro in linux/list.h
  19. C preprocessor: expand macro in a #warning
  20. C circular dependency
  21. Why my kernel log is not showing the latest output?
  22. What is a good reference documenting patterns of use of X-Macros in C (or possibly C++)?
  23. Should variable definition be in header files?
  24. What does request_mem_region() actually do and when it is needed?
  25. Checking if errno != EINTR: what does it mean?
  26. mmap, msync and linux process termination
  27. addr2line on kernel module
  28. Why can’t I use sizeof in a preprocessor condition?
  29. How can I make a char string from a C macro’s value?
  30. Efficient way to find task_struct by pid

Leave a Comment