[PATCH AUTOSEL for 4.4 126/162] btrfs: Fix out of bounds access in btrfs_search_slot

2018-04-08 Thread Sasha Levin
From: Nikolay Borisov [ Upstream commit 9ea2c7c9da13c9073e371c046cbbc45481ecb459 ] When modifying a tree where the root is at BTRFS_MAX_LEVEL - 1 then the level variable is going to be 7 (this is the max height of the tree). On the other hand btrfs_cow_block is always called

[PATCH AUTOSEL for 4.4 125/162] Btrfs: set plug for fsync

2018-04-08 Thread Sasha Levin
From: Liu Bo [ Upstream commit 343e4fc1c60971b0734de26dbbd475d433950982 ] Setting plug can merge adjacent IOs before dispatching IOs to the disk driver. Without plug, it'd not be a problem for single disk usecases, but for multiple disks using raid profile, a large IO can

[PATCH AUTOSEL for 4.4 121/162] kconfig: Fix automatic menu creation mem leak

2018-04-08 Thread Sasha Levin
From: Ulf Magnusson [ Upstream commit ae7440ef0c8013d68c00dad6900e7cce5311bb1c ] expr_trans_compare() always allocates and returns a new expression, giving the following leak outline: ... *Allocate* basedep = expr_trans_compare(basedep, E_UNEQUAL,

[PATCH AUTOSEL for 4.4 129/162] scsi: fas216: fix sense buffer initialization

2018-04-08 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 96d5eaa9bb74d299508d811d865c2c41b38b0301 ] While testing with the ARM specific memset() macro removed, I ran into a compiler warning that shows an old bug: drivers/scsi/arm/fas216.c: In function 'fas216_rq_sns_done':

[PATCH AUTOSEL for 4.4 128/162] scsi: devinfo: fix format of the device list

2018-04-08 Thread Sasha Levin
From: Xose Vazquez Perez [ Upstream commit 3f884a0a8bdf28cfd1e9987d54d83350096cdd46 ] Replace "" with NULL for product revision level, and merge TEXEL duplicate entries. Cc: Hannes Reinecke Cc: Martin K. Petersen Cc: James

[PATCH AUTOSEL for 4.4 132/162] powerpc/numa: Use ibm,max-associativity-domains to discover possible nodes

2018-04-08 Thread Sasha Levin
From: Michael Bringmann [ Upstream commit a346137e9142b039fd13af2e59696e3d40c487ef ] On powerpc systems which allow 'hot-add' of CPU or memory resources, it may occur that the new resources are to be inserted into nodes that were not used for these resources at bootup.

[PATCH AUTOSEL for 4.4 130/162] HID: roccat: prevent an out of bounds read in kovaplus_profile_activated()

2018-04-08 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit 7ad81482cad67cbe1ec808490d1ddfc420c42008 ] We get the "new_profile_index" value from the mouse device when we're handling raw events. Smatch taints it as untrusted data and complains that we need a bounds check. This seems like a

linux-next: Tree for Apr 9

2018-04-08 Thread Stephen Rothwell
Hi all, Please do not add any v4.18 destined stuff to your linux-next included trees until after v4.17-rc1 has been released. Changes since 20180406: The vfs tree lost its build failure. The parisc-hd tree still had its build failure for which I applied a patch. The nvdimm tree gained a build

Re: [PATCH 1/2] tty: n_gsm: Fix long delays with control frame timeouts in ADM mode

2018-04-08 Thread Tony Lindgren
* Pavel Machek [180408 19:07]: > Hi! > > > > Do you have a tool to use and a script? > > > > Yes I used the shell script I posted earlier, but forgot it also > > needs the ldattach done. > > > > Anyways, last night and today I wrote a quick test utility called > > droid4-ngsm

[PATCH AUTOSEL for 4.9 084/293] r8152: add byte_enable for ocp_read_word function

2018-04-08 Thread Sasha Levin
From: hayeswang [ Upstream commit d8fbd27469fc02049c674de296a3263bef089131 ] Add byte_enable for ocp_read_word() to replace reading 4 bytes data with reading the desired 2 bytes data. This is used to avoid the issue which is described in commit b4d99def0938 ("r8152:

[PATCH AUTOSEL for 4.9 063/293] tpm_tis: Fix IRQ autoprobing when using platform_device

2018-04-08 Thread Sasha Levin
From: Jason Gunthorpe [ Upstream commit d27f81f061bbde627ac4fbd735114f9ea2c63615 ] The test was backwards, triggering IRQ autoprobing if the firmware did not specify an IRQ, instead of triggering it only when the module force parameter was specified. Since

[PATCH AUTOSEL for 4.9 071/293] x86/mce: Don't disable MCA banks when offlining a CPU on AMD

2018-04-08 Thread Sasha Levin
From: Yazen Ghannam [ Upstream commit ec33838244c8535b23b8d24b167996fd1318bb68 ] AMD systems have non-core, shared MCA banks within a die. These banks are controlled by a master CPU per die. If this CPU is offlined then all the shared banks are disabled in addition to the

[PATCH AUTOSEL for 4.9 052/293] scsi: lpfc: Fix return value of board_mode store routine in case of online failure

2018-04-08 Thread Sasha Levin
From: James Smart [ Upstream commit 522dceeb62ded1a7b538d2f1f61cc69a1402537d ] On hbacmd reset failure, observing wrong string "nline" in kernel log. On failure, non negative value (1) is returned from sysfs store routine. It is interpreted as count by kernel and store

[PATCH AUTOSEL for 4.9 057/293] PCI: Add domain number check to find_smbios_instance_string()

2018-04-08 Thread Sasha Levin
From: Sujith Pandel [ Upstream commit 6c51c82c60991bdbfb937f3bf0cdbe68d042073d ] The function find_smbios_instance_string() does not consider the PCI domain number. As a result, SMBIOS type 41 device type instance would be exported to sysfs for all the PCI domains

[PATCH AUTOSEL for 4.9 068/293] ixgbe: fix race condition with PTP_TX_IN_PROGRESS bits

2018-04-08 Thread Sasha Levin
From: Jacob Keller [ Upstream commit aaebaf50b502648b1d4d8c93b4be133944c2bbd0 ] Hardware related to the ixgbe driver is limited to handling a single Tx timestamp request at a time. Thus, the driver ignores requests for Tx timestamp while waiting for the current request

[PATCH AUTOSEL for 4.9 083/293] drm/mgag200: Fix to always set HiPri for G200e4 V2

2018-04-08 Thread Sasha Levin
From: Mathieu Larouche [ Upstream commit 0cbb738108927916a659b5b0b96e386fcd7cc6e1 ] - Changed the HiPri value for G200e4 to always be 0. - Added Bandwith limitation to block resolution above 1920x1200x60Hz Signed-off-by: Mathieu Larouche

[PATCH AUTOSEL for 3.18 060/101] fs: warn in case userspace lied about modprobe return

2018-04-08 Thread Sasha Levin
From: "Luis R. Rodriguez" [ Upstream commit 41124db869b7e00e12052555f8987867ac01d70c ] kmod <= v19 was broken -- it could return 0 to modprobe calls, incorrectly assuming that a kernel module was built-in, whereas in reality the module was just forming in the kernel. The

[PATCH AUTOSEL for 3.18 063/101] vmlfb: Fix error handling in cr_pll_init()

2018-04-08 Thread Sasha Levin
From: Alexey Khoroshilov [ Upstream commit 6af574e826740bf17663b48ba3f8fadb81d2113f ] There is an error path, where iomemory is left mapped. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov Cc: Alan

[PATCH AUTOSEL for 3.18 064/101] firewire-ohci: work around oversized DMA reads on JMicron controllers

2018-04-08 Thread Sasha Levin
From: Hector Martin [ Upstream commit 188775181bc05f29372b305ef96485840e351fde ] At least some JMicron controllers issue buggy oversized DMA reads when fetching context descriptors, always fetching 0x20 bytes at once for descriptors which are only 0x10 bytes long. This is

[PATCH AUTOSEL for 3.18 062/101] irqchip/gic-v3: Honor forced affinity setting

2018-04-08 Thread Sasha Levin
From: Suzuki K Poulose [ Upstream commit 65a30f8b300107266f316d550f060ccc186201a3 ] Honor the 'force' flag for set_affinity, by selecting a CPU from the given mask (which may not be reported "online" by the cpu_online_mask). Some drivers, like ARM PMU, rely on it. Cc:

[PATCH AUTOSEL for 3.18 058/101] arm64: ptrace: Fix incorrect get_user() use in compat_vfp_set()

2018-04-08 Thread Sasha Levin
From: Dave Martin [ Upstream commit 5fbd5fc49fc39ac8433da62d16682a1d0217ea4f ] Now that compat_vfp_get() uses the regset API to copy the FPSCR value out to userspace, compat_vfp_set() looks inconsistent. In particular, compat_vfp_set() will fail if called with kbuf != NULL

[PATCH AUTOSEL for 3.18 065/101] ASoC: au1x: Fix timeout tests in au1xac97c_ac97_read()

2018-04-08 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit 123af9043e93cb6f235207d260d50f832cdb5439 ] The loop timeout doesn't work because it's a post op and ends with "tmo" set to -1. I changed it from a post-op to a pre-op and I changed the initial the starting value from 5 to 6 so we

[PATCH AUTOSEL for 3.18 068/101] PCI: Add function 1 DMA alias quirk for Marvell 9128

2018-04-08 Thread Sasha Levin
From: Alex Williamson [ Upstream commit aa008206634363ef800fbd5f0262016c9ff81dea ] The Marvell 9128 is the original device generating bug 42679, from which many other Marvell DMA alias quirks have been sourced, but we didn't have positive confirmation of the fix on

[PATCH AUTOSEL for 3.18 059/101] x86/um: thin archives build fix

2018-04-08 Thread Sasha Levin
From: Nicholas Piggin [ Upstream commit 827880ec260ba048f95fe646b96a205c394fa0f0 ] The linker does not like vdso-syms.lds in input archive files. Make it an extra-y instead. Cc: Jeff Dike Cc: Richard Weinberger Cc:

[PATCH AUTOSEL for 4.4 133/162] powerpc/numa: Ensure nodes initialized for hotplug

2018-04-08 Thread Sasha Levin
From: Michael Bringmann [ Upstream commit ea05ba7c559c8e5a5946c3a94a2a266e9a6680a6 ] This patch fixes some problems encountered at runtime with configurations that support memory-less nodes, or that hot-add CPUs into nodes that are memoryless during system execution

[PATCH AUTOSEL for 4.4 144/162] x86/power: Fix swsusp_arch_resume prototype

