[PATCH 4/5] perf, x86: Support full width counting v3

From: Andi Kleen Recent Intel CPUs like Haswell and IvyBridge have a new alternative MSR range for perfctrs that allows writing the full counter width. Enable this range if the hardware reports it using a new capability bit. This lowers the overhead of perf stat slightly because it has to do

[PATCH 3/5] perf, x86: Basic Haswell PEBS support v4

From: Andi Kleen Add basic PEBS support for Haswell. The constraints are similar to SandyBridge with a few new events. v2: Readd missing pebs_aliases v3: Readd missing hunk. Fix some constraints. v4: Fix typo in PEBS event table (Stephane Eranian) Reviewed-by: Stephane Eranian Signed-off-by:

Basic perf PMU support for Haswell v6

This is based on v7 of the full Haswell PMU support, but ported to the latest perf/core and stripped down to the bare bones Only for very extremly basic usage. Most interesting new features are not in this patchkit (full version is

[PATCH 2/5] perf, x86: Basic Haswell PMU support v4

From: Andi Kleen Add basic Haswell PMU support. Similar to SandyBridge, but has a few new events and two new counter bits. There are some new counter flags that need to be prevented from being set on fixed counters, and allowed to be set for generic counters. Also we add support for the

[PATCH] ARM: exynos: move exynos4210-combiner to drivers/irqchip

From: Rob Herring Exynos boot is broken with commit 0529e315 (ARM: use common irqchip_init for GIC init). This commit split the irqchip initialization into 2 calls to of_irq_init. This does not work because of_irq_init requires interrupt parents to be in the match list. Rather than reverting

Re: [PATCH 06/16] ARM idle: delete pm_idle

Len Brown writes: > From: Len Brown > > pm_idle() on ARM was a synonym for default_idle(), > so simply invoke default_idle() directly. > > Signed-off-by: Len Brown > Cc: linux-arm-ker...@lists.infradead.org Looks good to me. Tested this patch along with 15/16 (removes global declaration) on

[PATCH] net: ethernet: ti: remove redundant NULL check.

cpdma_chan_destroy() on a NULL pointer is a no-op, so the NULL check in cpdma_ctlr_destroy() can safely be removed. Signed-off-by: Cyril Roelandt --- drivers/net/ethernet/ti/davinci_cpdma.c |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH 5/5] perf, x86: Move NMI clearing to end of PMI handler after the counter registers are reset

From: Andi Kleen This avoids some problems with spurious PMIs on Haswell. Haswell seems to behave more like P4 in this regard. Do the same thing as the P4 perf handler by unmasking the NMI only at the end. Shouldn't make any difference for earlier family 6 cores. Tested on Haswell, IvyBridge,

[GIT PULL] autofs: automounter fix for 3.8

Hi Linus, please consider pulling this late fix for autofs, which unbreaks automounter support for the parisc architecture (and probably aarch64 as well). Thanks, Helge --- The following changes since commit 124b69b6cc1020fff589312c62fcaf360abd8d12: Merge tag 'fixes-for-linus' of

[PATCH 1/5] perf, x86: Add Haswell PEBS record support v3

From: Andi Kleen Add support for the Haswell extended (fmt2) PEBS format. It has a superset of the nhm (fmt1) PEBS fields, but has a longer record so we need to adjust the code paths. The main advantage is the new "EventingRip" support which directly gives the instruction, not off-by-one

[PATCH] kbuild: limit dtc+cpp include path

From: Stephen Warren Device tree source files may now include header files. The intent is that those header files define/name constants used as part of the DT bindings. Currently this feature is open to abuse, since any kernel header file at all can be included, This could allow device tree

Re: compositing broken in -next (idr bug)

