summaryrefslogtreecommitdiff
path: root/net/unix
diff options
context:
space:
mode:
authorBen Skeggs <bskeggs@redhat.com>2016-05-25 17:11:40 +1000
committerBen Skeggs <bskeggs@redhat.com>2017-01-31 20:05:25 +1000
commitc966b6279f610a24ac1d42dcbe30e10fa61220b2 (patch)
tree5cb56dcbfa4042779d22ec9c4979133cd4def201 /net/unix
parent96692b097ba76d0c637ae8af47b29c73da33c9d0 (diff)
drm/nouveau: prevent userspace from deleting client object
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'net/unix')
0 files changed, 0 insertions, 0 deletions
nds-private-remove&id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7&id2=0c744ea4f77d72b3dcebb7a8f2684633ec79be88'>diff)
tracing: Fix hwlat kthread migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'tools/lib/api/Build')