1. Libvirt Rpc: Retrieve Peer Pid Via New Getsockopt For Mac Pro
2. Libvirt Rpc: Retrieve Peer Pid Via New Getsockopt For Mac 2017

The firmware doesn't relate the scan to a vif. The scan is run by a separate entity called auxiliary MAC (aka AUX MAC). This AUX MAC needs to get Tx power limitations that are not applied on a specific vif, but on the device as a whole. This can be implemented by using the minimum of all the values set by the user for all the MACs. But then we need to ignore the limitations that come from the AP or regulatory for a specific vif: a specific vif might have regulatory limitations because of the channel is works on.

This limit is irrelevant for the AUX MAC. Use the new API from mac80211: the userpowerlevel in bssconf to achieve this. Firmware -13.ucode has already moved to this API. Change-Id: Ifba83660f378e91b93bd46d29fe8ba35a7c168a4 Signed-off-by: Avri Altman Signed-off-by: Emmanuel Grumbach. The USB mini-driver in rtlwifi, which is used by rtl8192cu, issues a call to usbcontrolmsg with a timeout value of 0. In some instances where the interface is shutting down, this infinite wait results in a CPU deadlock. A one second timeout fixes this problem without affecting any normal operations.

This bug is reported at. Reported-by: Bernhard Wiedemann Tested-by: Bernhard Wiedemann Signed-off-by: Larry Finger Cc: Stable Cc: Bernhard Wiedemann Cc: Takashi Iwai Signed-off-by: Kalle Valo. Our device needs two different firmwares: the INIT firmware and the operational (OPER) firmware. The first one is run when the driver loads and it returns calibrations results as well as the NVM. The second one implements the WiFi protocol.

If the wlan interface is not brought up, the device is put to low power state: no firmware will be running. When the interface is brought up, we would run the OPER firmware only and reuse the results of the run of the INIT firmware when the driver was loaded.

This is changing with this patch. We now run the INIT firmware every time mac80211 calls start. The penalty for that is minimal since the INIT firwmare run fast. I now also avoid to power down the device between the INIT and OPER firmware on certains buses. The motivation for this change is that there are components on the device (MFUART) that are triggered by the INIT firmware and need the device to be powered up in order to keep running. Powering the device down between the INIT and OPER firmware would stop these components and prevent them from running again since they are triggered by the INIT firmware only.

The new flow allows this and also allows to trigger these components again when the interface is brought up after it has been brought down. Signed-off-by: Eran Harary Signed-off-by: Emmanuel Grumbach. This patch tracks total number of bytes acked for a TCP socket.

This is the sum of all changes done to tp-snduna, and allows for precise tracking of delivered data. RFC4898 named this: tcpEStatsAppHCThruOctetsAcked This is a 64bit field, and can be fetched both from TCPINFO getsockopt if one has a handle on a TCP socket, or from inetdiag netlink facility (iproute2/ss patch will follow) Note that tp-bytesacked was placed near tp-snduna for best data locality and minimal performance impact. Signed-off-by: Eric Dumazet Acked-by: Yuchung Cheng Cc: Matt Mathis Cc: Eric Salo Cc: Martin Lau Cc: Chris Rapier Signed-off-by: David S. This patch tracks total number of payload bytes received on a TCP socket. This is the sum of all changes done to tp-rcvnxt RFC4898 named this: tcpEStatsAppHCThruOctetsReceived This is a 64bit field, and can be fetched both from TCPINFO getsockopt if one has a handle on a TCP socket, or from inetdiag netlink facility (iproute2/ss patch will follow) Note that tp-bytesreceived was placed near tp-rcvnxt for best data locality and minimal performance impact. Signed-off-by: Eric Dumazet Cc: Yuchung Cheng Cc: Matt Mathis Cc: Eric Salo Cc: Martin Lau Cc: Chris Rapier Acked-by: Yuchung Cheng Signed-off-by: David S. We would like that optional info provided by Congestion Control modules using netlink can also be read using getsockopt This patch changes getinfo to put this information in a buffer, instead of skb, like tcpgetinfo, so that following patch can reuse this common infrastructure.

Signed-off-by: Eric Dumazet Cc: Yuchung Cheng Cc: Neal Cardwell Acked-by: Neal Cardwell Acked-by: Daniel Borkmann Acked-by: Yuchung Cheng Signed-off-by: David S. Some Congestion Control modules can provide per flow information, but current way to get this information is to use netlink. Like TCPINFO, let's add TCPCCINFO so that applications can issue a getsockopt if they have a socket file descriptor, instead of playing complex netlink games. Sample usage would be: union tcpccinfo info; socklent len = sizeof(info); if (getsockopt(fd, SOLTCP, TCPCCINFO, &info, &len) -1) Signed-off-by: Eric Dumazet Cc: Yuchung Cheng Cc: Neal Cardwell Acked-by: Neal Cardwell Acked-by: Daniel Borkmann Acked-by: Yuchung Cheng Signed-off-by: David S.

