Re: [PATCH] x86/xen: clean up clang build warning

On 18/09/17 10:38, Colin King wrote: > From: Colin Ian King > > In the case where sizeof(maddr) != sizeof(long) p is initialized and > never read and clang throws a warning on this. Move declaration of > p to clean up the clang build warning: > > warning: Value stored

[PATCH] ASoC: zte: spdif: remove duplicate initialization of dma_data

From: Colin Ian King dma_data is being initialized twice, remove the unused first initialization and use the latter one instead. Fixed clang warning: "warning: Value stored to 'dma_data' during its initialization is never read" Signed-off-by: Colin Ian King

Re: [PATCH RFC V2 00/10] perf top optimization

On Sun, Sep 10, 2017 at 07:23:13PM -0700, kan.li...@intel.com wrote: > From: Kan Liang > > The patch series intends to fix the severe performance issue in > Knights Landing/Mill, when monitoring in heavy load system. > perf top costs a few minutes to show the result, which

[PATCH 4.9 25/78] ip_tunnel: fix setting ttl and tos value in collect_md mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Haishuang Yan [ Upstream commit 0f693f1995cf002432b70f43ce73f79bf8d0b6c9 ] ttl and tos variables are declared and assigned, but are not used in

[PATCH 4.9 33/78] xfs: push buffer of flush locked dquot to avoid quotacheck deadlock

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 7912e7fef2aebe577f0b46d3cba261f2783c5695 upstream. Reclaim during quotacheck can lead to deadlocks on the dquot flush lock: - Quotacheck populates a

[PATCH 4.9 07/78] sctp: Avoid out-of-bounds reads from address storage

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit ee6c88bb754e3d363e568da78086adfedb692447 ] inet_diag_msg_sctp{,l}addr_fill() and sctp_get_sctp_info() copy sizeof(sockaddr_storage) bytes

[PATCH 4.9 29/78] x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 9584d98bed7a7a904d0702ad06bbcc94703cb5b4 upstream. In ELF_COPY_CORE_REGS, we're copying from the current task, so accessing thread.fsbase and

[PATCH 4.9 11/78] packet: Dont write vnet header beyond end of buffer

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Poirier [ Upstream commit edbd58be15a957f6a760c4a514cd475217eb97fd ] ... which may happen with certain values of tp_reserve and maclen. Fixes: 58d19b19cd99

[PATCH 4.9 30/78] x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit e137a4d8f4dd2e277e355495b6b2cb241a8693c3 upstream. Switching FS and GS is a mess, and the current code is still subtly wrong: it assumes that "Loading a

[PATCH 4.9 27/78] f2fs: check hot_data for roll-forward recovery

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 125c9fb1ccb53eb2ea9380df40f3c743f3fb2fed upstream. We need to check HOT_DATA to truncate any previous data block when doing roll-forward recovery.

[PATCH 4.9 57/78] xfs: always verify the log tail during recovery

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 5297ac1f6d7cbf45464a49b9558831f271dfc559 upstream. Log tail verification currently only occurs when torn writes are detected at the head of the log.

[PATCH 4.9 41/78] xfs: check _btree_check_block value

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Darrick J. Wong" commit 1e86eabe73b73c82e1110c746ed3ec6d5e1c0a0d upstream. Check the _btree_check_block return value for the firstrec and lastrec functions, since we

[PATCH 4.9 08/78] qlge: avoid memcpy buffer overflow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit e58f95831e7468d25eb6e41f234842ecfe6f014f ] gcc-8.0.0 (snapshot) points out that we copy a variable-length string into a fixed length field using

[PATCH 4.9 47/78] xfs: fix inobt inode allocation search optimization

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Omar Sandoval commit c44245b3d5435f533ca8346ece65918f84c057f9 upstream. When we try to allocate a free inode by searching the inobt, we try to find the inode nearest the

[PATCH] ASoC: qcom: remove duplicate initializations of dma_ch and v

