[PATCH 4.20 072/111] omap2fb: Fix stack memory disclosure

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Tsyrklevich commit a01421e4484327fe44f8e126793ed5a48a221e24 upstream. Using [1] for static analysis I found that the OMAPFB_QUERY_PLANE, OMAPFB_GET_COLOR_KEY, OMAPFB_GET_DISPLAY_INFO,

[PATCH 4.20 064/111] pstore/ram: Avoid allocation and leak of platform data

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 5631e8576a3caf606cdc375f97425a67983b420c upstream. Yue Hu noticed that when parsing device tree the allocated platform data was never freed. Since it's not used beyond the

RE: [PATCH 1/1] remoteproc: fix recovery procedure

> -Original Message- > From: xiang xiao > Sent: lundi 21 janvier 2019 14:22 > To: Loic PALLARDY > Cc: Bjorn Andersson ; o...@wizery.com; > linux-remotep...@vger.kernel.org; linux-kernel@vger.kernel.org; Arnaud > POULIQUEN ; benjamin.gaign...@linaro.org; s- > a...@ti.com > Subject: Re:

[PATCH 4.20 063/111] net: dsa: realtek-smi: fix OF child-node lookup

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 3f1bb6abdf19cfa89860b3bc9e7f31b44b6a0ba1 upstream. Use the new of_get_compatible_child() helper to look up child nodes to avoid ever matching non-child nodes elsewhere in

[PATCH 4.20 060/111] kbuild: Disable LD_DEAD_CODE_DATA_ELIMINATION with ftrace & GCC <= 4.7

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Paul Burton commit 16fd20aa98080c2fa666dc384036ec08c80af710 upstream. When building using GCC 4.7 or older, -ffunction-sections & the -pg flag used by ftrace are incompatible. This causes