Realtek ship a variety of bluetooth USB devices that identify themselves with standard USB Bluetooth device class values, but require a special driver to actually work. Without that driver, you never get any scan results. More recently however, Realtek appear to have wisened up and simply posted a firmware update that makes these devices comply with normal btusb protocols.

The firmware needs to be uploaded on each boot. Based on Realtek code from ('new' branch). Fix an oops happening due to typo in powersupply: Change ownership from driver to core. This code is based on commit ('cfg80211: pass nameassigntype to rdevaddvirtualintf') This will expose in sysfs whether the ifname of a IEEE-802.15.4 device is set by userspace or generated by the kernel. We are using two types of nameassigntypes o NETNAMEENUM: Default interface name provided by kernel o NETNAMEUSER: Interface name provided by user. Signed-off-by: Varka Bhadram Signed-off-by: Alexander Aring Signed-off-by: Marcel Holtmann. Using IDRSRR in RXFIFOID to test for the presence of data is only valid for standard frames.

For extended frames the bit is always 1 and IDRRTR should be used instead. This patch switches the check to use CANRTRFLAG which is correctly set when reading the ID.

The patch also changes the DW1/DW2 to be read unconditionally, since this is necessary to remove the frame from the RXFIFO. Signed-off-by: Jeppe Ledet-Pedersen Acked-by: Kedareswara rao Appana Cc: linux-stable Signed-off-by: Marc Kleine-Budde. Under presence of TSO/GSO/GRO packets, codel at low rates can be quite useless. In following example, not a single packet was ever dropped, while average delay in codel queue is 100 ms! Qdisc codel 0: parent 1:12 limit 16000p target 5.0ms interval 100.0ms Sent 134376498 bytes 88797 pkt (dropped 0, overlimits 0 requeues 0) backlog 13626b 3p requeues 0 count 0 lastcount 0 ldelay 96.9ms dropnext 0us maxpacket 9084 ecnmark 0 dropoverlimit 0 This comes from a confusion of what should be the minimal backlog. It is pretty clear it is not 64KB or whatever max GSO packet ever reached the qdisc. Codel intent was to use MTU of the device.

After the fix, we finally drop some packets, and rtt/cwnd of my single TCP flow are meeting our expectations. Qdisc codel 0: parent 1:12 limit 16000p target 5.0ms interval 100.0ms Sent 102798497 bytes 67912 pkt (dropped 1365, overlimits 0 requeues 0) backlog 6056b 3p requeues 0 count 1 lastcount 1 ldelay 36.3ms dropnext 0us maxpacket 10598 ecnmark 0 dropoverlimit 0 Signed-off-by: Eric Dumazet Cc: Kathleen Nichols Cc: Dave Taht Cc: Van Jacobson Signed-off-by: David S. Rdmaconnparam private data is copied using memcpy after headers such as cmahdr (see cmaresolveibudp as example).

So the start of the private data is aligned to the end of the structure that come before. If this structure end with u32 the meaning is that the start of the private data will be 4 bytes aligned. Structures that use u8/u16/u32/u64 are naturally aligned but in case the structure start is not 8 bytes aligned, all u64 members of this structure will not be aligned. To solve this issue we must use special macros that allow unaligned access to those unaligned members. Addresses the following kernel log seen when attempting to use RDMA: Kernel unaligned access at TPC10507a88 rdsibcmconnectcomplete+0x1bc/0x1e0 rdsrdma Acked-by: Chien Yen Signed-off-by: shamir rabinovitch Minor tweaks for top of tree by: Signed-off-by: David Ahern Signed-off-by: David S. Alexander Duyck says: Clean-up some bits related to netpoll This patch set cleans up some minor items related to netpoll. The first patch addresses an Rx clean-up bug that is triggered due to an assumption that napi-poll wouldn't be called with a budget of 0.

The other two patches address devkfreeskb being called in the xmit path which isn't valid since netpoll will call ndostartxmit with IRQs disabled. Signed-off-by: David S. This reverts commit. That patch is solving a non-existant problem while creating a real problem. Just because a socket is allocated in the init name space doesn't mean that it gets hashed in the init name space.