On 02/12/2013 10:55 PM, Jiri Slaby wrote: > --- a/drivers/gpu/drm/drm_gem.c > +++ b/drivers/gpu/drm/drm_gem.c > @@ -453,7 +453,8 @@ drm_gem_flink_ioctl(struct drm_device *dev, void *data, > spin_lock(>object_name_lock); > if (!obj->name) { > ret =

Re: [PATCH] MAINTAINERS: Remove Jarod Wilson and orphan LIRC drivers

Hi On 02/12/2013 10:20 PM, Joe Perches wrote: His email bounces jwil...@redhat.com should work I think. Note I think this may be the right call, but asking him directly is better :) Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: compositing broken in -next (idr bug)

On 02/12/2013 10:58 PM, Tejun Heo wrote: > Hello, Jiri. > > On Tue, Feb 12, 2013 at 10:55:37PM +0100, Jiri Slaby wrote: >> this commit in -next causes my KDE to get stuck while starting. I see >> only the splash screen. If I disable effects by alt-shift-f12, it continues. >> >> I bisected it to

Re: compositing broken in -next (idr bug)

Hello, Jiri. On Tue, Feb 12, 2013 at 10:55:37PM +0100, Jiri Slaby wrote: > this commit in -next causes my KDE to get stuck while starting. I see > only the splash screen. If I disable effects by alt-shift-f12, it continues. > > I bisected it to this commit: > commit

compositing broken in -next (idr bug)

Hi, this commit in -next causes my KDE to get stuck while starting. I see only the splash screen. If I disable effects by alt-shift-f12, it continues. I bisected it to this commit: commit 430440fce7da4ad52c2af06a04a5132e5d19faaf Author: Tejun Heo Date: Thu Feb 7 12:31:37 2013 +1100 drm:

Re: [PATCH 0/5] Add P state driver for Intel Core Processors

On Wed, Feb 06, 2013 at 09:02:07AM -0800, dirk.brande...@gmail.com wrote: > From: Dirk Brandewie > > This driver implements a scaling driver with an internal governor for > Intel Core processors. The driver follows the same model as the > Transmeta scaling driver (longrun.c) and implements

Re: linux-next: Tree for Feb 12 (drm_pci.c)

On Tue, Feb 12, 2013 at 08:06:00AM -0800, Randy Dunlap wrote: > On 02/11/13 21:09, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20130211: > > > > > when CONFIG_PCI is not enabled (on x86_64): > > CC [M] drivers/gpu/drm/drm_pci.o > drivers/gpu/drm/drm_pci.c: In function

Re: [PATCH 0/3] NBD fixes for caching and block device flags

On Tue, 12 Feb 2013 17:06:08 +0100 Paolo Bonzini wrote: > The first two patches improve the behavior of NBD with respect to the host > cache---respectively the server's cache and the client's. The first adds > support for flushing the backing storage, so that NBD is safe against > power losses.

Re: [PATCH 2/3] nbd: fsync and kill block device on shutdown

On Tue, 12 Feb 2013 17:06:10 +0100 Paolo Bonzini wrote: > There are two problems with shutdown in the NBD driver. The first is > that receiving the NBD_DISCONNECT ioctl does not sync the filesystem; > this is useful because BLKFLSBUF is restricted to processes that have > CAP_SYS_ADMIN, and the

Re: [RFC][PATCH v2] tracing/syscalls: Allow archs to ignore tracing compat syscalls

On Tue, 2013-02-12 at 13:33 -0800, H. Peter Anvin wrote: > On 02/12/2013 01:18 PM, Steven Rostedt wrote: > > [ > > Peter, how about this patch. Instead of showing garbage, just never > > trace compat syscalls, if the arch needs to ignore it. > > > > However, users can still use the

Re: linux-next: Tree for Feb 12 [ WARNING: at drivers/tty/tty_buffer.c:427 flush_to_ldisc | tty is NULL ]

On Tue, Feb 12, 2013 at 6:09 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20130211: > > The acpi tree lost its build failure. > > The net-next tree gained a conflict against the net tree. > > The arm-soc tree gained conflicts against the usb and metag trees. > >

Re: [char-misc-next 01/12 v3] mei: Rename mei_device to mei_host

On Tue, Feb 12, 2013 at 10:29:35PM +0100, Samuel Ortiz wrote: > Hi Tomas, > > On Tue, Feb 12, 2013 at 09:17:21PM +, Winkler, Tomas wrote: > > > > > > > In preparation for the MEI bus code merge, we rename the mei_device > > > structure to mei_host. > > > struct mei_device will be used for

Re: [RFC][PATCH v2] tracing/syscalls: Allow archs to ignore tracing compat syscalls

On 02/12/2013 01:18 PM, Steven Rostedt wrote: > [ > Peter, how about this patch. Instead of showing garbage, just never > trace compat syscalls, if the arch needs to ignore it. > > However, users can still use the raw_syscall interface if they need to > trace them. > ] > I can go for

NUMA allocations fail to be numa allocated

using libnuma calls on RedHat 6.3 x86_64 with the default kernel and up to 3.4.29 don't allocate on the specified numa nodes, even when forced with numactl. It appears that setting the NUMA policy, and or numa nodes does little for large allocations. Using HUGETLBFS, and you get memory on most

Re: [PATCH 1/3] nbd: support FLUSH requests

On Tue, 12 Feb 2013 19:06:09 +0100 Paolo Bonzini wrote: > Il 12/02/2013 18:37, Alex Bligh ha scritto: > > For my education, why remove the FUA stuff? > > Because I had no way to test it. > > >>> > > Hmmm... the underlying storage could be md/dm RAIDs in which case FUA > >>> > > should be

Re: [char-misc-next 01/12 v3] mei: Rename mei_device to mei_host

Hi Tomas, On Tue, Feb 12, 2013 at 09:17:21PM +, Winkler, Tomas wrote: > > > > In preparation for the MEI bus code merge, we rename the mei_device > > structure to mei_host. > > struct mei_device will be used for devices on the MEI bus in order to follow > > exisiting driver model

Re: [PATCH v2] lib/scatterlist: add simple page iterator

On Tue, 12 Feb 2013 19:07:20 +0200 Imre Deak wrote: > > So, exactly how big is this thing, and how do we know it's better this > > way than if we were to uninline some/all of the helpers? > > I admit I only hoped compiler optimization would keep the inlined parts > at a minimum, but now I

RE: [PATCH 0/2] NFSD: fix races in service per-net resources allocation

The "+" thing seems a little odd. Why not use "||" instead? The sum of the two returns isn't really the important thing, is it? It is that either call to svc_close_list() returns non-zero. Thanx... ps -Original Message- From: linux-nfs-ow...@vger.kernel.org

[GIT PULL] arch/tile bug fixes for v3.8

Linus, Please pull the following changes for 3.8 from: git://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile.git stable This includes a variety of minor bug fixes, mostly to do with testing "make allyesconfig", "make allmodconfig", "make allnoconfig", inspired to Tejun Heo's

Re: [REGRESSION] -rc7/-rc4+: unable to USB boot - enumeration partially broken (was: Linux v3.8-rc7)

Hi, On Tue, Feb 12, 2013 at 08:16:17AM -0800, Greg KH wrote: > On Tue, Feb 12, 2013 at 05:07:27PM +0100, Andreas Mohr wrote: > > On Sun, Feb 10, 2013 at 03:05:54PM +0100, Andreas Mohr wrote: > > > Regression sorta confirmed now. -rc3 with a fully suitable .config does > > > not boot either. Will

Re: [PATCH 1/6] idr: fix top layer handling

On Tue, 12 Feb 2013 09:10:49 -0800 Tejun Heo wrote: > Hey, Andrew. > > On Mon, Feb 11, 2013 at 03:39:55PM -0800, Andrew Morton wrote: > > This doesn't apply happily to 3.7, so Greg will be needing a redone > > version when the time arrives. > > > > But does it really need backporting? Is

Re: [PATCH linux-next] lockd: nlmsvc_mark_resources(): avoid stack overflow

On Tue, Feb 12, 2013 at 12:48:58PM -0700, Tim Gardner wrote: > Dynamically allocate the NLM host structure in order to avoid stack overflow. > nlmsvc_mark_resources() is several call levels deep in a stack > that has a number of large variables. 512 bytes seems like a lot > on the stack at this

[PATCH] MAINTAINERS: Remove Jarod Wilson and orphan LIRC drivers

His email bounces and he hasn't done work on these sections in a couple of years. Signed-off-by: Joe Perches --- MAINTAINERS | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 1d0651e..8d47b3a 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@

RE: [PATCH v6 -next 0/2] make efivars/efi_pstore interrupt-safe

> Changelog > v5 -> v6 > - Rebase to a latest linux-next tree. > - Modify a comment from "efivar_update_sysfs_entry" to > "efivar_update_sysfs_entries" in include/linux/efi.h (Patch 2/2) Applied to my internal pstore topic branch - which feeds to linux-next. Note that my branch was based

[RFC][PATCH v2] tracing/syscalls: Allow archs to ignore tracing compat syscalls

[ Peter, how about this patch. Instead of showing garbage, just never trace compat syscalls, if the arch needs to ignore it. However, users can still use the raw_syscall interface if they need to trace them. ] The tracing of ia32 compat system calls has been a bit of a pain as they use

Re: [PATCH linux-next] lockd: nlmclnt_reclaim(): avoid stack overflow

On Tue, Feb 12, 2013 at 12:33:15PM -0700, Tim Gardner wrote: > Even though nlmclnt_reclaim() is only one call into the stack frame, > 928 bytes on the stack seems like a lot. Recode to dynamically > allocate the request structure once from within the reclaimer task, > then pass this pointer into

RE: [char-misc-next 01/12 v3] mei: Rename mei_device to mei_host

> In preparation for the MEI bus code merge, we rename the mei_device > structure to mei_host. > struct mei_device will be used for devices on the MEI bus in order to follow > exisiting driver model implementations practices. > I'd like to NACK this name, we use 'host' for the host part of the

RE: [PATCH] pstore: Create a convenient mount point for pstore

> > Signed-off-by: Josh Boyer > > Acked-by: Kees Cook Queued for next merge window. Thanks. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: pull request: wireless 2013-02-12

From: "John W. Linville" Date: Tue, 12 Feb 2013 11:03:16 -0500 > Here is another handful of late-breaking fixes intended for the 3.8 > stream... Hopefully the will still make it! :-) > > There are three mac80211 fixes pulled from Johannes: > > "Here are three fixes still for the 3.8 stream,

[ 08/61] Bluetooth: Fix handling of unexpected SMP PDUs

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hedberg commit 8cf9fa1240229cbdd888236c0c43fcbad680cf00 upstream. The conn->smp_chan pointer can be NULL if SMP PDUs arrive at unexpected moments. To avoid NULL pointer dereferences the

[ 02/61] rtlwifi: Fix scheduling while atomic bug

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Larry Finger commit a5ffbe0a1993a27072742ef7db6cf9839956fce9 upstream. Kernel commits 41affd5 and 6539306 changed the locking in rtl_lps_leave() from a spinlock to a mutex by doing the calls

[ 07/61] virtio_console: Dont access uninitialized data.

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Sjur Brændeland commit aded024a12b32fc1ed9a80639681daae2d07ec25 upstream. Don't access uninitialized work-queue when removing device. The work queue is initialized only if the device

[ 09/61] Revert "iwlwifi: fix the reclaimed packet tracking upon flush queue"

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit ae023b2795d36f0f077e157428eb7eafa29ee412 upstream. This reverts commit f590dcec944552f9a4a61155810f3abd17d6465d which has been reported to cause issues. See

[ 10/61] can: c_can: Set reserved bit in IFx_MASK2 to 1 on write

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Stein commit 2bd3bc4e8472424f1a6009825397639a8968920a upstream. According to C_CAN documentation, the reserved bit in IFx_MASK2 register is fixed 1. Signed-off-by: Alexander Stein

[ 11/61] mwifiex: fix incomplete scan in case of IE parsing error

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Bing Zhao commit 8a7d7cbf7b5ff9912ef50b3e94c9ad9f37b1c75f upstream. A scan request is split into multiple scan commands queued in scan_pending_q. Each scan command will be sent to firmware and

[ 12/61] e1000e: enable ECC on I217/I218 to catch packet buffer memory errors

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Bruce Allan commit 286003048aaef49b26bb9d93611dc69085e8982e upstream. In rare instances, memory errors have been detected in the internal packet buffer memory on I217/I218 when stressed under

Re: Performance issue since 3.2.6

Hello, A quick update on my latest tests : I was able to compile a working 3.7.1 kernel (by 'working', I mean with no performance penalty). I'm sure 3.7.7 will be OK also (do you want me to test latest RC of 3.8 ?) I had to disable CONFIG_ACPI_PROCESSOR to disable power management. So now these

[ 13/61] media: pwc-if: must check vb2_queue_init() success

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit eda94710d6502672c5ee7de198fa78a63ddfae3a upstream. drivers/media/usb/pwc/pwc-if.c: In function 'usb_pwc_probe': drivers/media/usb/pwc/pwc-if.c:1003:16: warning:

[ 14/61] ath9k_hw: fix calibration issues on chainmask that dont include chain 0

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau commit 4a8f199508d79ff8a7d1e22f47b912baaf225336 upstream. Signed-off-by: Felix Fietkau Signed-off-by: John W. Linville Signed-off-by: CAI Qian Signed-off-by: Greg

[ 16/61] dm thin: fix queue limits stacking

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit 0f640dca08330dfc7820d610578e5935b5e654b2 upstream. thin_io_hints() is blindly copying the queue limits from the thin-pool which can lead to incorrect limits being set. The

[ 18/61] ipv6: fix the noflags test in addrconf_get_prefix_route

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Romain Kuntz [ Upstream commit 85da53bf1c336bb07ac038fb951403ab0478d2c5 ] The tests on the flags in addrconf_get_prefix_route() does no make much sense: the 'noflags' parameter contains the

Re: iio: adc: add exynos5 adc driver under iio framwork

On Wed, Jan 23, 2013 at 04:58:06AM -, Naveen Krishna Chatradhi wrote: > This patch add an ADC IP found on EXYNOS5 series socs from Samsung. > Also adds the Documentation for device tree bindings. > > Signed-off-by: Naveen Krishna Chatradhi > > --- > Changes since v1: > > 1. Fixed comments

[ 21/61] MAINTAINERS: Stephen Hemminger email change

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Hemminger [ Upstream commit adbbf69d1a54abf424e91875746a610dcc80017d ] I changed my email because the vyatta.com mail server is now redirected to brocade.com; and the Brocade mail

[ 19/61] net, wireless: overwrite default_ethtool_ops

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Stanislaw Gruszka [ Upstream commit d07d7507bfb4e23735c9b83e397c43e1e8a173e8 ] Since: commit 2c60db037034d27f8c636403355d52872da92f81 Author: Eric Dumazet Date: Sun Sep 16 09:17:26 2012

[ 06/61] IB/qib: Fix for broken sparse warning fix

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Mike Marciniszyn commit d359f35430c4ea4dd4e24d809aeaeff1fa54c314 upstream. Commit 1fb9fed6d489 ("IB/qib: Fix QP RCU sparse warning") broke QP hash list deletion in qp_remove() badly. This

[ 15/61] mfd: db8500-prcmu: Fix irqdomain usage

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 89d9b1c99374997d68910ba49d5b7df80e7f2061 upstream. This fixes two issues with the DB8500 PRCMU irqdomain: - You have to state the irq base 0 to get a linear domain for

[ 03/61] regulator: max8998: fix incorrect min_uV value for ldo10

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit 36a6f8c035760dcbd0c3acb4c2fd56268588a9cb upstream. Correct value for minimal voltage for ldo10 output is 95 uV. This patch fixes the typo introduced by patch

[ 05/61] regulator: s2mps11: fix incorrect register for buck10

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Alim Akhtar commit c76edd52bf19c9d01da7edc4ff04d3707c299779 upstream. For BUCK10 the control registers are wrongly set as buck9 control register This patch corrects the control registers for

[ 04/61] regulator: clear state each invocation of of_regulator_match

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Warren commit a2f95c363701deba2205f81929b40222ea6f4f80 upstream. of_regulator_match() saves some dynamcially allocated state into the match table that's passed to it. By implementation

[ 01/61] rtlwifi: Fix the usage of the wrong variable in usb.c

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Larry Finger commit 0a06ad8e3a1cb5311b7dbafde45410aa1bce9d40 upstream. In routine _rtl_rx_pre_process(), skb_dequeue() is called to get an skb; however, the wrong variable name is used in

[ 22/61] ipv6: fix header length calculation in ip6_append_data()

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Romain KUNTZ [ Upstream commit 7efdba5bd9a2f3e2059beeb45c9fa55eefe1bced ] Commit 299b0767 (ipv6: Fix IPsec slowpath fragmentation problem) has introduced a error in the header length

[ 23/61] macvlan: fix macvlan_get_size()

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 01fe944f1024bd4e5c327ddbe8d657656b66af2f ] commit df8ef8f3aaa (macvlan: add FDB bridge ops and macvlan flags) forgot to update macvlan_get_size() after the

[ 24/61] net: calxedaxgmac: throw away overrun frames

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Rob Herring [ Upstream commit d6fb3be544b46a7611a3373fcaa62b5b0be01888 ] The xgmac driver assumes 1 frame per descriptor. If a frame larger than the descriptor's buffer size is received, the

[ 27/61] tcp: fix incorrect LOCKDROPPEDICMPS counter

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit b74aa930ef49a3c0d8e4c1987f89decac768fb2c ] commit 563d34d057 (tcp: dont drop MTU reduction indications) added an error leading to incorrect accounting of

[ 28/61] isdn/gigaset: fix zero size border case in debug dump

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Tilman Schmidt [ Upstream commit d721a1752ba544df8d7d36959038b26bc92bdf80 ] If subtracting 12 from l leaves zero we'd do a zero size allocation, leading to an oops later when we try to set

[ 29/61] netxen: fix off by one bug in netxen_release_tx_buffer()

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit a05948f296ce103989b28a2606e47d2e287c3c89 ] Christoph Paasch found netxen could trigger a BUG in its dismantle phase, in netxen_release_tx_buffer(), using full

Re: [PATCH] usb: musb: fix context save over suspend.

NeilBrown writes: > On Mon, 21 Jan 2013 13:38:59 +0200 Igor Grinberg > wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi Neil, >> >> On 01/21/13 11:28, NeilBrown wrote: >> > >> > >> > The standard suspend sequence involves runtime_resuming >> > devices before suspending

[ 30/61] r8169: remove the obsolete and incorrect AMD workaround

3.7-stable review patch. If anyone has any objections, please let me know. -- From: =?UTF-8?q?Timo=20Ter=C3=A4s?= [ Upstream commit 5d0feaff230c0abfe4a112e6f09f096ed99e0b2d ] This was introduced in commit 6dccd16 "r8169: merge with version 6.001.00 of Realtek's r8169

[ 31/61] net: loopback: fix a dst refcounting issue

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 794ed393b707f01858f5ebe2ae5eabaf89d00022 ] Ben Greear reported crashes in ip_rcv_finish() on a stress test involving many macvlans. We tracked the bug to a dst

[ 33/61] pktgen: correctly handle failures when adding a device

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 604dfd6efc9b79bce432f2394791708d8e8f6efc ] The return value of pktgen_add_device() is not checked, so even if we fail to add some device, for example, non-exist

[ 34/61] ipv6: do not create neighbor entries for local delivery

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner [ Upstream commit bd30e947207e2ea0ff2c08f5b4a03025ddce48d3 ] They will be created at output, if ever needed. This avoids creating empty neighbor entries when

[ 36/61] packet: fix leakage of tx_ring memory

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Phil Sutter [ Upstream commit 9665d5d62487e8e7b1f546c00e11107155384b9a ] When releasing a packet socket, the routine packet_set_ring() is reused to free rings instead of allocating them. But

[ 38/61] atm/iphase: rename fregt_t -> ffreg_t

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Carstens [ Upstream commit ab54ee80aa7585f9666ff4dd665441d7ce41f1e8 ] We have conflicting type qualifiers for "freg_t" in s390's ptrace.h and the iphase atm device driver, which causes

[ 37/61] ipv6/ip6_gre: fix error case handling in ip6gre_tunnel_xmit()

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Tommi Rantala [ Upstream commit 41ab3e31bd50b42c85ac0aa0469642866aee2a9a ] ip6gre_tunnel_xmit() is leaking the skb when we hit this error branch, and the -1 return value from this function is

[ 39/61] xen/netback: shutdown the ring if it contains garbage.

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Ian Campbell [ Upstream commit 48856286b64e4b66ec62b94e504d0b29c1ade664 ] A buggy or malicious frontend should not be able to confuse netback. If we spot anything which is not as it should be

[ 41/61] xen/netback: free already allocated memory on failure in xen_netbk_get_requests

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Ian Campbell [ Upstream commit 4cc7c1cb7b11b6f3515bd9075527576a1eecc4aa ] Signed-off-by: Ian Campbell Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman ---

[ 42/61] netback: correct netbk_tx_err to handle wrap around.

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Ian Campbell [ Upstream commit b9149729ebdcfce63f853aa54a404c6a8f6ebbf3 ] Signed-off-by: Ian Campbell Acked-by: Jan Beulich Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman

[ 35/61] via-rhine: Fix bugs in NAPI support.

3.7-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 559bcac35facfed49ab4f408e162971612dcfdf3 ] 1) rhine_tx() should use dev_kfree_skb() not dev_kfree_skb_irq() 2) rhine_slow_event_task's NAPI triggering

[ 45/61] ipv6: Add an error handler for icmp6

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert [ Upstream commit 6f809da27c94425e07be4a64d5093e1df95188e9 ] pmtu and redirect events are now handled in the protocols error handler, so add an error handler for icmp6 to do

[ 46/61] ipv4: Invalidate the socket cached route on pmtu events if possible

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert [ Upstream commit 9cb3a50c5f63ed745702972f66eaee8767659acd ] The route lookup in ipv4_sk_update_pmtu() might return a route different from the route we cached at the socket.

[ 49/61] sctp: refactor sctp_outq_teardown to insure proper re-initalization

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Neil Horman [ Upstream commit 2f94aabd9f6c925d77aecb3ff020f1cc12ed8f86 ] Jamie Parsons reported a problem recently, in which the re-initalization of an association (The duplicate init case),

[ 50/61] net: sctp: sctp_setsockopt_auth_key: use kzfree instead of kfree

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit 6ba542a291a5e558603ac51cda9bded347ce7627 ] In sctp_setsockopt_auth_key, we create a temporary copy of the user passed shared auth key for the endpoint or

[ 51/61] net: sctp: sctp_endpoint_free: zero out secret key data

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit b5c37fe6e24eec194bb29d22fdd55d73bcc709bf ] On sctp_endpoint_destroy, previously used sensitive keying material should be zeroed out before the memory is

[ 52/61] tcp: detect SYN/data drop when F-RTO is disabled

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Yuchung Cheng [ Upstream commit 66555e92fb7a619188c02cceae4bbc414f15f96d ] On receiving the SYN-ACK, Fast Open checks icsk_retransmit for SYN retransmission to detect SYN/data drops. But if

[ 54/61] tcp: frto should not set snd_cwnd to 0

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 2e5f421211ff76c17130b4597bc06df4eeead24f ] Commit 9dc274151a548 (tcp: fix ABC in tcp_slow_start()) uncovered a bug in FRTO code : tcp_process_frto() is setting

[ 55/61] tcp: fix for zero packets_in_flight was too broad

3.7-stable review patch. If anyone has any objections, please let me know. -- From: =?UTF-8?q?Ilpo=20J=C3=A4rvinen?= [ Upstream commit 6731d2095bd4aef18027c72ef845ab1087c3ba63 ] There are transients during normal FRTO procedure during which the packets_in_flight can go to

[ 56/61] tcp: dont abort splice() after small transfers

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Willy Tarreau [ Upstream commit 02275a2ee7c0ea475b6f4a6428f5df592bc9d30b ] TCP coalescing added a regression in splice(socket->pipe) performance, for some workloads because of the way