From: Colin Ian King dma_ch is being initialized to zero and then immediately afterwards being updated again, so the first initialization is redundant and can be remove. Likewise, the pointer v is being initialized twice, so remove the second duplicate initialization.

[PATCH 4.9 48/78] xfs: clear MS_ACTIVE after finishing log recovery

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Darrick J. Wong" commit 8204f8ddaafafcae074746fcf2a05a45e6827603 upstream. Way back when we established inode block-map redo log items, it was discovered that we

Re: [PATCH v4 2/3] media: ov7670: Add the get_fmt callback

Hi Sakari, On 2017/9/18 15:36, Sakari Ailus wrote: Hi Wenyou, On Mon, Sep 18, 2017 at 02:45:13PM +0800, Wenyou Yang wrote: @@ -998,8 +1002,15 @@ static int ov7670_set_fmt(struct v4l2_subdev *sd, ret = ov7670_try_fmt_internal(sd, >format, NULL, NULL); if (ret)

[PATCH 4.12 41/52] ipv6: fix memory leak with multiple tables during netns destruction

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit ba1cc08d9488c94cb8d94f545305688b72a2a300 ] fib6_net_exit only frees the main and local tables. If another table was created with

Re: [PATCH v3 0/3] STM32 CRYP crypto driver

Just a gentle ping ... or have I missed out on a reply? On 18/08/17 11:19, Fabien Dessenne wrote: > This set of patches adds a new crypto driver for STMicroelectronics stm32 HW. > This drivers uses the crypto API and provides with HW-enabled AEAD and block > cipher algorithms. > It makes use of

[PATCH 4.12 39/52] vhost_net: correctly check tx avail during rx busy polling

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit 8b949bef9172ca69d918e93509a4ecb03d0355e0 ] We check tx avail through vhost_enable_notify() in the past which is wrong since it only checks

Re: [kernel-hardening] Re: [PATCH v4] security/keys: rewrite all of big_key crypto

Am Montag, 18. September 2017, 11:04:55 CEST schrieb Greg KH: Hi Greg, > On Mon, Sep 18, 2017 at 10:49:56AM +0200, Stephan Mueller wrote: > > Am Samstag, 16. September 2017, 15:00:34 CEST schrieb Jason A. Donenfeld: > > > > Hi Jason, > > > > > This started out as just replacing the use of

[PATCH 4.12 40/52] ip6_gre: update mtu properly in ip6gre_err

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 5c25f30c93fdc5bf25e62101aeaae7a4f9b421b3 ] Now when probessing ICMPV6_PKT_TOOBIG, ip6gre_err only subtracts the offset of gre header from mtu

[PATCH 4.12 05/52] udp: on peeking bad csum, drop packets even if not at head

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit fd6055a806edc4019be1b9fb7d25262599bca5b1 ] When peeking, if a bad csum is discovered, the skb is unlinked from the queue with

[PATCH 4.12 09/52] qlge: avoid memcpy buffer overflow

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit e58f95831e7468d25eb6e41f234842ecfe6f014f ] gcc-8.0.0 (snapshot) points out that we copy a variable-length string into a fixed length field

[PATCH 4.12 21/52] kcm: do not attach PF_KCM sockets to avoid deadlock

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 351050ecd6523374b370341cc29fe61e2201556b ] syzkaller had no problem to trigger a deadlock, attaching a KCM socket to another one (or

[PATCH 4.12 12/52] net: bcmgenet: Be drop monitor friendly

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit d4fec855905fa8bd5fb1c59f73ad2d74a944876a ] There are 3 spots where we call dev_kfree_skb() but we are actually just doing a normal

[PATCH 4.12 13/52] net: systemport: Free DMA coherent descriptors on errors

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit c2062ee3d9615828109ffe8089fbf69bed394d05 ] In case bcm_sysport_init_tx_ring() is not able to allocate ring->cbs, we would return with

[PATCH] ASoC: hdmi-codec: use sizeof_field rather than declaring hcp

