summaryrefslogtreecommitdiff
path: root/security/tomoyo/common.c
diff options
context:
space:
mode:
authorDmitry Vyukov <dvyukov@google.com>2021-12-14 12:45:26 +0300
committerTetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>2021-12-15 14:11:07 +0300
commit04e57a2d952bbd34bc45744e72be3eecdc344294 (patch)
tree672e92876fcf0d63d97290f42e21fa2fea2a084a /security/tomoyo/common.c
parent5472f14a37421d1bca3dddf33cabd3bd6dbefbbc (diff)
downloadlinux-04e57a2d952bbd34bc45744e72be3eecdc344294.tar.xz
tomoyo: Check exceeded quota early in tomoyo_domain_quota_is_ok().
If tomoyo is used in a testing/fuzzing environment in learning mode, for lots of domains the quota will be exceeded and stay exceeded for prolonged periods of time. In such cases it's pointless (and slow) to walk the whole acl list again and again just to rediscover that the quota is exceeded. We already have the TOMOYO_DIF_QUOTA_WARNED flag that notes the overflow condition. Check it early to avoid the slowdown. [penguin-kernel] This patch causes a user visible change that the learning mode will not be automatically resumed after the quota is increased. To resume the learning mode, administrator will need to explicitly clear TOMOYO_DIF_QUOTA_WARNED flag after increasing the quota. But I think that this change is generally preferable, for administrator likely wants to optimize the acl list for that domain before increasing the quota, or that domain likely hits the quota again. Therefore, don't try to care to clear TOMOYO_DIF_QUOTA_WARNED flag automatically when the quota for that domain changed. Signed-off-by: Dmitry Vyukov <dvyukov@google.com> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Diffstat (limited to 'security/tomoyo/common.c')
0 files changed, 0 insertions, 0 deletions