[PATCH 4.20 068/111] arm64: dts: marvell: armada-ap806: reserve PSCI area

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Heinrich Schuchardt commit 132ac39cffbcfed80ada38ef0fc6d34d95da7be6 upstream. The memory area [0x400-0x420[ is occupied by the PSCI firmware. Any attempt to access it from Linux leads

[PATCH 4.20 048/111] mips: fix n32 compat_ipc_parse_version

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 5a9372f751b5350e0ce3d2ee91832f1feae2c2e5 upstream. While reading through the sysvipc implementation, I noticed that the n32 semctl/shmctl/msgctl system calls behave

[PATCH 4.20 082/111] drm/vkms: Fix plane duplicate_state

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit 7cdf33ab02e01300e7e6289acbac9cd8759f8712 upstream. We need to handle allocation failures and bail out. While at it, tune the allocation failures down to debug level.

[PATCH 4.20 077/111] LSM: Check for NULL cred-security on free

4.20-stable review patch. If anyone has any objections, please let me know. -- From: James Morris commit a5795fd38ee8194451ba3f281f075301a3696ce2 upstream. From: Casey Schaufler Check that the cred security blob has been set before trying to clean it up. There is a case

[PATCH 4.20 076/111] ipv6: make icmp6_send() robust against null skb->dev

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 8d933670452107e41165bea70a30dffbd281bef1 upstream. syzbot was able to crash one host with the following stack trace : kasan: GPF could be caused by NULL-ptr deref or user

[PATCH 4.20 080/111] netfilter: ebtables: account ebt_table_info to kmemcg

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Shakeel Butt commit e2c8d550a973bb34fc28bc8d0ec996f84562fb8a upstream. The [ip,ip6,arp]_tables use x_tables_info internally and the underlying memory is already accounted to kmemcg. Do the

Re: [PATCH v10 3/3] dt-bindings: dma: uart: rename binding

On Fri, 18 Jan 2019 11:10:16 +0800, Long Cheng wrote: > The filename matches mtk-uart-apdma.c. > So using "mtk-uart-apdma.txt" should be better. > > Signed-off-by: Long Cheng > --- > .../devicetree/bindings/dma/8250_mtk_dma.txt | 33 > >

Re: [PATCHv2 1/3] perf report: Display s390 diagnostic counter sets

Em Mon, Jan 21, 2019 at 02:13:36PM +0100, Jiri Olsa escreveu: > On Sun, Jan 20, 2019 at 07:18:14PM +0100, Jiri Olsa wrote: > > On Thu, Jan 17, 2019 at 11:00:53AM -0300, Arnaldo Carvalho de Melo wrote: > > > > SNIP > > > > > --- a/tools/perf/util/python-ext-sources > > > +++

[PATCH 4.20 052/111] drm/i915/gvt: Fix mmap range check

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Zhenyu Wang commit 51b00d8509dc69c98740da2ad07308b630d3eb7d upstream. This is to fix missed mmap range check on vGPU bar2 region and only allow to map vGPU allocated GMADDR range, which means

[PATCH 4.20 083/111] gpu/drm: Fix lock held when returning to user space.

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit 4089e272ac61603931beb024d4d640de2cb390e0 upstream. We need to call drm_modeset_acquire_fini() when drm_atomic_state_alloc() failed or call drm_modeset_acquire_init() after

[PATCH 4.20 104/111] loop: Move special partition reread handling in loop_clr_fd()

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit d57f3374ba4817f7c8d26fae8a13d20ac8d31b92 upstream. The call of __blkdev_reread_part() from loop_reread_partition() happens only when we need to invalidate partitions from

[PATCH 4.20 102/111] loop: Push loop_ctl_mutex down to loop_set_fd()

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 757ecf40b7e029529768eb5f9562d5eeb3002106 upstream. Push lo_ctl_mutex down to loop_set_fd(). We will need this to be able to call loop_reread_partitions() without lo_ctl_mutex.

[PATCH 4.20 097/111] loop: Push lo_ctl_mutex down into individual ioctls

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit a13165441d58b216adbd50252a9cc829d78a6bce upstream. Push acquisition of lo_ctl_mutex down into individual ioctl handling branches. This is a preparatory step for pushing the

[PATCH 4.20 101/111] loop: Push loop_ctl_mutex down to loop_set_status()

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 550df5fdacff94229cde0ed9b8085155654c1696 upstream. Push loop_ctl_mutex down to loop_set_status(). We will need this to be able to call loop_reread_partitions() without

[PATCH 4.20 087/111] tipc: fix uninit-value in in tipc_conn_rcv_sub

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Ying Xue commit a88289f4ddee4165d5f796bd99e09eec3133c16b upstream. syzbot reported: BUG: KMSAN: uninit-value in tipc_conn_rcv_sub+0x184/0x950 net/tipc/topsrv.c:373 CPU: 0 PID: 66 Comm:

[PATCH 4.20 098/111] loop: Split setting of lo_state from loop_clr_fd

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit a2505b799a496b7b84d9a4a14ec870ff9e42e11b upstream. Move setting of lo_state to Lo_rundown out into the callers. That will allow us to unlock loop_ctl_mutex while the loop

[PATCH 4.20 096/111] loop: Get rid of loop_index_mutex

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 0a42e99b58a208839626465af194cfe640ef9493 upstream. Now that loop_ctl_mutex is global, just get rid of loop_index_mutex as there is no good reason to keep these two separate

[PATCH 4.20 050/111] MIPS: lantiq: Fix IPI interrupt handling

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Hauke Mehrtens commit 2b4dba55b04b212a7fd1f0395b41d79ee3a9801b upstream. This makes SMP on the vrx200 work again, by removing all the MIPS CPU interrupt specific code and making it fully use

[PATCH 4.20 088/111] tipc: fix uninit-value in tipc_nl_compat_link_reset_stats

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Ying Xue commit 8b66fee7f8ee18f9c51260e7a43ab37db5177a05 upstream. syzbot reports following splat: BUG: KMSAN: uninit-value in strlen+0x3b/0xa0 lib/string.c:486 CPU: 1 PID: 11057 Comm:

[PATCH 4.20 106/111] loop: Fix deadlock when calling blkdev_reread_part()

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 0da03cab87e6323ff2e05b14bc7d5c6fcc531efd upstream. Calling blkdev_reread_part() under loop_ctl_mutex causes lockdep to complain about circular lock dependency between

[PATCH 4.20 105/111] loop: Move loop_reread_partitions() out of loop_ctl_mutex

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 85b0a54a82e4fbceeb1aebb7cb6909edd1a24668 upstream. Calling loop_reread_partitions() under loop_ctl_mutex causes lockdep to complain about circular lock dependency between

[PATCH 4.20 109/111] loop: Fix double mutex_unlock(_ctl_mutex) in loop_control_ioctl()

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit 628bd85947091830a8c4872adfd5ed1d515a9cf2 upstream. Commit 0a42e99b58a20883 ("loop: Get rid of loop_index_mutex") forgot to remove mutex_unlock(_ctl_mutex) from

[PATCH 4.20 110/111] loop: drop caches if offset or block_size are changed

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 5db470e229e22b7eda6e23b5566e532c96fb5bc3 upstream. If we don't drop caches used in old offset or block_size, we can get old data from new offset/block_size, which gives

Re: [RFC PATCH] ALSA: core: Add DMA share buffer support

Dne 21.1.2019 v 13:40 Mark Brown napsal(a): > On Fri, Jan 18, 2019 at 08:39:32PM +0100, Takashi Iwai wrote: >> Mark Brown wrote: > multiple tasks). I would probably go in this way and add more extended permission control for the PCM device, so permissions can be restricted for the

[PATCH 4.20 091/111] tipc: fix uninit-value in tipc_nl_compat_name_table_dump

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Ying Xue commit 974cb0e3e7c963ced06c4e32c5b2884173fa5e01 upstream. syzbot reported: BUG: KMSAN: uninit-value in __arch_swab32 arch/x86/include/uapi/asm/swab.h:10 [inline] BUG: KMSAN:

[PATCH 4.20 092/111] tipc: fix uninit-value in tipc_nl_compat_doit

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Ying Xue commit 2753ca5d9009c180dbfd4c802c80983b4b6108d1 upstream. BUG: KMSAN: uninit-value in tipc_nl_compat_doit+0x404/0xa10 net/tipc/netlink_compat.c:335 CPU: 0 PID: 4514 Comm:

[PATCH 4.20 094/111] block/loop: Use global lock for ioctl() operation.

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit 310ca162d779efee8a2dc3731439680f3e9c1e86 upstream. syzbot is reporting NULL pointer dereference [1] which is caused by race condition between ioctl(loop_fd, LOOP_CLR_FD,

[PATCH 4.20 093/111] block/loop: Dont grab "struct file" for vfs_getattr() operation.

4.20-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit b1ab5fa309e6c49e4e06270ec67dd7b3e9971d04 upstream. vfs_getattr() needs "struct path" rather than "struct file". Let's use path_get()/path_put() rather than

Re: [PATCH] perf script: fix crash when processing recorded stat data

Em Mon, Jan 21, 2019 at 11:16:26AM +0530, Ravi Bangoria escreveu: > > > On 1/21/19 12:44 AM, Tony Jones wrote: > > While updating Perf to work with Python3 and Python2 I noticed that the > > stat-cpi script was dumping core. > > [...] > > Fixes: 1fcd03946b52 ("perf stat: Update per-thread

Re: [PATCH v1 07/12] usb: roles: Find the usb role switch by also matching against the device node

Hi, On Mon, Jan 21, 2019 at 04:36:13PM +0800, Chen Yu wrote: > Have the fwnode_get_name() patches been accepted? No, I didn't have a user for the function anymore: https://lkml.org/lkml/2018/12/17/284 > And I will be grateful if you can tell me your plan about the >

Verificacion de email

Web Admin Notificación de correo electrónico Este mensaje se envía desde nuestro centro de mensajería de Web Admin a todos nuestros propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a todos nuestros clientes de correo web. Su cuenta de correo electrónico se

[PATCH 4.14 16/59] bonding: update nest level on unlink

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 001e465f09a18857443489a57e74314a3368c805 ] A network device stack with multiple layers of bonding devices can trigger a false positive lockdep warning.

[PATCH 4.14 15/59] packet: Do not leak dev refcounts on error exit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gunthorpe [ Upstream commit d972f3dce8d161e2142da0ab1ef25df00e2f21a9 ] 'dev' is non NULL when the addr_len check triggers so it must goto a label that does the dev_put otherwise dev

Re: [PATCH 1/3] iommu/arm-smmu: Move to bitmap for arm_smmu_domain atrributes

On 21/01/2019 05:53, Vivek Gautam wrote: A number of arm_smmu_domain's attributes can be assigned based on the iommu domains's attributes. These local attributes better be managed by a bitmap. So remove boolean flags and move to a 32-bit bitmap, and enable each bits separtely. Signed-off-by:

RE: [PATCH 1/1] remoteproc: fix recovery procedure

> -Original Message- > From: xiang xiao > Sent: lundi 21 janvier 2019 13:45 > To: Loic PALLARDY > Cc: bjorn.anders...@linaro.org; o...@wizery.com; linux- > remotep...@vger.kernel.org; linux-kernel@vger.kernel.org; Arnaud > POULIQUEN ; benjamin.gaign...@linaro.org; s- > a...@ti.com >

[PATCH 4.14 13/59] ipv6: fix kernel-infoleak in ipv6_local_error()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7d033c9f6a7fd3821af75620a0257db87c2b552a ] This patch makes sure the flow label in the IPv6 header forged in ipv6_local_error() is initialized. BUG: KMSAN:

[PATCH 4.14 05/59] can: gw: ensure DLC boundaries after CAN frame modification

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Hartkopp commit 0aaa81377c5a01f686bcdb8c7a6929a7bf330c68 upstream. Muyu Yu provided a POC where user root with CAP_NET_ADMIN can create a CAN frame modification rule that makes the

[PATCH 4.14 26/59] scsi: sd: Fix cache_type_store()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Mironov commit 44759979a49bfd2d20d789add7fa81a21eb1a4ab upstream. Changing of caching mode via /sys/devices/.../scsi_disk/.../cache_type may fail if device responds to MODE SENSE command

[PATCH 4.14 21/59] crypto: authenc - fix parsing key with misaligned rta_len

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 8f9c469348487844328e162db57112f7d347c49f upstream. Keys for "authenc" AEADs are formatted as an rtattr containing a 4-byte 'enckeylen', followed by an authentication key

[PATCH 4.14 25/59] scsi: core: Synchronize request queue PM status only on successful resume

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stanley Chu commit 3f7e62bba0003f9c68f599f5997c4647ef5b4f4e upstream. The commit 356fd2663cff ("scsi: Set request queue runtime PM status back to active on resume") fixed up the inconsistent

[tip:sched/core] sched/topology: Introduce a sysctl for Energy Aware Scheduling

Commit-ID: 570139c80d73a5aa60c2500163378412b3836fc9 Gitweb: https://git.kernel.org/tip/570139c80d73a5aa60c2500163378412b3836fc9 Author: Quentin Perret AuthorDate: Mon, 3 Dec 2018 09:56:23 + Committer: Ingo Molnar CommitDate: Mon, 21 Jan 2019 14:40:28 +0100 sched/topology:

[PATCH 4.14 04/59] tty: Dont hold ldisc lock in tty_reopen() if ldisc present

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Safonov commit d3736d82e8169768218ee0ef68718875918091a0 upstream. Try to get reference for ldisc during tty_reopen(). If ldisc present, we don't need to do tty_ldisc_reinit() and lock

[PATCH 4.14 23/59] btrfs: wait on ordered extents on abort cleanup

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Josef Bacik commit 74d5d229b1bf60f93bff244b2dfc0eb21ec32a07 upstream. If we flip read-only before we initiate writeback on all dirty pages for ordered extents we've created then we'll have

[PATCH 4.14 19/59] crypto: authencesn - Avoid twice completion call in decrypt path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Harsh Jain commit a7773363624b034ab198c738661253d20a8055c2 upstream. Authencesn template in decrypt path unconditionally calls aead_request_complete after ahash_verify which leads to

[PATCH 4.14 09/59] Revert "scsi: target: iscsi: cxgbit: fix csk leak"

4.14-stable review patch. If anyone has any objections, please let me know. -- This reverts commit b831528038e3cad0d745c53bcaeedb642f5cbc1f. A wrong commit message was used for the stable commit because of a human error (and duplicate commit subject lines). This patch reverts

[PATCH 4.14 11/59] arm64/kvm: consistently handle host HCR_EL2 flags

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Backport of upstream commit 4eaed6aa2c628101246bcabc91b203bfac1193f8 ] In KVM we define the configuration of HCR_EL2 for a VHE HOST in HCR_HOST_VHE_FLAGS, but we don't have a similar definition for

