summaryrefslogtreecommitdiff
path: root/tools/usb/usbip/README
diff options
context:
space:
mode:
authorSeunghun Han <kkamagui@gmail.com>2018-03-06 17:21:43 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-03-15 12:56:51 +0300
commit291a0c2764e4b8f714a6e102ac2fcad6ed7711ba (patch)
tree9e0f20efd868de544e4e41c71120d810ff519142 /tools/usb/usbip/README
parentf89515c2e0391a4e0c9acac97dafe5a8b190948d (diff)
downloadlinux-291a0c2764e4b8f714a6e102ac2fcad6ed7711ba.tar.xz
x86/MCE: Serialize sysfs changes
commit b3b7c4795ccab5be71f080774c45bbbcc75c2aaf upstream. The check_interval file in /sys/devices/system/machinecheck/machinecheck<cpu number> directory is a global timer value for MCE polling. If it is changed by one CPU, mce_restart() broadcasts the event to other CPUs to delete and restart the MCE polling timer and __mcheck_cpu_init_timer() reinitializes the mce_timer variable. If more than one CPU writes a specific value to the check_interval file concurrently, mce_timer is not protected from such concurrent accesses and all kinds of explosions happen. Since only root can write to those sysfs variables, the issue is not a big deal security-wise. However, concurrent writes to these configuration variables is void of reason so the proper thing to do is to serialize the access with a mutex. Boris: - Make store_int_with_restart() use device_store_ulong() to filter out negative intervals - Limit min interval to 1 second - Correct locking - Massage commit message Signed-off-by: Seunghun Han <kkamagui@gmail.com> Signed-off-by: Borislav Petkov <bp@suse.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Tony Luck <tony.luck@intel.com> Cc: linux-edac <linux-edac@vger.kernel.org> Cc: stable@vger.kernel.org Link: http://lkml.kernel.org/r/20180302202706.9434-1-kkamagui@gmail.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/usb/usbip/README')
0 files changed, 0 insertions, 0 deletions