[PATCH AUTOSEL 4.20 237/304] drbd: narrow rcu_read_lock in drbd_sync_handshake

2019-01-28 Thread Sasha Levin
From: Roland Kammerer [ Upstream commit d29e89e34952a9ad02c77109c71a80043544296e ] So far there was the possibility that we called genlmsg_new(GFP_NOIO)/mutex_lock() while holding an rcu_read_lock(). This included cases like: drbd_sync_handshake (acquire the RCU lock) drbd_asb_recover_1p

[PATCH AUTOSEL 4.20 245/304] md: fix raid10 hang issue caused by barrier

2019-01-28 Thread Sasha Levin
From: Guoqing Jiang [ Upstream commit e820d55cb99dd93ac2dc949cf486bb187e5cd70d ] When both regular IO and resync IO happen at the same time, and if we also need to split regular. Then we can see tasks hang due to barrier. 1. resync thread [ 1463.757205] INFO: task md1_resync:5215 blocked for mo

[PATCH AUTOSEL 4.20 243/304] drm/amd/display: validate extended dongle caps

2019-01-28 Thread Sasha Levin
From: Wenjing Liu [ Upstream commit 99b922f9ed6a6313c0d2247cde8aa1e4a0bd67e4 ] [why] Some dongle doesn't have a valid extended dongle caps, but we still set the extended dongle caps to be valid. This causes validation fails for all timing. [how] If no dp_hdmi_max_pixel_clk is provided, don't us

[PATCH AUTOSEL 4.20 244/304] video: clps711x-fb: release disp device node in probe()

2019-01-28 Thread Sasha Levin
From: Alexey Khoroshilov [ Upstream commit fdac751355cd76e049f628afe6acb8ff4b1399f7 ] clps711x_fb_probe() increments refcnt of disp device node by of_parse_phandle() and leaves it undecremented on both successful and error paths. Found by Linux Driver Verification project (linuxtesting.org). S

[PATCH AUTOSEL 4.20 252/304] bpf: sk_msg, zap ingress queue on psock down

2019-01-28 Thread Sasha Levin
From: John Fastabend [ Upstream commit a136678c0bdbb650daff5df5eec1dab960e074a7 ] In addition to releasing any cork'ed data on a psock when the psock is removed we should also release any skb's in the ingress work queue. Otherwise the skb's eventually get free'd but late in the tear down process

[PATCH AUTOSEL 4.20 251/304] fbdev: fbcon: Fix unregister crash when more than one framebuffer

2019-01-28 Thread Sasha Levin
From: Noralf Trønnes [ Upstream commit 2122b40580dd9d0620398739c773d07a7b7939d0 ] When unregistering fbdev using unregister_framebuffer(), any bound console will unbind automatically. This is working fine if this is the only framebuffer, resulting in a switch to the dummy console. However if the

[PATCH AUTOSEL 4.20 257/304] KVM: x86: svm: report MSR_IA32_MCG_EXT_CTL as unsupported

2019-01-28 Thread Sasha Levin
From: Vitaly Kuznetsov [ Upstream commit e87555e550cef4941579cd879759a7c0dee24e68 ] AMD doesn't seem to implement MSR_IA32_MCG_EXT_CTL and svm code in kvm knows nothing about it, however, this MSR is among emulated_msrs and thus returned with KVM_GET_MSR_INDEX_LIST. The consequent KVM_GET_MSRS,

[PATCH AUTOSEL 4.20 248/304] ice: Do not enable NAPI on q_vectors that have no rings

2019-01-28 Thread Sasha Levin
From: Young Xiao [ Upstream commit eec903769b4ea47659173bb7359f14f38c51 ] If ice driver has q_vectors w/ active NAPI that has no rings, then this will result in a divide by zero error. To correct it I am updating the driver code so that we only support NAPI on q_vectors that have 1 or more r

[PATCH AUTOSEL 4.20 254/304] bpf: sk_msg, fix socket data_ready events

2019-01-28 Thread Sasha Levin
From: John Fastabend [ Upstream commit 552de91068828daef50a227a665068cf8dde835e ] When a skb verdict program is in-use and either another BPF program redirects to that socket or the new SK_PASS support is used the data_ready callback does not wake up application. Instead because the stream parse

[PATCH AUTOSEL 4.20 250/304] ACPI/APEI: Clear GHES block_status before panic()

2019-01-28 Thread Sasha Levin
From: Lenny Szubowicz [ Upstream commit 98cff8b23ed1c763a029ee81ea300df0d153d07d ] In __ghes_panic() clear the block status in the APEI generic error status block for that generic hardware error source before calling panic() to prevent a second panic() in the crash kernel for exactly the same fa

[PATCH AUTOSEL 4.20 256/304] pinctrl: meson: meson8b: fix the GPIO function for the GPIOAO pins

2019-01-28 Thread Sasha Levin
From: Martin Blumenstingl [ Upstream commit 2b745ac3cceb8fc1d9985990c8241a821ea97e53 ] The GPIOAO pins (as well as the two exotic GPIO_BSD_EN and GPIO_TEST_N) only belong to the pin controller in the AO domain. With the current definition these pins cannot be referred to in .dts files as group (

[PATCH AUTOSEL 4.20 258/304] powerpc/fadump: Do not allow hot-remove memory from fadump reserved area.

2019-01-28 Thread Sasha Levin
From: Mahesh Salgaonkar [ Upstream commit 0db6896ff6332ba694f1e61b93ae3b2640317633 ] For fadump to work successfully there should not be any holes in reserved memory ranges where kernel has asked firmware to move the content of old kernel memory in event of crash. Now that fadump uses CMA for re

[PATCH AUTOSEL 4.20 270/304] f2fs: fix use-after-free issue when accessing sbi->stat_info

2019-01-28 Thread Sasha Levin
From: Sahitya Tummala [ Upstream commit 60aa4d5536ab7fe32433ca1173bd9d6633851f27 ] iput() on sbi->node_inode can update sbi->stat_info in the below context, if the f2fs_write_checkpoint() has failed with error. f2fs_balance_fs_bg+0x1ac/0x1ec f2fs_write_node_pages+0x4c/0x260 do_writepages+0x80/0

[PATCH AUTOSEL 4.20 260/304] kvm: Change offset in kvm_write_guest_offset_cached to unsigned

2019-01-28 Thread Sasha Levin
From: Jim Mattson [ Upstream commit 7a86dab8cf2f0fdf508f3555dddfc236623bff60 ] Since the offset is added directly to the hva from the gfn_to_hva_cache, a negative offset could result in an out of bounds write. The existing BUG_ON only checks for addresses beyond the end of the gfn_to_hva_cache,

[PATCH AUTOSEL 4.20 261/304] NFS: nfs_compare_mount_options always compare auth flavors.

2019-01-28 Thread Sasha Levin
From: Chris Perl [ Upstream commit 594d1644cd59447f4fceb592448d5cd09eb09b5e ] This patch removes the check from nfs_compare_mount_options to see if a `sec' option was passed for the current mount before comparing auth flavors and instead just always compares auth flavors. Consider the following

[PATCH AUTOSEL 4.20 266/304] crypto: ux500 - Use proper enum in cryp_set_dma_transfer

2019-01-28 Thread Sasha Levin
From: Nathan Chancellor [ Upstream commit 9d880c5945c748d8edcac30965f3349a602158c4 ] Clang warns when one enumerated type is implicitly converted to another: drivers/crypto/ux500/cryp/cryp_core.c:559:5: warning: implicit conversion from enumeration type 'enum dma_data_direction' to different en

[PATCH AUTOSEL 4.20 263/304] hwmon: (lm80) fix a missing check of the status of SMBus read

2019-01-28 Thread Sasha Levin
From: Kangjie Lu [ Upstream commit c9c63915519b1def7043b184680f33c24cd49d7b ] If lm80_read_value() fails, it returns a negative number instead of the correct read data. Therefore, we should avoid using the data if it fails. The fix checks if lm80_read_value() fails, and if so, returns with the

[PATCH AUTOSEL 4.20 259/304] selftests: kvm: report failed stage when exit reason is unexpected

2019-01-28 Thread Sasha Levin
From: Vitaly Kuznetsov [ Upstream commit b85c32dd27495075380350fcd5d614a6b45311b8 ] When we get a report like Test Assertion Failure x86_64/state_test.c:157: run->exit_reason == KVM_EXIT_IO pid=955 tid=955 - Success 1 0x00401350: main at state_test.c:154 2 0x00

[PATCH AUTOSEL 4.20 272/304] niu: fix missing checks of niu_pci_eeprom_read

2019-01-28 Thread Sasha Levin
From: Kangjie Lu [ Upstream commit 26fd962bde0b15e54234fe762d86bc0349df1de4 ] niu_pci_eeprom_read() may fail, so we should check its return value before using the read data. Signed-off-by: Kangjie Lu Acked-by: Shannon Nelson Signed-off-by: David S. Miller Signed-off-by: Sasha Levin --- dri

[PATCH AUTOSEL 4.20 265/304] seq_buf: Make seq_buf_puts() null-terminate the buffer

2019-01-28 Thread Sasha Levin
From: Michael Ellerman [ Upstream commit 0464ed24380905d640030d368cd84a4e4d1e15e2 ] Currently seq_buf_puts() will happily create a non null-terminated string for you in the buffer. This is particularly dangerous if the buffer is on the stack. For example: char buf[8]; char secret = "secret

[PATCH AUTOSEL 4.20 269/304] cifs: check ntwrk_buf_start for NULL before dereferencing it

2019-01-28 Thread Sasha Levin
From: Ronnie Sahlberg [ Upstream commit 59a63e479ce36a3f2c3a36efe82b78e4a8e0 ] RHBZ: 1021460 There is an issue where when multiple threads open/close the same directory ntwrk_buf_start might end up being NULL, causing the call to smbCalcSize later to oops with a NULL deref. The real bug is

[PATCH AUTOSEL 4.20 276/304] scripts/decode_stacktrace: only strip base path when a prefix of the path

2019-01-28 Thread Sasha Levin
From: Marc Zyngier [ Upstream commit 67a28de47faa83585dd644bd4c31e5a1d9346c50 ] Running something like: decodecode vmlinux . leads to interested results where not only the leading "." gets stripped from the displayed paths, but also anywhere in the string, displaying something like:

[PATCH AUTOSEL 4.20 275/304] perf python: Do not force closing original perf descriptor in evlist.get_pollfd()

2019-01-28 Thread Sasha Levin
From: Jiri Olsa [ Upstream commit a389aece97938966616ce0336466b98b0351ef10 ] Ondřej reported that when compiled with python3, the python extension regresses in evlist.get_pollfd function behaviour. The evlist.get_pollfd function creates file objects from evlist's fds and returns them in a list.

[PATCH AUTOSEL 4.20 273/304] f2fs: fix sbi->extent_list corruption issue

2019-01-28 Thread Sasha Levin
From: Sahitya Tummala [ Upstream commit e4589fa545e0020dbbc3c9bde35f35f949901392 ] When there is a failure in f2fs_fill_super() after/during the recovery of fsync'd nodes, it frees the current sbi and retries again. This time the mount is successful, but the files that got recovered before retry

[PATCH AUTOSEL 4.20 279/304] ocfs2: don't clear bh uptodate for block read

2019-01-28 Thread Sasha Levin
From: Junxiao Bi [ Upstream commit 70306d9dce75abde855cefaf32b3f71eed8602a3 ] For sync io read in ocfs2_read_blocks_sync(), first clear bh uptodate flag and submit the io, second wait io done, last check whether bh uptodate, if not return io error. If two sync io for the same bh were issued, it

[PATCH AUTOSEL 4.20 277/304] arch/sh/boards/mach-kfr2r09/setup.c: fix struct mtd_oob_ops build warning

2019-01-28 Thread Sasha Levin
From: Randy Dunlap [ Upstream commit 440e7b379f91acd245d5c8de94d533f40f5dffb3 ] arch/sh/boards/mach-kfr2r09/setup.c does not need to #include , and doing so causes a build warning, so drop that header file. In file included from ../arch/sh/boards/mach-kfr2r09/setup.c:28: ../include/linux/mtd/on

[PATCH AUTOSEL 4.20 280/304] ocfs2: improve ocfs2 Makefile

2019-01-28 Thread Sasha Levin
From: Larry Chen [ Upstream commit 9e6aea22802b5684c7e1d69822aeb0844dd01953 ] Included file path was hard-wired in the ocfs2 makefile, which might causes some confusion when compiling ocfs2 as an external module. Say if we compile ocfs2 module as following. cp -r /kernel/tree/fs/ocfs2 /other/di

[PATCH AUTOSEL 4.20 284/304] gdrom: fix a memory leak bug

2019-01-28 Thread Sasha Levin
From: Wenwen Wang [ Upstream commit 093c48213ee37c3c3ff1cf5ac1aa2a9d8bc66017 ] In probe_gdrom(), the buffer pointed by 'gd.cd_info' is allocated through kzalloc() and is used to hold the information of the gdrom device. To register and unregister the device, the pointer 'gd.cd_info' is passed to

Re: [PATCH] block: set rq->cmd_flags with bio->opf instead of data->cmd_flags when bio is not Null

2019-01-28 Thread Christoph Hellwig
On Mon, Jan 28, 2019 at 03:36:58PM +, John Garry wrote: > As I understood, the problem is the scenario of calling > blk_mq_make_request()->bio_integrity_prep() where we then allocate a bio > integrity payload in calling bio_integrity_alloc(). > > In this case, bio_integrity_alloc() sets bio->b

[PATCH AUTOSEL 4.20 287/304] thermal: bcm2835: enable hwmon explicitly

2019-01-28 Thread Sasha Levin
From: Matthias Brugger [ Upstream commit d56c19d07e0bc3ceff366a49b7d7a2440c967b1b ] By defaul of-based thermal driver do not enable hwmon. This patch does this explicitly, so that the temperature can be read through the common hwmon sysfs. Signed-off-by: Matthias Brugger Acked-by: Stefan Wahre

[PATCH AUTOSEL 4.20 282/304] zram: fix lockdep warning of free block handling

2019-01-28 Thread Sasha Levin
From: Minchan Kim [ Upstream commit 3c9959e025472122a61faebb208525cf26b305d1 ] Patch series "zram idle page writeback", v3. Inherently, swap device has many idle pages which are rare touched since it was allocated. It is never problem if we use storage device as swap. However, it's just waste

[PATCH AUTOSEL 4.20 285/304] fsl/fman: Use GFP_ATOMIC in {memac,tgec}_add_hash_mac_address()

2019-01-28 Thread Sasha Levin
From: Scott Wood [ Upstream commit 0d9c9a238faf925823bde866182c663b6d734f2e ] These functions are called from atomic context: [9.150239] BUG: sleeping function called from invalid context at /home/scott/git/linux/mm/slab.h:421 [9.158159] in_atomic(): 1, irqs_disabled(): 0, pid: 4432, n

[PATCH AUTOSEL 4.20 281/304] mm/page_alloc.c: don't call kasan_free_pages() at deferred mem init

2019-01-28 Thread Sasha Levin
From: Waiman Long [ Upstream commit 3c0c12cc8f00ca5f81acb010023b8eb13e9a7004 ] When CONFIG_KASAN is enabled on large memory SMP systems, the deferrred pages initialization can take a long time. Below were the reported init times on a 8-socket 96-core 4TB IvyBridge system. 1) Non-debug kernel

[PATCH AUTOSEL 4.20 288/304] kdb: Don't back trace on a cpu that didn't round up

2019-01-28 Thread Sasha Levin
From: Douglas Anderson [ Upstream commit 162bc7f5afd75b72acbe3c5f3488ef7e64a3fe36 ] If you have a CPU that fails to round up and then run 'btc' you'll end up crashing in kdb becaue we dereferenced NULL. Let's add a check. It's wise to also set the task to NULL when leaving the debugger so that

[PATCH AUTOSEL 4.20 294/304] HID: lenovo: Add checks to fix of_led_classdev_register

2019-01-28 Thread Sasha Levin
From: Aditya Pakki [ Upstream commit 6ae16dfb61bce538d48b7fe98160fada446056c5 ] In lenovo_probe_tpkbd(), the function of_led_classdev_register() could return an error value that is unchecked. The fix adds these checks. Signed-off-by: Aditya Pakki Signed-off-by: Jiri Kosina Signed-off-by: Sash

[PATCH AUTOSEL 4.20 297/304] kernel/hung_task.c: break RCU locks based on jiffies

2019-01-28 Thread Sasha Levin
From: Tetsuo Handa [ Upstream commit 304ae42739b108305f8d7b3eb3c1aec7c2b643a9 ] check_hung_uninterruptible_tasks() is currently calling rcu_lock_break() for every 1024 threads. But check_hung_task() is very slow if printk() was called, and is very fast otherwise. If many threads within some 10

[PATCH AUTOSEL 4.20 291/304] block/swim3: Fix regression on PowerBook G3

2019-01-28 Thread Sasha Levin
From: Finn Thain [ Upstream commit 427c5ce4417cba0801fbf79c8525d1330704759c ] As of v4.20, the swim3 driver crashes when loaded on a PowerBook G3 (Wallstreet). MacIO PCI driver attached to Gatwick chipset MacIO PCI driver attached to Heathrow chipset swim3 0.00015000:floppy: [fd0] SWIM3 floppy

[PATCH AUTOSEL 4.20 292/304] thermal: generic-adc: Fix adc to temp interpolation

2019-01-28 Thread Sasha Levin
From: Bjorn Andersson [ Upstream commit 9d216211fded20fff301d0317af3238d8383634c ] First correct the edge case to return the last element if we're outside the range, rather than at the last element, so that interpolation is not omitted for points between the two last entries in the table. Then

[PATCH AUTOSEL 4.20 298/304] proc/sysctl: fix return error for proc_doulongvec_minmax()

2019-01-28 Thread Sasha Levin
From: Cheng Lin [ Upstream commit 09be178400829dddc1189b50a7888495dd26aa84 ] If the number of input parameters is less than the total parameters, an EINVAL error will be returned. For example, we use proc_doulongvec_minmax to pass up to two parameters with kern_table: { .procname

[PATCH AUTOSEL 4.20 296/304] fs/proc/base.c: use ns_capable instead of capable for timerslack_ns

2019-01-28 Thread Sasha Levin
From: Benjamin Gordon [ Upstream commit 8da0b4f692c6d90b09c91f271517db746a22ff67 ] Access to timerslack_ns is controlled by a process having CAP_SYS_NICE in its effective capability set, but the current check looks in the root namespace instead of the process' user namespace. Since a process is

[PATCH AUTOSEL 4.20 301/304] exec: load_script: don't blindly truncate shebang string

2019-01-28 Thread Sasha Levin
From: Oleg Nesterov [ Upstream commit 8099b047ecc431518b9bb6bdbba3549bbecdc343 ] load_script() simply truncates bprm->buf and this is very wrong if the length of shebang string exceeds BINPRM_BUF_SIZE-2. This can silently truncate i_arg or (worse) we can execute the wrong binary if buf[2:126] h

[PATCH AUTOSEL 4.20 299/304] kernel/hung_task.c: force console verbose before panic

2019-01-28 Thread Sasha Levin
From: "Liu, Chuansheng" [ Upstream commit 168e06f7937d96c7222037d8a05565e8a6eb00fe ] Based on commit 401c636a0eeb ("kernel/hung_task.c: show all hung tasks before panic"), we could get the call stack of hung task. However, if the console loglevel is not high, we still can not see the useful pan

[PATCH AUTOSEL 4.20 303/304] scripts/gdb: fix lx-version string output

2019-01-28 Thread Sasha Levin
From: Du Changbin [ Upstream commit b058809bfc8faeb7b7cae047666e23375a060059 ] A bug is present in GDB which causes early string termination when parsing variables. This has been reported [0], but we should ensure that we can support at least basic printing of the core kernel strings. For curr

[PATCH AUTOSEL 4.20 302/304] kernel/kcov.c: mark write_comp_data() as notrace

2019-01-28 Thread Sasha Levin
From: Anders Roxell [ Upstream commit 634724431607f6f46c495dfef801a1c8b44a96d9 ] Since __sanitizer_cov_trace_const_cmp4 is marked as notrace, the function called from __sanitizer_cov_trace_const_cmp4 shouldn't be traceable either. ftrace_graph_caller() gets called every time func write_comp_dat

[PATCH AUTOSEL 4.20 304/304] xprtrdma: Don't wake pending tasks until disconnect is done

2019-01-28 Thread Sasha Levin
From: Chuck Lever [ Upstream commit 0c0829bcf51aef713806e49b8ea2bac7962f54e2 ] Transport disconnect processing does a "wake pending tasks" at various points. Suppose an RPC Reply is being processed. The RPC task that Reply goes with is waiting on the pending queue. If a disconnect wake-up happe

[PATCH AUTOSEL 4.19 002/258] staging: iio: adc: ad7280a: handle error from __ad7280_read32()

2019-01-28 Thread Sasha Levin
From: Slawomir Stepien [ Upstream commit 0559ef7fde67bc6c83c6eb6329dbd6649528263e ] Inside __ad7280_read32(), the spi_sync_transfer() can fail with negative error code. This change will ensure that this error is being passed up in the call stack, so it can be handled. Signed-off-by: Slawomir St

[PATCH AUTOSEL 4.19 003/258] drm/vgem: Fix vgem_init to get drm device available.

2019-01-28 Thread Sasha Levin
From: Deepak Sharma [ Upstream commit d5c04dff24870ef07ce6453a3f4e1ffd9cf88d27 ] Modify vgem_init to take platform dev as parent in drm_dev_init. This will make drm device available at "/sys/devices/platform/vgem" in x86 chromebook. v2: rebase, address checkpatch typo and line over 80 character

[PATCH AUTOSEL 4.19 004/258] pinctrl: bcm2835: Use raw spinlock for RT compatibility

2019-01-28 Thread Sasha Levin
From: Lukas Wunner [ Upstream commit 3c7b30f704b6f5e53eed6bf89cf2c8d1b38b02c0 ] The BCM2835 pinctrl driver acquires a spinlock in its ->irq_enable, ->irq_disable and ->irq_set_type callbacks. Spinlocks become sleeping locks with CONFIG_PREEMPT_RT_FULL=y, therefore invocation of one of the callb

[PATCH AUTOSEL 4.19 006/258] gpiolib: Fix possible use after free on label

2019-01-28 Thread Sasha Levin
From: Muchun Song [ Upstream commit 18534df419041e6c1f4b41af56ee7d41f757815c ] gpiod_request_commit() copies the pointer to the label passed as an argument only to be used later. But there's a chance the caller could immediately free the passed string(e.g., local variable). This could trigger a

[PATCH AUTOSEL 4.19 010/258] nds32: Fix gcc 8.0 compiler option incompatible.

2019-01-28 Thread Sasha Levin
From: Nickhu [ Upstream commit 4c3d6174e0e17599549f636ec48ddf78627a17fe ] When the kernel configs of ftrace and frame pointer options are choosed, the compiler option of kernel will incompatible. Error message: nds32le-linux-gcc: error: -pg and -fomit-frame-pointer are i

[PATCH AUTOSEL 4.19 009/258] gpu: ipu-v3: image-convert: Prevent race between run and unprepare

2019-01-28 Thread Sasha Levin
From: Steve Longerbeam [ Upstream commit 819bec35c8c9706185498c9222bd244e0781ad35 ] Prevent possible race by parallel threads between ipu_image_convert_run() and ipu_image_convert_unprepare(). This involves setting ctx->aborting to true unconditionally so that no new job runs can be queued durin

Re: [PATCH 2/2] mm: Consider subtrees in memory.events

2019-01-28 Thread Shakeel Butt
Hi Tejun, On Fri, Jan 25, 2019 at 10:28 AM Tejun Heo wrote: > > Hello, Michal. > > On Fri, Jan 25, 2019 at 06:37:13PM +0100, Michal Hocko wrote: > > > What if a user wants to monitor any ooms in the subtree tho, which is > > > a valid use case? > > > > How is that information useful without know

[PATCH AUTOSEL 4.19 019/258] ARM: 8808/1: kexec:offline panic_smp_self_stop CPU

2019-01-28 Thread Sasha Levin
From: Yufen Wang [ Upstream commit 82c08c3e7f171aa7f579b231d0abbc1d62e91974 ] In case panic() and panic() called at the same time on different CPUS. For example: CPU 0: panic() __crash_kexec machine_crash_shutdown crash_smp_send_stop machine_kexec BUG_ON(nu

[PATCH AUTOSEL 4.19 014/258] ath9k: dynack: use authentication messages for 'late' ack

2019-01-28 Thread Sasha Levin
From: Lorenzo Bianconi [ Upstream commit 3831a2a0010c72e3956020cbf1057a1701a2e469 ] In order to properly support dynack in ad-hoc mode running wpa_supplicant, take into account authentication frames for 'late ack' detection. This patch has been tested on devices mounted on offshore high-voltage

[PATCH AUTOSEL 4.19 015/258] scsi: lpfc: Correct LCB RJT handling

2019-01-28 Thread Sasha Levin
From: James Smart [ Upstream commit b114d9009d386276bfc3352289fc235781ae3353 ] When LCB's are rejected, if beaconing was already in progress, the Reason Code Explanation was not being set. Should have been set to command in progress. Signed-off-by: Dick Kennedy Signed-off-by: James Smart Revi

[PATCH AUTOSEL 4.19 021/258] dlm: Don't swamp the CPU with callbacks queued during recovery

2019-01-28 Thread Sasha Levin
From: Bob Peterson [ Upstream commit 216f0efd19b9cc32207934fd1b87a45f2c4c593e ] Before this patch, recovery would cause all callbacks to be delayed, put on a queue, and afterward they were all queued to the callback work queue. This patch does the same thing, but occasionally takes a break after

Re: [PATCH v3 4/8] dt-bindings: Add vendor prefix for LeMaker

2019-01-28 Thread Thierry Reding
On Wed, Nov 07, 2018 at 07:18:39PM +0100, Paul Kocialkowski wrote: > This introduces a new device-tree binding vendor prefix for Shenzhen > LeMaker Technology Co., Ltd. > > This vendor was already in use but it was not documented until now. > > Signed-off-by: Paul Kocialkowski > Reviewed-by: Rob

[PATCH AUTOSEL 4.19 011/258] wil6210: fix reset flow for Talyn-mb

2019-01-28 Thread Sasha Levin
From: Alexei Avshalom Lazar [ Upstream commit d083b2e2b7db5cca1791643d036e6597af27f49b ] With current reset flow, Talyn sometimes get stuck causing PCIe enumeration to fail. Fix this by removing some reset flow operations that are not relevant for Talyn. Setting bit 15 in RGF_HP_CTRL is WBE spec

Re: [tip:x86/timers] x86/tsc: Make calibration refinement more robust

2019-01-28 Thread Thomas Gleixner
On Wed, 16 Jan 2019, Daniel Vacek wrote: > On Fri, Jan 11, 2019 at 10:03 PM Thomas Gleixner wrote: > > > > No. The branch was not sent to Linus during the merge window due to holiday > > season induced oversight. > > So does it wait for the next merge window now or is it still going to > be sent

Re: [PATCH v3 5/8] dt-bindings: Add bindings for the LeMaker BL035-RGB-002 LCD panel

2019-01-28 Thread Thierry Reding
On Wed, Nov 07, 2018 at 07:18:40PM +0100, Paul Kocialkowski wrote: > This adds the device-tree bindings for the LeMaker BL035-RGB-002 3.5" > QVGA TFT LCD panel, compatible with simple-panel. > > Signed-off-by: Paul Kocialkowski > --- > .../bindings/display/panel/lemaker,bl035-rgb-002.txt | 12 ++

[PATCH AUTOSEL 4.19 022/258] x86/PCI: Fix Broadcom CNB20LE unintended sign extension (redux)

2019-01-28 Thread Sasha Levin
From: Colin Ian King [ Upstream commit 53bb565fc5439f2c8c57a786feea5946804aa3e9 ] In the expression "word1 << 16", word1 starts as u16, but is promoted to a signed int, then sign-extended to resource_size_t, which is probably not what was intended. Cast to resource_size_t to avoid the sign exte

[PATCH AUTOSEL 4.19 026/258] crypto: aes_ti - disable interrupts while accessing S-box

2019-01-28 Thread Sasha Levin
From: Eric Biggers [ Upstream commit 0a6a40c2a8c184a2fb467efacfb1cd338d719e0b ] In the "aes-fixed-time" AES implementation, disable interrupts while accessing the S-box, in order to make cache-timing attacks more difficult. Previously it was possible for the CPU to be interrupted while the S-bo

[PATCH AUTOSEL 4.19 034/258] sctp: Fix SKB list traversal in sctp_intl_store_reasm().

2019-01-28 Thread Sasha Levin
From: "David S. Miller" [ Upstream commit 348bbc25c40844c5efa083a3842c7f53d70a815e ] To be fully correct, an iterator has an undefined value when something like skb_queue_walk() naturally terminates. This will actually matter when SKB queues are converted over to list_head. Formalize what this

[PATCH AUTOSEL 4.19 035/258] iwlwifi: fw: do not set sgi bits for HE connection

2019-01-28 Thread Sasha Levin
From: Naftali Goldstein [ Upstream commit 5c2dbebb446539eb9640bf59a02756d6e7f1fc53 ] If the association supports HE, HT/VHT rates will never be used for Tx and therefore there's no need to set the sgi-per-channel-width-support bits, so don't set them in this case. Fixes: 110b32f065f3 ("iwlwifi:

[PATCH AUTOSEL 4.19 041/258] platform/chrome: don't report EC_MKBP_EVENT_SENSOR_FIFO as wakeup

2019-01-28 Thread Sasha Levin
From: Brian Norris [ Upstream commit 6ad16b78a039b45294b1ad5d69c14ac57b2fe706 ] EC_MKBP_EVENT_SENSOR_FIFO events can be triggered for a variety of reasons, and there are very few cases in which they should be treated as wakeup interrupts (particularly, when a certain MOTIONSENSE_MODULE_FLAG_* is

[PATCH AUTOSEL 4.19 045/258] usbnet: smsc95xx: fix rx packet alignment

2019-01-28 Thread Sasha Levin
From: Ben Dooks [ Upstream commit 810eeb1f41a9a272eedc94ca18c072e75678ede4 ] The smsc95xx driver already takes into account the NET_IP_ALIGN parameter when setting up the receive packet data, which means we do not need to worry about aligning the packets in the usbnet driver. Adding the EVENT_N

[PATCH AUTOSEL 4.19 047/258] ARM: OMAP2+: hwmod: Fix some section annotations

2019-01-28 Thread Sasha Levin
From: Nathan Chancellor [ Upstream commit c10b26abeb53cabc1e6271a167d3f3d396ce0218 ] When building the kernel with Clang, the following section mismatch warnings appears: WARNING: vmlinux.o(.text+0x2d398): Section mismatch in reference from the function _setup() to the function .init.text:_setu

[PATCH AUTOSEL 4.19 043/258] scsi: hisi_sas: change the time of SAS SSP connection

2019-01-28 Thread Sasha Levin
From: Xiang Chen [ Upstream commit 15bc43f31a074076f114e0b87931e3b220b7bff1 ] Currently the time of SAS SSP connection is 1ms, which means the link connection will fail if no IO response after this period. For some disks handling large IO (such as 512k), 1ms is not enough, so change it to 5ms.

[PATCH AUTOSEL 4.19 037/258] fpga: altera-cvp: Fix registration for CvP incapable devices

2019-01-28 Thread Sasha Levin
From: Andreas Puhm [ Upstream commit 68f60538daa4bc3da5d0764d46f391916fba20fd ] The probe function needs to verify the CvP enable bit in order to properly determine if FPGA Manager functionality can be safely enabled. Fixes: 34d1dc17ce97 ("fpga manager: Add Altera CvP driver") Signed-off-by: An

[PATCH AUTOSEL 4.19 046/258] drm/rockchip: fix for mailbox read size

2019-01-28 Thread Sasha Levin
From: Damian Kos [ Upstream commit fa68d4f8476bea4cdf441062b614b41bb85ef1da ] Some of the functions (like cdn_dp_dpcd_read, cdn_dp_get_edid_block) allow to read 64KiB, but the cdn_dp_mailbox_read_receive, that is used by them, can read only up to 255 bytes at once. Normally, it's not a big issue

[PATCH AUTOSEL 4.19 042/258] i40e: prevent overlapping tx_timeout recover

2019-01-28 Thread Sasha Levin
From: Alan Brady [ Upstream commit d5585b7b6846a6d0f9517afe57be3843150719da ] If a TX hang occurs, we attempt to recover by incrementally resetting. If we're starved for CPU time, it's possible the reset doesn't actually complete (or even fire) before another tx_timeout fires causing us to fly t

[PATCH AUTOSEL 4.19 051/258] net/mlx5: EQ, Use the right place to store/read IRQ affinity hint

2019-01-28 Thread Sasha Levin
From: Saeed Mahameed [ Upstream commit 1e86ace4c140fd5a693e266c9b23409358f25381 ] Currently the cpu affinity hint mask for completion EQs is stored and read from the wrong place, since reading and storing is done from the same index, there is no actual issue with that, but internal irq_info for

[PATCH AUTOSEL 4.19 049/258] drm/amd/display: calculate stream->phy_pix_clk before clock mapping

2019-01-28 Thread Sasha Levin
From: Yogesh Mohan Marimuthu [ Upstream commit 08e1c28dd521c7b08d1b0af0bae9fb22ccc012a4 ] [why] phy_pix_clk is one of the variable used to check if one PLL can be shared with displays having common mode set configuration. As of now phy_pix_clock varialbe is calculated in function dc_validate_str

[PATCH AUTOSEL 4.19 038/258] Tools: hv: kvp: Fix a warning of buffer overflow with gcc 8.0.1

2019-01-28 Thread Sasha Levin
From: Dexuan Cui [ Upstream commit 4fcba7802c3e15a6e56e255871d6c72f829b9dd8 ] The patch fixes: hv_kvp_daemon.c: In function 'kvp_set_ip_info': hv_kvp_daemon.c:1305:2: note: 'snprintf' output between 41 and 4136 bytes into a destination of size 4096 The "(unsigned int)str_len" is to avoid: hv_

[PATCH AUTOSEL 4.19 053/258] perf tools: Add Hygon Dhyana support

2019-01-28 Thread Sasha Levin
From: Pu Wen [ Upstream commit 4787eff3fa88f62fede6ed7afa06477ae6bf984d ] The tool perf is useful for the performance analysis on the Hygon Dhyana platform. But right now there is no Hygon support for it to analyze the KVM guest os data. So add Hygon Dhyana support to it by checking vendor strin

[PATCH AUTOSEL 4.19 052/258] modpost: validate symbol names also in find_elf_symbol

2019-01-28 Thread Sasha Levin
From: Sami Tolvanen [ Upstream commit 5818c683a619c534c113e1f66d24f636defc29bc ] If an ARM mapping symbol shares an address with a valid symbol, find_elf_symbol can currently return the mapping symbol instead, as the symbol is not validated. This can result in confusing warnings: WARNING: vml

[PATCH AUTOSEL 4.19 058/258] staging: erofs: fix the definition of DBG_BUGON

2019-01-28 Thread Sasha Levin
From: Gao Xiang [ Upstream commit eef168789866514e5d4316f030131c9fe65b643f ] It's better not to positively BUG_ON the kernel, however developers need a way to locate issues as soon as possible. DBG_BUGON is introduced and it could only crash when EROFS_FS_DEBUG (EROFS developping feature) is on

[PATCH AUTOSEL 4.19 057/258] media: mtk-vcodec: Release device nodes in mtk_vcodec_init_enc_pm()

2019-01-28 Thread Sasha Levin
From: Alexey Khoroshilov [ Upstream commit 8ea0f2ba0fa3f91ea1b8d823a54b042026ada6b3 ] of_parse_phandle() returns the device node with refcount incremented. There are two nodes that are used temporary in mtk_vcodec_init_enc_pm(), but their refcounts are not decremented. The patch adds one of_nod

[PATCH AUTOSEL 4.19 065/258] powerpc/32: Add .data..Lubsan_data*/.data..Lubsan_type* sections explicitly

2019-01-28 Thread Sasha Levin
From: Mathieu Malaterre [ Upstream commit beba24ac59133cb36ecd03f9af9ccb11971ee20e ] When both `CONFIG_LD_DEAD_CODE_DATA_ELIMINATION=y` and `CONFIG_UBSAN=y` are set, link step typically produce numberous warnings about orphan section: + powerpc-linux-gnu-ld -EB -m elf32ppc -Bstatic --orphan-h

[PATCH AUTOSEL 4.19 060/258] clk: meson: meson8b: do not use cpu_div3 for cpu_scale_out_sel

2019-01-28 Thread Sasha Levin
From: Martin Blumenstingl [ Upstream commit a5ac1ead32c9aac285f6436e09b4f6111996e9b8 ] The cpu_div3 clock (cpu_in divided by 3) generates a signal with a duty cycle of 33%. The CPU clock however requires a clock signal with a duty cycle of 50% to run stable. cpu_div3 was observed to be problemat

[PATCH AUTOSEL 4.19 063/258] ptp: Fix pass zero to ERR_PTR() in ptp_clock_register

2019-01-28 Thread Sasha Levin
From: YueHaibing [ Upstream commit aea0a897af9e44c258e8ab9296fad417f1bc063a ] Fix smatch warning: drivers/ptp/ptp_clock.c:298 ptp_clock_register() warn: passing zero to 'ERR_PTR' 'err' should be set while device_create_with_groups and pps_register_source fails Fixes: 85a66e550195 ("ptp: crea

Re: [PATCH v2 1/3] platform/x86: wmi: move struct wmi_device_id to mod_devicetable.h

2019-01-28 Thread Andy Shevchenko
On Mon, Jan 28, 2019 at 3:55 PM Mattias Jacobsson <2...@mok.nu> wrote: > On 2019-01-27, Andy Shevchenko wrote: > > On Sun, Jan 27, 2019 at 9:04 PM Mattias Jacobsson <2...@mok.nu> wrote: > > > +#define WMI_GUID_STRING_LEN36 > > > > Isn't this already defined in UUID namespace? > > (include/linu

[PATCH AUTOSEL 4.19 054/258] soc/tegra: Don't leak device tree node reference

2019-01-28 Thread Sasha Levin
From: Yangtao Li [ Upstream commit 9eb40fa2cd2d1f6829e7b49bb22692f754b9cfe0 ] of_find_node_by_path() acquires a reference to the node returned by it and that reference needs to be dropped by its caller. soc_is_tegra() doesn't do that, so fix it. Signed-off-by: Yangtao Li Acked-by: Jon Hunter

[PATCH AUTOSEL 4.19 064/258] dmaengine: xilinx_dma: Remove __aligned attribute on zynqmp_dma_desc_ll

2019-01-28 Thread Sasha Levin
From: Nathan Chancellor [ Upstream commit aeaebcc17cdf37065d2693865eeb1ff1c7dc5bf3 ] Clang warns: drivers/dma/xilinx/zynqmp_dma.c:166:4: warning: attribute 'aligned' is ignored, place it after "struct" to apply attribute to type declaration [-Wignored-attributes] }; __aligned(64) ^ ./include

[PATCH AUTOSEL 4.19 059/258] x86/resctrl: Fixup the user-visible strings

2019-01-28 Thread Sasha Levin
From: Babu Moger [ Upstream commit 723f1a0dd8e26a7523ba068204bee11c95ded38d ] Fix the messages in rdt_last_cmd_printf() and rdt_last_cmd_puts() to make them more meaningful and consistent. [ bp: s/cpu/CPU/; s/mem\W/memory ] Signed-off-by: Babu Moger Signed-off-by: Borislav Petkov Cc: Andrew

[PATCH AUTOSEL 4.19 066/258] iio: adc: meson-saradc: check for devm_kasprintf failure

2019-01-28 Thread Sasha Levin
From: Nicholas Mc Guire [ Upstream commit aad172b017617994343e36d8659c69e14cd694fd ] devm_kasprintf() may return NULL on failure of internal allocation thus the assignments to init.name are not safe if not checked. On error meson_sar_adc_clk_init() returns negative values so -ENOMEM in the (un

[PATCH AUTOSEL 4.19 067/258] iio: adc: meson-saradc: fix internal clock names

2019-01-28 Thread Sasha Levin
From: Martin Blumenstingl [ Upstream commit 50314f98b0ac468218e7c9af8c99f215a35436df ] Before this patch we are registering the internal clocks (for example on Meson8b, where the SAR ADC IP block implements the divider and gate clocks) with the following names: - /soc/cbus@c110/adc@8680#adc_

[PATCH AUTOSEL 4.19 068/258] iio: accel: kxcjk1013: Add KIOX010A ACPI Hardware-ID

2019-01-28 Thread Sasha Levin
From: Hans de Goede [ Upstream commit 7f6232e69539971cf9eaed07a6c14ab4a2361133 ] Various 2-in-1's use KIOX010A and KIOX020A as HIDs for 2 KXCJ91008 accelerometers. The KIOX010A HID is for the one in the base and the KIOX020A for the accelerometer in the keyboard. Since userspace does not have a

[PATCH AUTOSEL 4.19 071/258] staging: pi433: fix potential null dereference

2019-01-28 Thread Sasha Levin
From: Michael Straube [ Upstream commit 64c4c4ca6c129a4191e8e1e91b2d5d9b8d08c518 ] Add a test for successful call to cdev_alloc() to avoid potential null dereference. Issue reported by smatch. Signed-off-by: Michael Straube Fixes: 874bcba65f9a ("staging: pi433: New driver") Signed-off-by: Greg

[PATCH AUTOSEL 4.19 070/258] ACPI: SPCR: Consider baud rate 0 as preconfigured state

2019-01-28 Thread Sasha Levin
From: Andy Shevchenko [ Upstream commit b413b1abeb21b4a152c0bf8d1379efa30759b6e3 ] Since SPCR 1.04 [1] the baud rate of 0 means a preconfigured state of UART. Assume firmware or bootloader configures console correctly. [1]: https://docs.microsoft.com/en-us/windows-hardware/drivers/serports/ser

[PATCH AUTOSEL 4.19 072/258] f2fs: move dir data flush to write checkpoint process

2019-01-28 Thread Sasha Levin
From: Yunlei He [ Upstream commit b61ac5b720146c619c7cdf17eff2551b934399e5 ] This patch move dir data flush to write checkpoint process, by doing this, it may reduce some time for dir fsync. pre: -f2fs_do_sync_file enter -file_write_and_wait_range <- flush & wait

[PATCH AUTOSEL 4.19 074/258] f2fs: fix race between write_checkpoint and write_begin

2019-01-28 Thread Sasha Levin
From: Sheng Yong [ Upstream commit 2866fb16d67992195b0526d19e65acb6640fb87f ] The following race could lead to inconsistent SIT bitmap: Task A Task B == == f2fs_write_checkpoint block_operations f2fs_lock_all down_write(node_

[PATCH AUTOSEL 4.19 080/258] soc: bcm: brcmstb: Don't leak device tree node reference

2019-01-28 Thread Sasha Levin
From: Yangtao Li [ Upstream commit 1861a7f07e02292830a1ca256328d370deefea30 ] of_find_node_by_path() acquires a reference to the node returned by it and that reference needs to be dropped by its caller. soc_is_brcmstb() doesn't do that, so fix it. [treding: slightly rewrite to avoid inline comp

[PATCH AUTOSEL 4.19 086/258] Thermal: do not clear passive state during system sleep

2019-01-28 Thread Sasha Levin
From: Wei Wang [ Upstream commit 964f4843a455d2ffb199512b08be8d5f077c4cac ] commit ff140fea847e ("Thermal: handle thermal zone device properly during system sleep") added PM hook to call thermal zone reset during sleep. However resetting thermal zone will also clear the passive state and thus ca

[PATCH AUTOSEL 4.19 081/258] nfsd4: fix crash on writing v4_end_grace before nfsd startup

2019-01-28 Thread Sasha Levin
From: "J. Bruce Fields" [ Upstream commit 62a063b8e7d1db684db3f207261a466fa3194e72 ] Anatoly Trosinenko reports that this: 1) Checkout fresh master Linux branch (tested with commit e195ca6cb) 2) Copy x84_64-config-4.14 to .config, then enable NFS server v4 and build 3) From `kvm-xfstests shell`

[PATCH AUTOSEL 4.19 079/258] sunvdc: Do not spin in an infinite loop when vio_ldc_send() returns EAGAIN

2019-01-28 Thread Sasha Levin
From: Young Xiao [ Upstream commit a11f6ca9aef989b56cd31ff4ee2af4fb31a172ec ] __vdc_tx_trigger should only loop on EAGAIN a finite number of times. See commit adddc32d6fde ("sunvnet: Do not spin in an infinite loop when vio_ldc_send() returns EAGAIN") for detail. Signed-off-by: Young Xiao Sig

[PATCH AUTOSEL 4.19 076/258] i2c: sh_mobile: add support for r8a77990 (R-Car E3)

2019-01-28 Thread Sasha Levin
From: Simon Horman [ Upstream commit 5eb316e636eb298c204f5b368526d4480b63c0ba ] Add support for the IIC code for the r8a77990 (R-Car E3). It is not considered compatible with existing fallback bindings due to the documented absence of automatic transmission registers. These registers are curre

[PATCH AUTOSEL 4.19 083/258] drm: Move drm_mode_setcrtc() local re-init to failure path

2019-01-28 Thread Sasha Levin
From: Sean Paul [ Upstream commit c232e9f41b136c141df9938024e521191a7b910d ] Instead of always re-initializing the variables we need to clean up on out, move the re-initialization into the branch that goes back to retry label. This is a lateral move right now, but will allow us to pull out the

[PATCH AUTOSEL 4.19 088/258] firmware/efi: Add NULL pointer checks in efivars API functions

2019-01-28 Thread Sasha Levin
From: Arend van Spriel [ Upstream commit ab2180a15ce54739fed381efb4cb12e78dfb1561 ] Since commit: ce2e6db554fa ("brcmfmac: Add support for getting nvram contents from EFI variables") we have a device driver accessing the efivars API. Several functions in the efivars API assume __efivars is

[PATCH AUTOSEL 4.19 093/258] ARM: dts: mmp2: fix TWSI2

2019-01-28 Thread Sasha Levin
From: Lubomir Rintel [ Upstream commit 1147e05ac9fc2ef86a3691e7ca5c2db7602d81dd ] Marvell keeps their MMP2 datasheet secret, but there are good clues that TWSI2 is not on 0xd4025000 on that platform, not does it use IRQ 58. In fact, the IRQ 58 on MMP2 seems to be a signal processor: arch/arm

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