[PATCH 4.14 41/59] LSM: Check for NULL cred-security on free

4.14-stable review patch. If anyone has any objections, please let me know. -- From: James Morris commit a5795fd38ee8194451ba3f281f075301a3696ce2 upstream. From: Casey Schaufler Check that the cred security blob has been set before trying to clean it up. There is a case

[tip:sched/core] sched/fair: Robustify CFS-bandwidth timer locking

Commit-ID: 3cd126af79ed5a4d6b06eba63d3349e143a3bd3b Gitweb: https://git.kernel.org/tip/3cd126af79ed5a4d6b06eba63d3349e143a3bd3b Author: Peter Zijlstra AuthorDate: Mon, 7 Jan 2019 13:52:31 +0100 Committer: Ingo Molnar CommitDate: Mon, 21 Jan 2019 14:40:28 +0100 sched/fair: Robustify

[PATCH 4.14 49/59] tipc: fix uninit-value in tipc_nl_compat_bearer_enable

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ying Xue commit 0762216c0ad2a2fccd63890648eca491f2c83d9a upstream. syzbot reported: BUG: KMSAN: uninit-value in strlen+0x3b/0xa0 lib/string.c:484 CPU: 1 PID: 6371 Comm: syz-executor652 Not

[PATCH 4.14 44/59] netfilter: ebtables: account ebt_table_info to kmemcg

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Shakeel Butt commit e2c8d550a973bb34fc28bc8d0ec996f84562fb8a upstream. The [ip,ip6,arp]_tables use x_tables_info internally and the underlying memory is already accounted to kmemcg. Do the