From: Colin Ian King Use FIELD_SIZEOF rather than declaring and initializing hcp. Remove unused variables. Cleans up clang warning: warning: Value stored to 'hcp' during its initialization is never read Signed-off-by: Colin Ian King ---

[PATCH 4.12 15/52] udp6: set rx_dst_cookie on rx_dst updates

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni [ Upstream commit 64f0f5d18a47c703c85576375cc010e83dac6a48 ] Currently, in the udp6 code, the dst cookie is not initialized/updated concurrently with the RX

[PATCH 4.13 28/52] xfs: Add infrastructure needed for error propagation during buffer IO failure

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Carlos Maiolino commit 0b80ae6ed13169bd3a244e71169f2cc020b0c57a upstream. With the current code, XFS never re-submit a failed buffer for IO, because the failed item in

[PATCH 4.13 25/52] libnvdimm: fix integer overflow static analysis warning

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 58738c495e15badd2015e19ff41f1f1ed55200bc upstream. Dan reports: The patch 62232e45f4a2: "libnvdimm: control (ioctl) messages for

[PATCH 4.13 24/52] libnvdimm, btt: check memory allocation failure

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Jaillet commit ed36b4dba54a421ce5551638f6a9790b2c2116b1 upstream. Check memory allocation failures and return -ENOMEM in such cases, as already done

[PATCH 4.13 26/52] xfs: write unmount record for ro mounts

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit 757a69ef6cf2bf839bd4088e5609d663b0c4 upstream. There are dueling comments in the xfs code about intent for log writes when unmounting a readonly

Re: [PATCH v2 5/9] mtd: nand: atmel: Report PMECC failures as errors

Hi Romain, On Fri, 15 Sep 2017 16:04:07 +0200 Romain Izard wrote: > It is not normal for the PMECC to fail when trying to fix ECC errors. > Report these cases as errors. I'm not sure we want to have ECC error messages at this level. ECC errors are rather unusual but

[PATCH 4.13 01/52] Revert "net: use lib/percpu_counter API for fragmentation mem accounting"

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Jesper Dangaard Brouer [ Upstream commit fb452a1aa3fd4034d7999e309c5466ff2d7005aa ] This reverts commit 6d7b857d541ecd1d9bd997c97242d4ef94b19de2. There is a bug in

[PATCH 4.13 00/52] 4.13.3-stable review

This is the start of the stable review cycle for the 4.13.3 release. There are 52 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 20 09:08:28 UTC 2017. Anything

[PATCH 4.13 03/52] gianfar: Fix Tx flow control deactivation

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Claudiu Manoil [ Upstream commit 5d621672bc1a1e5090c1ac5432a18c79e0e13e03 ] The wrong register is checked for the Tx flow control bit, it should have been maccfg1 not

[PATCH 4.13 02/52] Revert "net: fix percpu memory leaks"

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Jesper Dangaard Brouer [ Upstream commit 5a63643e583b6a9789d7a225ae076fb4e603991c ] This reverts commit 1d6119baf0610f813eb9d9580eb4fd16de5b4ceb. After reverting commit

Re: [PATCH v4 00/14] mpt3sas driver NVMe support:

Hi Martin, On Fri, Sep 15, 2017 at 6:37 AM, Martin K. Petersen wrote: > > Suganath, > >> Is there any update on the submitted mpt3sas patches. > > We are waiting for you to report back your findings on PRP vs. SGL. We are working on this, since there is h/w

[RESEND PATCH v2 1/3] ASoC: rockchip: Add dapm route for HDMI

Add dapm route for DP codec. Signed-off-by: Jeffy Chen --- Changes in v2: Separate HDMI/DMIC patches. sound/soc/rockchip/rk3399_gru_sound.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sound/soc/rockchip/rk3399_gru_sound.c

[RESEND PATCH v2 2/3] ASoC: rockchip: Add dapm route for DMic

Add dapm route for DMIC codec. Signed-off-by: Jeffy Chen --- Changes in v2: None sound/soc/rockchip/rk3399_gru_sound.c | 1 + 1 file changed, 1 insertion(+) diff --git a/sound/soc/rockchip/rk3399_gru_sound.c b/sound/soc/rockchip/rk3399_gru_sound.c index

