/*
* netsniff-ng - the packet sniffing beast
* Copyright 2009, 2010 Daniel Borkmann.
* Subject to the GPL, version 2.
*/
#ifndef DISSECTOR_80211_H
#define DISSECTOR_80211_H
#include "hash.h"
#include "proto.h"
#include "protos.h"
#include "tprintf.h"
#include "oui.h"
extern struct hash_table ieee80211_lay2;
extern void dissector_init_ieee80211(int fnttype);
extern void dissector_cleanup_ieee80211(void);
#ifdef __WITH_PROTOS
static inline struct protocol *dissector_get_ieee80211_entry_point(void)
{
return &ieee80211_ops;
}
static inline struct protocol *dissector_get_ieee80211_exit_point(void)
{
return &none_ops;
}
#else
static inline struct protocol *dissector_get_ieee80211_entry_point(void)
{
return NULL;
}
static inline struct protocol *dissector_get_ieee80211_exit_point(void)
{
return NULL;
}
#endif /* __WITH_PROTOS */
#endif /* DISSECTOR_80211_H */
'>
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>