When we unhash it the name space must be the same as the one we had when we hashed it. So this patch is completely bogus and causes socket leaks. Reported-by: Andrey Wagin Signed-off-by: Herbert Xu Signed-off-by: David S. When a macvlan device is placed in promiscuous mode, it currently just sets it's multicast mask to permissive, but doesn't change the state of the lower device.

As a result, not all multicast traffic can be received on such device. Additionally, none of a vlan traffic can be received on such device as well. This patch propagates the promiscuous mode setting to lower device so that lower device may receive all packets that macvlan may be interested in. Signed-off-by: Vladislav Yasevich Signed-off-by: David S.

The code in netdevupperdevlink has an over-stringent loop detection logic that actually prevents valid configurations from working correctly. In particular, the logic returns an error if an upper device is already in the list of all upper devices for a given dev. This particular check seems to be a overzealous as it disallows perfectly valid configurations. For example: # ip l a link eth0 name eth0.10 type vlan id 10 # ip l a dev br0 typ bridge # ip l s eth0.10 master br0 # ip l s eth0 master br0 Acked-by: Jiri Pirko Acked-by: Veaceslav Falico Signed-off-by: David S. When smsc911x uses GPIO as the interrupt controller, and if both are loaded as modules, we get following error: 'smsc911x: Could not allocate irq resource' This issue is because of smsc911x using platformgetresource to get device tree based irq resource. Commit '9ec36ca (of/irq: do irq resolution in platformgetirq)' and commit '7085a7 (drivers: platform: parse IRQ flags from resources)' add support in platformgetirq to resolve irq and irqflags respectively for both modern device tree and legacy static platform data platforms. Modify smsc911x driver to use platformgetirq to pick up irq resource correctly and use irqgettriggertype to get the IRQ trigger flags.

Signed-off-by: Kamlakant Patel Signed-off-by: David S. Introduced new sparse warnings: CHECK /home/dahern/kernels/linux.git/net/rds/ibcm.c net/rds/ibcm.c:191:34: warning: incorrect type in initializer (different base types) net/rds/ibcm.c:191:34: expected unsigned long long unsigned usertype dpackseq net/rds/ibcm.c:191:34: got restricted be64 net/rds/ibcm.c:194:51: warning: cast to restricted be64 The temporary variable for sequence number should have been declared as be64 rather than u64. Signed-off-by: David Ahern Cc: shamir rabinovitch Signed-off-by: David S. Nel/git/bluetooth/bluetooth-next Johan Hedberg says: pull request: bluetooth-next 2015-05-04 Here's the first bluetooth-next pull request for 4.2: - Various fixes for at86rf230 driver - ieee802154: trace events support for rdev-ops - HCI UART driver refactoring - New Realtek IDs added to btusb driver - Off-by-one fix for rtl8723b in btusb driver - Refactoring of btbcm driver for both UART & USB use Please let me know if there are any issues pulling. Signed-off-by: David S. /scm/linux/kernel/git/jberg/mac80211 Johannes Berg says: We have only a few fixes right now:. a fix for an issue with hash collision handling in the rhashtable conversion.

a merge issue - rhashtable removed default shrinking just before mac80211 was converted, so enable it now. remove an invalid WARN that can trigger with legitimate userspace behaviour. add a struct member missing from kernel-doc that caused a lot of warnings Signed-off-by: David S. The Firmware uses dynamic EQs allocation based on number of VFs and max EQs that can be allocated. As a result, VF can have EQ numbers that are larger than 256. According to the firmware spec, the max value is limited to be 1024 (10 bits), adapt the relevant code accordingly.

This bug was impossible to hit prior to commit ('net/mlx4core: Flexible (asymmetric) allocation of EQs and MSI-X vectors for PF/VFs') which actually enables large number of EQs for VFs. Signed-off-by: Yishai Hadas Signed-off-by: Or Gerlitz Signed-off-by: David S.

When changing the number of rings by ethtool -L, qvectors are reused, which causes oops because of uninitialized pointers. When an rx is reused as a tx, qvector-rx.ring is not set to NULL, which misleads igbpoll to determine that it has an rx ring although it actually points to the tx ring. When a tx is reused as an rx, qvector-rx.ring-skb (qvector-ring0.skb) has a value that was used as txstats before. Fix these problems by zeroing it out on reuseing it.

Fixes: ('igb: Fix queue allocation method to accommodate changing during runtime') Signed-off-by: Toshiaki Makita Tested-by: Aaron Brown Signed-off-by: Jeff Kirsher. If there are only IPv6 source specific default routes present, the host gets -ENETUNREACH on e.g.