[PATCH v5 1/5] ARM: dts: imx6qdl-icore: Add Sound card support

From: Jagan Teki Linux Sound card now uses generic simple-audio-card, so add the same along with related audmux and codec(via u2c3) for i.CoreM6 QDL module boards. Cc: Shawn Guo Cc: Matteo Lisi Cc: Michael Trimarchi

Re: [PATCH] ARM: dts: dra7: Set a default parent to mcasp3_ahclkx_mux

On Wednesday 06 September 2017 07:09 PM, Keerthy wrote: > Assign a default parent to mcasp3_ahclkx_mux clock using > the assigned-clock-parents property. This is helpful in > cases like kexec where in the clock parent can be something > other than the value at reset. Hi Tony, A gentle ping on

[PATCH v2 1/2] ARC: reset: add missing DT binding documentation for HSDKv1 reset driver

From: Eugeniy Paltsev When applying the original patch [1], the DT binding docs were lost. This patch adds them back. [1] https://patchwork.kernel.org/patch/9852997/ Fixes: e0be864f1424 ("ARC: reset: introduce HSDKv1 reset driver") Signed-off-by: Eugeniy Paltsev

[PATCH v2 2/2] ARC: reset: remove the misleading v1 suffix all over

From: Vineet Gupta There is no plan yet to do a v2 board. And even if we were to do it only some IPs would actually change, so it be best to add suffixes at that point, not now ! Signed-off-by: Vineet Gupta Signed-off-by: Philipp Zabel

[PATCH v4] PCI: quirks: update Cavium ThunderX ACS quirk implementation

This commit makes Cavium PCI ACS quirk applicable only to Cavium ThunderX (CN81/83/88XX) PCIE Root Ports which has limited PCI capabilities in terms of no ACS support advertisement. However, the RTL internally implements similar protection as if ACS had completion/request redirection, upstream

Re: 答复: 答复: [PATCH] mfd: rtsx: Add support for RTS5260

On Fri, 15 Sep 2017, 冯锐 wrote: > > On Thu, 14 Sep 2017, 冯锐 wrote: > > > > > On Fri, 08 Sep 2017, rui_f...@realsil.com.cn wrote: > > > > > > > From: rui_feng > > > > > > > > Add support for new chip rts5260. > > > > > > You are adding over 600 lines in this patch. It

Re: [PATCH v2 2/2] lockdep: Remove unnecessary acquisitions wrt workqueue flush

On Fri, Sep 08, 2017 at 05:46:25PM +0900, Byungchul Park wrote: > The workqueue added manual acquisitions to catch deadlock cases. > Now crossrelease was introduced, some of those are redundant, since > wait_for_completion() already includes the acquisition for itself. > Removed it. Now,

Re: [PATCH v4] security/keys: rewrite all of big_key crypto

Am Samstag, 16. September 2017, 15:00:34 CEST schrieb Jason A. Donenfeld: Hi Jason, > This started out as just replacing the use of crypto/rng with > get_random_bytes_wait, This change is a challenge. The use of the kernel crypto API's DRNG has been made to allow FIPS 140-2 compliance.

