mirror of
https://github.com/torvalds/linux.git
synced 2026-03-08 03:44:45 +01:00
fs: predict not reaching the limit in alloc_empty_file()
Eliminates a jump over a call to capable() in the common case. By default the limit is not even set, in which case the check can't even fail to begin with. It remains unset at least on Debian and Ubuntu. For this cases this can probably become a static branch instead. In the meantime tidy it up. I note the check separate from the bump makes the entire thing racy. Signed-off-by: Mateusz Guzik <mjguzik@gmail.com> Link: https://lore.kernel.org/r/20250319124923.1838719-1-mjguzik@gmail.com Signed-off-by: Christian Brauner <brauner@kernel.org>
This commit is contained in:
parent
5a607aa943
commit
9ae7e5a1cd
1 changed files with 2 additions and 1 deletions
|
|
@ -216,7 +216,8 @@ struct file *alloc_empty_file(int flags, const struct cred *cred)
|
|||
/*
|
||||
* Privileged users can go above max_files
|
||||
*/
|
||||
if (get_nr_files() >= files_stat.max_files && !capable(CAP_SYS_ADMIN)) {
|
||||
if (unlikely(get_nr_files() >= files_stat.max_files) &&
|
||||
!capable(CAP_SYS_ADMIN)) {
|
||||
/*
|
||||
* percpu_counters are inaccurate. Do an expensive check before
|
||||
* we go and fail.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue