summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorDaniel Borkmann <dborkman@redhat.com>2013-06-11 00:22:08 +0200
committerDaniel Borkmann <dborkman@redhat.com>2013-06-11 00:22:08 +0200
commit22aeecb491b346fe944f38e083cd26d4d235c632 (patch)
tree44d44c9b36ad442214ca04b32901b9f207859356 /README
parent42d1a29e7b7a55f39114115b9cb4814989ad5bf2 (diff)
curve: move selftest to own file
Move the curve selftest to its own file. Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-13 15:23:19 +0000
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 'net/netlabel/netlabel_mgmt.c')