Re: [PATCH v5 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

Hi Leon, Thanks for the update. Please see my comments below. On Fri, Sep 15, 2017 at 03:49:52PM +0800, Leon Luo wrote: > The imx274 is a Sony CMOS image sensor that has 1/2.5 image size. > It supports up to 3840x2160 (4K) 60fps, 1080p 120fps. The interface > is 4-lane MIPI CSI-2 running at

Re: [PATCH 3/3] ima: use fs method to read integrity data (updated patch description)

Hi, On 17/09/17 17:38, Al Viro wrote: On Sun, Sep 17, 2017 at 09:34:01AM -0700, Linus Torvalds wrote: Now, I suspect most (all?) do, but that's a historical artifact rather than "design". In particular, the VFS layer used to do the locking for the filesystems, to guarantee the POSIX

[PATCH 4.13 20/52] x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison pages

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit ce0fa3e56ad20f04d8252353dcd24e924abdafca upstream. Speculative processor accesses may reference any memory that has a valid page table entry. While a

Re: [PATCH][V2] i2c: i2c-stm32f7: make structure stm32f7_setup static const

On 09/18/2017 10:15 AM, Colin King wrote: > From: Colin Ian King > > The structure stm32f7_setup is local to the source and does not need > to be in global scope, make it static const. > > Cleans up sparse warning: > symbol 'stm32f7_setup' was not declared. Should it

[PATCH 4.9 77/78] xfs: use kmem_free to free return value of kmem_zalloc

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Pan Bian commit 6c370590cfe0c36bcd62d548148aa65c984540b7 upstream. In function xfs_test_remount_options(), kfree() is used to free memory allocated by kmem_zalloc(). But

[PATCH 4.9 76/78] xfs: open code end_buffer_async_write in xfs_finish_page_writeback

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 8353a814f2518dcfa79a5bb77afd0e7dfa391bb1 upstream. Our loop in xfs_finish_page_writeback, which iterates over all buffer heads in a page and then calls

[PATCH v4] [DVB][FRONTEND] Added a new ioctl for optimizing frontend property set operation

Hello Mr Chehab, It seems that there is a mismatch among tab spacing in local patch on my PC, the patch in email and the patch in lkml site. This is causing alignment problem. Even if I fix alignment problem in my PC, alignment is different in lkml and email. Anyway, I have run checkpatch and got

[PATCH 4.9 17/78] Revert "net: use lib/percpu_counter API for fragmentation mem accounting"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jesper Dangaard Brouer [ Upstream commit fb452a1aa3fd4034d7999e309c5466ff2d7005aa ] This reverts commit 6d7b857d541ecd1d9bd997c97242d4ef94b19de2. There is a bug in

[PATCH 4.9 18/78] Revert "net: fix percpu memory leaks"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jesper Dangaard Brouer [ Upstream commit 5a63643e583b6a9789d7a225ae076fb4e603991c ] This reverts commit 1d6119baf0610f813eb9d9580eb4fd16de5b4ceb. After reverting commit

[PATCH 4.9 10/78] cxgb4: Fix stack out-of-bounds read due to wrong size to t4_record_mbox()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit 0f3086868e8889a823a6e0f3d299102aa895d947 ] Passing commands for logging to t4_record_mbox() with size MBOX_LEN, when the actual command

[PATCH 4.9 19/78] gianfar: Fix Tx flow control deactivation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Claudiu Manoil [ Upstream commit 5d621672bc1a1e5090c1ac5432a18c79e0e13e03 ] The wrong register is checked for the Tx flow control bit, it should have been maccfg1 not

[PATCH 4.13 29/52] xfs: Properly retry failed inode items in case of error during buffer writeback

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Carlos Maiolino commit d3a304b6292168b83b45d624784f973fdc1ca674 upstream. When a buffer has been failed during writeback, the inode items into it are kept flush locked,

[PATCH 4.13 30/52] xfs: fix recovery failure when log record header wraps log end

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 284f1c2c9bebf871861184b0e2c40fa921dd380b upstream. The high-level log recovery algorithm consists of two loops that walk the physical log and process

[PATCH 4.13 13/52] f2fs: check hot_data for roll-forward recovery

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 125c9fb1ccb53eb2ea9380df40f3c743f3fb2fed upstream. We need to check HOT_DATA to truncate any previous data block when doing roll-forward recovery.

[PATCH 4.13 11/52] ip_tunnel: fix setting ttl and tos value in collect_md mode

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Haishuang Yan [ Upstream commit 0f693f1995cf002432b70f43ce73f79bf8d0b6c9 ] ttl and tos variables are declared and assigned, but are not used in

[PATCH 2/3] iio: trigger: stm32-timer: fix a corner case to write preset

