mm/damon/sysfs-schemes: fix wrong directories put orders in error paths
Subsystems (3)
SeongJae Park
maintainercover mm/damon/sysfs-schemes: fix wrong directories put orders in error paths
Error paths of damon_sysfs_access_pattern_add_dirs() and damon_sysfs_scheme_add_dirs() functions put references to directories in wrong orders. As a result, uninitialized memory dereference and/or memory leak can happen. Fix those.
Changes from RFC v1
- RFC v1: https://lore.kernel.org/[email protected]
- Add damon_sysfs_access_pattern_add_dirs() fix.
SeongJae Park (2):
mm/damon/sysfs-schemes: fix dir put orders in
access_pattern_add_dirs()
mm/damon/sysfs-schemes: put stats for scheme_add_dirs() internal error
mm/damon/sysfs-schemes.c | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-)
base-commit: 7590ff339c62226d7e1eeff03918b8d27eff0872
Signature · 1 line
2.47.3
SeongJae Park
maintainerRFC PATCH 1/2 mm/damon/sysfs-schemes: fix dir put orders in access_pattern_add_dirs()
In access_pattern_add_dirs(), error handling path puts references starting from setup failed directories. If the failure happpened from the initial allication in the setup functions, uninitialized memory dereference happen. The allocation failures will not commonly happen, but the consequence is quite bad. Fix the wrong reference put orders.
The issue was discovered [1] by Sashiko.
[1] https://lore.kernel.org/[email protected]
--- mm/damon/sysfs-schemes.c | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-)
mm/damon/sysfs-schemes.c +3 -6
@@ -1993,22 +1993,19 @@ static int damon_sysfs_access_pattern_add_dirs( err =damon_sysfs_access_pattern_add_range_dir (access_pattern, &access_pattern->sz,"sz" );if (err) - goto put_sz_out; +return err; err =damon_sysfs_access_pattern_add_range_dir (access_pattern, &access_pattern->nr_accesses,"nr_accesses" );if (err) - goto put_nr_accesses_sz_out; + goto put_sz_out; err =damon_sysfs_access_pattern_add_range_dir (access_pattern, &access_pattern->age,"age" );if (err) - goto put_age_nr_accesses_sz_out; + goto put_nr_accesses_sz_out;return 0 ; -put_age_nr_accesses_sz_out: -kobject_put (&access_pattern->age->kobj); - access_pattern->age =NULL ; put_nr_accesses_sz_out:kobject_put (&access_pattern->nr_accesses->kobj); access_pattern->nr_accesses =NULL ;
Signature · 1 line
2.47.3
SeongJae Park
maintainerRFC PATCH 2/2 mm/damon/sysfs-schemes: put stats for scheme_add_dirs() internal error
In reply to SeongJae Parkdamon_sysfs_scheme_add_dirs() setup the tried_regions directory after the stats directory setup is completed. When the tried_regions directory setup is failed, the setup function ensures the reference for the tried regions directory is released. Hence the error path should put references on setup succeeded directory objects, starting from the stats directory. However, the error path is putting the tried_regions directory instead of the stats directory.
As a direct result, the stats directory object is leaked. Worse yet, if the tried_regions directory setup failed from the initial allocation, the scheme->tried_regions field remains uninitialized. The following kobject_put(&scheme->tried_regions->kobj) call in the error path will dereference the uninitialized memory. The setup failures should not be common. But once it happens, the consequence is quite bad.
Fix this issue by correctly putting the stats directory instead of the tried_regions directory.
The issue was discovered [1] by Sashiko.
[1] https://lore.kernel.org/[email protected]
--- mm/damon/sysfs-schemes.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
mm/damon/sysfs-schemes.c +4 -4
@@ -2513,12 +2513,12 @@ static int damon_sysfs_scheme_add_dirs(struct damon_sysfs_scheme *scheme) goto put_filters_watermarks_quotas_access_pattern_out; err =damon_sysfs_scheme_set_tried_regions (scheme);if (err) - goto put_tried_regions_out; + goto put_stats_out;return 0 ; -put_tried_regions_out: -kobject_put (&scheme->tried_regions->kobj); - scheme->tried_regions =NULL ; +put_stats_out: +kobject_put (&scheme->stats->kobj); + scheme->stats =NULL ; put_filters_watermarks_quotas_access_pattern_out:kobject_put (&scheme->ops_filters->kobj); scheme->ops_filters =NULL ;
Signature · 1 line
2.47.3