Re: [PATCH 3/4] dt-bindings: spi: Add the DMA properties for the SPI dma mode

On Tue, Jan 15, 2019 at 7:47 AM Baolin Wang wrote: > > From: Lanqing Liu The email address should be updated with unisoc.com. > Add the DMA properties for the SPI dma mode. > > Signed-off-by: Lanqing Liu > Signed-off-by: Baolin Wang > --- > Documentation/devicetree/bindings/spi/spi-sprd.txt

[PATCH 4.14 52/59] tipc: fix uninit-value in tipc_nl_compat_doit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ying Xue commit 2753ca5d9009c180dbfd4c802c80983b4b6108d1 upstream. BUG: KMSAN: uninit-value in tipc_nl_compat_doit+0x404/0xa10 net/tipc/netlink_compat.c:335 CPU: 0 PID: 4514 Comm:

Re: [PATCH] dmaengine: fsl-edma: dma map slave device address

Hi Angelo, On 18.01.2019 23:50, Angelo Dureghello wrote: > Hi Laurentiu, > > On Fri, Jan 18, 2019 at 12:06:23PM +0200, Laurentiu Tudor wrote: >> This mapping needs to be created in order for slave dma transfers >> to work on systems with SMMU. The implementation mostly mimics the >> one in pl330

[PATCH 4.14 47/59] sctp: allocate sctp_sockaddr_entry with kzalloc

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long commit 400b8b9a2a17918f8ce00786f596f530e7f30d50 upstream. The similar issue as fixed in Commit 4a2eb0c37b47 ("sctp: initialize sin6_flowinfo for ipv6 addrs in sctp_inet6addr_event")