Balance timer start routine that sets ARPE: clear it in stop routine. This fixes a corner case, when timer is used successively as trigger (with sampling_frequency start/stop routines), then as a counter (with preset). Fixes: 93fbe91b5521 ("iio: Add STM32 timer trigger driver") Signed-off-by:

[PATCH 3/3] iio: trigger: stm32-timer: enable clock when in master mode

Clock should be enabled as soon as using master mode, even before enabling timer. Or, this may provoke bad behavior on the other end (slave timer). Then, introduce 'clk_enabled' flag, instead of relying on CR1 EN bit, to keep track of clock being enabled. Propagate this anywhere else in the

Re: [PATCH] mm: introduce sanity check on dirty ratio sysctl value

On Mon 18-09-17 01:39:28, Yafang Shao wrote: > we can find the logic in domain_dirty_limits() that > when dirty bg_thresh is bigger than dirty thresh, > bg_thresh will be set as thresh * 1 / 2. > if (bg_thresh >= thresh) > bg_thresh = thresh / 2; > > But actually we can set

[PATCH] KVM: x86: Fix the NULL pointer parameter in check_cr_write()

Routine check_cr_write() will trigger emulator_get_cpuid()-> kvm_cpuid() to get maxphyaddr, and NULL is passed as values for ebx/ecx/edx. This is problematic because kvm_cpuid() will dereference these pointers. Fixes: d1cd3ce90044 ("KVM: MMU: check guest CR3 reserved bits based on its physical

Re: [PATCH] arm: omap: dra7xx: Set OPT_CLKS_IN_RESET flag for gpio1

On Wednesday 06 September 2017 04:03 PM, Keerthy wrote: > gpio1 soft reset fails in the kexec path as the optional clock > is not enabled hence enable the HWMOD_CONTROL_OPT_CLKS_IN_RESET > flag for gpio1 hwmod. A gentle ping on this as well. > > Signed-off-by: Keerthy > ---

Re: [PATCH v2 2/2] ARC: reset: remove the misleading v1 suffix all over

On Mon, 2017-09-18 at 13:48 +0200, Philipp Zabel wrote: > From: Vineet Gupta > > There is no plan yet to do a v2 board. And even if we were to do it > only > some IPs would actually change, so it be best to add suffixes at that > point, not now ! > > Signed-off-by:

Re: [RESEND PATCH v4 0/2] add thermal nodes for UniPhier SoCs

2017-09-04 15:58 GMT+09:00 Kunihiko Hayashi : > This series adds thermal nodes for UniPhier PXs2 and LD20 SoCs. > > Resending the patches to apply the missing comments, > please ignore previous v4. > > Changes since v3: > - use the dt-bindings header to replace the

[PATCH 3/3] dt-bindings: Add KINGDISPLAY KD097D04 panel bindings

The KINGDISPLAY KD097D04 is a 9.7" panel with a 1536x2048 resolution and connected to DSI using 8 lanes. Signed-off-by: Nickey Yang --- .../display/panel/kingdisplay,kd097d04.txt | 22 ++ 1 file changed, 22 insertions(+) create mode

Re: [PATCH v7 2/8] mfd: wm97xx-core: core support for wm97xx Codec

On Thu, 14 Sep 2017, Mark Brown wrote: > On Thu, Sep 14, 2017 at 08:43:00AM +0100, Lee Jones wrote: > > > Change of plan. It looks like there are deps. > > > Unapplied. > > The core stuff went in during the merge window, you should be able to > wait for -rc1 or pick up the asoc-v4.14 tag.

[PATCH 4.13 14/52] thunderbolt: Remove superfluous check

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Bernat, Yehezkel commit 8fdd6ab36197ad891233572c57781b1f537da0ac upstream. The key size is tested by hex2bin() already (as '\0' isn't an hex digit) Suggested-by:

[PATCH 4.13 05/52] ip6_gre: update mtu properly in ip6gre_err

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 5c25f30c93fdc5bf25e62101aeaae7a4f9b421b3 ] Now when probessing ICMPV6_PKT_TOOBIG, ip6gre_err only subtracts the offset of gre header from mtu

[PATCH 4.13 07/52] ipv6: fix memory leak with multiple tables during netns destruction

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit ba1cc08d9488c94cb8d94f545305688b72a2a300 ] fib6_net_exit only frees the main and local tables. If another table was created with

