[PATCH 3.16 025/114] regmap: spmi: Fix regmap_spmi_ext_read in multi-byte case

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Jack Pham commit dec8e8f6e6504aa3496c0f7cc10c756bb0e10f44 upstream. Specifically for the case of reads that use the Extended Register Read Long command, a multi-byte read operation is broken

[PATCH 3.16 060/114] batman-adv: fix DAT candidate selection (must use vid)

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Antonio Quartulli commit 2871734e85e920503d49b3a8bc0afbe0773b6036 upstream. Now that DAT is VLAN aware, it must use the VID when computing the DHT address of the candidate nodes where an

[PATCH 3.16 045/114] batman-adv: Reduce refcnt of removed router when updating route

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Sven Eckelmann commit d1a65f1741bfd9c69f9e4e2ad447a89b6810427d upstream. _batadv_update_route rcu_derefences orig_ifinfo->router outside of a spinlock protected region to print some

[PATCH 3.16 004/114] HID: usbhid: fix inconsistent reset/resume/reset-resume behavior

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit 972e6a993f278b416a8ee3ec65475724fc36feb2 upstream. The usbhid driver has inconsistently duplicated code in its post-reset, resume, and reset-resume pathways.

[PATCH 3.16 005/114] ARM: OMAP2+: Only write the sysconfig on idle when necessary

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Jon Hunter commit 127500ccb766f0e963436e25ddd57be8f1695498 upstream. Currently, whenever we idle a device _idle_sysc() is called and writes to the devices SYSCONFIG

[PATCH 3.16 005/114] ARM: OMAP2+: Only write the sysconfig on idle when necessary

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Jon Hunter commit 127500ccb766f0e963436e25ddd57be8f1695498 upstream. Currently, whenever we idle a device _idle_sysc() is called and writes to the devices SYSCONFIG register to set the idle

Re: [PATCH 5/7] random: replace non-blocking pool with a Chacha20-based CRNG

On Mon, Jun 13, 2016 at 08:00:33PM +0200, Stephan Mueller wrote: > > 1. The ChaCha20 is seeded with 256 bits (let us assume it is full entropy) > > 2. The ChaCha20 block operation shuffles the 256 bits of entropy over the 512 > bit state -- already here we see that after shuffling, the entropy

Re: [PATCH 5/7] random: replace non-blocking pool with a Chacha20-based CRNG

On Mon, Jun 13, 2016 at 08:00:33PM +0200, Stephan Mueller wrote: > > 1. The ChaCha20 is seeded with 256 bits (let us assume it is full entropy) > > 2. The ChaCha20 block operation shuffles the 256 bits of entropy over the 512 > bit state -- already here we see that after shuffling, the entropy

Re: [PATCH 2/8] kexec_file: Generalize kexec_add_buffer.

Hello Dave, Thanks for the quick review and for your comments. I'll separate the change to add arch_walk_system_ram and the change to add kexec_locate_mem_hole into different patches, and add error handling for KEXEC_ON_CRASH. Am Montag, 13 Juni 2016, 15:29:39 schrieb Dave Young: > On

[PATCH 3.16 037/114] net: ethernet: davinci_emac: Fix platform_data overwrite

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Neil Armstrong commit 210990b05a1247886539078e857cd038881bb2d6 upstream. When the DaVinci emac driver is removed and re-probed, the actual pdev->dev.platform_data is

[PATCH 3.16 021/114] usb: xhci: fix wild pointers in xhci_mem_cleanup

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Lu Baolu commit 71504062a7c34838c3fccd92c447f399d3cb5797 upstream. This patch fixes some wild pointers produced by xhci_mem_cleanup. These wild pointers will cause

[PATCH 3.16 054/114] drm/i915: Fix system resume if PCI device remained enabled

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Imre Deak commit dab9a2663f4e688106c041f7cd2797a721382f0a upstream. During system resume we depended on pci_enable_device() also putting the device into PCI D0 state.

Re: [PATCH 2/8] kexec_file: Generalize kexec_add_buffer.

Hello Dave, Thanks for the quick review and for your comments. I'll separate the change to add arch_walk_system_ram and the change to add kexec_locate_mem_hole into different patches, and add error handling for KEXEC_ON_CRASH. Am Montag, 13 Juni 2016, 15:29:39 schrieb Dave Young: > On

[PATCH 3.16 037/114] net: ethernet: davinci_emac: Fix platform_data overwrite

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Neil Armstrong commit 210990b05a1247886539078e857cd038881bb2d6 upstream. When the DaVinci emac driver is removed and re-probed, the actual pdev->dev.platform_data is populated with an

[PATCH 3.16 021/114] usb: xhci: fix wild pointers in xhci_mem_cleanup

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Lu Baolu commit 71504062a7c34838c3fccd92c447f399d3cb5797 upstream. This patch fixes some wild pointers produced by xhci_mem_cleanup. These wild pointers will cause system crash if

[PATCH 3.16 054/114] drm/i915: Fix system resume if PCI device remained enabled

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Imre Deak commit dab9a2663f4e688106c041f7cd2797a721382f0a upstream. During system resume we depended on pci_enable_device() also putting the device into PCI D0 state. This won't work if the

[PATCH 3.16 064/114] Drivers: hv_vmbus: Fix signal to host condition

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Christopher Oo commit a5cca686ce0ef4909deaee4ed46dd991e3a9ece4 upstream. Fixes a bug where previously hv_ringbuffer_read would pass in the old number of bytes

[PATCH 3.16 038/114] atl2: Disable unimplemented scatter/gather feature

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit f43bfaeddc79effbf3d0fcb53ca477cca66f3db8 upstream. atl2 includes NETIF_F_SG in hw_features even though it has no support for non-linear skbs. This

RE: [PATCH] crypto : async implementation for sha1-mb

-Original Message- From: Herbert Xu [mailto:herb...@gondor.apana.org.au] Sent: Monday, June 13, 2016 1:22 AM To: Dey, Megha Cc: tim.c.c...@linux.intel.com; da...@davemloft.net; linux-cry...@vger.kernel.org; linux-kernel@vger.kernel.org; Yu, Fenghua

[PATCH 3.16 070/114] drm/radeon: make sure vertical front porch is at least 1

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 3104b8128d4d646a574ed9d5b17c7d10752cd70b upstream. hw doesn't like a 0 value. Signed-off-by: Alex Deucher [bwh:

[PATCH 3.16 063/114] atomic_open(): fix the handling of create_error

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 10c64cea04d3c75c306b3f990586ffb343b63287 upstream. * if we have a hashed negative dentry and either CREAT|EXCL on r/o filesystem, or CREAT|TRUNC on r/o

[PATCH 3.16 064/114] Drivers: hv_vmbus: Fix signal to host condition

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Christopher Oo commit a5cca686ce0ef4909deaee4ed46dd991e3a9ece4 upstream. Fixes a bug where previously hv_ringbuffer_read would pass in the old number of bytes available to read instead of the

[PATCH 3.16 038/114] atl2: Disable unimplemented scatter/gather feature

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit f43bfaeddc79effbf3d0fcb53ca477cca66f3db8 upstream. atl2 includes NETIF_F_SG in hw_features even though it has no support for non-linear skbs. This bug was originally

RE: [PATCH] crypto : async implementation for sha1-mb

-Original Message- From: Herbert Xu [mailto:herb...@gondor.apana.org.au] Sent: Monday, June 13, 2016 1:22 AM To: Dey, Megha Cc: tim.c.c...@linux.intel.com; da...@davemloft.net; linux-cry...@vger.kernel.org; linux-kernel@vger.kernel.org; Yu, Fenghua ; Megha Dey Subject: Re: [PATCH]

[PATCH 3.16 070/114] drm/radeon: make sure vertical front porch is at least 1

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 3104b8128d4d646a574ed9d5b17c7d10752cd70b upstream. hw doesn't like a 0 value. Signed-off-by: Alex Deucher [bwh: Backported to 3.16: adjust context] Signed-off-by: Ben

[PATCH 3.16 063/114] atomic_open(): fix the handling of create_error

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 10c64cea04d3c75c306b3f990586ffb343b63287 upstream. * if we have a hashed negative dentry and either CREAT|EXCL on r/o filesystem, or CREAT|TRUNC on r/o filesystem, or

[PATCH 3.16 058/114] mm/huge_memory: replace VM_NO_THP VM_BUG_ON with actual VMA check

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit 3486b85a29c1741db99d0c522211c82d2b7a56d0 upstream. Khugepaged detects own VMAs by checking vm_file and vm_ops but this way it cannot distinguish

[PATCH 3.16 042/114] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Javier Martinez Canillas commit 10ff4c5239a137abfc896ec73ef3d15a0f86a16a upstream. The exynos5 I2C controller driver always prepares and enables a clock before using

[PATCH 3.16 069/114] tracing: Don't display trigger file for events that can't be enabled

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Chunyu Hu commit 854145e0a8e9a05f7366d240e2f99d9c1ca6d6dd upstream. Currently register functions for events will be called through the 'reg' field of event class directly

[PATCH 3.16 042/114] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Javier Martinez Canillas commit 10ff4c5239a137abfc896ec73ef3d15a0f86a16a upstream. The exynos5 I2C controller driver always prepares and enables a clock before using it and then disables

[PATCH 3.16 069/114] tracing: Don't display trigger file for events that can't be enabled

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Chunyu Hu commit 854145e0a8e9a05f7366d240e2f99d9c1ca6d6dd upstream. Currently register functions for events will be called through the 'reg' field of event class directly without any check

[PATCH 3.16 058/114] mm/huge_memory: replace VM_NO_THP VM_BUG_ON with actual VMA check

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit 3486b85a29c1741db99d0c522211c82d2b7a56d0 upstream. Khugepaged detects own VMAs by checking vm_file and vm_ops but this way it cannot distinguish private /dev/zero

Re: [PATCH v5 6/6] hwmon: use smp_call_on_cpu() for dell-smm i8k

On Wednesday 06 April 2016 16:17:46 Juergen Gross wrote: > Use the smp_call_on_cpu() function to call system management > mode on cpu 0. > Make call secure by adding get_online_cpus() to avoid e.g. suspend > resume cycles in between. > > Signed-off-by: Juergen Gross > --- > V4:

[PATCH v6 1/3] PCI: Add Precision Time Measurement (PTM) support

From: Jonathan Yong Add Precision Time Measurement (PTM) support (see PCIe r3.1, sec 6.22). Enable PTM on PTM Root devices and switch ports. This does not enable PTM on endpoints. There currently are no PTM-capable devices on the market, but it is expected to be

Re: [PATCH v5 6/6] hwmon: use smp_call_on_cpu() for dell-smm i8k

On Wednesday 06 April 2016 16:17:46 Juergen Gross wrote: > Use the smp_call_on_cpu() function to call system management > mode on cpu 0. > Make call secure by adding get_online_cpus() to avoid e.g. suspend > resume cycles in between. > > Signed-off-by: Juergen Gross > --- > V4: add call to

[PATCH v6 1/3] PCI: Add Precision Time Measurement (PTM) support

From: Jonathan Yong Add Precision Time Measurement (PTM) support (see PCIe r3.1, sec 6.22). Enable PTM on PTM Root devices and switch ports. This does not enable PTM on endpoints. There currently are no PTM-capable devices on the market, but it is expected to be supported by the Intel Apollo

[PATCH v6 3/3] PCI: Add PTM clock granularity information

I don't know how to figure out clock granularity for Root Complex Integrated Endpoints. The spec (PCIe r3.1, sec 7.32.3) says: system software must set [Effective Granularity] to the value reported in the Local Clock Granularity field by the associated PTM Time Source but I don't know how

[PATCH v6 3/3] PCI: Add PTM clock granularity information

I don't know how to figure out clock granularity for Root Complex Integrated Endpoints. The spec (PCIe r3.1, sec 7.32.3) says: system software must set [Effective Granularity] to the value reported in the Local Clock Granularity field by the associated PTM Time Source but I don't know how

[PATCH v6 2/3] PCI: Add pci_enable_ptm() for drivers to enable PTM on endpoints

Signed-off-by: Bjorn Helgaas --- drivers/pci/pcie/ptm.c| 45 + include/linux/pci.h |7 ++ include/uapi/linux/pci_regs.h |1 + 3 files changed, 53 insertions(+) diff --git a/drivers/pci/pcie/ptm.c

[PATCH v6 0/3] PCI: Precision Time Measurement support

This is a slightly different proposal for the PTM support Jonathan proposed here: http://lkml.kernel.org/r/1462956446-27361-2-git-send-email-jonathan.y...@intel.com I split this into three pieces mostly for ease in reviewing. They could all be squashed: - Enable PTM in root ports and

[PATCH v6 0/3] PCI: Precision Time Measurement support

This is a slightly different proposal for the PTM support Jonathan proposed here: http://lkml.kernel.org/r/1462956446-27361-2-git-send-email-jonathan.y...@intel.com I split this into three pieces mostly for ease in reviewing. They could all be squashed: - Enable PTM in root ports and

[PATCH v6 2/3] PCI: Add pci_enable_ptm() for drivers to enable PTM on endpoints

Signed-off-by: Bjorn Helgaas --- drivers/pci/pcie/ptm.c| 45 + include/linux/pci.h |7 ++ include/uapi/linux/pci_regs.h |1 + 3 files changed, 53 insertions(+) diff --git a/drivers/pci/pcie/ptm.c b/drivers/pci/pcie/ptm.c

[PATCH 3.16 057/114] IB/security: Restrict use of the write() interface

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Jason Gunthorpe commit e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3 upstream. The drivers/infiniband stack uses write() as a replacement for bi-directional

[PATCH 3.16 057/114] IB/security: Restrict use of the write() interface

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Jason Gunthorpe commit e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3 upstream. The drivers/infiniband stack uses write() as a replacement for bi-directional ioctl(). This is not safe. There are

[PATCH 3.16 065/114] Drivers: hv: vmbus: Fix signaling logic in hv_need_to_signal_on_read()

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: "K. Y. Srinivasan" commit 1db488d12894f1936360779d6ab2aede3dd7f06a upstream. On the consumer side, we have interrupt driven flow management of the producer. It is

[PATCH 3.16 061/114] batman-adv: Fix reference counting of vlan object for tt_local_entry

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Sven Eckelmann commit a33d970d0b54b09746d5540af8271fad4eb10229 upstream. The batadv_tt_local_entry was specific to a batadv_softif_vlan and held an implicit reference to

Re: [PATCH 44/48] clocksource: atmel-pit: allow unselecting ATMEL_PIT

On Sat, 11 Jun 2016 12:53:51 +0200 Alexandre Belloni wrote: > On 11/06/2016 at 11:43:54 +0200, Thomas Gleixner wrote : > > On Sat, 11 Jun 2016, Alexandre Belloni wrote: > > > > > With the new TCB clocksource driver, atmel platforms are now able to boot >

[PATCH 3.16 062/114] EDAC: i7core, sb_edac: Don't return NOTIFY_BAD from mce_decoder callback

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit c4fc1956fa31003bfbe4f597e359d751568e2954 upstream. Both of these drivers can return NOTIFY_BAD, but this terminates processing other callbacks that were

[PATCH 3.16 065/114] Drivers: hv: vmbus: Fix signaling logic in hv_need_to_signal_on_read()

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: "K. Y. Srinivasan" commit 1db488d12894f1936360779d6ab2aede3dd7f06a upstream. On the consumer side, we have interrupt driven flow management of the producer. It is sufficient to base the

[PATCH 3.16 061/114] batman-adv: Fix reference counting of vlan object for tt_local_entry

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Sven Eckelmann commit a33d970d0b54b09746d5540af8271fad4eb10229 upstream. The batadv_tt_local_entry was specific to a batadv_softif_vlan and held an implicit reference to it. But this

Re: [PATCH 44/48] clocksource: atmel-pit: allow unselecting ATMEL_PIT

On Sat, 11 Jun 2016 12:53:51 +0200 Alexandre Belloni wrote: > On 11/06/2016 at 11:43:54 +0200, Thomas Gleixner wrote : > > On Sat, 11 Jun 2016, Alexandre Belloni wrote: > > > > > With the new TCB clocksource driver, atmel platforms are now able to boot > > > without the PIT driver. Allow

[PATCH 3.16 062/114] EDAC: i7core, sb_edac: Don't return NOTIFY_BAD from mce_decoder callback

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit c4fc1956fa31003bfbe4f597e359d751568e2954 upstream. Both of these drivers can return NOTIFY_BAD, but this terminates processing other callbacks that were registered later on

[PATCH 3.16 076/114] propogate_mnt: Handle the first propogated copy being a slave

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: "Eric W. Biederman" commit 5ec0811d30378ae104f250bfc9b3640242d81e3f upstream. When the first propgated copy was a slave the following oops would result: > BUG: unable

[PATCH 3.16 073/114] crypto: hash - Fix page length clamping in hash walk

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 13f4bb78cf6a312bbdec367ba3da044b09bf0e29 upstream. The crypto hash walk code is broken when supplied with an offset greater than or equal to

[RFC PATCH] tty: serial: msm_serial: Don't reset uart on set_termios

Upon opening the tty, uart_open() ends up calling msm_set_baud_rate() which resets the uart block. If this happens as we're coming out of msm_console_write() a full fifo worth of console output will be discarded. Cc: Stephen Boyd Signed-off-by: Bjorn Andersson

[PATCH 3.16 076/114] propogate_mnt: Handle the first propogated copy being a slave

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: "Eric W. Biederman" commit 5ec0811d30378ae104f250bfc9b3640242d81e3f upstream. When the first propgated copy was a slave the following oops would result: > BUG: unable to handle kernel NULL

[PATCH 3.16 073/114] crypto: hash - Fix page length clamping in hash walk

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 13f4bb78cf6a312bbdec367ba3da044b09bf0e29 upstream. The crypto hash walk code is broken when supplied with an offset greater than or equal to PAGE_SIZE. This patch fixes it

[RFC PATCH] tty: serial: msm_serial: Don't reset uart on set_termios

Upon opening the tty, uart_open() ends up calling msm_set_baud_rate() which resets the uart block. If this happens as we're coming out of msm_console_write() a full fifo worth of console output will be discarded. Cc: Stephen Boyd Signed-off-by: Bjorn Andersson --- As reported here:

[PATCH 3.16 071/114] MAINTAINERS: Remove asterisk from EFI directory names

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Matt Fleming commit e8dfe6d8f6762d515fcd4f30577f7bfcf7659887 upstream. Mark reported that having asterisks on the end of directory names confuses get_maintainer.pl

[PATCH 3.16 001/114] Revert "ax25: add link layer header validation function"

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings This reverts commit ea47781c26510e5d97f80f9aceafe9065bd5e3aa, which was commit ea47781c26510e5d97f80f9aceafe9065bd5e3aa upstream. It is pointless unless

[PATCH 3.16 099/114] KEYS: Fix ASN.1 indefinite length object parsing

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: David Howells commit 23c8a812dc3c621009e4f0e5342aa4e2ede1ceaa upstream. This fixes CVE-2016-0758. In the ASN.1 decoder, when the length field of an ASN.1 value is

[PATCH 3.16 068/114] Minimal fix-up of bad hashing behavior of hash_64()

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 689de1d6ca95b3b5bd8ee446863bf81a4883ea25 upstream. This is a fairly minimal fixup to the horribly bad behavior of hash_64() with certain

[PATCH 3.16 075/114] fs/pnode.c: treat zero mnt_group_id-s as unequal

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Maxim Patlasov commit 7ae8fd0351f912b075149a1e03a017be8b903b9a upstream. propagate_one(m) calculates "type" argument for copy_tree() like this: >if

[PATCH 3.16 071/114] MAINTAINERS: Remove asterisk from EFI directory names

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Matt Fleming commit e8dfe6d8f6762d515fcd4f30577f7bfcf7659887 upstream. Mark reported that having asterisks on the end of directory names confuses get_maintainer.pl when it encounters

[PATCH 3.16 001/114] Revert "ax25: add link layer header validation function"

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings This reverts commit ea47781c26510e5d97f80f9aceafe9065bd5e3aa, which was commit ea47781c26510e5d97f80f9aceafe9065bd5e3aa upstream. It is pointless unless af_packet calls the new

[PATCH 3.16 099/114] KEYS: Fix ASN.1 indefinite length object parsing

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: David Howells commit 23c8a812dc3c621009e4f0e5342aa4e2ede1ceaa upstream. This fixes CVE-2016-0758. In the ASN.1 decoder, when the length field of an ASN.1 value is extracted, it isn't

[PATCH 3.16 068/114] Minimal fix-up of bad hashing behavior of hash_64()

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 689de1d6ca95b3b5bd8ee446863bf81a4883ea25 upstream. This is a fairly minimal fixup to the horribly bad behavior of hash_64() with certain input patterns. In particular,

[PATCH 3.16 075/114] fs/pnode.c: treat zero mnt_group_id-s as unequal

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Maxim Patlasov commit 7ae8fd0351f912b075149a1e03a017be8b903b9a upstream. propagate_one(m) calculates "type" argument for copy_tree() like this: >if (m->mnt_group_id ==

[PATCH 3.16 094/114] xfs: take i_mmap_lock on extent manipulation operations

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit e8e9ad42c1f1e1bfbe0e8c32c8cac02e9ebfb7ef upstream. Now we have the i_mmap_lock being held across the page fault IO path, we now add extent

[PATCH 3.16 094/114] xfs: take i_mmap_lock on extent manipulation operations

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit e8e9ad42c1f1e1bfbe0e8c32c8cac02e9ebfb7ef upstream. Now we have the i_mmap_lock being held across the page fault IO path, we now add extent manipulation operation exclusion

[PATCH 3.16 095/114] xfs: xfs_setattr_size no longer races with page faults

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit 0f9160b444e4de33b65dfcd3b901358a3129461a upstream. Now that truncate locks out new page faults, we no longer need to do special writeback hacks in

[PATCH 3.16 072/114] ACPICA: Dispatcher: Update thread ID for recursive method calls

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Prarit Bhargava commit 93d68841a23a5779cef6fb9aa0ef32e7c5bd00da upstream. ACPICA commit 7a3bd2d962f221809f25ddb826c9e551b916eb25 Set the mutex owner thread ID. Original

[PATCH 3.16 072/114] ACPICA: Dispatcher: Update thread ID for recursive method calls

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Prarit Bhargava commit 93d68841a23a5779cef6fb9aa0ef32e7c5bd00da upstream. ACPICA commit 7a3bd2d962f221809f25ddb826c9e551b916eb25 Set the mutex owner thread ID. Original patch from: Prarit

[PATCH 3.16 095/114] xfs: xfs_setattr_size no longer races with page faults

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit 0f9160b444e4de33b65dfcd3b901358a3129461a upstream. Now that truncate locks out new page faults, we no longer need to do special writeback hacks in truncate to work around

[PATCH 3.16 066/114] powerpc: Fix bad inline asm constraint in create_zero_mask()

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Anton Blanchard commit b4c112114aab9aff5ed4568ca5e662bb02cdfe74 upstream. In create_zero_mask() we have: addi%1,%2,-1 andc%1,%1,%2 popcntd

[PATCH 3.16 108/114] ARC: unbork !LLSC build

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Vineet Gupta commit daaf40e53b5dbdf75255d58a45ce8ac65ca511a8 upstream. Fixes: f7d11e93ee97a locking,arch,arc: Fold atomic_ops Signed-off-by: Vineet Gupta

[PATCH 3.16 066/114] powerpc: Fix bad inline asm constraint in create_zero_mask()

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Anton Blanchard commit b4c112114aab9aff5ed4568ca5e662bb02cdfe74 upstream. In create_zero_mask() we have: addi%1,%2,-1 andc%1,%1,%2 popcntd %0,%1 using the

[PATCH 3.16 108/114] ARC: unbork !LLSC build

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Vineet Gupta commit daaf40e53b5dbdf75255d58a45ce8ac65ca511a8 upstream. Fixes: f7d11e93ee97a locking,arch,arc: Fold atomic_ops Signed-off-by: Vineet Gupta Signed-off-by: Ben Hutchings Cc:

Re: [RESEND PATCH 1/3] rfkill: Create "rfkill-airplane-mode" LED trigger

Hi! > > João, that means you should send a patch to add the ::rfkill suffix. > > > > IMO "airplane" (or maybe "airplane-mode") is a better suffix, as it > reflects the label on the machine's chassis. I'll name it > "asus-wireless::airplane" and send this through platform-drivers-x86, > as this

[PATCH 3.16 081/114] get_rock_ridge_filename(): handle malformed NM entries

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 99d825822eade8d827a1817357cbf3f889a552d6 upstream. Payloads of NM entries are not supposed to contain NUL. When we run into such, only the part prior

[PATCH 3.16 081/114] get_rock_ridge_filename(): handle malformed NM entries

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 99d825822eade8d827a1817357cbf3f889a552d6 upstream. Payloads of NM entries are not supposed to contain NUL. When we run into such, only the part prior to the first NUL goes

Re: [RESEND PATCH 1/3] rfkill: Create "rfkill-airplane-mode" LED trigger

Hi! > > João, that means you should send a patch to add the ::rfkill suffix. > > > > IMO "airplane" (or maybe "airplane-mode") is a better suffix, as it > reflects the label on the machine's chassis. I'll name it > "asus-wireless::airplane" and send this through platform-drivers-x86, > as this

[PATCH 3.16 107/114] arm64: psci: move psci firmware calls out of line

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit f5e0a12ca2d939e47995f73428d9bf1ad372b289 upstream. An arm64 allmodconfig fails to build with GCC 5 due to __asmeq assertions in the PSCI firmware

[PATCH 3.16 107/114] arm64: psci: move psci firmware calls out of line

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit f5e0a12ca2d939e47995f73428d9bf1ad372b289 upstream. An arm64 allmodconfig fails to build with GCC 5 due to __asmeq assertions in the PSCI firmware calling code firing due to

Re: [PATCH 3/4] Documentation: DT: dma: Delete binding doc for AXI DMA

On Fri, Jun 10, 2016 at 02:42:33PM +0530, Kedareswara rao Appana wrote: > The AXI DMA support is added to the existing AXI VDMA > driver. Device tree binding information also updated > in the VDMA binding doc. > > Signed-off-by: Kedareswara rao Appana > --- >

Re: [PATCH 3/4] Documentation: DT: dma: Delete binding doc for AXI DMA

On Fri, Jun 10, 2016 at 02:42:33PM +0530, Kedareswara rao Appana wrote: > The AXI DMA support is added to the existing AXI VDMA > driver. Device tree binding information also updated > in the VDMA binding doc. > > Signed-off-by: Kedareswara rao Appana > --- >

[PATCH 3.16 103/114] net: fix a kernel infoleak in x25 module

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Kangjie Lu commit 79e48650320e6fba48369fccf13fd045315b19b8 upstream. Stack object "dte_facilities" is allocated in x25_rx_call_request(), which is supposed to be

[PATCH 3.16 101/114] net: fix infoleak in llc

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Kangjie Lu commit b8670c09f37bdf2847cc44f36511a53afc6161fd upstream. The stack object “info” has a total size of 12 bytes. Its last byte is padding which is not

[PATCH 3.16 103/114] net: fix a kernel infoleak in x25 module

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Kangjie Lu commit 79e48650320e6fba48369fccf13fd045315b19b8 upstream. Stack object "dte_facilities" is allocated in x25_rx_call_request(), which is supposed to be initialized in

[PATCH 3.16 101/114] net: fix infoleak in llc

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Kangjie Lu commit b8670c09f37bdf2847cc44f36511a53afc6161fd upstream. The stack object “info” has a total size of 12 bytes. Its last byte is padding which is not initialized and leaked via

[PATCH 3.16 048/114] USB: serial: cp210x: add Straizona Focusers device ids

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Jasem Mutlaq commit 613ac23a46e10d4d4339febdd534fafadd68e059 upstream. Adding VID:PID for Straizona Focusers to cp210x driver. Signed-off-by: Jasem Mutlaq

Re: [PATCH 1/4] Documentation: DT: vdma: Update binding doc for multi-channel dma mode

On Fri, Jun 10, 2016 at 02:42:31PM +0530, Kedareswara rao Appana wrote: > This patch updates the device-tree binding doc for > AXI DMA multi channel dma mode. > > Signed-off-by: Kedareswara rao Appana > --- > .../devicetree/bindings/dma/xilinx/xilinx_vdma.txt |4 >

Re: [PATCH 5/7] ARM: OMAP: dmtimer: Do not call PM runtime functions when not needed.

Hi, On 13.06.2016 10:10, Tony Lindgren wrote: * Ivaylo Dimitrov [160610 14:23]: On 10.06.2016 13:22, Tony Lindgren wrote: OK. And I just applied the related dts changes. Please repost the driver changes and DT binding doc with Rob's ack to the driver

[PATCH 3.16 048/114] USB: serial: cp210x: add Straizona Focusers device ids

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Jasem Mutlaq commit 613ac23a46e10d4d4339febdd534fafadd68e059 upstream. Adding VID:PID for Straizona Focusers to cp210x driver. Signed-off-by: Jasem Mutlaq Signed-off-by: Johan Hovold

Re: [PATCH 1/4] Documentation: DT: vdma: Update binding doc for multi-channel dma mode

On Fri, Jun 10, 2016 at 02:42:31PM +0530, Kedareswara rao Appana wrote: > This patch updates the device-tree binding doc for > AXI DMA multi channel dma mode. > > Signed-off-by: Kedareswara rao Appana > --- > .../devicetree/bindings/dma/xilinx/xilinx_vdma.txt |4 > 1 files changed, 4

Re: [PATCH 5/7] ARM: OMAP: dmtimer: Do not call PM runtime functions when not needed.

Hi, On 13.06.2016 10:10, Tony Lindgren wrote: * Ivaylo Dimitrov [160610 14:23]: On 10.06.2016 13:22, Tony Lindgren wrote: OK. And I just applied the related dts changes. Please repost the driver changes and DT binding doc with Rob's ack to the driver maintainers to apply. Already did,

[PATCH 3.16 104/114] arm64: kernel: fix architected PMU registers unconditional access

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Lorenzo Pieralisi commit f436b2ac90a095746beb6729b8ee8ed87c9eaede upstream. The Performance Monitors extension is an optional feature of the AArch64 architecture,

[PATCH 3.16 113/114] sched,dl: Remove return value from pull_dl_task()

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 0ea60c2054fc3b0c3eb68ac4f6884f3ee78d9925 upstream. In order to be able to use pull_dl_task() from a callback, we need to do away with the return

[PATCH 3.16 104/114] arm64: kernel: fix architected PMU registers unconditional access

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Lorenzo Pieralisi commit f436b2ac90a095746beb6729b8ee8ed87c9eaede upstream. The Performance Monitors extension is an optional feature of the AArch64 architecture, therefore, in order to

[PATCH 3.16 113/114] sched,dl: Remove return value from pull_dl_task()

3.16.36-rc1 review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 0ea60c2054fc3b0c3eb68ac4f6884f3ee78d9925 upstream. In order to be able to use pull_dl_task() from a callback, we need to do away with the return value. Since the return

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