# # Configuration for 802.1Q VLAN support # config VLAN_8021Q tristate "802.1Q/802.1ad VLAN Support" ---help--- Select this and you will be able to create 802.1Q VLAN interfaces on your Ethernet interfaces. 802.1Q VLAN supports almost everything a regular Ethernet interface does, including firewalling, bridging, and of course IP traffic. You will need the 'ip' utility in order to effectively use VLANs. See the VLAN web page for more information: To compile this code as a module, choose M here: the module will be called 8021q. If unsure, say N. config VLAN_8021Q_GVRP bool "GVRP (GARP VLAN Registration Protocol) support" depends on VLAN_8021Q select GARP help Select this to enable GVRP end-system support. GVRP is used for automatic propagation of registered VLANs to switches. If unsure, say N. config VLAN_8021Q_MVRP bool "MVRP (Multiple VLAN Registration Protocol) support" depends on VLAN_8021Q select MRP help Select this to enable MVRP end-system support. MVRP is used for automatic propagation of registered VLANs to switches; it supersedes GVRP and is not backwards-compatible. If unsure, say N. ove net-next plumbingsTobias Klauser
summaryrefslogtreecommitdiff
path: root/net/ipv6/mcast_snoop.c
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2017-01-31 09:37:34 +0100
committerThomas Gleixner <tglx@linutronix.de>2017-01-31 21:47:58 +0100
commit0becc0ae5b42828785b589f686725ff5bc3b9b25 (patch)
treebe6d0e1f37c38ed0a7dd5da2d4b1e93f0fb43101 /net/ipv6/mcast_snoop.c
parent24c2503255d35c269b67162c397a1a1c1e02f6ce (diff)
x86/mce: Make timer handling more robust
Erik reported that on a preproduction hardware a CMCI storm triggers the BUG_ON in add_timer_on(). The reason is that the per CPU MCE timer is started by the CMCI logic before the MCE CPU hotplug callback starts the timer with add_timer_on(). So the timer is already queued which triggers the BUG. Using add_timer_on() is pretty pointless in this code because the timer is strictlty per CPU, initialized as pinned and all operations which arm the timer happen on the CPU to which the timer belongs. Simplify the whole machinery by using mod_timer() instead of add_timer_on() which avoids the problem because mod_timer() can handle already queued timers. Use __start_timer() everywhere so the earliest armed expiry time is preserved. Reported-by: Erik Veijola <erik.veijola@intel.com> Tested-by: Borislav Petkov <bp@alien8.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Borislav Petkov <bp@alien8.de> Cc: Tony Luck <tony.luck@intel.com> Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1701310936080.3457@nanos Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'net/ipv6/mcast_snoop.c')