[PATCH 4.13 12/52] f2fs: let fill_super handle roll-forward errors

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit afd2b4da40b3b567ef8d8e6881479345a2312a03 upstream. If we set CP_ERROR_FLAG in roll-forward error, f2fs is no longer to proceed any IOs due to

[PATCH 4.13 18/52] x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 9584d98bed7a7a904d0702ad06bbcc94703cb5b4 upstream. In ELF_COPY_CORE_REGS, we're copying from the current task, so accessing thread.fsbase and

[PATCH 4.13 04/52] vhost_net: correctly check tx avail during rx busy polling

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit 8b949bef9172ca69d918e93509a4ecb03d0355e0 ] We check tx avail through vhost_enable_notify() in the past which is wrong since it only checks

[PATCH 4.13 21/52] ovl: fix false positive ESTALE on lookup

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Amir Goldstein commit 939ae4efd51c627da270af74ef069db5124cb5b0 upstream. Commit b9ac5c274b8c ("ovl: hash overlay non-dir inodes by copy up origin") verifies that the

[PATCH 4.9 45/78] xfs: fix multi-AG deadlock in xfs_bunmapi

4.9-stable review patch. If anyone has any objections, please let me know. -- commit 5b094d6dac0451ad89b1dc088395c7b399b7e9e8 upstream. Just like in the allocator we must avoid touching multiple AGs out of order when freeing blocks, as freeing still locks the AGF and can cause

[PATCH 4.9 68/78] xfs: dont log dirty ranges for ordered buffers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 8dc518dfa7dbd079581269e51074b3c55a65a880 upstream. Ordered buffers are attached to transactions and pushed through the logging infrastructure just like

[PATCH 4.9 70/78] xfs: move bmbt owner change to last step of extent swap

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 6fb10d6d22094bc4062f92b9ccbcee2f54033d04 upstream. The extent swap operation currently resets bmbt block owners before the inode forks are swapped. The

[PATCH 4.9 62/78] xfs: evict all inodes involved with log redo item

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Darrick J. Wong" commit 799ea9e9c59949008770aab4e1da87f10e99dbe4 upstream. When we introduced the bmap redo log items, we set MS_ACTIVE on the mountpoint and

[PATCH] kbuild: deb-pkg: remove firmware package support

Commit 5620a0d1aacd ("firmware: delete in-kernel firmware") deleted in-kernel firmware support, including the firmware install command. So, the firmware package does not make sense any more. Remove it. Signed-off-by: Masahiro Yamada --- scripts/package/builddeb

[PATCH v3] irq_work: improve the flag definitions

IRQ_WORK_FLAGS is defined simply to 3UL. This is confusing as it says nothing about its purpose. Define IRQ_WORK_FLAGS as a bitwise OR of IRQ_WORK_PENDING and IRQ_WORK_BUSY and change its name to IRQ_WORK_CLAIMED. While we're at it: use the BIT() macro for all flags. Signed-off-by: Bartosz

[PATCH 4.9 20/78] vhost_net: correctly check tx avail during rx busy polling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit 8b949bef9172ca69d918e93509a4ecb03d0355e0 ] We check tx avail through vhost_enable_notify() in the past which is wrong since it only checks

[PATCH 4.9 22/78] ipv6: fix memory leak with multiple tables during netns destruction

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit ba1cc08d9488c94cb8d94f545305688b72a2a300 ] fib6_net_exit only frees the main and local tables. If another table was created with