[PATCH 4.14 33/59] media: v4l: ioctl: Validate num_planes for debug messages

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sakari Ailus commit 7fe9f01c04c2673bd6662c35b664f0f91888b96f upstream. The num_planes field in struct v4l2_pix_format_mplane is used in a loop before validating it. As the use is printing a

[PATCH 4.14 56/59] loop: Get rid of loop_index_mutex

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 0a42e99b58a208839626465af194cfe640ef9493 upstream. Now that loop_ctl_mutex is global, just get rid of loop_index_mutex as there is no good reason to keep these two separate

[PATCH 4.14 57/59] loop: Fix double mutex_unlock(_ctl_mutex) in loop_control_ioctl()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit 628bd85947091830a8c4872adfd5ed1d515a9cf2 upstream. Commit 0a42e99b58a20883 ("loop: Get rid of loop_index_mutex") forgot to remove mutex_unlock(_ctl_mutex) from

Re: [PATCH 0/3] pinctrl: meson: g12a fixes

On Thu, Jan 17, 2019 at 11:23 AM Jerome Brunet wrote: > This patchset fixes the initial pinctrl support added for th g12a SoC > family, which is mainly around the register regions claimed by the > driver. > > Linus, would it possible for you to provide a tag with these changes to > Kevin ?

[PATCH 4.14 55/59] loop: Fold __loop_release into loop_release

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 967d1dc144b50ad005e5eecdfadfbcfb3996 upstream. __loop_release() has a single call site. Fold it there. This is currently not a huge win but it will make following

