summaryrefslogtreecommitdiffstats
path: root/security/smack/smack_lsm.c
diff options
context:
space:
mode:
authorVishal Goel <vishal.goel@samsung.com>2016-11-23 10:46:57 +0530
committerCasey Schaufler <casey@schaufler-ca.com>2017-01-10 09:47:20 -0800
commit2e962e2fec5c35b91e3b541e2b8373504bf91e27 (patch)
tree60f9eec5feb6f7b45fe43f80f9ee81a5a22c4905 /security/smack/smack_lsm.c
parent0c96d1f5328e834048480e4696e6867992115c33 (diff)
downloadlinux-stable-2e962e2fec5c35b91e3b541e2b8373504bf91e27.tar.gz
linux-stable-2e962e2fec5c35b91e3b541e2b8373504bf91e27.tar.bz2
linux-stable-2e962e2fec5c35b91e3b541e2b8373504bf91e27.zip
SMACK: Add new lock for adding entry in smack master list
"smk_set_access()" function adds a new rule entry in subject label specific list(rule_list) and in global rule list(smack_rule_list) both. Mutex lock (rule_lock) is used to avoid simultaneous updates. But this lock is subject label specific lock. If 2 processes tries to add different rules(i.e with different subject labels) simultaneously, then both the processes can take the "rule_lock" respectively. So it will cause a problem while adding entries in master rule list. Now a new mutex lock(smack_master_list_lock) has been taken to add entry in smack_rule_list to avoid simultaneous updates of different rules. Signed-off-by: Vishal Goel <vishal.goel@samsung.com> Signed-off-by: Himanshu Shukla <himanshu.sh@samsung.com> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
Diffstat (limited to 'security/smack/smack_lsm.c')
0 files changed, 0 insertions, 0 deletions