2018-04-08 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 328008a72d38b5bde6491e463405c34a81a65d3e ] The declaration for swsusp_arch_resume marks it as 'asmlinkage', but the definition in x86-32 does not, and it fails to include the header with the declaration. This leads to a warning when building

[PATCH AUTOSEL for 4.4 146/162] ACPI: processor_perflib: Do not send _PPC change notification if not ready

2018-04-08 Thread Sasha Levin
From: Chen Yu [ Upstream commit ba1edb9a5125a617d612f98eead14b9b84e75c3a ] The following warning was triggered after resumed from S3 - if all the nonboot CPUs were put offline before suspend: [ 1840.329515] unchecked MSR access error: RDMSR from 0x771 at rIP:

[PATCH AUTOSEL for 4.4 148/162] MIPS: TXx9: use IS_BUILTIN() for CONFIG_LEDS_CLASS

2018-04-08 Thread Sasha Levin
From: Matt Redfearn [ Upstream commit 0cde5b44a30f1daaef1c34e08191239dc63271c4 ] When commit b27311e1cace ("MIPS: TXx9: Add RBTX4939 board support") added board support for the RBTX4939, it added a call to led_classdev_register even if the LED class is built as a module.

[PATCH AUTOSEL for 4.4 147/162] bpf: fix selftests/bpf test_kmod.sh failure when CONFIG_BPF_JIT_ALWAYS_ON=y

2018-04-08 Thread Sasha Levin
From: Yonghong Song [ Upstream commit 09584b406742413ac4c8d7e030374d4daa045b69 ] With CONFIG_BPF_JIT_ALWAYS_ON is defined in the config file, tools/testing/selftests/bpf/test_kmod.sh failed like below: [root@localhost bpf]# ./test_kmod.sh sysctl: setting key

[PATCH AUTOSEL for 4.4 140/162] mm/mempolicy: add nodes_empty check in SYSC_migrate_pages

2018-04-08 Thread Sasha Levin
From: Yisheng Xie [ Upstream commit 0486a38bcc4749808edbc848f1bcf232042770fc ] As in manpage of migrate_pages, the errno should be set to EINVAL when none of the node IDs specified by new_nodes are on-line and allowed by the process's current cpuset context, or none of

[PATCH AUTOSEL for 4.4 141/162] asm-generic: provide generic_pmdp_establish()

2018-04-08 Thread Sasha Levin
From: "Kirill A. Shutemov" [ Upstream commit c58f0bb77ed8bf93dfdde762b01cb67eebbdfc29 ] Patch series "Do not lose dirty bit on THP pages", v4. Vlastimil noted that pmdp_invalidate() is not atomic and we can lose dirty and access bits if CPU sets them after pmdp

[PATCH AUTOSEL for 4.4 151/162] RDS: IB: Fix null pointer issue

2018-04-08 Thread Sasha Levin
From: Guanglei Li [ Upstream commit 2c0aa08631b86a4678dbc93b9caa5248014b4458 ] Scenario: 1. Port down and do fail over 2. Ap do rds_bind syscall PID: 47039 TASK: 89887e2fe640 CPU: 47 COMMAND: "kworker/u:6" #0 [898e35f159f0] machine_kexec at 8103abf9

Re: [GIT PULL] SELinux patches for v4.17

2018-04-08 Thread Xin Long
On Mon, Apr 9, 2018 at 6:44 AM, Richard Haines wrote: > On Sun, 2018-04-08 at 19:59 +0100, Richard Haines via Selinux wrote: >> On Mon, 2018-04-09 at 01:43 +0800, Xin Long wrote: >> > On Sun, Apr 8, 2018 at 10:09 PM, Richard Haines >> >

Re: [PATCH] crypto: DRBG - guard uninstantion by lock

2018-04-08 Thread Stephan Mueller
Am Montag, 9. April 2018, 00:46:03 CEST schrieb Theodore Y. Ts'o: Hi Theodore, > > So the syzbot will run while the patch goes through the normal e-mail > review process, which is kind of neat. :-) Thank you very much for the hint. That is a neat feature indeed. As I came late to the party

Re: [PATCH 4/4] x86: usercopy: reimplement arch_within_stack_frames with unwinder

2018-04-08 Thread Keun-O Park
Hi Kees, On Thu, Apr 5, 2018 at 3:11 AM, Kees Cook wrote: > [resending with the CCs I forgot...] > > On Thu, Mar 1, 2018 at 2:19 AM, wrote: >> From: Sahara >> >> The old arch_within_stack_frames which used the frame

Re: [PATCH V2 3/9] dt-bindings: Tegra186 tachometer device tree bindings

2018-04-08 Thread Mikko Perttunen
Rob, this binding is for a specific IP block (for measuring/aggregating input pulses) on the Tegra186 SoC, so I don't think it fits into any generic binding. Thanks, Mikko On 03/27/2018 05:52 PM, Rob Herring wrote: On Wed, Mar 21, 2018 at 10:10:38AM +0530, Rajkumar Rampelli wrote: Supply

[PATCH v3 0/4] zram memory tracking

2018-04-08 Thread Minchan Kim
zRam as swap is useful for small memory device. However, swap means those pages on zram are mostly cold pages due to VM's LRU algorithm. Especially, once init data for application are touched for launching, they tend to be not accessed any more and finally swapped out. zRAM can store such cold

[PATCH v3 4/4] zram: introduce zram memory tracking

2018-04-08 Thread Minchan Kim
zRam as swap is useful for small memory device. However, swap means those pages on zram are mostly cold pages due to VM's LRU algorithm. Especially, once init data for application are touched for launching, they tend to be not accessed any more and finally swapped out. zRAM can store such cold

[PATCH v3 3/4] zram: record accessed second

2018-04-08 Thread Minchan Kim
zRam as swap is useful for small memory device. However, swap means those pages on zram are mostly cold pages due to VM's LRU algorithm. Especially, once init data for application are touched for launching, they tend to be not accessed any more and finally swapped out. zRAM can store such cold

[PATCH v3 2/4] zram: mark incompressible page as ZRAM_HUGE

2018-04-08 Thread Minchan Kim
Mark incompressible pages so that we could investigate who is the owner of the incompressible pages once the page is swapped out via using upcoming zram memory tracker feature. With it, we could prevent such pages to be swapped out by using mlock. Otherwise we might remove them. This patch

[PATCH v3 1/4] zram: correct flag name of ZRAM_ACCESS

2018-04-08 Thread Minchan Kim
ZRAM_ACCESS is used for locking a slot of zram so correct the name. It is also not a common flag to indicate status of the block so move the declare position on top of the flag. Lastly, let's move the function to the top of source code to be able to use it easily without forward declaration.

Re: WARNING in kmem_cache_free

2018-04-08 Thread Al Viro
On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote: > Interesting type of bug, I think we see this for the first time. > > Al, do you see how this can happen? putname() on something that hasn't come from getname(). Short of reproducer, I don't see what can be done - it can be any

Re: WARNING in kmem_cache_free

2018-04-08 Thread Matthew Wilcox
On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote: > On Fri, Apr 6, 2018 at 3:24 PM, syzbot > wrote: > > Unfortunately, I don't have any reproducer for this crash yet. > > Interesting type of bug, I think we see this for the

Re: [GIT PULL] SELinux patches for v4.17

2018-04-08 Thread Xin Long
On Sat, Apr 7, 2018 at 7:07 AM, Linus Torvalds wrote: > On Tue, Apr 3, 2018 at 6:37 PM, Paul Moore wrote: >> >> Everything passes the selinux-testsuite, but there are a few known >> merge conflicts. The first is with the netdev tree and is in

Running syzkaller repros using kvm-xfstests

2018-04-08 Thread Theodore Y. Ts'o
On Thu, Apr 05, 2018 at 09:37:41PM -0400, Theodore Y. Ts'o wrote: > Note that I haven't just been complaining about it. I've been working > on ways so that the gce-xfstests and kvm-xfstests test appliances can > more easily be used to work on Syzbot reports. If I can make myself > more

Re: [PATCH 2/4] arm64: usercopy: implement arch_within_stack_frames

2018-04-08 Thread Keun-O Park
Hi Kees, On Thu, Apr 5, 2018 at 2:55 AM, Kees Cook wrote: > On Thu, Mar 1, 2018 at 2:19 AM, wrote: >> From: James Morse >> >> This implements arch_within_stack_frames() for arm64 that should >> validate if a given object is

[PATCH] free e820 reserved memory in bootargs memmap

2018-04-08 Thread zoucao
add a new chareater "-" in bootargs memmap, you can use this chareater to free e820 reserved memory, for example: reserved iomem: cat /proc/iomem: .. 0010-6aefefff : System RAM 0100-0165537a : Kernel code 0165537b-01a8873f : Kernel data

[PATCH] x86/boot/e820: add new chareater "-" to free BIOS memory in memmap bootargs

2018-04-08 Thread zoucao
From: zoucao Normally every BIOS reserved memory is used for some features, we can not use them, but in some conditions, users can ensure some BIOS memorys are not used and reserved memory is well to free, they have not a good way to free these memroys, here add a new

Re: [PATCH v3 2/4] mm/sparsemem: Defer the ms->section_mem_map clearing

2018-04-08 Thread Baoquan He
Hi Dave, Thanks a lot for your careful reviewing! On 04/06/18 at 07:23am, Dave Hansen wrote: > On 02/27/2018 07:26 PM, Baoquan He wrote: > > In sparse_init(), if CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y, system > > will allocate one continuous memory chunk for mem maps on one node and > >

[PATCH v5 0/1] Safe LSM (un)loading, and immutable hooks

2018-04-08 Thread Sargun Dhillon
The primary security benefit of this patchset is the introduction of read-only hooks, even if some security modules have mutable hooks. Currently, if you have any LSMs with mutable hooks it will render all heads, and list nodes mutable. These are a prime place to attack because being able to

[PATCH v5 1/1] security: Add mechanism to safely (un)load LSMs after boot time

2018-04-08 Thread Sargun Dhillon
This patch introduces a mechanism to add mutable hooks and immutable hooks to the callback chain. It adds an intermediary item to the chain which separates mutable and immutable hooks. Immutable hooks are then marked as read-only, as well as the hook heads. This does not preclude some hooks being

[PATCH 0/3] irqchip: meson-gpio: add support for Meson-AXG SoCs

2018-04-08 Thread Yixun Lan
This series try to add GPIO interrupt controller support for Meson-AXG SoCs. The first patch is a trivial typo fix, I can fold the first two patches together if necessary. Yixun Lan (3): dt-bindings: interrupt-controller: fix the double quotes dt-bindings: interrupt-controller: New

[PATCH 2/3] dt-bindings: interrupt-controller: New binding for Meson-AXG SoC

2018-04-08 Thread Yixun Lan
Update the dt-binding documentation to support new compatible string for the GPIO interrupt controller which found in Amlogic's Meson-AXG SoC. Signed-off-by: Yixun Lan --- .../devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.txt | 1 + 1 file changed, 1

[PATCH 3/3] irqchip/meson-gpio: add support for Meson-AXG SoCs

2018-04-08 Thread Yixun Lan
The Meson-AXG SoC uses the same GPIO interrupt controller IP block as the other Meson SoCs. A total of 100 pins can be spied on, which is the sum of: - 255:100 Undefined(no interrupt) - 99:84, 16 pins on bank GPIOY - 83:61, 23 pins on bank GPIOX - 60:40, 21 pins on bank GPIOA - 39:25, 15 pins on

[PATCH 1/3] dt-bindings: interrupt-controller: fix the double quotes

2018-04-08 Thread Yixun Lan
The double quotes seems not ASCII type, fix it here. Signed-off-by: Yixun Lan --- .../bindings/interrupt-controller/amlogic,meson-gpio-intc.txt | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH] mtd: spi-nor: clear Extended Address Reg on switch to 3-byte addressing.

2018-04-08 Thread NeilBrown
According to section 8.2.7 Write Extended Address Register (C5h) of the Winbond W25Q256FV data sheet (256M-BIT SPI flash) The Extended Address Register is only effective when the device is in the 3-Byte Address Mode. When the device operates in the 4-Byte Address Mode (ADS=1), any

[PATCH AUTOSEL for 4.4 049/162] scsi: lpfc: Fix crash after firmware flash when IO is running.

2018-04-08 Thread Sasha Levin
From: James Smart [ Upstream commit 569dbe84a3e769009aa4a5d1030d000168889580 ] OS crashes after the completion of firmware download. Failure in posting SCSI SGL buffers because number of SGL buffers is less than total count. Some of the pending IOs are not completed by

[PATCH AUTOSEL for 4.4 050/162] ALSA: hda: Fix potential race at unregistration and unsol events

2018-04-08 Thread Sasha Levin
From: Takashi Iwai [ Upstream commit eb8d0eaaf84b0398533a7c091a0b65663f2fd7ea ] When the codec device is unregistered / freed, it may release the resource while being used in an unsolicited event like the jack detection work. This leads to use-after-free. The fix here is to

[PATCH AUTOSEL for 4.4 041/162] i2c: ismt: fix wrong device address when unmap the data buffer

2018-04-08 Thread Sasha Levin
From: Liwei Song [ Upstream commit 17e83549e199d89aace7788a9f11c108671eecf5 ] Fix the following kernel bug: kernel BUG at drivers/iommu/intel-iommu.c:3260! invalid opcode: [#5] PREEMPT SMP Hardware name: Intel Corp. Harcuvar/Server, BIOS

[PATCH AUTOSEL for 4.4 048/162] clk: socfpga: Fix the smplsel on Arria10 and Stratix10

2018-04-08 Thread Sasha Levin
From: Dinh Nguyen [ Upstream commit b7f8101d6e75fefd22c39624a30c9ed3d7a72463 ] The smplsel bits for the SDMMC clock on Arria10 and Stratix10 platforms are offset by 1 additional bit. Add a new macro SYSMGR_SDMMC_CTRL_SET_AS10 for usage on the Arria10 and Stratix10

[PATCH AUTOSEL for 4.4 040/162] firmware: dmi_scan: Check DMI structure length

2018-04-08 Thread Sasha Levin
From: Jean Delvare [ Upstream commit a814c3597a6b6040e2ef9459748081a6d5b7312d ] Before accessing DMI data to record it for later, we should ensure that the DMI structures are large enough to contain the data in question. Signed-off-by: Jean Delvare

[PATCH AUTOSEL for 4.4 046/162] Btrfs: skip commit transaction if we don't have enough pinned bytes

2018-04-08 Thread Sasha Levin
From: Liu Bo [ Upstream commit 28785f70ef882e4798cd5706066a55dbf7adf80e ] We commit transaction in order to reclaim space from pinned bytes because it could process delayed refs, and in may_commit_transaction(), we check first if pinned bytes are enough for the required

[PATCH AUTOSEL for 4.4 044/162] ip_tunnel: fix potential issue in ip_tunnel_rcv

2018-04-08 Thread Sasha Levin
From: Haishuang Yan [ Upstream commit 469f87e158628fe66dcbbce9dd5e7b7acfe934a9 ] When ip_tunnel_rcv fails, the tun_dst won't be freed, so call dst_release to free it in error code path. Fixes: 2e15ea390e6f ("ip_gre: Add support to collect tunnel metadata.")

[PATCH AUTOSEL for 4.4 042/162] drm/mgag200: Fix to always set HiPri for G200e4 V2

2018-04-08 Thread Sasha Levin
From: Mathieu Larouche [ Upstream commit 0cbb738108927916a659b5b0b96e386fcd7cc6e1 ] - Changed the HiPri value for G200e4 to always be 0. - Added Bandwith limitation to block resolution above 1920x1200x60Hz Signed-off-by: Mathieu Larouche

[PATCH AUTOSEL for 4.4 034/162] ixgbe: avoid permanent lock of *_PTP_TX_IN_PROGRESS

2018-04-08 Thread Sasha Levin
From: Jacob Keller [ Upstream commit 5fef124d9c75942dc5c2445a3faa8ad37cbf4c82 ] The ixgbe driver uses a state bit lock to avoid handling more than one Tx timestamp request at once. This is required because hardware is limited to a single set of registers for Tx

[PATCH AUTOSEL for 4.4 043/162] r8152: add byte_enable for ocp_read_word function

2018-04-08 Thread Sasha Levin
From: hayeswang [ Upstream commit d8fbd27469fc02049c674de296a3263bef089131 ] Add byte_enable for ocp_read_word() to replace reading 4 bytes data with reading the desired 2 bytes data. This is used to avoid the issue which is described in commit b4d99def0938 ("r8152:

[PATCH AUTOSEL for 4.4 037/162] net_sched: move tcf_lock down after gen_replace_estimator()

2018-04-08 Thread Sasha Levin
From: WANG Cong [ Upstream commit 74030603dfd9f76c0f279f19f1dd1ee3028fee7a ] Laura reported a sleep-in-atomic kernel warning inside tcf_act_police_init() which calls gen_replace_estimator() with spinlock protection. It is not necessary in this case, we already have

[PATCH AUTOSEL for 4.4 038/162] PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()

2018-04-08 Thread Sasha Levin
From: Christoph Hellwig [ Upstream commit b014e96d1abbd67404bbe2018937b46466299e9e ] Every method in struct device_driver or structures derived from it like struct pci_driver MUST provide exclusion vs the driver's ->remove() method, usually by using device_lock(). Protect use of

Re: [alsa-devel] [PATCH] ASoC: fsl_esai: Add freq check in set_dai_sysclk()

2018-04-08 Thread Fabio Estevam
On Sun, Apr 8, 2018 at 9:33 PM, Nicolin Chen wrote: > The freq parameter indicates the physical frequency of an actual > input clock or a desired frequency of an output clock for HCKT/R. > It should never be passed 0. This might cause Division-by-zero. > > So this patch

[PATCH AUTOSEL for 4.4 036/162] x86/mce: Don't disable MCA banks when offlining a CPU on AMD

2018-04-08 Thread Sasha Levin
From: Yazen Ghannam [ Upstream commit ec33838244c8535b23b8d24b167996fd1318bb68 ] AMD systems have non-core, shared MCA banks within a die. These banks are controlled by a master CPU per die. If this CPU is offlined then all the shared banks are disabled in addition to the

[PATCH AUTOSEL for 4.4 039/162] firmware: dmi_scan: Look for SMBIOS 3 entry point first

2018-04-08 Thread Sasha Levin
From: Jean Delvare [ Upstream commit c9aba14362a6eec583819ec8f4b872c1816f5cbe ] Since version 3.0.0 of the SMBIOS specification, there can be multiple entry points in memory, pointing to one or two DMI tables. If both a 32-bit ("_SM_") entry point and a 64-bit ("_SM3_") entry

[PATCH AUTOSEL for 4.4 031/162] platform/x86: acer-wmi: Detect RF Button capability

2018-04-08 Thread Sasha Levin
From: João Paulo Rechi Vita [ Upstream commit 3e2bc5c5b3274ec7402fabbfba557ea58084985e ] If a machine reports a RF Button in the communication button device bitmap, we need to remove it before calling Get Device Status otherwise it will return the "Undefined device" (0xE2)

[PATCH AUTOSEL for 4.4 035/162] ixgbe: pci_set_drvdata must be called before register_netdev

2018-04-08 Thread Sasha Levin
From: Jeff Mahoney [ Upstream commit a09c0fc3f5d775231f1884e0e66c495065a461ee ] We call pci_set_drvdata immediately after calling register_netdev, which leaves a window where tasks writing to the sriov_numvfs sysfs attribute can sneak in and crash the kernel. register_netdev

[PATCH AUTOSEL for 4.4 033/162] caif: Add sockaddr length check before accessing sa_family in connect handler

2018-04-08 Thread Sasha Levin
From: Mateusz Jurczyk [ Upstream commit 20a3d5bf5e5b13c02450ab6178ec374abd830686 ] Verify that the caller-provided sockaddr structure is large enough to contain the sa_family field, before accessing it in the connect() handler of the AF_CAIF socket. Since the syscall

[PATCH AUTOSEL for 4.4 032/162] leds: bcm6328: fix signal source assignment for leds 4 to 7

2018-04-08 Thread Sasha Levin
From: Jonas Gorski [ Upstream commit 4f02b50ece11dcf75263fb7a4cfe8a5df1cfabea ] Each nibble represents 4 LEDs, and in case of the higher register, bit 0 represents LED 4, so we need to use modulus for the LED number as well. Fixes:

[PATCH] Revert "ata: ahci-platform: add reset control support"

2018-04-08 Thread Kunihiko Hayashi
This reverts commit f0f56716fc3e5d547fd7811eb218a30ed0695605. According to Thierry's view, https://www.spinics.net/lists/linux-ide/msg55357.html some hardware-specific drivers already use their own resets, and the common reset might make a path to occur double controls of resets. For now, revert

[PATCH AUTOSEL for 4.4 028/162] PCI: Correct PCI_STD_RESOURCE_END usage

2018-04-08 Thread Sasha Levin
From: Bjorn Helgaas [ Upstream commit 2f686f1d9beee135de6d08caea707ec7bfc916d4 ] PCI_STD_RESOURCE_END is (confusingly) the index of the last valid BAR, not the *number* of BARs. To iterate through all possible BARs, we need to include PCI_STD_RESOURCE_END. Fixes:

[PATCH AUTOSEL for 4.9 290/293] locking/qspinlock: Ensure node->count is updated before initialising node

2018-04-08 Thread Sasha Levin
From: Will Deacon [ Upstream commit 11dc13224c975efcec96647a4768a6f1bb7a19a8 ] When queuing on the qspinlock, the count field for the current CPU's head node is incremented. This needn't be atomic because locking in e.g. IRQ context is balanced and so an IRQ will return

Re: [alsa-devel] [PATCH] ASoC: fsl_esai: Fix divisor calculation failure at lower ratio

2018-04-08 Thread Fabio Estevam
Hi Nicolin, On Sun, Apr 8, 2018 at 8:57 PM, Nicolin Chen wrote: > When the desired ratio is less than 256, the savesub (tolerance) > in the calculation would become 0. This will then fail the loop- > search immediately without reporting any errors. > > But if the ratio is

[PATCH AUTOSEL for 4.4 026/162] usb: usbip tool: Check the return of get_nports()

2018-04-08 Thread Sasha Levin
From: Yuyang Du [ Upstream commit c3509715fc9484a48b69a9f0196b728c960840c9 ] If we get nonpositive number of ports, there is no sense to continue, then fail gracefully. In addition, the commit 0775a9cbc694e8c72 ("usbip: vhci extension: modifications to vhci driver")

[PATCH AUTOSEL for 4.4 001/162] ALSA: timer: Wrap with spinlock for queue access

2018-04-08 Thread Sasha Levin
From: Takashi Iwai [ Upstream commit d7f910bfedd863d13ea320030fe98e42d0938ed5 ] For accessing the snd_timer_user queue indices, we take tu->qlock. But it's forgotten in a couple of places. The one in snd_timer_user_params() should be safe without the spinlock as the timer is

[PATCH AUTOSEL for 4.4 027/162] usb: usbip tool: Fix refresh_imported_device_list()

2018-04-08 Thread Sasha Levin
From: Yuyang Du [ Upstream commit fd92b7deb98a4edd31ffcc2d64cee36103805ff5 ] The commit 0775a9cbc694e8c7 ("usbip: vhci extension: modifications to vhci driver") introduced multiple controllers, but the status of the ports are only extracted from the first status file, fix

[PATCH AUTOSEL for 4.4 024/162] scsi: megaraid: Fix a sleep-in-atomic bug

2018-04-08 Thread Sasha Levin
From: Jia-Ju Bai [ Upstream commit 896f6966fc815abe71f85fb26f0193875df8a035 ] The driver may sleep under a spin lock, and the function call path is: mraid_mm_attach_buf (acquire the lock by spin_lock_irqsave) pci_pool_alloc(GFP_KERNEL) --> may sleep To fix it, the

[PATCH AUTOSEL for 4.4 025/162] scsi: lpfc: Fix return value of board_mode store routine in case of online failure

2018-04-08 Thread Sasha Levin
From: James Smart [ Upstream commit 522dceeb62ded1a7b538d2f1f61cc69a1402537d ] On hbacmd reset failure, observing wrong string "nline" in kernel log. On failure, non negative value (1) is returned from sysfs store routine. It is interpreted as count by kernel and store

[PATCH AUTOSEL for 4.4 022/162] vxlan: dont migrate permanent fdb entries during learn

2018-04-08 Thread Sasha Levin
From: Roopa Prabhu [ Upstream commit e0090a9e979de5202c7d16c635dea2f005221073 ] This patch fixes vxlan_snoop to not move permanent fdb entries on learn events. This is consistent with the bridge fdb handling of permanent entries. Fixes: 26a41ae60438 ("vxlan: only

[PATCH AUTOSEL for 4.4 021/162] s390/dasd: fix hanging safe offline

2018-04-08 Thread Sasha Levin
From: Stefan Haberland [ Upstream commit e8ac01555d9e464249e8bb122337d6d6e5589ccc ] The safe offline processing may hang forever because it waits for I/O which can not be started because of the offline flag that prevents new I/O from being started. Allow I/O to be

[PATCH AUTOSEL for 4.4 020/162] s390/dasd: Display read-only attribute correctly

2018-04-08 Thread Sasha Levin
From: Jan Höppner [ Upstream commit b487a914f853545842a0899329b6b72fe56c4081 ] We have two flags, DASD_FLAG_DEVICE_RO and DASD_FEATURE_READONLY, that tell us whether a device is read-only. DASD_FLAG_DEVICE_RO is set when a device is attached as read-only to z/VM and

[PATCH AUTOSEL for 4.4 017/162] cpuidle: dt: Add missing 'of_node_put()'

2018-04-08 Thread Sasha Levin
From: Christophe Jaillet [ Upstream commit b2cdd8e1b54849477a32d820acc2e87828a38f3d ] 'of_node_put()' should be called on pointer returned by 'of_parse_phandle()' when done. In this function this is done in all path except this 'continue', so add it. Fixes:

[PATCH AUTOSEL for 4.4 016/162] Bluetooth: Send HCI Set Event Mask Page 2 command only when needed

2018-04-08 Thread Sasha Levin
From: Marcel Holtmann [ Upstream commit 313f6888c8fbb1bc8b36c9012ce4e1de848df696 ] The Broadcom BCM20702 Bluetooth controller in ThinkPad-T530 devices report support for the Set Event Mask Page 2 command, but actually do return an error when trying to use it. < HCI

[PATCH AUTOSEL for 4.9 292/293] cpumask: Make for_each_cpu_wrap() available on UP as well

2018-04-08 Thread Sasha Levin
From: Michael Kelley [ Upstream commit d207af2eab3f8668b95ad02b21930481c42806fd ] for_each_cpu_wrap() was originally added in the #else half of a large "#if NR_CPUS == 1" statement, but was omitted in the #if half. This patch adds the missing #if half to prevent compile

[PATCH AUTOSEL for 4.4 019/162] ACPICA: Disassembler: Abort on an invalid/unknown AML opcode

2018-04-08 Thread Sasha Levin
From: Bob Moore [ Upstream commit 6f0527b77d9e0129dd8e50945b0d610ed943d6b2 ] ACPICA commit ed0389cb11a61e63c568ac1f67948fc6a7bd1aeb An invalid opcode indicates something seriously wrong with the input AML file. The AML parser is immediately confused and lost, causing

[PATCH AUTOSEL for 4.4 015/162] iio: magnetometer: st_magn_spi: fix spi_device_id table

2018-04-08 Thread Sasha Levin
From: Lorenzo Bianconi [ Upstream commit c83761ff0aac954aa368c623bb0f0d1a3214e834 ] Remove LSM303DLHC, LSM303DLM from st_magn_id_table since LSM303DL series does not support spi interface Fixes: 872e79add756 (iio: magn: Add STMicroelectronics magn driver)

[PATCH AUTOSEL for 4.4 014/162] sparc64: ldc abort during vds iso boot

2018-04-08 Thread Sasha Levin
From: Jag Raman [ Upstream commit 6c95483b768c62f8ee933ae08a1bdbcb78b5410f ] Orabug: 20902628 When an ldc control-only packet is received during data exchange in read_nonraw(), a new rx head is calculated but the rx queue head is not actually advanced (rx_set_head() is

[PATCH AUTOSEL for 4.4 010/162] xen: avoid type warning in xchg_xen_ulong

2018-04-08 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 9cc91f212111cdcbefa02dcdb7dd443f224bf52c ] The improved type-checking version of container_of() triggers a warning for xchg_xen_ulong, pointing out that 'xen_ulong_t' is unsigned, but atomic64_t contains a signed value:

[PATCH AUTOSEL for 4.4 011/162] KEYS: put keyring if install_session_keyring_to_cred() fails

2018-04-08 Thread Sasha Levin
From: Eric Biggers [ Upstream commit d636bd9f12a66ea3775c9fabbf3f8e118253467a ] In join_session_keyring(), if install_session_keyring_to_cred() were to fail, we would leak the keyring reference, just like in the bug fixed by commit 23567fd052a9 ("KEYS: Fix keyring ref leak

[PATCH AUTOSEL for 4.4 012/162] bnx2x: Allow vfs to disable txvlan offload

2018-04-08 Thread Sasha Levin
From: "Mintz, Yuval" [ Upstream commit 92f85f05caa51d844af6ea14ffbc7a786446a644 ] VF clients are configured as enforced, meaning firmware is validating the correctness of their ethertype/vid during transmission. Once txvlan is disabled, VF would start getting SKBs for

[PATCH AUTOSEL for 4.4 006/162] Fix loop device flush before configure v3

2018-04-08 Thread Sasha Levin
From: James Wang [ Upstream commit 6460495709aeb651896bc8e5c134b2e4ca7d34a8 ] While installing SLES-12 (based on v4.4), I found that the installer will stall for 60+ seconds during LVM disk scan. The root cause was determined to be the removal of a bound device check in

[PATCH AUTOSEL for 4.4 009/162] perf tests: Decompress kernel module before objdump

2018-04-08 Thread Sasha Levin
From: Namhyung Kim [ Upstream commit 94df1040b1e6aacd8dec0ba3c61d7e77cd695f26 ] If a kernel modules is compressed, it should be decompressed before running objdump to parse binary data correctly. This fixes a failure of object code reading test for me. Signed-off-by:

[PATCH AUTOSEL for 4.4 013/162] sctp: fix recursive locking warning in sctp_do_peeloff

2018-04-08 Thread Sasha Levin
From: Xin Long [ Upstream commit 6dfe4b97e08ec3d1a593fdaca099f0ef0a3a19e6 ] Dmitry got the following recursive locking report while running syzkaller fuzzer, the Call Trace: __dump_stack lib/dump_stack.c:16 [inline] dump_stack+0x2ee/0x3ef lib/dump_stack.c:52

[PATCH AUTOSEL for 4.9 288/293] bpf: fix rlimit in reuseport net selftest

2018-04-08 Thread Sasha Levin
From: Daniel Borkmann [ Upstream commit 941ff6f11c020913f5cddf543a9ec63475d7c082 ] Fix two issues in the reuseport_bpf selftests that were reported by Linaro CI: [...] + ./reuseport_bpf IPv4 UDP Testing EBPF mod 10... Reprograming, testing mod 5...

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