Connect because ip6dstlookuptail calls ip6routeoutput first, and given source address any, it fails, and ip6routegetsaddr is never called. The change is to use the ip6routegetsaddr, even if the initial ip6routeoutput fails, and then doing ip6routeoutput again after we have appropriate source address available. Note that this is '99% fix' to the problem; a correct fix would be to do route lookups only within addrconf.c when picking a source address, and never call ip6routeoutput before source address has been populated.

Signed-off-by: Markus Stenberg Signed-off-by: David S. When running RDS over TCP, the active (client) side connects to the listening ('passive') side at the RDSTCPPORT.

After the connection is established, if the client side reboots (potentially without even sending a FIN) the server still has a TCP socket in the esablished state. If the server-side now gets a new SYN comes from the client with a different client port, TCP will create a new socket-pair, but the RDS layer will incorrectly pull up the old rdsconnection (which is still associated with the stale tsock and RDS socket state). This patch corrects this behavior by having rdstcpacceptone always create a new connection for an incoming TCP SYN. The rds and tcp state associated with the old socket-pair is cleaned up via the rdstcpstatechange callback which would typically be invoked in most cases when the client-TCP sends a FIN on TCP restart, triggering a transition to CLOSEWAIT state. In the rarer event of client death without a FIN, TCPKEEPALIVE probes on the socket will detect the stale socket, and the TCP transition to CLOSE state will trigger the RDS state cleanup.

Signed-off-by: Sowmini Varadhan Signed-off-by: David S. Sowmini Varadhan says: net/rds: RDS-TCP robustness fixes This patch-set contains bug fixes for state-recovery at the RDS layer when the underlying transport is TCP and the TCP state at one of the endpoints is reset V2 changes: DaveM comments to reduce memory footprint, follow NFS/RPC model where possible. Added test-case Without the changes in this set, when one of the endpoints is reset, the existing code does not correctly clean up RDS socket state for stale connections, resulting in some unstable, timing-dependant behavior on the wire, including an infinite exchange of 3WHs back-and-forth, and a resulting potential to never converge RDS state.

Test cases used to verify the changes in this set are: 1. Start rds client/server applications on two participating nodes, node1 and node2. After at least one packet has been sent (to establish the TCP connection), restart the rdstcp module on the client, and now resend packets.

Tcpdump should show server sending a FIN for the 'old' client port, and clean connection establishment/exchange for the new client port. At the end of step 1, restart rds srever on node2, and start client on node1, make sure using tcpdump, 'netstat -an grep 16385' that packets flow correctly. Start RDS client/server application on two participating nodes, and repeat steps 1 and 2, but this time, simulate node failure by doing 'ifconfig down', so no FIN is sent. Signed-off-by: David S. This patch should have been part of the previous patch having the same summary.

See Unfortunately, I didn't check to see where else this lock was used before submitting that patch. This should take care of it for netxennic, as I did a thorough search this time. To recap from the original patch; although testing this driver with DEBUGLOCKDEP and DEBUGSPINLOCK enabled did not produce any traces, it would be more prudent in the case of txcleanlock to use bh versions of spinunlock, since this lock is manipulated in both the process and softirq contexts. This patch was tested for functionality and regressions with netperf and DEBUGLOCKDEP and DEBUGSPINLOCK enabled. Signed-off-by: Tony Camuso Acked-By: Neil Horman Acked-By: Manish Chopra Signed-off-by: David S.

Urn value can't fit into 12bits. The ARM JIT code emits 'ldr rX, pc, #offset' to access the literal pool. #offset maximum value is 4095 and if the generated code is too large, the #offset value can overflow and not point to the expected slot in the literal pool. Additionally, when overflow occurs, bits of the overflow can end up changing the destination register of the ldr instruction. Fix that by detecting the overflow in immoffset and setting a flag that is checked for each BPF instructions converted in buildbody. As of now it can only be detected in the second pass.

As a result the second buildbody call can now fail, so add the corresponding cleanup code in that case. Using multiple literal pools in the JITed code is going to require lots of intrusive changes to the JIT code (which would better be done as a feature instead of fix), just delegating to the kernel BPF interpreter in that case is a more straight forward, minimal fix and easy to backport. Fixes: ('ARM: 7259/3: net: JIT compiler for packet filters') Signed-off-by: Nicolas Schichan Acked-by: Daniel Borkmann Signed-off-by: David S. Commit 'bnx2x: Delay during kdump load' added a 5 seconds delay to bnx2x's probe function in the kdump case to let the firmware realize the old driver is gone. The problem with the delay is that it is per-device, so if you have several bnx2x NICs in NPAR mode, the delays can accumulate to minutes.

