[PATCH 3.19.y-ckt 007/251] tcp: Do not call tcp_fastopen_reset_cipher from interrupt context

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Christoph Paasch [ Upstream commit dfea2aa654243f70dc53b8648d0bbdeec55a7df1 ] tcp_fastopen_reset_cipher really cannot be called from interrupt context. It allocates the tcp_fastopen_c

[PATCH 3.19.y-ckt 011/251] net: phy: fix phy link up when limiting speed via device tree

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Mugunthan V N [ Upstream commit eb686231fce3770299760f24fdcf5ad041f44153 ] When limiting phy link speed using "max-speed" to 100mbps or less on a giga bit phy, phy never completes aut

Re: [PATCH 6/6] cputime: Introduce cputime_to_timespec64()/timespec64_to_cputime()

On 15 July 2015 at 19:55, Thomas Gleixner wrote: > On Wed, 15 Jul 2015, Baolin Wang wrote: > >> On 15 July 2015 at 18:31, Thomas Gleixner wrote: >> > On Wed, 15 Jul 2015, Baolin Wang wrote: >> > >> >> The cputime_to_timespec() and timespec_to_cputime() functions are >> >> not year 2038 safe on 32

[PATCH 3.19.y-ckt 021/251] [media] af9013: Don't accept invalid bandwidth

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit d7b76c91f471413de9ded837bddeca2164786571 upstream. If userspace sends an invalid bandwidth, it should either return EINVAL or switch to auto mode. This d

[PATCH 3.19.y-ckt 022/251] [media] cx24117: fix a buffer overflow when checking userspace params

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 82e3b88b679049f043fe9b03991d6d66fc0a43c8 upstream. The maximum size for a DiSEqC command is 6, according to the userspace API. However, the code allows to

[PATCH 3.19.y-ckt 015/251] net: mvneta: introduce compatible string "marvell, armada-xp-neta"

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Simon Guinot [ Upstream commit f522a975a8101895a85354b9c143f41b8248e71a ] The mvneta driver supports the Ethernet IP found in the Armada 370, XP, 380 and 385 SoCs. Since at least one

[PATCH 3.19.y-ckt 013/251] sctp: Fix race between OOTB responce and route removal

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Alexander Sverdlin [ Upstream commit 29c4afc4e98f4dc0ea9df22c631841f9c220b944 ] There is NULL pointer dereference possible during statistics update if the route used for OOTB responce

[PATCH 3.19.y-ckt 012/251] bnx2x: fix lockdep splat

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit d53c66a5b80698620f7c9ba2372fff4017e987b8 ] Michel reported following lockdep splat [ 44.718117] INFO: trying to register non-static key. [ 44.72308

[PATCH 3.19.y-ckt 005/251] packet: avoid out of bounds read in round robin fanout

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 468479e6043c84f5a65299cc07cb08a22a28c2b1 ] PACKET_FANOUT_LB computes f->rr_cur such that it is modulo f->num_members. It returns the old value uncon

[PATCH 3.19.y-ckt 017/251] net: mvneta: disable IP checksum with jumbo frames for Armada 370

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Simon Guinot [ Upstream commit b65657fc240ae6c1d2a1e62db9a0e61ac9631d7a ] The Ethernet controller found in the Armada 370, 380 and 385 SoCs don't support TCP/IP checksumming with fram

[PATCH 3.19.y-ckt 016/251] ARM: mvebu: update Ethernet compatible string for Armada XP

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Simon Guinot [ Upstream commit ea3b55fe83b5fcede82d183164b9d6831b26e33b ] This patch updates the Ethernet DT nodes for Armada XP SoCs with the compatible string "marvell,armada-xp-net

[PATCH 3.19.y-ckt 018/251] sparc: Use GFP_ATOMIC in ldc_alloc_exp_dring() as it can be called in softirq context

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Sowmini Varadhan [ Upstream commit 0edfad5959df7379c9e554fbe8ba264ae232d321 ] Since it is possible for vnet_event_napi to end up doing vnet_control_pkt_engine -> ... -> vnet_send_attr

[PATCH 3.19.y-ckt 014/251] amd-xgbe: Add the __GFP_NOWARN flag to Rx buffer allocation

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky [ Upstream commit 472cfe7127760d68b819cf35a26e5a1b44b30f4e ] When allocating Rx related buffers, alloc_pages is called using an order number that is decreased until succe

[PATCH 3.19.y-ckt 025/251] bus: arm-ccn: Fix node->XP config conversion

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Pawel Moll commit a18f8e97fe69195823d7fb5c68a8d6565f39db4b upstream. Events defined as watchpoints on nodes must have their config values converted so that they apply to the respectiv

[PATCH] kprobes: Use debugfs_remove_recursive instead debugfs_remove

In debugfs_kprobe_init, we create a directory 'kprobes' and three files 'list', 'enabled' and 'blacklist'. When any one of the three files creation fails, we should remove all of them. But debugfs_remove function can not complete this work. So use debugfs_remove_recursive instead. Signed-off-by: W

Re: [PATCH v3 04/11] otg-fsm: move usb_bus_start_enum into otg-fsm->ops

On Wed, Jul 15, 2015 at 04:30:27PM +0300, Roger Quadros wrote: > On 14/07/15 03:34, Peter Chen wrote: > > On Mon, Jul 13, 2015 at 01:13:54PM +0300, Roger Quadros wrote: > >> Peter, > >> > >> On 13/07/15 04:58, Peter Chen wrote: > >>> On Wed, Jul 08, 2015 at 01:19:30PM +0300, Roger Quadros wrote: >

[PATCH 3.19.y-ckt 032/251] intel_pstate: set BYT MSR with wrmsrl_on_cpu()

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Joe Konno commit 0dd23f94251f49da99a6cbfb22418b2d757d77d6 upstream. Commit 007bea098b86 (intel_pstate: Add setting voltage value for baytrail P states.) introduced byt_set_pstate() wi

[PATCH 3.19.y-ckt 029/251] spi: fix race freeing dummy_tx/rx before it is unmapped

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Martin Sperl commit 8e76ef88f607174082023f50b87fe12dcdbe5db5 upstream. Fix a race (with some kernel configurations) where a queued master->pump_messages runs and frees dummy_tx/rx bef

Re: [PATCH v2 5/6] locking/pvqspinlock: Opportunistically defer kicking to unlock time

On 07/15/2015 06:03 AM, Peter Zijlstra wrote: On Tue, Jul 14, 2015 at 10:13:36PM -0400, Waiman Long wrote: +static void pv_kick_node(struct qspinlock *lock, struct mcs_spinlock *node) { struct pv_node *pn = (struct pv_node *)node; + if (xchg(&pn->state, vcpu_running) == vcpu_run

[PATCH 3.19.y-ckt 004/251] packet: read num_members once in packet_rcv_fanout()

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit f98f4514d07871da7a113dd9e3e330743fd70ae4 ] We need to tell compiler it must not read f->num_members multiple times. Otherwise testing if num is not zero

[PATCH 3.19.y-ckt 023/251] [media] saa7164: fix querycap warning

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 534bc3e2ee93835badca753bedce8073c67caa92 upstream. Fix the VIDIOC_QUERYCAP warning due to the missing device_caps. Don't fill in the version field, the V4L2 core w

[PATCH 3.19.y-ckt 026/251] ARM: tegra20: Store CPU "resettable" status in IRAM

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Osipenko commit 4d48edb3c3e1234d6b3fcdfb9ac24d7c6de449cb upstream. Commit 7232398abc6a ("ARM: tegra: Convert PMC to a driver") changed tegra_resume() location storing from lat

[PATCH 3.19.y-ckt 024/251] [media] cx18: add missing caps for the PCM video device

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 2b4fd3ede3bab65ef5b97387b90899d11e4d3202 upstream. The cx18 PCM video device didn't have any capabilities set, which caused a warnings in the v4l2 core: [6.2

[PATCH 3.19.y-ckt 040/251] mnt: Refactor the logic for mounting sysfs and proc in a user namespace

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: "Eric W. Biederman" commit 1b852bceb0d111e510d1a15826ecc4a19358d512 upstream. Fresh mounts of proc and sysfs are a very special case that works very much like a bind mount. Unfortuna

[PATCH 3.19.y-ckt 027/251] iio: accel: kxcjk-1013: add the "KXCJ9000" ACPI id

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Antonio Ospite commit 61e2c70da9cfc79e8485eafa0f98b5919b04bbe1 upstream. This id has been seen in the DSDT of the Teclast X98 Air 3G tablet based on Intel Bay Trail. Signed-off-by: A

[PATCH 3.19.y-ckt 028/251] video: mxsfb: Make sure axi clock is enabled when accessing registers

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Liu Ying commit 2fa3b4c4a78a5db3502ab9e32630ea660ff923d0 upstream. The LCDIF engines embedded in i.MX6sl and i.MX6sx SoCs need the axi clock as the engine's system clock. The clock s

[PATCH 3.19.y-ckt 031/251] [media] rc-core: fix dib0700 scancode generation for RC5

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: =?UTF-8?q?David=20H=C3=A4rdeman?= commit 4d298b8539ed59f1d69d3aa6e41a2c4908137612 upstream. commit af3a4a9bbeb0 ("[media] dib0700: NEC scancode cleanup") cleaned up the NEC scancode l

[PATCH 3.19.y-ckt 041/251] ASoC: wm8955: Fix setting wrong register for WM8955_K_8_0_MASK bits

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Axel Lin commit 12c350050538c7dc779c083b7342bfd20f74949c upstream. WM8955_K_8_0_MASK bits is controlled by WM8955_PLL_CONTROL_3 rather than WM8955_PLL_CONTROL_2. Signed-off-by: Axel

[PATCH 3.19.y-ckt 039/251] [media] media: Fix regression in some more dib0700 based devices

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Thomas Reitmayr commit e989a73ebd09d22c22ead51fa363a2f56f70f28a upstream. Fix an oops during device initialization by correctly setting size_of_priv instead of leaving it 0. The regre

[PATCH 3.19.y-ckt 030/251] mtd: fix: avoid race condition when accessing mtd->usecount

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit 073db4a51ee43ccb827f54a4261c0583b028d5ab upstream. On A MIPS 32-cores machine a BUG_ON was triggered because some acesses to mtd->usecount were done without taking

[PATCH 3.19.y-ckt 003/251] bridge: fix br_stp_set_bridge_priority race conditions

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Aleksandrov [ Upstream commit 2dab80a8b486f0a69daca6859519e05781d9 ] After the ->set() spinlocks were removed br_stp_set_bridge_priority was left running without any prote

[PATCH 3.19.y-ckt 042/251] of/pci: Fix pci_address_to_pio() conversion of CPU address to I/O port

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Zhichang Yuan commit 5dbb4c6167229c8d4f528e8ec26699a7305000a3 upstream. 41f8bba7f555 ("of/pci: Add pci_register_io_range() and pci_pio_to_address()") added support for systems with se

[PATCH 3.19.y-ckt 049/251] KVM: mips: use id_to_memslot correctly

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 69a1220060c1523fd0515216eaa29e22f133b894 upstream. The argument to KVM_GET_DIRTY_LOG is a memslot id; it may not match the position in the memslots array, which i

[PATCH 3.19.y-ckt 038/251] ASoC: wm8903: Fix define for WM8903_VMID_RES_250K

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Axel Lin commit ebb6ad73e645b8f2d098dd3c41d2ff0da4146a02 upstream. VMID Control 0 BIT[2:1] is VMID Divider Enable and Select 00 = VMID disabled (for OFF mode) 01 = 2 x 50kΩ divider (

[PATCH 3.19.y-ckt 034/251] crypto: talitos - avoid memleak in talitos_alg_alloc()

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Horia Geant? commit 5fa7dadc898567ce14d6d6d427e7bd8ce6eb5d39 upstream. Fixes: 1d11911a8c57 ("crypto: talitos - fix warning: 'alg' may be used uninitialized in this function") Signed-

[PATCH 3.19.y-ckt 035/251] Revert "crypto: talitos - convert to use be16_add_cpu()"

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Horia Geant? commit 69d9cd8c592f1abce820dbce7181bbbf6812cfbd upstream. This reverts commit 7291a932c6e27d9768e374e9d648086636daf61c. The conversion to be16_add_cpu() is incorrect in

Re: [PATCH v2 6/6] locking/pvqspinlock: Queue node adaptive spinning

On 07/15/2015 06:01 AM, Peter Zijlstra wrote: On Tue, Jul 14, 2015 at 10:13:37PM -0400, Waiman Long wrote: +static void pv_wait_node(struct mcs_spinlock *node, struct mcs_spinlock *prev) { struct pv_node *pn = (struct pv_node *)node; + struct pv_node *pp = (struct pv_node *)prev;

[PATCH 3.19.y-ckt 051/251] ima: do not measure or appraise the NSFS filesystem

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Mimi Zohar commit cd025f7f94108995383edddfb61fc8afea6c66a9 upstream. Include don't appraise or measure rules for the NSFS filesystem in the builtin ima_tcb and ima_appraise_tcb polici

[PATCH 3.19.y-ckt 050/251] ima: skip measurement of cgroupfs files and update documentation

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Roberto Sassu commit 6438de9f3fb5180d78a0422695d0b88c687757d3 upstream. This patch adds a rule in the default measurement policy to skip inodes in the cgroupfs filesystem. Measurement

[PATCH 3.19.y-ckt 052/251] KEYS: fix "ca_keys=" partial key matching

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Mimi Zohar commit f2b3dee484f9cee967a54ef05a66866282337519 upstream. The call to asymmetric_key_hex_to_key_id() from ca_keys_setup() silently fails with -ENOMEM. Instead of dynamical

[PATCH 3.19.y-ckt 046/251] IB/srp: Fix a connection setup race

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 8de9fe3a1d4ac8c3e4953fa4b7d81f863f5196ad upstream. Avoid that receiving a DREQ while RDMA channels are being established causes target->qp_in_error to be reset.

[PATCH 3.19.y-ckt 043/251] scsi_transport_srp: Introduce srp_wait_for_queuecommand()

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit be34c62ddf39d1931780b07a6f4241393e4ba2ee upstream. Introduce the helper function srp_wait_for_queuecommand(). Move the definition of scsi_request_fn_active(). A

[PATCH 3.19.y-ckt 053/251] PCI: Propagate the "ignore hotplug" setting to parent

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: "Rafael J. Wysocki" commit 0824965140fff1bf640a987dc790d1594a8e0699 upstream. Refine the mechanism introduced by commit f244d8b623da ("ACPIPHP / radeon / nouveau: Fix VGA switcheroo p

[PATCH 3.19.y-ckt 045/251] IB/srp: Remove an extraneous scsi_host_put() from an error path

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit fb49c8bbaae70b14fea2b4590a90a21539f88526 upstream. Fix a scsi_get_host() / scsi_host_put() imbalance in the error path of srp_create_target(). See also patch "I

[PATCH 3.19.y-ckt 044/251] scsi_transport_srp: Fix a race condition

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 535fb906225fb7436cb658144d0c0cea14a26f3e upstream. Avoid that srp_terminate_io() can get invoked while srp_queuecommand() is in progress. This patch avoids that

[PATCH 3.19.y-ckt 037/251] ASoC: wm8737: Fixup setting VMID Impedance control register

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Axel Lin commit 14ba3ec1de043260cecd9e828ea2e3a0ad302893 upstream. According to the datasheet: R10 (0Ah) VMID Impedance Control BIT 3:2 VMIDSEL DEFAULT 00 DESCRIPTION: VMID impedanc

[PATCH 3.19.y-ckt 054/251] mei: txe: reduce suspend/resume time

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Tomas Winkler commit fe292283c23329218e384bffc6cb4bfa3fd92277 upstream. HW has to be in known state before the initialisation sequence is started. The polling step for settling aliven

[PATCH 3.19.y-ckt 047/251] IB/srp: Fix connection state tracking

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit c014c8cd31b161e12deb81c0f7f477811bd1eddc upstream. Reception of a DREQ message only causes the state of a single channel to change. Hence move the 'connected' m

[PATCH 3.19.y-ckt 055/251] w1_therm reference count family data

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: David Fries commit f7134eea05b2fb4a2c0935f8a540539fff01f3eb upstream. A temperature conversion can take 750 ms and when possible the w1_therm slave driver drops the bus_mutex to allow

[PATCH 3.19.y-ckt 057/251] spi: orion: Fix maximum baud rates for Armada 370/XP

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Gregory CLEMENT commit ce2f6ea1cbd41d78224f703af980a6ceeb0eb56a upstream. The commit df59fa7f4bca "spi: orion: support armada extended baud rates" was too optimistic for the maximum b

[PATCH 3.19.y-ckt 036/251] genirq: devres: Fix testing return value of request_any_context_irq()

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Axel Lin commit 63781394c540dd9e666a6b21d70b64dd52bce76e upstream. request_any_context_irq() returns a negative value on failure. It returns either IRQC_IS_HARDIRQ or IRQC_IS_NESTED o

[PATCH 3.19.y-ckt 056/251] tty/serial: at91: RS485 mode: 0 is valid for delay_rts_after_send

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Ferre commit 8687634b7908c42eb700e0469e110e02833611d1 upstream. In RS485 mode, we may want to set the delay_rts_after_send value to 0. In the datasheet, the 0 value is said to

[PATCH 3.19.y-ckt 059/251] drm/radeon: take the mode_config mutex when dealing with hpds (v2)

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 39fa10f7e21574a70cecf1fed0f9b36535aa68a0 upstream. Since we are messing with state in the worker. v2: drop the changes in the mst worker Signed-off-by: Alex Deuc

[PATCH 3.19.y-ckt 060/251] rcu: Correctly handle non-empty Tiny RCU callback list with none ready

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: "Paul E. McKenney" commit 6e91f8cb138625be96070b778d9ba71ce520ea7e upstream. If, at the time __rcu_process_callbacks() is invoked, there are callbacks in Tiny RCU's callback list, bu

[PATCH 3.19.y-ckt 064/251] PCI: Add pci_bus_addr_t

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Yinghai Lu commit 3a9ad0b4fdcd57f775d3615004c8c64c021a9e7d upstream. David Ahern reported that d63e2e1f3df9 ("sparc/PCI: Clip bridge windows to fit in upstream windows") fails to boot

[PATCH 3.19.y-ckt 061/251] ASoC: arizona: Fix noise generator gain TLV

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Richard Fitzgerald commit 15575ed544910464715df5c45a44b9732e415b93 upstream. The Arizona codec drivers had an incorrect dB scaling for the noise generator gain that started at 0dB and

[PATCH 3.19.y-ckt 062/251] usb: dwc3: gadget: don't clear EP_BUSY too early

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Felipe Balbi commit e18b7975c885bc3a938b9a76daf32957ea0235fa upstream. In case of non-Isochronous transfers, we don't want to clear DWC3_EP_BUSY flag until XferComplete event. That's

[PATCH 3.19.y-ckt 069/251] megaraid_sas : Modify return value of megasas_issue_blocked_cmd() and wait_and_poll() to consider command status returned by firmware

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: "sumit.sax...@avagotech.com" commit 2be2a98845e6742a96d48534294d2c5ba582e57f upstream. This patch is rebased on top of recently sent 18 patches(submitted by me) for megaraid_sas drive

[PATCH 3.19.y-ckt 072/251] gpio: crystalcove: set IRQCHIP_SKIP_SET_WAKE for the irqchip

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Aaron Lu commit 61e749d7e1627d375156553ea0ae83c4f6bb5a9b upstream. The CrystalCove GPIO irqchip doesn't have irq_set_wake callback defined so we should set IRQCHIP_SKIP_SET_WAKE for i

[PATCH 3.19.y-ckt 063/251] dm cache: fix race when issuing a POLICY_REPLACE operation

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Joe Thornber commit fb4100ae7f312c3d614b37621c2b17b3b7cf65f8 upstream. There is a race between a policy deciding to replace a cache entry, the core target writing back any dirty data

[PATCH 3.19.y-ckt 073/251] SUNRPC: Fix a memory leak in the backchannel code

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 88de6af24f2b48b06c514d3c3d0a8f22fafe30bd upstream. req->rq_private_buf isn't initialised when xprt_setup_backchannel calls xprt_free_allocation. Fixes: fb7a0b9

[PATCH 3.19.y-ckt 071/251] powerpc/perf: Fix book3s kernel to userspace backtraces

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Anton Blanchard commit 72e349f1124a114435e599479c9b8d14bfd1ebcd upstream. When we take a PMU exception or a software event we call perf_read_regs(). This overloads regs->result with a

[PATCH 3.19.y-ckt 076/251] ARM: at91/dt: sama5d4ek: mci0 uses slot 0

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit ea25525ce0d195724fead07fe6562fe478a3bf6f upstream. Mci0 uses slot 0 not 1. Signed-off-by: Ludovic Desroches Fixes: 7a4752677c44 ("ARM: at91: dt: add device

[PATCH 3.19.y-ckt 075/251] Btrfs: don't invalidate root dentry when subvolume deletion fails

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Omar Sandoval commit 64ad6c488975d7516230cf7849190a991fd615ae upstream. Since commit bafc9b754f75 ("vfs: More precise tests in d_invalidate"), mounted subvolumes can be deleted becaus

[PATCH 3.19.y-ckt 074/251] ipr: Increase default adapter init stage change timeout

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Brian King commit 45c44b5ff9caa743ed9c2bfd44307c536c9caf1e upstream. Increase the default init stage change timeout from 15 seconds to 30 seconds. This resolves issues we have seen wi

[PATCH 3.19.y-ckt 077/251] mnt: Modify fs_fully_visible to deal with locked ro nodev and atime

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: "Eric W. Biederman" commit 8c6cf9cc829fcd0b179b59f7fe288941d0e31108 upstream. Ignore an existing mount if the locked readonly, nodev or atime attributes are less permissive than the d

[PATCH 3.19.y-ckt 067/251] staging: vt6655: device_rx_srv check sk_buff is NULL

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Malcolm Priestley commit b5eeed8cb6097c8ea660b6598d36fdbb94065a22 upstream. There is a small chance that pRD->pRDInfo->skb could go NULL while the interrupt is processing. Put NULL c

[PATCH] staging: rtl8188eu: core: find and remove code valid only for 5 HGz.

This one of the TODO tasks for staging rtl8188eu driver. I have removed the code referring to channel > 14 for rtw_ap.c, rtw_ieee80211.c and rtw_mlme.c files. Please review. Signed-off-by: Sreenath Madasu --- drivers/staging/rtl8188eu/core/rtw_ap.c| 31 +++--- drivers

[PATCH 3.19.y-ckt 080/251] drm/qxl: Do not cause spice-server to clean our objects

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Frediano Ziglio commit 2fa19535ca6abcbfd1ccc9ef694db52f49f77747 upstream. If objects are moved back from system memory to VRAM (and spice id created again) memory is already initializ

[PATCH 3.19.y-ckt 079/251] ASoC: tas2552: Fix kernel crash caused by wrong kcontrol entry

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi commit 1cf0f44811b754b64283b11ef0e60cb0de07b29c upstream. SOC_DAPM_SINGLE("Playback AMP", ..) should not be under kcontrols. It causes kernel crash (NULL pointer) when

[PATCH 3.19.y-ckt 068/251] fixing infinite OPEN loop in 4.0 stateid recovery

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Olga Kornievskaia commit e8d975e73e5fa05f983fbf2723120edcf68e0b38 upstream. Problem: When an operation like WRITE receives a BAD_STATEID, even though recovery code clears the RECLAIM_

[PATCH 3.19.y-ckt 078/251] ASoC: tas2552: Fix kernel crash when the codec is loaded but not part of a card

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi commit 80ba2669ec8c3e6517aa935001f6cb8809bf3df4 upstream. If the card is not part of any card the tas_data->codec is NULL since it is set only during snd_soc_codec_driv

[PATCH 3.19.y-ckt 082/251] ASoC: rt5645: Init jack_detect_work before registering irq

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Boichat commit 7ea3470a7277380248135a592a849e1c27960b2f upstream. Prevents frequent panic on boot, if the irq handler rt5645_irq gets called before the workqueue rt5645_jack_d

[PATCH 3.19.y-ckt 081/251] drm/qxl: Do not leak memory if qxl_release_list_add fails

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Frediano Ziglio commit 8451cc964c1d193b989c41a44e5e77109cc696f8 upstream. If the function fails reference counter to the object is not decremented causing leaks. This is hard to spot

[PATCH 3.19.y-ckt 085/251] ath3k: add support of 13d3:3474 AR3012 device

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Tunin commit 0d0cef6183aec0fb6d0c9f00a09ff51ee086bbe2 upstream. BugLink: https://bugs.launchpad.net/bugs/1427680 This device requires new firmware files AthrBT_0x11020100.dfu

[PATCH 3.19.y-ckt 084/251] ath3k: Add support of 0489:e076 AR3012 device

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Tunin commit 692c062e7c282164fd7cda68077f79dafd176eaf upstream. BugLink: https://bugs.launchpad.net/bugs/1462614 This device requires new firmware files AthrBT_0x11020100.dfu

[PATCH 3.19.y-ckt 083/251] selinux: fix setting of security labels on NFS

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit 9fc2b4b436cff7d8403034676014f1be9d534942 upstream. Before calling into the filesystem, vfs_setxattr calls security_inode_setxattr, which ends up calling selin

[PATCH 3.19.y-ckt 086/251] Bluetooth: btusb: Fix memory leak in Intel setup routine

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Marcel Holtmann commit ecffc80478cdce122f0ecb6a4e4f909132dd5c47 upstream. The SKB returned from the Intel specific version information command is missing a kfree_skb. Signed-off-by:

[PATCH 3.19.y-ckt 088/251] b43: fix support for 14e4:4321 PCI dev with BCM4321 chipset

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: =?UTF-8?q?Rafa=C5=82=20Mi=C5=82ecki?= commit 90f91b129810c3f169e443252be30ed7c0130326 upstream. It seems Broadcom released two devices with conflicting device id. There are for sure 1

Re: [PATCH v2 4/6] locking/pvqspinlock: Allow vCPUs kick-ahead

On 07/15/2015 05:39 AM, Peter Zijlstra wrote: On Tue, Jul 14, 2015 at 10:13:35PM -0400, Waiman Long wrote: Frequent CPU halting (vmexit) and CPU kicking (vmenter) lengthens critical section and block forward progress. This patch implements a kick-ahead mechanism where the unlocker will kick the

[PATCH 3.19.y-ckt 066/251] usb: core: Fix USB 3.0 devices lost in NOTATTACHED state after a hub port reset

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Robert Schlabbach commit fb6d1f7df5d25299fd7b3e84b72b8851d3634764 upstream. Fix USB 3.0 devices lost in NOTATTACHED state after a hub port reset. Dissolve the function hub_port_finis

[PATCH 3.19.y-ckt 087/251] ath9k: fix DMA stop sequence for AR9003+

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau commit 300f77c08ded96d33f492aaa02549103852f0c12 upstream. AR93xx and newer needs to stop rx before tx to avoid getting the DMA engine or MAC into a stuck state. This sho

Re: [RFC PATCH v2] memory-barriers: remove smp_mb__after_unlock_lock()

On Wed, 2015-07-15 at 11:44 +0100, Will Deacon wrote: > Hi Michael, > > On Wed, Jul 15, 2015 at 04:06:18AM +0100, Michael Ellerman wrote: > > On Tue, 2015-07-14 at 08:31 +1000, Benjamin Herrenschmidt wrote: > > > On Mon, 2015-07-13 at 13:15 +0100, Will Deacon wrote: > > > > This didn't go anywhere

[PATCH 3.19.y-ckt 089/251] cdc-acm: Add support of ATOL FPrint fiscal printers

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Alexey Sokolov commit 15bf722e6f6c0b884521a0363204532e849deb7f upstream. ATOL FPrint fiscal printers require usb_clear_halt to be executed to work properly. Add quirk to fix the issue

[PATCH 3.19.y-ckt 058/251] rtlwifi: Remove the clear interrupt routine from all drivers

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Vincent Fann commit 1277fa2ab2f9a624a4b0177119ca13b5fd65edd0 upstream. Several of these drivers have there TX randomly blocked for 3~5 seconds while measuring tx throughput (iperf). T

[PATCH 3.19.y-ckt 093/251] PCI: pciehp: Wait for hotplug command completion where necessary

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Alex Williamson commit a5dd4b4b0570b3bf880d563969b245dfbd170c1e upstream. The commit referenced below deferred waiting for command completion until the start of the next command, allo

[PATCH 3.19.y-ckt 092/251] NFC: st21nfcb: remove st21nfcb_nci_i2c_disable

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Christophe Ricard commit 4ac82e894825126816d7b7f662743335ce2b015e upstream. ndlc_remove already calls st21nfcb_nci_i2c_disable and phy->powered is already set to 0. Signed-off-by: Ch

[PATCH 3.19.y-ckt 091/251] NFC: st21nfcb: Do not remove header once the payload is sent

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Christophe Ricard commit 09f39a950523b1bb830c30a8670b77e0067da092 upstream. Once the data is sent, we need to preserve the full frame for the ndlc state machine. If the NDLC ACK is no

[PATCH 3.19.y-ckt 096/251] x86/PCI: Use host bridge _CRS info on Foxconn K8M890-8237A

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit 1dace0116d0b05c967d94644fc4dfe96be2ecd3d upstream. The Foxconn K8M890-8237A has two PCI host bridges, and we can't assign resources correctly without the informat

[PATCH 3.19.y-ckt 095/251] ACPI / PM: Add missing pm_generic_complete() invocation

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: "Rafael J. Wysocki" commit 3d56402d3fa8d10749eeb36293dd1992bd5ad0c3 upstream. Add missing invocation of pm_generic_complete() to acpi_subsys_complete() to allow ->complete callbacks p

[PATCH 3.19.y-ckt 070/251] ideapad_laptop: Lenovo G50-30 fix rfkill reports wireless blocked

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Tunin commit 4fa9dabcffc8e16601307d3d56b58c68d9716ba4 upstream. Lenovo G30-50 does not have a hardware wireless switch and wireless is always blocked. BugLink: https://bugs.la

[PATCH 3.19.y-ckt 097/251] pinctrl: mvebu: armada-38x: fix PCIe functions

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit 331642fbf24a1c16b2669ca0a6479b5fcd6dd5b2 upstream. A new revision of the Marvell Armada 38x hardware datasheet unveiled that the definition of some of the PCIe

[PATCH 3.19.y-ckt 094/251] regulator: core: fix constraints output buffer

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Stefan Wahren commit a7068e3932eee8268c4ce4e080a338ee7b8a27bf upstream. The buffer for condtraints debug isn't big enough to hold the output in all cases. So fix this issue by increas

[PATCH 3.19.y-ckt 065/251] staging: rtl8712: prevent buffer overrun in recvbuf2recvframe

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Haggai Eran commit cab462140f8a183e3cca0b51c8b59ef715cb6148 upstream. With an RTL8191SU USB adaptor, sometimes the hints for a fragmented packet are set, but the packet length is too

[PATCH 3.19.y-ckt 098/251] pinctrl: mvebu: armada-370: fix spi0 pin description

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit 438881dfddb9107ef0eb30b49368e91e092f0b3e upstream. Due to a mistake, the CS0 and CS1 SPI0 functions were incorrectly named "spi0-1" instead of just "spi0". Thi

[PATCH 3.19.y-ckt 099/251] pinctrl: mvebu: armada-375: remove non-existing NAND re/we pins

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit e5447d26092c72ef3346615ee558c9112ef8063f upstream. After updating to a more recent version of the Armada 375, we realized that some of the pins documented as h

[PATCH 3.19.y-ckt 090/251] NFC: st21nfcb: Remove inappropriate kfree on a devm_kzalloc pointer

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Firo Yang commit 38bd83f04c5e9695011dc5c294e0c4e6a9f9052d upstream. Since ndev->driver_data is allocated by devm_kzalloc(), we do not need the inappropriate kfree to free it in driver

[PATCH 3.19.y-ckt 108/251] arm64: Do not attempt to use init_mm in reset_context()

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Catalin Marinas commit 565630d503ef24e44c252bed55571b3a0d68455f upstream. After secondary CPU boot or hotplug, the active_mm of the idle thread is &init_mm. The init_mm.pgd (swapper_p

[PATCH 3.19.y-ckt 100/251] pinctrl: mvebu: armada-xp: remove non-existing NAND pins

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit bc99357f3690c11817756adfee0ece811a3db2e7 upstream. After updating to a more recent version of the Armada XP datasheet, we realized that some of the pins docume

[PATCH 3.19.y-ckt 105/251] i2c: at91: fix a race condition when using the DMA controller

3.19.8-ckt4 -stable review patch. If anyone has any objections, please let me know. -- From: Cyrille Pitchen commit 93563a6a71bb69dd324fc7354c60fb05f84aae6b upstream. For TX transactions, the TXCOMP bit in the Status Register is cleared when the first data is written into the

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