aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/evsel.c
diff options
context:
space:
mode:
authorGravatar Vishal Verma <vishal.l.verma@intel.com> 2023-06-23 15:20:00 -0600
committerGravatar Vishal Verma <vishal.l.verma@intel.com> 2023-06-23 15:20:00 -0600
commit95bf6df03d412f678a7b558da186c2ef797ac40c (patch)
treeae7c6b57d11bf3e5a2c898c7b33e21687118f2d2 /tools/perf/util/evsel.c
parentnvdimm: make security_show static (diff)
parentdax/kmem: Pass valid argument to memory_group_register_static (diff)
downloadlinux-95bf6df03d412f678a7b558da186c2ef797ac40c.tar.gz
linux-95bf6df03d412f678a7b558da186c2ef797ac40c.tar.bz2
linux-95bf6df03d412f678a7b558da186c2ef797ac40c.zip
Merge branch 'for-6.5/dax-cleanups' into nvdimm-for-next
The reference counting of dax_region objects is needlessly complicated, has lead to confusion [1], and has hidden a bug [2]. While testing the cleanup for those issues, a CONFIG_DEBUG_KOBJECT_RELEASE test run uncovered a use-after-free in dax_mapping_release(). Clean all of that up. Thanks to Yongqiang, Paul, and Ira for their analysis. Additionally, clean up a redundant variable in fsdax, and fix memory hotplug registration in the kmem driver. [1]: http://lore.kernel.org/r/20221203095858.612027-1-liuyongqiang13@huawei.com [2]: http://lore.kernel.org/r/3cf0890b-4eb0-e70e-cd9c-2ecc3d496263@hpe.com
Diffstat (limited to 'tools/perf/util/evsel.c')
0 files changed, 0 insertions, 0 deletions