Re: [KJ] setting fops member pointers to NULL?

[Aaron Cripps <acripps@gmail.com>]

Robert P. J. Day wrote:
>   is there any rationale for setting a member of the file_operations
> structure explicitly to NULL as opposed to leaving it initialized?  i
> would think that's the default just based on the rules for C
> initialization, but i just wanted to make sure since i see it done
> every so often and wonder if there's something tricky going on that i
> don't know about.
>
> rday
>
>   
Actually, C doesn't really care ... if you declare something, but don't 
initialize it explicitly,
it will be filled with some random value (probably whatever was at the 
given memory address
before C gave it to your var). It makes sense to initialize something to 
NULL because then
we can run value checks and we know what to expect if the value isn't  
something we put in there.
Hope this helps.
-acripps
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors