[PATCH 3.4 115/172] ASoC: wm8904: Fix wrong value references for boolean kctl

2015-06-16 Thread lizf
From: Takashi Iwai 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit eaddf6fd959074f6a6e71deffe079c71eef35da6 upstream. The correct values referred by a boolean control are value.integer.value[], not value.enumerated.item[]. The former is

[PATCH 3.4 117/172] ASoC: wm8960: Fix wrong value references for boolean kctl

2015-06-16 Thread lizf
From: Takashi Iwai 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit b4a18c8b1af15ebfa9054a3d2aef7b0a7e6f2a05 upstream. The correct values referred by a boolean control are value.integer.value[], not value.enumerated.item[]. The former is

[PATCH 3.4 120/172] IB/mlx4: Saturate RoCE port PMA counters in case of overflow

2015-06-16 Thread lizf
From: Majd Dibbiny 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 61a3855bb726cbb062ef02a31a832dea455456e0 upstream. For RoCE ports, we set the u32 PMA values based on u64 HCA counters. In case of overflow, according to the IB spec, we

[PATCH 3.4 108/172] x86/asm/entry/32: Fix user_mode() misuses

2015-06-16 Thread lizf
From: Andy Lutomirski 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 394838c96013ba414a24ffe7a2a593a9154daadf upstream. The one in do_debug() is probably harmless, but better safe than sorry. Signed-off-by: Andy Lutomirski Cc:

[PATCH 3.4 092/172] ALSA: snd-usb: add quirks for Roland UA-22

2015-06-16 Thread lizf
From: Daniel Mack 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit fcdcd1dec6d2c7b718385ec743ae5a9a233edad4 upstream. The device complies to the UAC1 standard but hides that fact with proprietary descriptors. The autodetect quirk for

[PATCH 3.4 125/172] net: ethernet: pcnet32: Setup the SRAM and NOUFLO on Am79C97{3, 5}

2015-06-16 Thread lizf
From: Markos Chandras 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 87f966d97b89774162df04d2106c6350c8fe4cb3 upstream. On a MIPS Malta board, tons of fifo underflow errors have been observed when using u-boot as bootloader instead of

[PATCH 3.4 124/172] nbd: fix possible memory leak

2015-06-16 Thread lizf
From: Sudip Mukherjee 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit ff6b8090e26ef7649ef0cc6b42389141ef48b0cf upstream. we have already allocated memory for nbd_dev, but we were not releasing that memory and just returning the error

[PATCH 3.4 127/172] sched: Fix RLIMIT_RTTIME when PI-boosting to RT

2015-06-16 Thread lizf
From: Brian Silverman 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 746db9443ea57fd9c059f62c4bfbf41cf224fe13 upstream. When non-realtime tasks get priority-inheritance boosted to a realtime scheduling class, RLIMIT_RTTIME starts to

Re: [PATCH 4/8] ARCv2: perf: Support sampling events using overflow interrupts

2015-06-16 Thread Peter Zijlstra
On Tue, Jun 16, 2015 at 05:37:40AM +, Vineet Gupta wrote: > On Monday 15 June 2015 09:55 PM, Peter Zijlstra wrote: > > On Tue, Jun 09, 2015 at 05:49:28PM +0530, Vineet Gupta wrote: > >> + if (arc_pmu->has_interrupts) { > >> + int irq = platform_get_irq(pdev, 0); > > Hmm, so you're

Re: [PATCH v2] gpio: pcf857x: handle only enabled irqs

2015-06-16 Thread Geert Uytterhoeven
On Tue, Jun 16, 2015 at 10:58 AM, Linus Walleij wrote: > wrote: > >> Now pcf857x_irq() IRQ's dispatcher will try to run nested >> IRQ handlers for each GPIO pin which state has changed. >> Such IRQs are, actually, spurious and nested IRQ handlers >> have to be called only for IRQs wich were

[PATCH 3.4 126/172] perf: Fix irq_work 'tail' recursion

2015-06-16 Thread lizf
From: Peter Zijlstra 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit d525211f9d1be8b523ec7633f080f2116f5ea536 upstream. Vince reported a watchdog lockup like: [] perf_tp_event+0xc4/0x210 [] perf_trace_lock+0x12a/0x160

Re: serial: stm32-usart: use of undefined SERIAL_STM32_USART_CONSOLE

2015-06-16 Thread Maxime Coquelin
Hi Andreas, 2015-06-15 14:45 GMT+02:00 Andreas Ruprecht : > Hi Maxime, > > your commit 48a6092fb41f ("serial: stm32-usart: Add STM32 USART Driver") > was merged into linux-next today (i.e., next-20150615), and contains the > following piece of code: > > [...] > #if

[PATCH 3.4 131/172] ALSA: hda - Add one more node in the EAPD supporting candidate list

2015-06-16 Thread lizf
From: Hui Wang 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit af95b41426e0b58279f8ff0ebe420df49a4e96b8 upstream. We have a HP machine which use the codec node 0x17 connecting the internal speaker, and from the node capability, we saw

[PATCH 3.4 135/172] usb: xhci: apply XHCI_AVOID_BEI quirk to all Intel xHCI controllers

2015-06-16 Thread lizf
From: Lu Baolu 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 227a4fd801c8a9fa2c4700ab98ec1aec06e3b44d upstream. When a device with an isochronous endpoint is plugged into the Intel xHCI host controller, and the driver submits multiple

[PATCH 3.4 128/172] writeback: fix possible underflow in write bandwidth calculation

2015-06-16 Thread lizf
From: Tejun Heo 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit c72efb658f7c8b27ca3d0efb5cfd5ded9fcac89e upstream. >From 1ebf33901ecc75d9496862dceb1ef0377980587c Mon Sep 17 00:00:00 2001 From: Tejun Heo Date: Mon, 23 Mar 2015 00:08:19

[PATCH 3.4 134/172] usb: xhci: handle Config Error Change (CEC) in xhci driver

2015-06-16 Thread lizf
From: Lu Baolu 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 9425183d177aa4a2f09d01a74925124f0778b595 upstream. Linux xHCI driver doesn't report and handle port cofig error change. If Port Configure Error for root hub port occurs, CEC

[PATCH 3.4 137/172] USB: ftdi_sio: Use jtag quirk for SNAP Connect E10

2015-06-16 Thread lizf
From: Doug Goldstein 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit b229a0f840f774d29d8fedbf5deb344ca36b7f1a upstream. This patch uses the existing CALAO Systems ftdi_8u2232c_probe in order to avoid attaching a TTY to the JTAG port as

[PATCH 3.4 140/172] mac80211: fix RX A-MPDU session reorder timer deletion

2015-06-16 Thread lizf
From: Johannes Berg 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 788211d81bfdf9b6a547d0530f206ba6ee76b107 upstream. There's an issue with the way the RX A-MPDU reorder timer is deleted that can cause a kernel crash like this: *

[PATCH 3.4 138/172] radeon: Do not directly dereference pointers to BIOS area.

2015-06-16 Thread lizf
From: David Miller 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit f2c9e560b406f2f6b14b345c7da33467dee9cdf2 upstream. Use readb() and memcpy_fromio() accessors instead. Reviewed-by: Christian König Signed-off-by: David S. Miller

Re: [RFC NEXT] mm: Fix suspicious RCU usage at kernel/sched/core.c:7318

2015-06-16 Thread Catalin Marinas
On Tue, Jun 16, 2015 at 09:44:24AM +0100, Catalin Marinas wrote: > On Mon, Jun 15, 2015 at 10:25:18PM +0100, Larry Finger wrote: > > Beginning at commit d52d399, the following INFO splat is logged: > > > > [2.816564] === > > [2.816986] [ INFO: suspicious RCU

[PATCH 3.4 139/172] x86/reboot: Add ASRock Q1900DC-ITX mainboard reboot quirk

2015-06-16 Thread lizf
From: Stefan Lippers-Hollmann 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 80313b3078fcd2ca51970880d90757f05879a193 upstream. The ASRock Q1900DC-ITX mainboard (Baytrail-D) hangs randomly in both BIOS and UEFI mode while rebooting

[PATCH 3.4 136/172] net: use for_each_netdev_safe() in rtnl_group_changelink()

2015-06-16 Thread lizf
From: WANG Cong 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit d079535d5e1bf5e2e7c856bae2483414ea21e137 upstream. In case we move the whole dev group to another netns, we should call for_each_netdev_safe(), otherwise we get a soft

[PATCH 3.4 145/172] ALSA: usb - Creative USB X-Fi Pro SB1095 volume knob support

2015-06-16 Thread lizf
From: "Dmitry M. Fedin" 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 3dc8523fa7412e731441c01fb33f003eb3cfece1 upstream. Adds an entry for Creative USB X-Fi to the rc_config array in mixer_quirks.c to allow use of volume knob on the

[PATCH 3.4 147/172] softirq: reduce latencies

2015-06-16 Thread lizf
From: Eric Dumazet 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit c10d73671ad30f54692f7f69f0e09e75d3a8926a upstream. In various network workloads, __do_softirq() latencies can be up to 20 ms if HZ=1000, and 200 ms if HZ=100. This is

[PATCH 3.4 146/172] x86/reboot: Fix a warning message triggered by stop_other_cpus()

2015-06-16 Thread lizf
From: Feng Tang 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 55c844a4dd16a4d1fdc0cf2a283ec631a02ec448 upstream. When rebooting our 24 CPU Westmere servers with 3.4-rc6, we always see this warning msg: Restarting system. machine

[PATCH 3.4 144/172] ocfs2: _really_ sync the right range

2015-06-16 Thread lizf
From: Al Viro 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 64b4e2526d1cf6e6a4db6213d6e2b6e6ab59479a upstream. "ocfs2 syncs the wrong range" had been broken; prior to it the code was doing the wrong thing in case of O_APPEND, all

[PATCH 3.4 148/172] Fix lockup related to stop_machine being stuck in __do_softirq.

2015-06-16 Thread lizf
From: Ben Greear 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 34376a50fb1fa095b9d0636fa41ed2e73125f214 upstream. The stop machine logic can lock up if all but one of the migration threads make it through the disable-irq step and the

[PATCH v4 5/5] serial/8250_fintek: Support for any io address.

2015-06-16 Thread Ricardo Ribalda Delgado
Fintek chip can be configured for io addresses different than the standard. Query the chip for the configured addresses and try to match it with the pnp address. Reported-by: Peter Hong Reviewed-by: Alan Cox Signed-off-by: Ricardo Ribalda Delgado --- drivers/tty/serial/8250/8250_fintek.c |

[PATCH v4 1/5] serial/8250_fintek: Use private data structure

2015-06-16 Thread Ricardo Ribalda Delgado
Save the port index and the line id in a private structure. Reported-by: Peter Hong Reviewed-by: Alan Cox Signed-off-by: Ricardo Ribalda Delgado --- drivers/tty/serial/8250/8250_fintek.c | 48 ++- 1 file changed, 31 insertions(+), 17 deletions(-) diff --git

[PATCH v4 2/5] serial/8250_fintek: Support for multiple base_ports

2015-06-16 Thread Ricardo Ribalda Delgado
Fintek chip can be connected at address 0x4e and also 0x2e. Add some logic to find out the address of the chip. Reported-by: Peter Hong Reviewed-by: Alan Cox Signed-off-by: Ricardo Ribalda Delgado --- drivers/tty/serial/8250/8250_fintek.c | 87 +-- 1 file

[PATCH v4 3/5] serial/8250_fintek: Support for chip_ip 0x0501

2015-06-16 Thread Ricardo Ribalda Delgado
There are some chips with the same interface but different chip ip. Reported-by: Peter Hong Reviewed-by: Alan Cox Signed-off-by: Ricardo Ribalda Delgado --- drivers/tty/serial/8250/8250_fintek.c | 21 +++-- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git

[PATCH v4 4/5] serial/8250_fintek: Support keys different than default

2015-06-16 Thread Ricardo Ribalda Delgado
Chip can be configured to use entry key different than 0x77. Try all the valid keys until one gives out the right chip id. Reported-by: Peter Hong Reviewed-by: Alan Cox Signed-off-by: Ricardo Ribalda Delgado --- v4: Fix comments by Jiri Slaby Use u8 instead of u16 for key

[PATCH v4 0/5] serial/8250_fintek Support any configuration

2015-06-16 Thread Ricardo Ribalda Delgado
The original driver only supported the default configuration of the chip. This patchset add supports for all the possible configurations: -Different io address -Multiple chips -Different chip_ids Patchset can be viewed online at https://github.com/ribalda/linux/tree/8250_fintek_try4 v4: Fix

Re: [PATCH v2] gpio: pcf857x: handle only enabled irqs

2015-06-16 Thread Linus Walleij
On Wed, Jun 10, 2015 at 11:01 PM, Grygorii Strashko wrote: > Now pcf857x_irq() IRQ's dispatcher will try to run nested > IRQ handlers for each GPIO pin which state has changed. > Such IRQs are, actually, spurious and nested IRQ handlers > have to be called only for IRQs wich were enabled by

[PATCH 3.4 157/172] hpsa: fix memory leak in kdump hard reset

2015-06-16 Thread lizf
From: Tomas Henzl 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 03741d956eaac31264952e0afa181b62713892a5 upstream. There is a potential memory leak in hpsa_kdump_hard_reset_controller. Reviewed-by: Don Brace Reviewed-by: Scott Teel

Re: [PATCH 3.4 000/172] 3.4.108-rc1 review

2015-06-16 Thread Guenter Roeck
On 06/16/2015 01:33 AM, l...@kernel.org wrote: From: Zefan Li This is the start of the stable review cycle for the 3.4.108 release. There are 172 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.

[PATCH 3.4 154/172] hpsa: refine the pci enable/disable handling

2015-06-16 Thread lizf
From: Tomas Henzl 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 132aa220b45d60e9b20def1e9d8be9422eed9616 upstream. When a second(kdump) kernel starts and the hard reset method is used the driver calls pci_disable_device without

[PATCH 3.4 153/172] IB/core: Avoid leakage from kernel to user space

2015-06-16 Thread lizf
From: Eli Cohen 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 377b513485fd885dea1083a9a5430df65b35e048 upstream. Clear the reserved field of struct ib_uverbs_async_event_desc which is copied to user space. Signed-off-by: Eli Cohen

[PATCH 3.4 156/172] hpsa: turn off interrupts when kdump starts

2015-06-16 Thread lizf
From: Tomas Henzl 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 3b747298786355c6934b0892fc9ae4ca44105192 upstream. Sometimes when the card is restarted it may cause - "irq 16: nobody cared (try booting with the "irqpoll" option)" that

[PATCH 3.4 155/172] hpsa: add missing pci_set_master in kdump path

2015-06-16 Thread lizf
From: Tomas Henzl 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 859c75aba20264d87dd026bab0d0ca3bff385955 upstream. Add a call to pci_set_master(...) missing in the previous patch "hpsa: refine the pci enable/disable handling". Found

[PATCH 3.4 159/172] openvswitch: Check currect return value from skb_gso_segment()

2015-06-16 Thread lizf
From: Pravin B Shelar 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 92e5dfc34cf39c20ae1087bd5e676238b5d0dfac upstream. Fix return check typo. Signed-off-by: Pravin B Shelar Signed-off-by: Jesse Gross Signed-off-by: Zefan Li ---

[PATCH 3.4 160/172] net: make skb_gso_segment error handling more robust

2015-06-16 Thread lizf
From: Florian Westphal 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 330966e501ffe282d7184fde4518d5e0c24bc7f8 upstream. skb_gso_segment has three possible return values: 1. a pointer to the first segmented skb 2. an errno value

[PATCH 3.4 158/172] fs: take i_mutex during prepare_binprm for set[ug]id executables

2015-06-16 Thread lizf
From: Jann Horn 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 8b01fc86b9f425899f8a3a8fc1c47d73c2c20543 upstream. This prevents a race between chown() and execve(), where chowning a setuid-user binary to root would momentarily make the

[PATCH 3.4 161/172] ipvs: uninitialized data with IP_VS_IPV6

2015-06-16 Thread lizf
From: Dan Carpenter 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 3b05ac3824ed9648c0d9c02d51d9b54e4e7e874f upstream. The app_tcp_pkt_out() function expects "*diff" to be set and ends up using uninitialized data if CONFIG_IP_VS_IPV6 is

[PATCH] small update for strlen, strnlen, use less cpu instructions

2015-06-16 Thread Luke Skywalker
very small update to strlen and strnlen that now use less cpu instructions by using a counter avoiding the memory addresses substraction to find the length of the string, Orestes Leal Rodriguez. --- lib/string.c.orig 2015-06-15 23:59:32.768346193 -0400 +++ lib/string.c2015-06-16

[PATCH] small update for strlen, strnlen, use less cpu instructions

2015-06-16 Thread Orestes Leal Rodriguez
very small update to strlen and strnlen that now use less cpu instructions by using a counter to avoid the memory addresses substraction to find the length of the string. Orestes Leal Rodriguez. --- lib/string.c.orig 2015-06-15 23:59:32.768346193 -0400 +++ lib/string.c2015-06-16

[PATCH 3.4 151/172] sb_edac: Fix erroneous bytes->gigabytes conversion

2015-06-16 Thread lizf
From: Jim Snow 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 8c009100295597f23978c224aec5751a365bc965 upstream. Signed-off-by: Jim Snow Signed-off-by: Lukasz Anaczkowski Signed-off-by: Mauro Carvalho Chehab Cc: Vinson Lee [lizf:

[PATCH 3.4 150/172] powerpc/mpc85xx: Add ranges to etsec2 nodes

2015-06-16 Thread lizf
From: Scott Wood 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit bb344ca5b90df62b1a3b7a35c6a9d00b306a170d upstream. Commit 746c9e9f92dd "of/base: Fix PowerPC address parsing hack" limited the applicability of the workaround whereby a

[PATCH 3.4 149/172] splice: Apply generic position and size checks to each write

2015-06-16 Thread lizf
From: Ben Hutchings 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- 3.2.67-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings We need to check the position and size of file writes

[PATCH 3.4 162/172] autofs4: check dev ioctl size before allocating

2015-06-16 Thread lizf
From: Sasha Levin 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit e53d77eb8bb616e903e34cc7a918401bee3b5149 upstream. There wasn't any check of the size passed from userspace before trying to allocate the memory required. This meant that

Re: [PATCH] Staging: wilc1000: Boolean tests don't need comparisons

2015-06-16 Thread Abdul, Hussain (H.)
On Tuesday 16 June 2015 01:40 PM, Sudip Mukherjee wrote: > On Tue, Jun 16, 2015 at 07:33:42AM +, Abdul, Hussain (H.) wrote: >> From: Abdul Hussain >> >> This patch removes unwanted true and false from boolean tests. >> >> Signed-off-by: Abdul Hussain >> --- > >> diff --git

[PATCH 3.4 168/172] cdc-acm: prevent infinite loop when parsing CDC headers.

2015-06-16 Thread lizf
From: Quentin Casasnovas 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 0d3bba0287d4e284c3ec7d3397e81eec920d5e7e upstream. Phil and I found out a problem with commit: 7e860a6e7aa6 ("cdc-acm: add sanity checks") It added some sanity

[PATCH 3.4 165/172] config: Enable NEED_DMA_MAP_STATE by default when SWIOTLB is selected

2015-06-16 Thread lizf
From: Konrad Rzeszutek Wilk 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit a6dfa128ce5c414ab46b1d690f7a1b8decb8526d upstream. A huge amount of NIC drivers use the DMA API, however if compiled under 32-bit an very important part of the

Re: [PATCH v2 0/3] Add the efuse driver on rockchip platform

2015-06-16 Thread Stefan Wahren
Hi Caesar, [add Maxime and Srinivas] Am 16.06.2015 um 09:27 schrieb Caesar Wang: > The original driver is uploaded by Jianqun. > Here is his patchs: > https://patchwork.kernel.org/patch/5410341/ > https://patchwork.kernel.org/patch/5410351/ > > Jianqun, nevermind! > I check-pick it and

[PATCH 2/4][RFC] regmap: add regmap_write_bits()

2015-06-16 Thread Kuninori Morimoto
regmap_write_bits() is similar to regmap_update_bits(), but regmap_write_bits() write data to register even though it is same value. Signed-off-by: Kuninori Morimoto --- drivers/base/regmap/regmap.c | 23 +++ include/linux/regmap.h | 9 + 2 files changed, 32

[PATCH 4/4][RFC] ASoC: rsnd: gen: add rsnd_force_write()

2015-06-16 Thread Kuninori Morimoto
rsnd_force_write() is similar to rsnd_write(), but rsnd_force_write() write data to register even though it is same value. Signed-off-by: Kuninori Morimoto --- sound/soc/sh/rcar/gen.c | 16 sound/soc/sh/rcar/rsnd.h | 4 2 files changed, 20 insertions(+) diff --git

Re: [PATCH] ARM: dts: vf610: Extend I2C support to all available buses.

2015-06-16 Thread Stefan Agner
On 2015-06-15 02:19, Cory Tusar wrote: > This commit extends the existing Vybrid I2C support to cover buses i2c1, > i2c2, and i2c3. Based in (very) large part on an initial patch by > Stefan Agner that was just lacking a couple of DMA assignments. > > Signed-off-by: Cory Tusar Thx Cory for

[PATCH 3/4][RFC] regmap: add regmap_fields_force_write()

2015-06-16 Thread Kuninori Morimoto
regmap_fields_force_write() is similar to regmap_fields_write(), but regmap_fields_force_write() write data to register even though it is same value. Signed-off-by: Kuninori Morimoto --- drivers/base/regmap/regmap.c | 12 include/linux/regmap.h | 2 ++ 2 files changed, 14

[PATCH 3.4 169/172] IB/core: don't disallow registering region starting at 0x0

2015-06-16 Thread lizf
From: Yann Droneaud 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 66578b0b2f69659f00b6169e6fe7377c4b100d18 upstream. In a call to ib_umem_get(), if address is 0x0 and size is already page aligned, check added in commit 8494057ab5e4

Re: [PATCH 09/10] x86/intel_rdt: Hot cpu support for Cache Allocation

2015-06-16 Thread Thomas Gleixner
On Fri, 12 Jun 2015, Vikas Shivappa wrote: > +static inline void intel_rdt_cpu_start(int cpu) > +{ > + struct intel_pqr_state *state = _cpu(pqr_state, cpu); > + > + state->closid = 0; > + mutex_lock(_group_mutex); This is called from CPU_STARTING, which runs on the starting cpu with

[PATCH 3.4 167/172] don't bugger nd->seq on set_root_rcu() from follow_dotdot_rcu()

2015-06-16 Thread lizf
From: Al Viro 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 7bd88377d482e1eae3c5329b12e33cfd664fa6a9 upstream. return the value instead, and have path_init() do the assignment. Broken by "vfs: Fix absolute RCU path walk failures due

[PATCH 1/4][RFC] regmap: add force_write option on _regmap_update_bits()

2015-06-16 Thread Kuninori Morimoto
Sometimes we want to write data even though it doesn't change value. Then, force_write option on _regmap_update_bits() helps this purpose. Signed-off-by: Kuninori Morimoto --- drivers/base/regmap/regmap.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git

Re: [PATCH v3 4/5] serial/8250_fintek: Support keys different than default

2015-06-16 Thread Jiri Slaby
On 06/16/2015, 10:41 AM, Ricardo Ribalda Delgado wrote: > @@ -148,20 +148,25 @@ static int fintek_8250_rs485_config(struct uart_port > *port, > return 0; > } > > -static int fintek_8250_base_port(void) > +static int fintek_8250_base_port(u8 *key) > { > static const u16 addr[] =

[PATCH 0/4][RFC] regmap: add force write option

2015-06-16 Thread Kuninori Morimoto
Hi Mark Current _regmap_update_bits() writes data to register if current value and write value was different. This means it doesn't write data if the value was same as current value. But, some device needs to write data even though it was same value. This RFC patch-set adds new "force_write"

[PATCH 3.4 170/172] writeback: use |1 instead of +1 to protect against div by zero

2015-06-16 Thread lizf
From: Tejun Heo 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 464d1387acb94dc43ba772b35242345e3d2ead1b upstream. mm/page-writeback.c has several places where 1 is added to the divisor to prevent division by zero exceptions; however, if

[PATCH 3.4 172/172] slub: refactoring unfreeze_partials()

2015-06-16 Thread lizf
From: Joonsoo Kim 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 43d77867a4f333de4e4189114c480dd365133c09 upstream. Current implementation of unfreeze_partials() is so complicated, but benefit from it is insignificant. In addition many

[PATCH 3.4 166/172] PCI: Convert pcibios_resource_to_bus() to take a pci_bus, not a pci_dev

2015-06-16 Thread lizf
From: Yinghai Lu 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit fc2798502f860b18f3c7121e4dc659d3d9d28d74 upstream. These interfaces: pcibios_resource_to_bus(struct pci_dev *dev, *bus_region, *resource)

[PATCH 3.4 171/172] xen-pciback: Add name prefix to global 'permissive' variable

2015-06-16 Thread lizf
From: Ben Hutchings 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 8014bcc86ef112eab9ee1db312dba4e6b608cf89 upstream. The variable for the 'permissive' module parameter used to be static but was recently changed to be extern. This puts

[PATCH 3.4 164/172] perf tools: Fix build with perl 5.18

2015-06-16 Thread lizf
From: "Kirill A. Shutemov" 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 575bf1d04e908469d26da424b52fc1b12a1db9d8 upstream. perl.h from new Perl release doesn't like -Wundef and -Wswitch-default:

[PATCH 3.4 141/172] IB/uverbs: Prevent integer overflow in ib_umem_get address arithmetic

2015-06-16 Thread lizf
From: Shachar Raindel 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 8494057ab5e40df590ef6ef7d66324d3ae33356b upstream. Properly verify that the resulting page aligned end address is larger than both the start address and the length of

[PATCH 3.4 132/172] USB: ftdi_sio: Added custom PID for Synapse Wireless product

2015-06-16 Thread lizf
From: Doug Goldstein 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 4899c054a90439477b24da8977db8d738376fe90 upstream. Synapse Wireless uses the FTDI VID with a custom PID of 0x9090 for their SNAP Stick 200 product. Signed-off-by: Doug

[PATCH 3.4 143/172] Defer processing of REQ_PREEMPT requests for blocked devices

2015-06-16 Thread lizf
From: Bart Van Assche 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit bba0bdd7ad4713d82338bcd9b72d57e9335a664b upstream. SCSI transport drivers and SCSI LLDs block a SCSI device if the transport layer is not operational. This means that

[PATCH 3.4 133/172] cifs: fix use-after-free bug in find_writable_file

2015-06-16 Thread lizf
From: David Disseldorp 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit e1e9bda22d7ddf88515e8fe401887e313922823e upstream. Under intermittent network outages, find_writable_file() is susceptible to the following race condition, which

[PATCH 3.4 129/172] selinux: fix sel_write_enforce broken return value

2015-06-16 Thread lizf
From: Joe Perches 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 6436a123a147db51a0b06024a8350f4c230e73ff upstream. Return a negative error value like the rest of the entries in this function. Signed-off-by: Joe Perches Acked-by:

[PATCH 3.4 130/172] hfsplus: fix B-tree corruption after insertion at position 0

2015-06-16 Thread lizf
From: Sergei Antonov 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 98cf21c61a7f5419d82f847c4d77bf6e96a76f5f upstream. Fix B-tree corruption when a new record is inserted at position 0 in the node in hfs_brec_insert(). In this case a

[PATCH 3.4 163/172] UBI: fix soft lockup in ubi_check_volume()

2015-06-16 Thread lizf
From: hujianyang 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 9aa272b492e7551a9ee0e2c83c720ea013698485 upstream. Running mtd-utils/tests/ubi-tests/io_basic.c could cause soft lockup or watchdog reset. It is because *updatevol* will

[PATCH 3.4 152/172] spi: spidev: fix possible arithmetic overflow for multi-transfer message

2015-06-16 Thread lizf
From: Ian Abbott 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit f20fbaad7620af2df36a1f9d1c9ecf48ead5b747 upstream. `spidev_message()` sums the lengths of the individual SPI transfers to determine the overall SPI message length. It

[PATCH 3.4 142/172] be2iscsi: Fix kernel panic when device initialization fails

2015-06-16 Thread lizf
From: John Soni Jose 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 2e7cee027b26cbe7e6685a7a14bd2850bfe55d33 upstream. Kernel panic was happening as iscsi_host_remove() was called on a host which was not yet added. Signed-off-by: John

[PATCH 3.4 111/172] ASoC: cs4271: Fix wrong value references for boolean kctl

2015-06-16 Thread lizf
From: Takashi Iwai 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit e8371aa0fecb73fb8a4b2e0296b025b11e7d6229 upstream. The correct values referred by a boolean control are value.integer.value[], not value.enumerated.item[]. The former is

[PATCH 3.4 093/172] fuse: notify: don't move pages

2015-06-16 Thread lizf
From: Miklos Szeredi 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 0d2783626a53d4c922f82d51fa675cb5d13f0d36 upstream. fuse_try_move_page() is not prepared for replacing pages that have already been read. Reported-by: Al Viro

[PATCH 3.4 113/172] ASoC: wm8731: Fix wrong value references for boolean kctl

2015-06-16 Thread lizf
From: Takashi Iwai 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit bd14016fbf31aa199026f1e2358eab695f374eb1 upstream. The correct values referred by a boolean control are value.integer.value[], not value.enumerated.item[]. The former is

[PATCH 3.4 096/172] dm io: deal with wandering queue limits when handling REQ_DISCARD and REQ_WRITE_SAME

2015-06-16 Thread lizf
From: "Darrick J. Wong" 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit e5db29806b99ce2b2640d2e4d4fcb983cea115c5 upstream. Since it's possible for the discard and write same queue limits to change while the upper level command is being

[PATCH 3.4 090/172] drm/vmwgfx: Reorder device takedown somewhat

2015-06-16 Thread lizf
From: Thomas Hellstrom 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 3458390b9f0ba784481d23134798faee27b5f16f upstream. To take down the MOB and GMR memory types, the driver may have to issue fence objects and thus make sure that the

[PATCH 3.4 109/172] ASoC: adav80x: Fix wrong value references for boolean kctl

2015-06-16 Thread lizf
From: Takashi Iwai 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 2bf4c1d483d911cda5dd385527194d23e5cea73d upstream. The correct values referred by a boolean control are value.integer.value[], not value.enumerated.item[]. The former is

[PATCH 3.4 114/172] ASoC: wm8903: Fix wrong value references for boolean kctl

2015-06-16 Thread lizf
From: Takashi Iwai 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 24cc883c1fd16df34211ae41624aa6d3cd906693 upstream. The correct values referred by a boolean control are value.integer.value[], not value.enumerated.item[]. The former is

[PATCH 3.4 112/172] ASoC: wm2000: Fix wrong value references for boolean kctl

2015-06-16 Thread lizf
From: Takashi Iwai 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 00a14c2968e3d55817e0fa35c78106ca840537bf upstream. The correct values referred by a boolean control are value.integer.value[], not value.enumerated.item[]. The former is

[PATCH 3.4 095/172] dm: hold suspend_lock while suspending device during device deletion

2015-06-16 Thread lizf
From: Mikulas Patocka 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit ab7c7bb6f4ab95dbca96fcfc4463cd69843e3e24 upstream. __dm_destroy() must take the suspend_lock so that its presuspend and postsuspend calls do not race with an internal

[PATCH 3.4 116/172] ASoC: wm8955: Fix wrong value references for boolean kctl

2015-06-16 Thread lizf
From: Takashi Iwai 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 07892b10356f17717abdc578acbef72db86c880e upstream. The correct values referred by a boolean control are value.integer.value[], not value.enumerated.item[]. The former is

[PATCH 3.4 091/172] ALSA: control: Add sanity checks for user ctl id name string

2015-06-16 Thread lizf
From: Takashi Iwai 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit be3bb8236db2d0fcd705062ae2e2a9d75131222f upstream. There was no check about the id string of user control elements, so we accepted even a control element with an empty

[PATCH 3.4 074/172] xhci: Workaround for PME stuck issues in Intel xhci

2015-06-16 Thread lizf
From: Mathias Nyman 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit b8cb91e058cd0c0f02059c1207293c5b31d350fa upstream. The xhci in Intel Sunrisepoint and Cherryview platforms need a driver workaround for a Stuck PME that might either

[PATCH 3.4 086/172] can: add missing initialisations in CAN related skbuffs

2015-06-16 Thread lizf
From: Oliver Hartkopp 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 969439016d2cf61fef53a973d7e6d2061c3793b1 upstream. When accessing CAN network interfaces with AF_PACKET sockets e.g. by dhclient this can lead to a skb_under_panic due

[PATCH 3.4 056/172] USB: ftdi_sio: add PIDs for Actisense USB devices

2015-06-16 Thread lizf
From: Mark Glover 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit f6950344d3cf4a1e231b5828b50c4ac168db3886 upstream. These product identifiers (PID) all deal with marine NMEA format data used on motor boats and yachts. We supply the

Re: [PATCH 02/21] ARM: tegra: Add gpio-ranges property

2015-06-16 Thread Tomeu Vizoso
On 2 June 2015 at 17:40, Stephen Warren wrote: > On 06/02/2015 05:28 AM, Linus Walleij wrote: >> >> On Tue, May 26, 2015 at 9:41 PM, Stephen Warren >> wrote: >>> >>> On 05/25/2015 08:53 AM, Tomeu Vizoso wrote: Specify how the GPIOs map to the pins in T124, so the dependency is

[PATCH 3.4 057/172] USB: serial: fix potential use-after-free after failed probe

2015-06-16 Thread lizf
From: Johan Hovold 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 07fdfc5e9f1c966be8722e8fa927e5ea140df5ce upstream. Fix return value in probe error path, which could end up returning success (0) on errors. This could in turn lead to

[PATCH 3.4 089/172] xen-pciback: limit guest control of command register

2015-06-16 Thread lizf
From: Jan Beulich 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit af6fc858a35b90e89ea7a7ee58e66628c55c776b upstream. Otherwise the guest can abuse that control to cause e.g. PCIe Unsupported Request responses by disabling memory and/or

[PATCH 3.4 068/172] drm/radeon: do a posting read in si_set_irq

2015-06-16 Thread lizf
From: Alex Deucher 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 0586915ec10d0ae60de5cd3381ad25a704760402 upstream. To make sure the writes go through the pci bridge. bug: https://bugzilla.kernel.org/show_bug.cgi?id=90741

[PATCH 3.4 065/172] drm/radeon: do a posting read in rs600_set_irq

2015-06-16 Thread lizf
From: Alex Deucher 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 54acf107e4e66d1f4a697e08a7f60dba9fcf07c3 upstream. To make sure the writes go through the pci bridge. bug: https://bugzilla.kernel.org/show_bug.cgi?id=90741

[PATCH 3.4 059/172] mac80211: Send EAPOL frames at lowest rate

2015-06-16 Thread lizf
From: Jouni Malinen 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit 9c1c98a3bb7b7593b60264b9a07e001e68b46697 upstream. The current minstrel_ht rate control behavior is somewhat optimistic in trying to find optimum TX rate. While this is

[PATCH 3.4 058/172] USB: serial: fix tty-device error handling at probe

2015-06-16 Thread lizf
From: Johan Hovold 3.4.108-rc1 review patch. If anyone has any objections, please let me know. -- commit ca4383a3947a83286bc9b9c598a1f55e867871d7 upstream. Add missing error handling when registering the tty device at port probe. This avoids trying to remove an uninitialised

[PATCH] small update for strlen, strnlen, use less cpu instructions

2015-06-16 Thread Orestes Leal Rodriguez
very small update to strlen and strnlen that now use less cpu instructions by using a counter to avoid the memory addresses substraction to find the length of the string. Orestes Leal Rodriguez. --- lib/string.c.orig 2015-06-15 23:59:32.768346193 -0400 +++ lib/string.c2015-06-16

<    3   4   5   6   7   8   9   10   11   12   >