[PATCH 4.9 24/78] sctp: fix missing wake ups in some situations

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner [ Upstream commit 7906b00f5cd1cd484fced7fcda892176e3202c8a ] Commit fb586f25300f ("sctp: delay calls to sk_data_ready() as much as

Re: [PATCH] tools/kvm_stat: Add Python 3 support to kvm_stat

On Sun, Sep 17, 2017 at 05:49:51PM +, Jeremy Cline wrote: > Make kvm_stat support Python 3 by changing the use of "print" to a > function rather than a statement and switching from "iteritems" (removed > in Python 3) to "items". > > With this change, kvm_stat is usable with Python 2.6 and

[PATCH 4.9 23/78] ipv6: fix typo in fib6_net_exit()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 32a805baf0fb70b6dbedefcd7249ac7f580f9e3b ] IPv6 FIB should use FIB6_TABLE_HASHSZ, not FIB_TABLE_HASHSZ. Fixes: ba1cc08d9488 ("ipv6: fix

[PATCH 4.12 06/52] bpf: fix map value attribute for hash of maps

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit 33ba43ed0afc13a29b1314e3e45a9938d310ba13 ] Currently, iproute2's BPF ELF loader works fine with array of maps when retrieving the fd

[PATCH 4.12 02/52] ipv6: add rcu grace period before freeing fib6_node

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Wei Wang [ Upstream commit c5cff8561d2d0006e972bd114afd51f082fee77c ] We currently keep rt->rt6i_node pointing to the fib6_node for the route. And some functions make use

[PATCH 4.12 01/52] ipv6: accept 64k - 1 packet length in ip6_find_1stfragopt()

4.12-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit 3de33e1ba0506723ab25734e098cf280ecc34756 ] A packet length of exactly IPV6_MAXPLEN is allowed, we should refuse parsing options only if

Re: [PATCH 3/3] ima: use fs method to read integrity data (updated patch description)

On Mon 18-09-17 10:19:25, Steven Whitehouse wrote: > On 17/09/17 17:38, Al Viro wrote: > >On Sun, Sep 17, 2017 at 09:34:01AM -0700, Linus Torvalds wrote: > >>Now, I suspect most (all?) do, but that's a historical artifact rather > >>than "design". In particular, the VFS layer used to do the

[PATCHv7 00/19] Boot-time switching between 4- and 5-level paging for 4.15

The basic idea is to implement the same logic as pgtable-nop4d.h provides, but at runtime. Runtime folding is only implemented for CONFIG_X86_5LEVEL=y case. With the option disabled, we do compile-time folding as before. Initially, I tried to fold pgd instread. I've got to shell, but it required

Re: [RFC RESEND 0/3] Add support for Hisilicon Hi3521A SoC

On Sun, Sep 17, 2017 at 03:23:24AM -0500, Marty E. Plummer wrote: > Greetings, > > I'd like the community's feedback on the following patchset. I've attempted to > split my changes up in what I believe to be a sensible setup. > > The device I'm working against is the 'SamsungSV SDR-B74301' HD

[PATCHv7 06/19] x86/boot/compressed/64: Detect and handle 5-level paging at boot-time

This patch prepare decompression code to boot-time switching between 4- and 5-level paging. Signed-off-by: Kirill A. Shutemov --- arch/x86/boot/compressed/head_64.S | 24 1 file changed, 24 insertions(+) diff --git

[PATCHv7 10/19] x86/mm: Make __PHYSICAL_MASK_SHIFT and __VIRTUAL_MASK_SHIFT dynamic

For boot-time switching between paging modes, we need to be able to adjust physical and virtual mask shifts. It has significant effect on kernel image size: textdata bss dec hex filename 10710666488 860160 16450826 fb050a vmlinux.before 10735996

[PATCHv7 08/19] x86/mm: Make PGDIR_SHIFT and PTRS_PER_P4D variable

For boot-time switching between 4- and 5-level paging we need to be able to fold p4d page table level at runtime. It requires variable PGDIR_SHIFT and PTRS_PER_P4D. The change doesn't affect the kernel image size much: textdata bss dec hex filename 107101724879964

  1   2   3   4   5   6   7   8   9   10   >