Use of i_security in fs/nfs/inode.c

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




There is a check for inode->i_security == NULL in nfs_setsecurity
in fs/nfs/inode.c. What is the intent of this check? Are you looking
for an uninitialized security blob, are you looking to see if there
is an active security module or something else?

Is there any reason that you can see that a call to security_inode_getsecid()
followed by a check to see if the secid == 0 would not be equivalent?
I understand that the NULL check is faster, but it may not always be correct.

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux