[PATCH] RDMA/ucma: check fd type in ucma_migrate_id()

The current code grabs the private_data of whatever file descriptor userspace has supplied and implicitly casts it to a `struct ucma_file *`, potentially causing a type confusion. This is probably fine in practice because the pointer is only used for comparisons, it is never actually dereferenced;

[PATCH 4.4 08/80] drm/bridge: adv7511: Reset registers on hotplug

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sean Paul [ Upstream commit 5f3417569165a8ee57654217f73e0160312f409c ] The bridge loses its hw state when the cable is unplugged. If we detect this case in the hpd handler, reset its state. Re

[PATCH 4.4 34/80] enic: handle mtu change for vf properly

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Govindarajulu Varadarajan [ Upstream commit ab123fe071c9aa9680ecd62eb080eb26cff4892c ] When driver gets notification for mtu change, driver does not handle it for all RQs. It handles only RQ[0]

[PATCH 4.4 32/80] tools/power turbostat: Read extended processor family from CPUID

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Calvin Walton [ Upstream commit 5aa3d1a20a233d4a5f1ec3d62da3f19d9afea682 ] This fixes the reported family on modern AMD processors (e.g. Ryzen, which is family 0x17). Previously these processor

[PATCH 4.4 36/80] arc: fix type warnings in arc/mm/cache.c

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit ec837d620c750c0d4996a907c8c4f7febe1bbeee ] Fix type warnings in arch/arc/mm/cache.c. ../arch/arc/mm/cache.c: In function 'flush_anon_page': ../arch/arc/mm/cache.

[PATCH 4.4 09/80] scsi: libiscsi: fix possible NULL pointer dereference in case of TMF

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Varun Prakash [ Upstream commit a17037e7d59075053b522048742a08ac9500bde8 ] In iscsi_check_tmf_restrictions() task->hdr is dereferenced to print the opcode, it is possible that task->hdr is NULL

[PATCH 4.4 06/80] mac80211: add stations tied to AP_VLANs during hw reconfig

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "mpubb...@codeaurora.org" [ Upstream commit 19103a4bfb42f320395daa5616ece3e89e759d63 ] As part of hw reconfig, only stations linked to AP interfaces are added back to the driver ignoring those

[PATCH 4.4 30/80] selftests/ftrace: Add snapshot and tracing_on test case

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu [ Upstream commit 82f4f3e69c5c29bce940dd87a2c0f16c51d48d17 ] Add a testcase for checking snapshot and tracing_on relationship. This ensures that the snapshotting doesn't affect

[PATCH 4.4 00/80] 4.4.154-stable review

This is the start of the stable review cycle for the 4.4.154 release. There are 80 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed Sep 5 16:49:18 UTC 2018. Anything receiv

[PATCH 4.4 21/80] net: prevent ISA drivers from building on PPC32

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit c9ce1fa1c24b08e13c2a3b5b1f94a19c9eaa982c ] Prevent drivers from building on PPC32 if they use isa_bus_to_virt(), isa_virt_to_bus(), or isa_page_to_bus(), which ar

[PATCH 4.4 31/80] zswap: re-check zswap_is_full() after do zswap_shrink()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Li Wang [ Upstream commit 16e536ef47f567289a5699abee9ff7bb304bc12d ] /sys/../zswap/stored_pages keeps rising in a zswap test with "zswap.max_pool_percent=0" parameter. But it should not compre

[PATCH 4.4 02/80] Cipso: cipso_v4_optptr enter infinite loop

4.4-stable review patch. If anyone has any objections, please let me know. -- From: yujuan.qi commit 40413955ee265a5e42f710940ec78f5450d49149 upstream. in for(),if((optlen > 0) && (optptr[1] == 0)), enter infinite loop. Test: receive a packet which the ip length > 20 and the

[PATCH 4.4 19/80] qed: Fix possible race for the link state value.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sudarsana Reddy Kalluru [ Upstream commit 58874c7b246109d8efb2b0099d1aa296d6bfc3fa ] There's a possible race where driver can read link status in mid-transition and see that virtual-link is up

[PATCH 4.4 04/80] xfrm: fix missing dst_release() after policy blocking lbcast and multicast

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tommi Rantala [ Upstream commit 8cc88773855f988d6a3bbf102bbd9dd9c828eb81 ] Fix missing dst_release() when local broadcast or multicast traffic is xfrm policy blocked. For IPv4 this results to

[PATCH 4.4 05/80] xfrm: free skb if nlsk pointer is NULL

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal [ Upstream commit 86126b77dcd551ce223e7293bb55854e3df05646 ] nlmsg_multicast() always frees the skb, so in case we cannot call it we must do that ourselves. Fixes: 21ee543edc0

[PATCH 4.4 03/80] vti6: fix PMTU caching and reporting on xmit

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eyal Birger [ Upstream commit d6990976af7c5d8f55903bfb4289b6fb030bf754 ] When setting the skb->dst before doing the MTU check, the route PMTU caching and reporting is done on the new dst which

[PATCH 4.4 18/80] net: caif: Add a missing rcu_read_unlock() in caif_flow_cb

4.4-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing [ Upstream commit 64119e05f7b31e83e2555f6782e6cdc8f81c63f4 ] Add a missing rcu_read_unlock in the error path Fixes: c95567c80352 ("caif: added check for potential null return") Sign

[PATCH 4.4 17/80] tools/power turbostat: fix -S on UP systems

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Len Brown [ Upstream commit 9d83601a9cc1884d1b5706ee2acc661d558c6838 ] The -S (system summary) option failed to print any data on a 1-processor system. Reported-by: Artem Bityutskiy Signed-of

[PATCH 4.4 16/80] usb: gadget: f_uac2: fix endianness of struct cntrl_*_lay3

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eugeniu Rosca [ Upstream commit eec24f2a0d4dc3b1d95a3ccd2feb523ede3ba775 ] The list [1] of commits doing endianness fixes in USB subsystem is long due to below quote from USB spec Revision 2.0

[PATCH 4.4 12/80] usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in init_controller()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai [ Upstream commit 0602088b10a7c0b4e044a810678ef93d7cc5bf48 ] The driver may sleep with holding a spinlock. The function call paths (from bottom to top) in Linux-4.16.7 are: [FUNC] m

[PATCH 4.4 01/80] sched/sysctl: Check user input value of sysctl_sched_time_avg

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ethan Zhao commit 5ccba44ba118a500050076b0344632459779 upstream. System will hang if user set sysctl_sched_time_avg to 0: [root@XXX ~]# sysctl kernel.sched_time_avg_ms=0 Stack traceba

[PATCH 4.4 14/80] usb/phy: fix PPC64 build errors in phy-fsl-usb.c

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit a39ba90a1cc7010edb0a7132e1b67f3d80b994e9 ] Fix build errors when built for PPC64: These variables are only used on PPC32 so they don't need to be initialized for

[PATCH 4.4 11/80] drm/imx: imx-ldb: check if channel is enabled before printing warning

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach [ Upstream commit c80d673b91a6c81d765864e10f2b15110ee900ad ] If the second LVDS channel has been disabled in the DT when using dual-channel mode we should not print a warning. Sign

[PATCH 4.4 13/80] usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in r8a66597_queue()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai [ Upstream commit f36b507c14c4b6e634463a610294e9cb0065c8ea ] The driver may sleep in an interrupt handler. The function call path (from bottom to top) in Linux-4.16.7 is: [FUNC] r8a

[PATCH 3.18 53/56] MIPS: Correct the 64-bit DSP accumulator register size

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit f5958b4cf4fc38ed4583ab83fb7c4cd1ab05f47b upstream. Use the `unsigned long' rather than `__u32' type for DSP accumulator registers, like with the regular MIPS multiply/

[PATCH 3.18 54/56] scsi: sysfs: Introduce sysfs_{un,}break_active_protection()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 2afc9166f79b8f6da5f347f48515215ceee4ae37 upstream. Introduce these two functions and export them such that the next patch can add calls to these functions from the SCSI

[PATCHv2 1/4] tty: Drop tty->count on tty_reopen() failure

In case of tty_ldisc_reinit() failure, tty->count should be decremented back, otherwise we will never release_tty(). Tetsuo reported that it fixes noisy warnings on tty release like: pts pts4033: tty_release: tty->count(10529) != (#fd's(7) + #kopen's(0)) Cc: Greg Kroah-Hartman Cc: Jiri Slaby C

[PATCHv2 4/4] tty: Simplify tty->count math in tty_reopen()

As noted by Jiri, tty_ldisc_reinit() shouldn't rely on tty counter. Simplify math by increasing the counter after reinit success. Cc: Greg Kroah-Hartman Cc: Jiri Slaby Link: lkml.kernel.org/r/<20180829022353.23568-2-d...@arista.com> Suggested-by: Jiri Slaby Signed-off-by: Dmitry Safonov --- d

[PATCH 3.18 29/56] enic: handle mtu change for vf properly

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Govindarajulu Varadarajan [ Upstream commit ab123fe071c9aa9680ecd62eb080eb26cff4892c ] When driver gets notification for mtu change, driver does not handle it for all RQs. It handles only RQ[0

[PATCH 3.18 26/56] zswap: re-check zswap_is_full() after do zswap_shrink()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Li Wang [ Upstream commit 16e536ef47f567289a5699abee9ff7bb304bc12d ] /sys/../zswap/stored_pages keeps rising in a zswap test with "zswap.max_pool_percent=0" parameter. But it should not compr

[PATCH 3.18 27/56] tools/power turbostat: Read extended processor family from CPUID

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Calvin Walton [ Upstream commit 5aa3d1a20a233d4a5f1ec3d62da3f19d9afea682 ] This fixes the reported family on modern AMD processors (e.g. Ryzen, which is family 0x17). Previously these processo

[PATCH 3.18 45/56] udl-kms: change down_interruptible to down

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 8456b99c16d193c4c3b7df305cf431e027f0189c upstream. If we leave urbs around, it causes not only leak, but also memory corruption. This patch fixes the function udl_free_u

[PATCH 3.18 55/56] scsi: core: Avoid that SCSI device removal through sysfs triggers a deadlock

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 0ee223b2e1f67cb2de9c0e3247c510d846e74d63 upstream. A long time ago the unfortunate decision was taken to add a self-deletion attribute to the sysfs SCSI device directory

[PATCH 3.18 41/56] KVM: arm/arm64: Skip updating PMD entry if no change

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Punit Agrawal commit 86658b819cd0a9aa584cd84453ed268a6f013770 upstream. Contention on updating a PMD entry by a large number of vcpus can lead to duplicate work when handling stage 2 page faul

[PATCH 3.18 44/56] fuse: Add missed unlock_page() to fuse_readpages_fill()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kirill Tkhai commit 109728ccc5933151c68d1106e4065478a487a323 upstream. The above error path returns with page unlocked, so this place seems also to behave the same. Fixes: f8dbdf81821b ("fuse

[PATCH 3.18 51/56] s390/pci: fix out of bounds access during irq setup

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 866f3576a72b2233a76dffb80290f8086dc49e17 upstream. During interrupt setup we allocate interrupt vectors, walk the list of msi descriptors, and fill in the message data. Re

[PATCH 3.18 42/56] x86/process: Re-export start_thread()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Rian Hunter commit dc76803e57cc86589c4efcb5362918f9b0c0436f upstream. The consolidation of the start_thread() functions removed the export unintentionally. This breaks binfmt handlers built as

[PATCH 3.18 50/56] s390/qdio: reset old sbal_state flags

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann commit 64e03ff72623b8c2ea89ca3cb660094e019ed4ae upstream. When allocating a new AOB fails, handle_outbound() is still capable of transmitting the selected buffer (just without

[PATCH 3.18 56/56] cdrom: Fix info leak/OOB read in cdrom_ioctl_drive_status

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Scott Bauer commit 8f3fafc9c2f0ece10832c25f7ffcb07c97a32ad4 upstream. Like d88b6d04: "cdrom: information leak in cdrom_ioctl_media_changed()" There is another cast from unsigned long to int w

[PATCH 3.18 43/56] fuse: Dont access pipe->buffers without pipe_lock()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit a2477b0e67c52f4364a47c3ad70902bc2a61bd4c upstream. fuse_dev_splice_write() reads pipe->buffers to determine the size of 'bufs' array before taking the pipe_lock(). This

[PATCH 3.18 25/56] selftests/ftrace: Add snapshot and tracing_on test case

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu [ Upstream commit 82f4f3e69c5c29bce940dd87a2c0f16c51d48d17 ] Add a testcase for checking snapshot and tracing_on relationship. This ensures that the snapshotting doesn't affec

[PATCH 3.18 52/56] kprobes: Make list and blacklist root user read only

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit f2a3ab36077222437b4826fc76111caa14562b7c upstream. Since the blacklist and list files on debugfs indicates a sensitive address information to reader, it should be restr

[PATCH 3.18 48/56] ASoC: sirf: Fix potential NULL pointer dereference

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit ae1c696a480c67c45fb23b35162183f72c6be0e1 upstream. There is a potential execution path in which function platform_get_resource() returns NULL. If this happens, we wi

[PATCH 3.18 36/56] btrfs: dont leak ret from do_chunk_alloc

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Josef Bacik commit 4559b0a71749c442d34f7cfb9e72c9e58db83948 upstream. If we're trying to make a data reservation and we have to allocate a data chunk we could leak ret == 1, as do_chunk_alloc(

[PATCH 3.18 47/56] udl-kms: fix crash due to uninitialized memory

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 09a00abe3a9941c2715ca83eb88172cd2f54d8fd upstream. We must use kzalloc when allocating the fb_deferred_io structure. Otherwise, the field first_io is undefined and it ca

[PATCH 3.18 46/56] udl-kms: handle allocation failure

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit 542bb9788a1f485eb1a2229178f665d8ea166156 upstream. Allocations larger than PAGE_ALLOC_COSTLY_ORDER are unreliable and they may fail anytime. This patch fixes the udl kms

[PATCH 3.18 37/56] s390/kvm: fix deadlock when killed by oom

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Claudio Imbrenda commit 306d6c49ac9ded4cb53b0925da52f2c2ada1 upstream. When the oom killer kills a userspace process in the page fault handler while in guest context, the fault handler fai

[PATCH 3.18 40/56] KVM: arm/arm64: Skip updating PTE entry if no change

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Punit Agrawal commit 976d34e2dab10ece5ea8fe7090b7692913f89084 upstream. When there is contention on faulting in a particular page table entry at stage 2, the break-before-make requirement of t

[PATCH 3.18 38/56] ext4: reset error code in ext4_find_entry in fallback

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit f39b3f45dbcb0343822cce31ea7636ad66e60bc2 upstream. When ext4_find_entry() falls back to "searching the old fashioned way" due to a corrupt dx dir, it needs to reset the err

[PATCH 3.18 39/56] arm64: mm: check for upper PAGE_SHIFT bits in pfn_valid()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Hackmann commit 5ad356eabc47d26a92140a0c4b20eba471c10de3 upstream. ARM64's pfn_valid() shifts away the upper PAGE_SHIFT bits of the input before seeing if the PFN is valid. This leads to

[PATCH 3.18 21/56] net: axienet: Fix double deregister of mdio

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Shubhrajyoti Datta [ Upstream commit 03bc7cab7d7218088412a75e141696a89059ab00 ] If the registration fails then mdio_unregister is called. However at unbind the unregister ia attempted again re

[PATCH 3.18 22/56] fscache: Allow cancelled operations to be enqueued

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kiran Kumar Modukuri [ Upstream commit d0eb06afe712b7b103b6361f40a9a0c638524669 ] Alter the state-check assertion in fscache_enqueue_operation() to allow cancelled operations to be given proce

[PATCH 3.18 05/56] mac80211: add stations tied to AP_VLANs during hw reconfig

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "mpubb...@codeaurora.org" [ Upstream commit 19103a4bfb42f320395daa5616ece3e89e759d63 ] As part of hw reconfig, only stations linked to AP interfaces are added back to the driver ignoring those

[PATCH 3.18 08/56] drm/imx: imx-ldb: disable LDB on driver bind

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach [ Upstream commit b58262396fabd43dc869b576e3defdd23b32fe94 ] The LVDS signal integrity is only guaranteed when the correct enable sequence (first IPU DI, then LDB) is used. If the

[PATCH 3.18 09/56] drm/imx: imx-ldb: check if channel is enabled before printing warning

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach [ Upstream commit c80d673b91a6c81d765864e10f2b15110ee900ad ] If the second LVDS channel has been disabled in the DT when using dual-channel mode we should not print a warning. Sig

[PATCH 3.18 35/56] mm/memory.c: check return value of ioremap_prot

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "jie@chenj...@huwei.com" [ Upstream commit 24eee1e4c47977bdfb71d6f15f6011e7b6188d04 ] ioremap_prot() can return NULL which could lead to an oops. Link: http://lkml.kernel.org/r/1533195441-58

[PATCH 3.18 06/56] nl80211: Add a missing break in parse_station_flags

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bernd Edlinger [ Upstream commit 5cf3006cc81d9aa09a10aa781fc065546b12919d ] I was looking at usually suppressed gcc warnings, [-Wimplicit-fallthrough=] in this case: The code definitely looks

[PATCH 3.18 34/56] scsi: vmw_pvscsi: Return DID_RESET for status SAM_STAT_COMMAND_TERMINATED

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jim Gill [ Upstream commit e95153b64d03c2b6e8d62e51bdcc33fcad6e0856 ] Commands that are reset are returned with status SAM_STAT_COMMAND_TERMINATED. PVSCSI currently returns DID_OK | SAM_STAT_C

[PATCH 3.18 24/56] cachefiles: Wait rather than BUGing on "Unexpected object collision"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kiran Kumar Modukuri [ Upstream commit c2412ac45a8f8f1cd582723c1a139608694d410d ] If we meet a conflicting object that is marked FSCACHE_OBJECT_IS_LIVE in the active object tree, we have been

[PATCH 3.18 33/56] scsi: fcoe: drop frames in ELS LOGO error path

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn [ Upstream commit 63d0e3dffda311e77b9a8c500d59084e960a824a ] Drop the frames in the ELS LOGO error path instead of just returning an error. This fixes the following kmemlea

[PATCH 3.18 07/56] scsi: libiscsi: fix possible NULL pointer dereference in case of TMF

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Varun Prakash [ Upstream commit a17037e7d59075053b522048742a08ac9500bde8 ] In iscsi_check_tmf_restrictions() task->hdr is dereferenced to print the opcode, it is possible that task->hdr is NUL

[PATCH 3.18 00/56] 3.18.121-stable review

This is the start of the stable review cycle for the 3.18.121 release. There are 56 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed Sep 5 16:49:09 UTC 2018. Anything recei

[PATCH 3.18 04/56] xfrm: free skb if nlsk pointer is NULL

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal [ Upstream commit 86126b77dcd551ce223e7293bb55854e3df05646 ] nlmsg_multicast() always frees the skb, so in case we cannot call it we must do that ourselves. Fixes: 21ee543edc

[PATCH 3.18 03/56] xfrm: fix missing dst_release() after policy blocking lbcast and multicast

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tommi Rantala [ Upstream commit 8cc88773855f988d6a3bbf102bbd9dd9c828eb81 ] Fix missing dst_release() when local broadcast or multicast traffic is xfrm policy blocked. For IPv4 this results to

[PATCH 3.18 20/56] bnx2x: Fix invalid memory access in rss hash config path.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sudarsana Reddy Kalluru [ Upstream commit ae2dcb28c24794a87e424a726a1cf1a61980f52d ] Rx hash/filter table configuration uses rss_conf_obj to configure filters in the hardware. This object is i

[PATCH 3.18 02/56] Cipso: cipso_v4_optptr enter infinite loop

3.18-stable review patch. If anyone has any objections, please let me know. -- From: yujuan.qi commit 40413955ee265a5e42f710940ec78f5450d49149 upstream. in for(),if((optlen > 0) && (optptr[1] == 0)), enter infinite loop. Test: receive a packet which the ip length > 20 and the

[PATCH 3.18 10/56] usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in init_controller()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai [ Upstream commit 0602088b10a7c0b4e044a810678ef93d7cc5bf48 ] The driver may sleep with holding a spinlock. The function call paths (from bottom to top) in Linux-4.16.7 are: [FUNC]

Re: [PATCH] ath10k: retrieve MAC address from firmware if provided

Brian Norris writes: > On Tue, Aug 28, 2018 at 05:33:01PM +0300, Kalle Valo wrote: >> Arend van Spriel writes: >> >> > On 8/13/2018 7:14 PM, Brian Norris wrote: >> >> On Sat, Aug 11, 2018 at 11:26 AM Arend van Spriel >> >> wrote: >> >>> >> >>> On 8/11/2018 1:39 AM, Brian Norris wrote: >>

[PATCH 3.18 17/56] atl1c: reserve min skb headroom

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal [ Upstream commit 6e56830776828d8ca9897fc4429eeab47c3bb432 ] Got crash report with following backtrace: BUG: unable to handle kernel paging request at 8801869daffe RIP: 00

[PATCH 3.18 16/56] net: caif: Add a missing rcu_read_unlock() in caif_flow_cb

3.18-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing [ Upstream commit 64119e05f7b31e83e2555f6782e6cdc8f81c63f4 ] Add a missing rcu_read_unlock in the error path Fixes: c95567c80352 ("caif: added check for potential null return") Sig

[PATCH 3.18 11/56] usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in r8a66597_queue()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai [ Upstream commit f36b507c14c4b6e634463a610294e9cb0065c8ea ] The driver may sleep in an interrupt handler. The function call path (from bottom to top) in Linux-4.16.7 is: [FUNC] r8

[PATCH 3.18 01/56] sched/sysctl: Check user input value of sysctl_sched_time_avg

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ethan Zhao commit 5ccba44ba118a500050076b0344632459779 upstream. System will hang if user set sysctl_sched_time_avg to 0: [root@XXX ~]# sysctl kernel.sched_time_avg_ms=0 Stack traceb

[PATCH 3.18 18/56] can: mpc5xxx_can: check of_iomap return before use

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire [ Upstream commit b5c1a23b17e563b656cc9bb76ce5323b997d90e8 ] of_iomap() can return NULL so that return needs to be checked and NULL treated as failure. While at it also take

[PATCH 3.18 19/56] media: staging: omap4iss: Include asm/cacheflush.h after generic includes

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck [ Upstream commit 0894da849f145af51bde88a6b84f95b9c9e0bc66 ] Including asm/cacheflush.h first results in the following build error when trying to build sparc32:allmodconfig, beca

[PATCH 3.18 15/56] tools/power turbostat: fix -S on UP systems

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Len Brown [ Upstream commit 9d83601a9cc1884d1b5706ee2acc661d558c6838 ] The -S (system summary) option failed to print any data on a 1-processor system. Reported-by: Artem Bityutskiy Signed-o

[PATCH 3.18 14/56] usb: gadget: f_uac2: fix endianness of struct cntrl_*_lay3

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eugeniu Rosca [ Upstream commit eec24f2a0d4dc3b1d95a3ccd2feb523ede3ba775 ] The list [1] of commits doing endianness fixes in USB subsystem is long due to below quote from USB spec Revision 2.0

Re: [PATCH v2] regulator: fix kernel-doc function parameter and warning

On Mon, Sep 03, 2018 at 09:05:20AM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > Fix kernel-doc warning by using correct parameter description: This doesn't apply against current code, please check and resend. signature.asc Description: PGP signature

Re: [PATCH] arm64/ptrace: add PTRACE_SYSEMU and PTRACE_SYSEMU_SINGLESTEP support

Am Montag, 3. September 2018, 18:31:03 CEST schrieb Will Deacon: > On Mon, Sep 03, 2018 at 02:23:17PM +0800, Haibo.Xu wrote: > > Add PTRACE_SYSEMU and PTRACE_SYSEMU_SINGLESTEP support on ARM64. > > This copies the x86 semantics for invoking ptrace hooks, and have > > been verified on ARM64 machine.

Re: [PATCH] staging: android: ion: check for kref overflow

On Fri, Aug 31, 2018 at 02:31:38PM -0700, Daniel Rosenberg wrote: > > > On 08/31/2018 08:56 AM, Greg Kroah-Hartman wrote: > > On Thu, Aug 30, 2018 at 06:36:18PM -0700, Daniel Rosenberg wrote: > > > The sign off was on the 4.4.y version that I cherry-picked this from. > > Ah that wasn't obvious at

Re: [PATCH] arm64/ptrace: add PTRACE_SYSEMU and PTRACE_SYSEMU_SINGLESTEP support

On Mon, Sep 03, 2018 at 02:23:17PM +0800, Haibo.Xu wrote: > Add PTRACE_SYSEMU and PTRACE_SYSEMU_SINGLESTEP support on ARM64. > This copies the x86 semantics for invoking ptrace hooks, and have > been verified on ARM64 machine. > > Signed-off-by: Haibo.Xu > Signed-off-by: Bin.Lu > --- > arch/arm

Applied "regulator: Fix useless O^2 complexity in suspend/resume" to the regulator tree

The patch regulator: Fix useless O^2 complexity in suspend/resume has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

RE: Affinity managed interrupts vs non-managed interrupts

On Mon, 3 Sep 2018, Kashyap Desai wrote: > I am using " for-4.19/block " and this particular patch "a0c9259 > irq/matrix: Spread interrupts on allocation" is included. Can you please try against 4.19-rc2 or later? > I can see that 16 extra reply queues via pre_vectors are still assigned to > CPU

Applied "regulator: Fix 'do-nothing' value for regulators without suspend state" to the regulator tree

The patch regulator: Fix 'do-nothing' value for regulators without suspend state has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime

[PATCH v4 6/8] perf, tools, script: Make itrace script default to all calls

From: Andi Kleen By default perf script for itrace outputs sampled instructions or branches. In my experience this is confusing to users because it's hard to correlate with real program behavior. The sampling makes sense for tools like report that actually sample to reduce the run time, but run t

[PATCH v4 3/8] tools, perf, script: Add --insn-trace for instruction decoding

From: Andi Kleen Add a --insn-trace short hand option for decoding and disassembling instruction streams for intel_pt. This automatically pipes the output into the xed disassembler to generate disassembled instructions. This just makes this use model much nicer to use Before % perf record -e in

[PATCH v4 8/8] tools, perf, script: Implement --graph-function

From: Andi Kleen Add a ftrace style --graph-function argument to perf script that allows to print itrace function calls only below a given function. This makes it easier to find the code of interest in a large trace. % perf record -e intel_pt//k -a sleep 1 % perf script --graph-function group_sc

[PATCH v4 7/8] tools, perf, script: Add --call-trace and --call-ret-trace

From: Andi Kleen Add short cut options to print PT call trace and call-ret-trace, for calls and call and returns. Roughly corresponds to ftrace function tracer and function graph tracer. Just makes these common use cases nicer to use. % perf record -a -e intel_pt// sleep 1 % perf script --call-

[PATCH v4 4/8] perf, tools, script: Allow sym and dso without ip, addr

From: Andi Kleen Currently sym and dso require printing ip and addr because the print function is tied to those outputs. With callindent it makes sense to print the symbol or dso without numerical IP or ADDR. So change the dependency check to only check the underlying attribute. Also the branch

[PATCH v4 5/8] perf, tools, script: Print DSO for callindent

From: Andi Kleen Now that we don't need to print the IP/ADDR for callindent the DSO is also not printed. It's useful for some cases, so add an own DSO printout for callindent for the case when IP/ADDR is not enabled. Before: % perf script --itrace=cr -F +callindent,-ip,-sym,-symoff,-addr

[PATCH v4 2/8] tools, pager: Support overwriting the pager

From: Andi Kleen Add an interface to the auto pager code that allows callers to overwrite the pager. Signed-off-by: Andi Kleen --- tools/lib/subcmd/pager.c | 11 ++- tools/lib/subcmd/pager.h | 1 + 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/tools/lib/subcmd/pager.c

[PATCH v4 1/8] perf tools: Report itrace options in help

From: Andi Kleen I often forget all the options that --itrace accepts. Instead of burying them in the man page only report them in the normal command line help too to make them easier accessible. v2: Align Signed-off-by: Andi Kleen --- tools/perf/builtin-inject.c | 3 ++- tools/perf/builtin-r

Make perf script easier to use for itrace

Implement a range of improvements to make it easier to look at itrace traces with perf script. Nothing here couldn't be done before with some additional scripting, but add simple high level options to make it easier to use. % perf record -e intel_pt//k -a sleep 1 Show function calls: % perf scr

Re: [PATCH v2 04/10] perf, tools, script: Allow sym and dso without ip, addr

On Mon, Sep 03, 2018 at 09:15:10AM +0200, Jiri Olsa wrote: > On Fri, Aug 31, 2018 at 03:02:00PM -0700, Andi Kleen wrote: > > From: Andi Kleen > > > > Currently sym and dso require printing ip and addr because > > the print function is tied to those outputs. With callindent > > it makes sense to p

[PATCH v2] regulator: fix kernel-doc function parameter and warning

From: Randy Dunlap Fix kernel-doc warning by using correct parameter description: ../drivers/regulator/core.c:4479: warning: Excess function parameter 'state' description in 'regulator_suspend' Signed-off-by: Randy Dunlap Cc: Liam Girdwood Cc: Mark Brown --- v2: add Cc:s and update patch de

Re: [PATCH] reiserfs: propagate errors from fill_with_dentries properly

On Thu, Aug 2, 2018 at 6:33 PM Jann Horn wrote: > > fill_with_dentries() failed to propagate errors up to > reiserfs_for_each_xattr() properly. Plumb them through. > > Note that reiserfs_for_each_xattr() is only used by > reiserfs_delete_xattrs() and reiserfs_chown_xattrs(). > The result of reiser

Re: [RFC][PATCH 1/5] [PATCH 1/5] kvm: register in task_struct

On 09/03/2018 04:10 PM, Nikita Leshenko wrote: > On September 2, 2018 5:21:15 AM, fengguang...@intel.com wrote: >> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c >> index 8b47507faab5..0c483720de8d 100644 >> --- a/virt/kvm/kvm_main.c >> +++ b/virt/kvm/kvm_main.c >> @@ -3892,6 +3892,7 @@

Re: [PATCH v12 07/12] livepatch: Use lists to manage patches, objects and functions

> -#define klp_for_each_object(patch, obj) \ > +#define klp_for_each_object_static(patch, obj) \ > for (obj = patch->objs; obj->funcs || obj->name; obj++) > > -#define klp_for_each_func(obj, func) \ > +#define klp_for_each_object(patch, obj) \ > + list_for_each_entry(obj, &patch-

Re: [PATCH] firewire: nosy: don't read packets bigger than requested

On 09/03/2018 08:55 AM, Jann Horn wrote: > On Fri, Jul 6, 2018 at 5:16 PM Jann Horn wrote: >> In general, accessing userspace memory beyond the length of the supplied >> buffer in VFS read/write handlers can lead to both kernel memory corruption >> (via kernel_read()/kernel_write(), which can e.g.

Re: [PATCH] firewire: nosy: don't read packets bigger than requested

On Fri, Jul 6, 2018 at 5:16 PM Jann Horn wrote: > In general, accessing userspace memory beyond the length of the supplied > buffer in VFS read/write handlers can lead to both kernel memory corruption > (via kernel_read()/kernel_write(), which can e.g. be triggered via > sys_splice()) and privileg

Re: [PATCH] HID: i2c-hid: Don't reset device upon system resume

Hi Benjamin, I forgot to include mailing list, first time -in-reply-to user :) at 17:39, Benjamin Tissoires wrote: On Mon, Sep 3, 2018 at 11:09 AM Kai-Heng Feng wrote: Raydium touchscreen triggers interrupt storm after system-wide suspend: [ 179.085033] i2c_hid i2c-CUST:00: i2c_hid_get_

<    3   4   5   6   7   8   9   10   11   >