diff options
| author | Baokun Li <[email protected]> | 2024-03-19 19:33:21 +0800 |
|---|---|---|
| committer | Theodore Ts'o <[email protected]> | 2024-05-02 23:48:30 -0400 |
| commit | b7b2a5799b8fafe95fcd5455c32ba2c643c86f99 (patch) | |
| tree | ace7ef46cfc467b8f08b699aaf0649236a09d559 /tools/perf/scripts/python | |
| parent | 13df4d44a3aaabe61cd01d277b6ee23ead2a5206 (diff) | |
ext4: add new attr pointer attr_mb_order
The s_mb_best_avail_max_trim_order is of type unsigned int, and has a
range of values well beyond the normal use of the mb_order. Although the
mballoc code is careful enough that large numbers don't matter there, but
this can mislead the sysadmin into thinking that it's normal to set such
values. Hence add a new attr_id attr_mb_order with values in the range
[0, 64] to avoid storing garbage values and make us more resilient to
surprises in the future.
Suggested-by: Jan Kara <[email protected]>
Signed-off-by: Baokun Li <[email protected]>
Reviewed-by: Jan Kara <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Theodore Ts'o <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions