diff options
author | Jithu Joseph <jithu.joseph@intel.com> | 2018-10-12 15:51:01 -0700 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-12-01 09:16:43 +0100 |
commit | 3d02e3bb3cfe1a9289b1ee27dec2f6d1248d48bd (patch) | |
tree | 5fca9adfea00e5dcbe99d699c06f257e66b3fa00 /arch/sparc | |
parent | b6e44f7439510a0058afed5779ed9640a802e0e9 (diff) | |
download | linux-stable-3d02e3bb3cfe1a9289b1ee27dec2f6d1248d48bd.tar.gz linux-stable-3d02e3bb3cfe1a9289b1ee27dec2f6d1248d48bd.tar.bz2 linux-stable-3d02e3bb3cfe1a9289b1ee27dec2f6d1248d48bd.zip |
x86/intel_rdt: Prevent pseudo-locking from using stale pointers
[ Upstream commit b61b8bba18fe2b63d38fdaf9b83de25e2d787dfe ]
When the last CPU in an rdt_domain goes offline, its rdt_domain struct gets
freed. Current pseudo-locking code is unaware of this scenario and tries to
dereference the freed structure in a few places.
Add checks to prevent pseudo-locking code from doing this.
While further work is needed to seamlessly restore resource groups (not
just pseudo-locking) to their configuration when the domain is brought back
online, the immediate issue of invalid pointers is addressed here.
Fixes: f4e80d67a5274 ("x86/intel_rdt: Resctrl files reflect pseudo-locked information")
Fixes: 443810fe61605 ("x86/intel_rdt: Create debugfs files for pseudo-locking testing")
Fixes: 746e08590b864 ("x86/intel_rdt: Create character device exposing pseudo-locked region")
Fixes: 33dc3e410a0d9 ("x86/intel_rdt: Make CPU information accessible for pseudo-locked regions")
Signed-off-by: Jithu Joseph <jithu.joseph@intel.com>
Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: fenghua.yu@intel.com
Cc: tony.luck@intel.com
Cc: gavin.hindman@intel.com
Cc: hpa@zytor.com
Link: https://lkml.kernel.org/r/231f742dbb7b00a31cc104416860e27dba6b072d.1539384145.git.reinette.chatre@intel.com
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'arch/sparc')
0 files changed, 0 insertions, 0 deletions