[tip:x86/mm] x86, mm: Redesign get_user with a __builtin_choose_expr hack

Commit-ID: 3578baaed4613a9fc09bab9f79f6ce2ac682e8a3 Gitweb: http://git.kernel.org/tip/3578baaed4613a9fc09bab9f79f6ce2ac682e8a3 Author: H. Peter Anvin AuthorDate: Tue, 12 Feb 2013 11:47:31 -0800 Committer: H. Peter Anvin CommitDate: Tue, 12 Feb 2013 12:46:40 -0800 x86, mm: Redesign

[ 57/61] tcp: splice: fix an infinite loop in tcp_read_sock()

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit ff905b1e4aad8ccbbb0d42f7137f19482742ff07 ] commit 02275a2ee7c0 (tcp: don't abort splice() after small transfers) added a regression. [ 83.843570] INFO:

[ 04/22] mac80211: synchronize scan off/on-channel and PS states

3.0-stable review patch. If anyone has any objections, please let me know. -- From: Stanislaw Gruszka commit aacde9ee45225f7e0b90960f479aef83c66bfdc0 upstream. Since: commit b23b025fe246f3acc2988eb6d400df34c27cb8ae Author: Ben Greear Date: Fri Feb 4 11:54:17 2011 -0800

[ 53/61] tcp: fix an infinite loop in tcp_slow_start()

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 973ec449bb4f2b8c514bacbcb4d9506fc31c8ce3 ] Since commit 9dc274151a548 (tcp: fix ABC in tcp_slow_start()), a nul snd_cwnd triggers an infinite loop in

[ 61/61] drm/nouveau: add lockdep annotations

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Marcin Slusarz commit 5f97ab913cf0fbc378ea8ffc3ee66f4890d11c55 upstream. 1) Lockdep thinks all nouveau subdevs belong to the same class and can be locked in arbitrary order, which is not true

[ 43/61] ipv4: Remove output route check in ipv4_mtu

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert [ Upstream commit 38d523e2948162776903349c89d65f7b9370dadb ] The output route check was introduced with git commit 261663b0 (ipv4: Don't use the cached pmtu informations for

[ 47/61] ipv4: Add a socket release callback for datagram sockets

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert [ Upstream commit 8141ed9fcedb278f4a3a78680591bef1e55f75fb ] This implements a socket release callback function to check if the socket cached route got invalid during the

[ 44/61] ipv4: Dont update the pmtu on mtu locked routes

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert [ Upstream commit fa1e492aa3cbafba9f8fc6d05e5b08a3091daf4a ] Routes with locked mtu should not use learned pmtu informations, so do not update the pmtu on these routes.

[ 40/61] xen/netback: dont leak pages on failure in xen_netbk_tx_check_gop.

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Matthew Daley [ Upstream commit 7d5145d8eb2b9791533ffe4dc003b129b9696c48 ] Signed-off-by: Matthew Daley Reviewed-by: Konrad Rzeszutek Wilk Acked-by: Ian Campbell Acked-by: Jan Beulich

[ 32/61] IP_GRE: Fix kernel panic in IP_GRE with GRE csum.

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Pravin B Shelar [ Upstream commit 5465740ace36f179de5bb0ccb5d46ddeb945e309 ] Due to IP_GRE GSO support, GRE can recieve non linear skb which results in panic in case of GRE_CSUM. Following

[ 25/61] net/mlx4_en: Fix bridged vSwitch configuration for non SRIOV mode

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Yan Burman [ Upstream commit 213815a1e6ae70b9648483b110bc5081795f99e8 ] Commit 5b4c4d36860e "mlx4_en: Allow communication between functions on same host" introduced a regression under which a

[ 17/61] net: prevent setting ttl=0 via IP_TTL

3.7-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit c9be4a5c49cf51cc70a993f004c5bb30067a65ce ] A regression is introduced by the following commit: commit 4d52cfbef6266092d535237ba5a4b981458ab171

<    1   2   3   4   5   6   7   8   9   10   >