[PATCH] mm: Remove duplicate header

Remove linux/ptrace.h which is included more than once Signed-off-by: Sabyasachi Gupta --- arch/nios2/mm/fault.c | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/nios2/mm/fault.c b/arch/nios2/mm/fault.c index 24fd84c..eb65f17 100644 --- a/arch/nios2/mm/fault.c +++ b/arch/nios2/mm/fault.c

[PATCH 4.14 34/59] pstore/ram: Avoid allocation and leak of platform data

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 5631e8576a3caf606cdc375f97425a67983b420c upstream. Yue Hu noticed that when parsing device tree the allocated platform data was never freed. Since it's not used beyond the

Re: [PATCH V2 2/2] dt-bindings: interrupt-controller: Update csky mpintc

On Fri, Jan 18, 2019 at 10:53 AM wrote: > > From: Guo Ren > > Add trigger type and priority setting for csky,mpintc. > > Signed-off-by: Guo Ren > --- > .../bindings/interrupt-controller/csky,mpintc.txt | 33 > +++--- > 1 file changed, 29 insertions(+), 4 deletions(-) > > diff

[PATCH 4.14 37/59] omap2fb: Fix stack memory disclosure

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Tsyrklevich commit a01421e4484327fe44f8e126793ed5a48a221e24 upstream. Using [1] for static analysis I found that the OMAPFB_QUERY_PLANE, OMAPFB_GET_COLOR_KEY, OMAPFB_GET_DISPLAY_INFO,

[PATCH 4.14 36/59] Disable MSI also when pcie-octeon.pcie_disable on

4.14-stable review patch. If anyone has any objections, please let me know. -- From: YunQiang Su commit a214720cbf50cd8c3f76bbb9c3f5c283910e9d33 upstream. Octeon has an boot-time option to disable pcie. Since MSI depends on PCI-E, we should also disable MSI also with this

[PATCH] mfd: Fix I2C_DESIGNWARE_PLATFORM dependencies

INTEL_SOC_PMIC, INTEL_SOC_PMIC_CHTWC and MFD_TPS68470 select the I2C_DESIGNWARE_PLATFORM without its dependencies making it possible to see warning and build error like below: WARNING: unmet direct dependencies detected for I2C_DESIGNWARE_PLATFORM Depends on [n]: I2C [=y] && HAS_IOMEM [=y] &&

[PATCH 4.14 40/59] bpf: in __bpf_redirect_no_mac pull mac only if present

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn commit e7c87bd6cc4ec7b0ac1ed0a88a58f8206c577488 upstream. Syzkaller was able to construct a packet of negative length by redirecting from bpf_prog_test_run_skb with

[PATCH 4.14 31/59] OF: properties: add missing of_node_put

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Julia Lawall commit 28b170e88bc0c7509e6724717c15cb4b5686026e upstream. Add an of_node_put when the result of of_graph_get_remote_port_parent is not available. The semantic match that finds

[PATCH 4.14 39/59] media: vivid: set min width/height to a value > 0

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 9729d6d282a6d7ce88e64c9119cecdf79edf4e88 upstream. The capture DV timings capabilities allowed for a minimum width and height of 0. So passing a timings struct with 0

Re: [PATCH 5/7] riscv: dts: add initial support for the SiFive FU540-C000 SoC

On Fri, Dec 14, 2018 at 09:21:52PM -0800, Paul Walmsley wrote: > Add initial support for the SiFive FU540-C000 SoC. This is a 28nm SoC > based around the SiFive U54-MC core complex and a TileLink > interconnect. > > This file is expected to grow considerably as more device drivers are > added to

Re: [tip:sched/core] PM/EM: Document the Energy Model framework

On Monday 21 Jan 2019 at 05:53:49 (-0800), tip-bot for Quentin Perret wrote: > Commit-ID: a6a2333618df721d942d37564f8c4b28d1f6924b > Gitweb: > https://git.kernel.org/tip/a6a2333618df721d942d37564f8c4b28d1f6924b > Author: Quentin Perret > AuthorDate: Thu, 10 Jan 2019 11:05:45 + >

Re: [PATCH] perf top: Fix wrong hottest instruction highlighted

Em Sun, Jan 20, 2019 at 07:40:43PM +0100, Jiri Olsa escreveu: > On Mon, Jan 21, 2019 at 12:05:22AM +0800, He Kuang wrote: > > Annotation line's percentage is compared and inserted into rbtree, but the > > percent field of 'struct annotation_data' is an array, the comparison > > result between them

Re: [PATCHv2 1/3] perf report: Display s390 diagnostic counter sets

On 01/21/2019 02:13 PM, Jiri Olsa wrote: > On Sun, Jan 20, 2019 at 07:18:14PM +0100, Jiri Olsa wrote: >> On Thu, Jan 17, 2019 at 11:00:53AM -0300, Arnaldo Carvalho de Melo wrote: >> >> SNIP >> >>> --- a/tools/perf/util/python-ext-sources >>> +++ b/tools/perf/util/python-ext-sources >>> @@ -25,6

[PATCH 4.9 11/51] arm64/kvm: consistently handle host HCR_EL2 flags

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Backport of upstream commit 4eaed6aa2c628101246bcabc91b203bfac1193f8 ] In KVM we define the configuration of HCR_EL2 for a VHE HOST in HCR_HOST_VHE_FLAGS, but we don't have a similar definition for

[PATCH 4.9 15/51] packet: Do not leak dev refcounts on error exit

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gunthorpe [ Upstream commit d972f3dce8d161e2142da0ab1ef25df00e2f21a9 ] 'dev' is non NULL when the addr_len check triggers so it must goto a label that does the dev_put otherwise dev will

[PATCH 4.9 16/51] bonding: update nest level on unlink

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 001e465f09a18857443489a57e74314a3368c805 ] A network device stack with multiple layers of bonding devices can trigger a false positive lockdep warning.

[PATCH 4.9 13/51] ipv6: fix kernel-infoleak in ipv6_local_error()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7d033c9f6a7fd3821af75620a0257db87c2b552a ] This patch makes sure the flow label in the IPv6 header forged in ipv6_local_error() is initialized. BUG: KMSAN:

[PATCH 4.9 02/51] tty: Hold tty_ldisc_lock() during tty_reopen()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Safonov commit 83d817f41070c48bc3eb7ec18e43000a548fca5c upstream. tty_ldisc_reinit() doesn't race with neither tty_ldisc_hangup() nor set_ldisc() nor tty_ldisc_release() as they use tty

[PATCH 4.9 22/51] Yama: Check for pid death before checking ancestry

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 9474f4e7cd71a633fa1ef93b7daefd44bbdfd482 upstream. It's possible that a pid has died before we take the rcu lock, in which case we can't walk the ancestry list as it may be

[PATCH 4.9 17/51] ip: on queued skb use skb_header_pointer instead of pskb_may_pull

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 4a06fa67c4da20148803525151845276cdb995c1 ] Commit 2efd4fca703a ("ip: in cmsg IP(V6)_ORIGDSTADDR call pskb_may_pull") avoided a read beyond the end of the skb

[PATCH 4.9 18/51] crypto: caam - fix zero-length buffer DMA mapping

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Aymen Sghaier commit 04e6d25c5bb244c1a37eb9fe0b604cc11a04e8c5 upstream. Recent changes - probably DMA API related (generic and/or arm64-specific) - exposed a case where driver maps a

Re: [PATCH RFC 13/24] mm: merge parameters for change_protection()

On Mon, Jan 21, 2019 at 03:57:11PM +0800, Peter Xu wrote: > change_protection() was used by either the NUMA or mprotect() code, > there's one parameter for each of the callers (dirty_accountable and > prot_numa). Further, these parameters are passed along the calls: > > -

[tip:sched/core] sched/doc: Document Energy Aware Scheduling

Commit-ID: 3948e120a22eb19276de2ecf9b5aea592af7031a Gitweb: https://git.kernel.org/tip/3948e120a22eb19276de2ecf9b5aea592af7031a Author: Quentin Perret AuthorDate: Thu, 10 Jan 2019 11:05:46 + Committer: Ingo Molnar CommitDate: Mon, 21 Jan 2019 14:40:28 +0100 sched/doc: Document

[PATCH 4.9 19/51] crypto: authencesn - Avoid twice completion call in decrypt path

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Harsh Jain commit a7773363624b034ab198c738661253d20a8055c2 upstream. Authencesn template in decrypt path unconditionally calls aead_request_complete after ahash_verify which leads to following

[PATCH 4.9 03/51] tty: Simplify tty->count math in tty_reopen()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Safonov commit cf62a1a13749db0d32b5cdd800ea91a4087319de upstream. As notted by Jiri, tty_ldisc_reinit() shouldn't rely on tty counter. Simplify math by increasing the counter after

[PATCH 4.9 28/51] mfd: tps6586x: Handle interrupts on suspend

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jonathan Hunter commit ac4ca4b9f4623ba5e1ea7a582f286567c611e027 upstream. The tps6586x driver creates an irqchip that is used by its various child devices for managing interrupts. The

[PATCH 4.9 27/51] mips: fix n32 compat_ipc_parse_version

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 5a9372f751b5350e0ce3d2ee91832f1feae2c2e5 upstream. While reading through the sysvipc implementation, I noticed that the n32 semctl/shmctl/msgctl system calls behave

[PATCH 4.9 31/51] omap2fb: Fix stack memory disclosure

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Tsyrklevich commit a01421e4484327fe44f8e126793ed5a48a221e24 upstream. Using [1] for static analysis I found that the OMAPFB_QUERY_PLANE, OMAPFB_GET_COLOR_KEY, OMAPFB_GET_DISPLAY_INFO, and

[PATCH 4.9 09/51] Revert "scsi: target: iscsi: cxgbit: fix csk leak"

4.9-stable review patch. If anyone has any objections, please let me know. -- This reverts commit 8323aafe67b31c7f73d18747604ba1cc6c3e4f3a. A wrong commit message was used for the stable commit because of a human error (and duplicate commit subject lines). This patch reverts

[PATCH 4.19 12/99] netfilter: nf_conncount: speculative garbage collection on empty lists

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Pablo Neira Ayuso commit c80f10bc973af2ace6b1414724eeff61eaa71837 upstream. Instead of removing a empty list node that might be reintroduced soon thereafter, tentatively place the empty list

[PATCH 4.19 14/99] mmc: sdhci-msm: Disable CDR function on TX

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Loic Poulain commit a89e7bcb18081c611eb6cf50edd440fa4983a71a upstream. The Clock Data Recovery (CDR) circuit allows to automatically adjust the RX sampling-point/phase for high frequency

[PATCH 4.19 19/99] arm64: Dont trap host pointer auth use to EL2

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b3669b1e1c09890d61109a1a8ece2c5b66804714 ] To allow EL0 (and/or EL1) to use pointer authentication functionality, we must ensure that pointer authentication instructions and

[PATCH 4.19 18/99] arm64/kvm: consistently handle host HCR_EL2 flags

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4eaed6aa2c628101246bcabc91b203bfac1193f8 ] In KVM we define the configuration of HCR_EL2 for a VHE HOST in HCR_HOST_VHE_FLAGS, but we don't have a similar definition for the non-VHE

[PATCH 4.19 23/99] tcp: change txhash on SYN-data timeout

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Yuchung Cheng [ Upstream commit c5715b8fabfca0ef85903f8bad2189940ed41cc8 ] Previously upon SYN timeouts the sender recomputes the txhash to try a different path. However this does not apply

[PATCH 4.19 27/99] r8169: dont try to read counters if chip is in a PCI power-save state

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 10262b0b53666cbc506989b17a3ead1e9c3b43b4 ] Avoid log spam caused by trying to read counters from the chip whilst it is in a PCI power-save state. Reference:

[PATCH 4.19 29/99] ip: on queued skb use skb_header_pointer instead of pskb_may_pull

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 4a06fa67c4da20148803525151845276cdb995c1 ] Commit 2efd4fca703a ("ip: in cmsg IP(V6)_ORIGDSTADDR call pskb_may_pull") avoided a read beyond the end of the

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