Fix it by adjusting the delay so that we do not wait more than necessary, i.e. No more delaying after 5 seconds of kernel boot time. Signed-off-by: Michal Schmidt Signed-off-by: David S.

In WRED mode, the backlog for a single virtual queue (VQ) should not be used to determine queue behavior; instead the backlog is summed across all VQs. This sum is currently used when calculating the average queue lengths. It also needs to be used when determining if the queue's hard limit has been reached, or when reporting each VQ's backlog via netlink. Q-backlog will only be used if the queue switches out of WRED mode. Signed-off-by: David Ward Signed-off-by: David S.

For listening endpoints bound to the wildcard address, we need to pass the wildcard address mapping to iwpmgetremoteinfo instead of the mapped address of the new child connection. Without this fix, and with iwarp port mapping enabled, each iwcxgb4 connection that is spawned from a listening endpoint bound to the wildcard address, will generate an annoying dmesg entry about failing to find the remote address mapping info, and the connection state displayed in debugfs under /sys/kernel/debug/iwcxgb4//eps will not have the peer's address/port mapping info. The connection still works though.

Fixes: ('RDMA/cxgb4: Report the actual address of the remote connecting peer') Signed-off-by: Steve Wise Reviewed-by: Tatyana Nikolova Reviewed-by: Jason Gunthorpe Signed-off-by: Doug Ledford. Commit ('MIPS: kernel: elf: Improve the overall ABI and FPU mode checks') reworked the ELF FP ABI mode selection logic, but when CONFIGMIPSO32FP64SUPPORT is enabled it breaks the use of binaries which have no PTMIPSABIFLAGS program header & associated.MIPS.abiflags section. A default mode is selected based upon whether the ELF contains MIPS32 or MIPS64 code, but that selection is made in archelfptproc.

Archelfptproc only executes when a PTMIPSABIFLAGS program header is found. If one is not found then archelfptproc is never called, and no default overallfpmode value is selected. When archcheckelf is called, both abi0 & abi1 are MIPSABIFPUNKNOWN which leads to both progreq & interpreq being set to nonereq. Nonereq matches none of the conditions for mode selection at the end of archcheckelf, so overallfpmode is left untouched. Finally once mipssetpersonalityfp is called the BUG in the default case is then hit & the kernel likely panics.

Fix this by moving the selection of a default overall mode to the start of archcheckelf, which runs once per ELF executed regardless of whether it has a PTMIPSABIFLAGS program header. Signed-off-by: Paul Burton Cc: Markos Chandras Cc: Matthew Fortune Cc: Ralf Baechle Cc: linux-mips@linux-mips.org Cc: stable@vger.kernel.org # v4.0+ Patchwork: Signed-off-by: Ralf Baechle. Pull power supply and reset fixes from Sebastian Reichel: 'misc fixes'. tag 'for-v4.1-rc' of git://git.infradead.org/battery-2.6: power: bq27x00battery: Add missing MODULEALIAS power: reset: Add MFDSYSCON depends for brcmstb power: reset: ltc2952: Remove bogus hrtimerstart return value checks powersupply: fix oops in colliebattery driver power/reset: at91: fix return value check in at91resetplatformprobe MAINTAINERS: Add me as maintainer of Nokia N900 power supply drivers axp288fuelgauge: Add original author details. Don't do clock-mode-select if clk NULL, since when building without CONFIGHAVECLK, clkget returns NULL and clkgetrate returns 0. Doing clock-mode-select in this cause causes kszphyprobe to return -EINVAL and thus prevents the device from being probed.

The original code (before regression) would return 0 when building without CONFIGHAVECLK. Cc: stable # 3.18+ Fixes: ('net/phy: micrel: Add clock support for KSZ8021/KSZ8031') Reviewed-by: Fabio Estevam Reviewed-by: Johan Hovold Signed-off-by: Niklas Cassel Signed-off-by: David S. Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed.

Wireless n 1202 driver for mac. KILLER WIRELESS N 1202 DRIVER FOR MAC DOWNLOAD - If you're a seller, Fulfillment by Amazon can help you increase your sales. Dell offers a variety of Software applications designed to provide you with the most optimized user and support experience possible.

Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch.

Libvirt Rpc: Retrieve Peer Pid Via New Getsockopt For Mac Pro

Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion.

Libvirt Rpc: Retrieve Peer Pid Via New Getsockopt For Mac 2017

Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews.