[PATCH 5.9 48/49] x86/resctrl: Remove unused struct mbm_state::chunks_bw

2020-12-19 Thread Greg Kroah-Hartman
From: James Morse commit abe8f12b44250d02937665033a8b750c1bfeb26e upstream Nothing reads struct mbm_states's chunks_bw value, its a copy of chunks. Remove it. Signed-off-by: James Morse Signed-off-by: Borislav Petkov Reviewed-by: Reinette Chatre Link:

[PATCH 5.9 28/49] bonding: fix feature flag setting at init time

2020-12-19 Thread Greg Kroah-Hartman
From: Jarod Wilson [ Upstream commit 007ab5345545aba2f9cbe4c096cc35d2fd3275ac ] Don't try to adjust XFRM support flags if the bond device isn't yet registered. Bad things can currently happen when netdev_change_features() is called without having wanted_features fully filled in yet. This code

[PATCH 5.9 29/49] ch_ktls: fix build warning for ipv4-only config

2020-12-19 Thread Greg Kroah-Hartman
From: Arnd Bergmann [ Upstream commit a54ba3465d86fa5dd7d41bb88c0b5e71fb3b627e ] When CONFIG_IPV6 is disabled, clang complains that a variable is uninitialized for non-IPv4 data: drivers/net/ethernet/chelsio/inline_crypto/ch_ktls/chcr_ktls.c:1046:6: error: variable 'cntrl1' is used

[PATCH 5.9 49/49] x86/resctrl: Fix incorrect local bandwidth when mba_sc is enabled

2020-12-19 Thread Greg Kroah-Hartman
From: Xiaochen Shen commit 06c5fe9b12dde1b62821f302f177c972bb1c81f9 upstream The MBA software controller (mba_sc) is a feedback loop which periodically reads MBM counters and tries to restrict the bandwidth below a user-specified value. It tags along the MBM counter overflow handler to do the

[PATCH 5.9 33/49] ktest.pl: If size of log is too big to email, email error message

2020-12-19 Thread Greg Kroah-Hartman
From: Steven Rostedt (VMware) commit 8cd6bc0359deebd8500e6de95899a8a78d3ec4ba upstream. If the size of the error log is too big to send via email, and the sending fails, it wont email any result. This can be confusing for the user who is waiting for an email on the completion of the tests. If

[PATCH 5.9 32/49] net: tipc: prevent possible null deref of link

2020-12-19 Thread Greg Kroah-Hartman
From: Cengiz Can [ Upstream commit 0398ba9e5a4b5675aa571e0445689d3c2e499c2d ] `tipc_node_apply_property` does a null check on a `tipc_link_entry` pointer but also accesses the same pointer out of the null check block. This triggers a warning on Coverity Static Analyzer because we're implying

[PATCH 5.9 34/49] ktest.pl: Fix the logic for truncating the size of the log file for email

2020-12-19 Thread Greg Kroah-Hartman
From: Steven Rostedt (VMware) commit 170f4869e66275f498ae4736106fb54c0fdcd036 upstream. The logic for truncating the log file for emailing based on the MAIL_MAX_SIZE option is confusing and incorrect. Simplify it and have the tail of the log file truncated to the max size specified in the

[PATCH 5.9 25/49] net/mlx4_en: Avoid scheduling restart task if it is already running

2020-12-19 Thread Greg Kroah-Hartman
From: Moshe Shemesh [ Upstream commit fed91613c9dd455dd154b22fa8e11b8526466082 ] Add restarting state flag to avoid scheduling another restart task while such task is already running. Change task name from watchdog_task to restart_task to better fit the task role. Fixes: 1e338db56e5a

[PATCH 5.9 31/49] net: stmmac: increase the timeout for dma reset

2020-12-19 Thread Greg Kroah-Hartman
From: Fugang Duan [ Upstream commit 9d14edfdeabf37d8d8f045e63e5873712aadcd6b ] Current timeout value is not enough for gmac5 dma reset on imx8mp platform, increase the timeout range. Signed-off-by: Fugang Duan Signed-off-by: Joakim Zhang Signed-off-by: David S. Miller Signed-off-by: Greg

[PATCH 5.9 45/49] serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access

2020-12-19 Thread Greg Kroah-Hartman
From: Alexander Sverdlin commit d96f04d347e4011977abdbb4da5d8f303ebd26f8 upstream. It has been observed that once per 300-1300 port openings the first transmitted byte is being corrupted on AM3352 ("v" written to FIFO appeared as "e" on the wire). It only happened if single byte has been

[PATCH 5.9 44/49] ALSA: pcm: oss: Fix potential out-of-bounds shift

2020-12-19 Thread Greg Kroah-Hartman
From: Takashi Iwai commit 175b8d89fe292796811fdee87fa39799a5b6b87a upstream. syzbot spotted a potential out-of-bounds shift in the PCM OSS layer where it calculates the buffer size with the arbitrary shift value given via an ioctl. Add a range check for avoiding the undefined behavior. As the

[PATCH 5.9 30/49] lan743x: fix for potential NULL pointer dereference with bare card

2020-12-19 Thread Greg Kroah-Hartman
From: Sergej Bauer [ Upstream commit e9e13b6adc338be1eb88db87bcb392696144bd02 ] This is the 3rd revision of the patch fix for potential null pointer dereference with lan743x card. The simpliest way to reproduce: boot with bare lan743x and issue "ethtool ethN" commant where ethN is the

[PATCH 5.9 26/49] net/mlx4_en: Handle TX error CQE

2020-12-19 Thread Greg Kroah-Hartman
From: Moshe Shemesh [ Upstream commit ba603d9d7b1215c72513d7c7aa02b6775fd4891b ] In case error CQE was found while polling TX CQ, the QP is in error state and all posted WQEs will generate error CQEs without any data transmitted. Fix it by reopening the channels, via same method used for TX

[PATCH 5.9 27/49] net: sched: Fix dump of MPLS_OPT_LSE_LABEL attribute in cls_flower

2020-12-19 Thread Greg Kroah-Hartman
From: Guillaume Nault [ Upstream commit 7fdd375e383097a785bb65c66802e468f398bf82 ] TCA_FLOWER_KEY_MPLS_OPT_LSE_LABEL is a u32 attribute (MPLS label is 20 bits long). Fixes the following bug: $ tc filter add dev ethX ingress protocol mpls_uc \ flower mpls lse depth 2 label 256

[PATCH 5.9 24/49] net: flow_offload: Fix memory leak for indirect flow block

2020-12-19 Thread Greg Kroah-Hartman
From: Chris Mi [ Upstream commit 5137d303659d8c324e67814b1cc2e1bc0c0d9836 ] The offending commit introduces a cleanup callback that is invoked when the driver module is removed to clean up the tunnel device flow block. But it returns on the first iteration of the for loop. The remaining

[PATCH 5.9 06/49] net: bridge: vlan: fix error return code in __vlan_add()

2020-12-19 Thread Greg Kroah-Hartman
From: Zhang Changzhong [ Upstream commit ee4f52a8de2c6f78b01f10b4c330867d88c1653a ] Fix to return a negative error code from the error handling case instead of 0, as done elsewhere in this function. Fixes: f8ed289fab84 ("bridge: vlan: use br_vlan_(get|put)_master to deal with refcounts")

[PATCH 5.9 21/49] e1000e: fix S0ix flow to allow S0i3.2 subset entry

2020-12-19 Thread Greg Kroah-Hartman
From: Vitaly Lifshits [ Upstream commit a379b01cd4b2aa3f12786b281a714871574e5ccb ] Changed a configuration in the flows to align with architecture requirements to achieve S0i3.2 substate. This helps both i219V and i219LM configurations. Also fixed a typo in the previous commit 632fbd5eb5b0

[PATCH 5.9 40/49] xhci-pci: Allow host runtime PM as default for Intel Alpine Ridge LP

2020-12-19 Thread Greg Kroah-Hartman
From: Hans de Goede commit c4d1ca05b8e68a4b5a3c4455cb6ec25b3df6d9dd upstream. The xHCI controller on Alpine Ridge LP keeps the whole Thunderbolt controller awake if the host controller is not allowed to sleep. This is the case even if no USB devices are connected to the host. Add the Intel

[PATCH 5.9 09/49] net: hns3: remove a misused pragma packed

2020-12-19 Thread Greg Kroah-Hartman
From: Huazhong Tan [ Upstream commit 61f54de2e9194f01874d5eda12037b0978e77519 ] hclge_dbg_reg_info[] is defined as an array of packed structure accidentally. However, this array contains pointers, which are no longer aligned naturally, and cannot be relocated on PPC64. Hence, when

[PATCH 5.9 20/49] tcp: select sane initial rcvq_space.space for big MSS

2020-12-19 Thread Greg Kroah-Hartman
From: Eric Dumazet [ Upstream commit 72d05c00d7ecda85df29abd046da7e41cc071c17 ] Before commit a337531b942b ("tcp: up initial rmem to 128KB and SYN rwin to around 64KB") small tcp_rmem[1] values were overridden by tcp_fixup_rcvbuf() to accommodate various MSS. This is no longer the case, and

[PATCH 5.9 07/49] vrf: packets with lladdr src needs dst at input with orig_iif when needs strict

2020-12-19 Thread Greg Kroah-Hartman
From: Stephen Suryaputra [ Upstream commit 205704c618af0ab2366015d2281a3b0814d918a0 ] Depending on the order of the routes to fe80::/64 are installed on the VRF table, the NS for the source link-local address of the originator might be sent to the wrong interface. This patch ensures that

[PATCH 5.9 02/49] net/sched: fq_pie: initialize timer earlier in fq_pie_init()

2020-12-19 Thread Greg Kroah-Hartman
From: Davide Caratti [ Upstream commit 4eef8b1f36f2ff06966b8f7c2143ef0c447877de ] with the following tdc testcase: 83be: (qdisc, fq_pie) Create FQ-PIE with invalid number of flows as fq_pie_init() fails, fq_pie_destroy() is called to clean up. Since the timer is not yet initialized, it's

[PATCH 5.9 17/49] net: stmmac: delete the eee_ctrl_timer after napi disabled

2020-12-19 Thread Greg Kroah-Hartman
From: Fugang Duan [ Upstream commit 5f58591323bf3f342920179f24515935c4b5fd60 ] There have chance to re-enable the eee_ctrl_timer and fire the timer in napi callback after delete the timer in .stmmac_release(), which introduces to access eee registers in the timer function after clocks are

[PATCH 5.9 03/49] net: ipa: pass the correct size when freeing DMA memory

2020-12-19 Thread Greg Kroah-Hartman
From: Alex Elder [ Upstream commit 1130b252480f3c98cf468e78c1c5c516b390a29c ] When the coherent memory is freed in gsi_trans_pool_exit_dma(), we are mistakenly passing the size of a single element in the pool rather than the actual allocated size. Fix this bug. Fixes: 9dd441e4ed575 ("soc:

[PATCH 5.9 12/49] bridge: Fix a deadlock when enabling multicast snooping

2020-12-19 Thread Greg Kroah-Hartman
From: Joseph Huang [ Upstream commit 851d0a73c90e6c8c63fef106c6c1e73df7e05d9d ] When enabling multicast snooping, bridge module deadlocks on multicast_lock if 1) IPv6 is enabled, and 2) there is an existing querier on the same L2 network. The deadlock was caused by the following sequence:

[PATCH 5.9 15/49] net: stmmac: start phylink instance before stmmac_hw_setup()

2020-12-19 Thread Greg Kroah-Hartman
From: Fugang Duan [ Upstream commit 36d18b5664ef617ccf4da266291d2f2342fab89d ] Start phylink instance and resume back the PHY to supply RX clock to MAC before MAC layer initialization by calling .stmmac_hw_setup(), since DMA reset depends on the RX clock, otherwise DMA reset cost maximum

[PATCH 5.9 11/49] enetc: Fix reporting of h/w packet counters

2020-12-19 Thread Greg Kroah-Hartman
From: Claudiu Manoil [ Upstream commit eb96b686fc2c601e78903cc61b6cf4588ddde013 ] Noticed some inconsistencies in packet statistics reporting. This patch adds the missing Tx packet counter registers to ethtool reporting and fixes the information strings for a few of them. Fixes: 16eb4c85c964

[PATCH 5.9 00/49] 5.9.16-rc1 review

2020-12-19 Thread Greg Kroah-Hartman
-- Note, I would like to make this the past, or next-to-last 5.9.y kernel to be released. If anyone knows of any reason they can not move to the 5.10.y kernel now, please let me know! -- This is the start of the stable review cycle for the 5.9.16 release. There

[PATCH 5.10 11/16] xhci-pci: Allow host runtime PM as default for Intel Alpine Ridge LP

2020-12-19 Thread Greg Kroah-Hartman
From: Hans de Goede commit c4d1ca05b8e68a4b5a3c4455cb6ec25b3df6d9dd upstream. The xHCI controller on Alpine Ridge LP keeps the whole Thunderbolt controller awake if the host controller is not allowed to sleep. This is the case even if no USB devices are connected to the host. Add the Intel

[PATCH 5.10 15/16] ALSA: pcm: oss: Fix potential out-of-bounds shift

2020-12-19 Thread Greg Kroah-Hartman
From: Takashi Iwai commit 175b8d89fe292796811fdee87fa39799a5b6b87a upstream. syzbot spotted a potential out-of-bounds shift in the PCM OSS layer where it calculates the buffer size with the arbitrary shift value given via an ioctl. Add a range check for avoiding the undefined behavior. As the

[PATCH 5.9 14/49] net: stmmac: dwmac-meson8b: fix mask definition of the m250_sel mux

2020-12-19 Thread Greg Kroah-Hartman
From: Martin Blumenstingl [ Upstream commit 82ca4c922b8992013a238d65cf4e60cc33e12f36 ] The m250_sel mux clock uses bit 4 in the PRG_ETH0 register. Fix this by shifting the PRG_ETH0_CLK_M250_SEL_MASK accordingly as the "mask" in struct clk_mux expects the mask relative to the "shift" field in

[PATCH 5.9 10/49] udp: fix the proto value passed to ip_protocol_deliver_rcu for the segments

2020-12-19 Thread Greg Kroah-Hartman
From: Xin Long [ Upstream commit 10c678bd0a035ac2c64a9b26b222f20556227a53 ] Guillaume noticed that: for segments udp_queue_rcv_one_skb() returns the proto, and it should pass "ret" unmodified to ip_protocol_deliver_rcu(). Otherwize, with a negtive value passed, it will underflow inet_protos.

[PATCH 5.10 14/16] USB: sisusbvga: Make console support depend on BROKEN

2020-12-19 Thread Greg Kroah-Hartman
From: Thomas Gleixner commit 862ee699fefe1e6d6f2c1518395f0b999b8beb15 upstream. The console part of sisusbvga is broken vs. printk(). It uses in_atomic() to detect contexts in which it cannot sleep despite the big fat comment in preempt.h which says: Do not use in_atomic() in driver code.

[PATCH 5.10 07/16] ALSA: usb-audio: Fix potential out-of-bounds shift

2020-12-19 Thread Greg Kroah-Hartman
From: Takashi Iwai commit 43d5ca88dfcd35e43010fdd818e067aa9a55f5ba upstream. syzbot spotted a potential out-of-bounds shift in the USB-audio format parser that receives the arbitrary shift value from the USB descriptor. Add a range check for avoiding the undefined behavior. Reported-by:

[PATCH 5.9 01/49] ptrace: Prevent kernel-infoleak in ptrace_get_syscall_info()

2020-12-19 Thread Greg Kroah-Hartman
From: Peilin Ye commit 0032ce0f85a269a006e91277be5fdbc05fad8426 upstream. ptrace_get_syscall_info() is potentially copying uninitialized stack memory to userspace, since the compiler may leave a 3-byte hole near the beginning of `info`. Fix it by adding a padding field to `struct

[PATCH 5.10 16/16] serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access

2020-12-19 Thread Greg Kroah-Hartman
From: Alexander Sverdlin commit d96f04d347e4011977abdbb4da5d8f303ebd26f8 upstream. It has been observed that once per 300-1300 port openings the first transmitted byte is being corrupted on AM3352 ("v" written to FIFO appeared as "e" on the wire). It only happened if single byte has been

[PATCH 5.10 12/16] xhci-pci: Allow host runtime PM as default for Intel Maple Ridge xHCI

2020-12-19 Thread Greg Kroah-Hartman
From: Mika Westerberg commit 5a8e3229ac27956bdcc25b2709e5d196d109a27a upstream. Intel Maple Ridge is successor of Titan Ridge Thunderbolt controller. As Titan Ridge this one also includes xHCI host controller. In order to safe energy we should put it to low power state by default when idle. For

[PATCH 5.10 10/16] usb: xhci: Set quirk for XHCI_SG_TRB_CACHE_SIZE_QUIRK

2020-12-19 Thread Greg Kroah-Hartman
From: Tejas Joglekar commit bac1ec551434697ca3c5bb5d258811ba5446866a upstream. This commit uses the private data passed by parent device to set the quirk for Synopsys xHC. This patch fixes the SNPS xHC hang issue when the data is scattered across small buffers which does not make atleast MPS

[PATCH 5.10 08/16] ALSA: usb-audio: Fix control access overflow errors from chmap

2020-12-19 Thread Greg Kroah-Hartman
From: Takashi Iwai commit c6dde8ffd071aea9d1ce64279178e470977b235c upstream. The current channel-map control implementation in USB-audio driver may lead to an error message like "control 3:0:0:Playback Channel Map:0: access overflow" when CONFIG_SND_CTL_VALIDATION is set. It's because the

[PATCH 5.10 09/16] xhci: Give USB2 ports time to enter U3 in bus suspend

2020-12-19 Thread Greg Kroah-Hartman
From: Li Jun commit c1373f10479b624fb6dba0805d673e860f1b421d upstream. If a USB2 device wakeup is not enabled/supported the link state may still be in U0 in xhci_bus_suspend(), where it's then manually put to suspended U3 state. Just as with selective suspend the device needs time to enter U3

[PATCH 5.10 06/16] USB: add RESET_RESUME quirk for Snapscan 1212

2020-12-19 Thread Greg Kroah-Hartman
From: Oliver Neukum commit 08a02f954b0def3ada8ed6d4b2c7bcb67e885e9c upstream. I got reports that some models of this old scanner need this when using runtime PM. Signed-off-by: Oliver Neukum Cc: stable Link: https://lore.kernel.org/r/20201207130323.23857-1-oneu...@suse.com Signed-off-by:

[PATCH 5.10 04/16] USB: legotower: fix logical error in recent commit

2020-12-19 Thread Greg Kroah-Hartman
From: Alan Stern commit b175d273d4e4100b66e68f0675fef7a3c07a7957 upstream. Commit d9f0d82f06c6 ("USB: legousbtower: use usb_control_msg_recv()") contained an elementary logical error. The check of the return code from the new usb_control_msg_recv() function was inverted.

[PATCH 5.10 03/16] ktest.pl: Fix the logic for truncating the size of the log file for email

2020-12-19 Thread Greg Kroah-Hartman
From: Steven Rostedt (VMware) commit 170f4869e66275f498ae4736106fb54c0fdcd036 upstream. The logic for truncating the log file for emailing based on the MAIL_MAX_SIZE option is confusing and incorrect. Simplify it and have the tail of the log file truncated to the max size specified in the

[PATCH 5.10 02/16] ktest.pl: If size of log is too big to email, email error message

2020-12-19 Thread Greg Kroah-Hartman
From: Steven Rostedt (VMware) commit 8cd6bc0359deebd8500e6de95899a8a78d3ec4ba upstream. If the size of the error log is too big to send via email, and the sending fails, it wont email any result. This can be confusing for the user who is waiting for an email on the completion of the tests. If

[PATCH 5.10 01/16] ptrace: Prevent kernel-infoleak in ptrace_get_syscall_info()

2020-12-19 Thread Greg Kroah-Hartman
From: Peilin Ye commit 0032ce0f85a269a006e91277be5fdbc05fad8426 upstream. ptrace_get_syscall_info() is potentially copying uninitialized stack memory to userspace, since the compiler may leave a 3-byte hole near the beginning of `info`. Fix it by adding a padding field to `struct

[PATCH 5.10 00/16] 5.10.2-rc1 review

2020-12-19 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.2 release. There are 16 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 Mon, 21 Dec 2020 12:53:29 +. Anything

Re: [PATCH v16 1/3] scsi: ufs: Introduce HPB feature

2020-12-19 Thread Greg KH
On Sat, Dec 19, 2020 at 12:48:31PM +, Avri Altman wrote: > > > > > > On Sat, Dec 19, 2020 at 06:18:47PM +0900, Daejun Park wrote: > > > +static int ufshpb_get_state(struct ufshpb_lu *hpb) > > > +{ > > > + return atomic_read(>hpb_state); > > > +} > > > + > > > +static void

Re: [PATCH] [v11] wireless: Initial driver submission for pureLiFi STA devices

2020-12-19 Thread Kalle Valo
Srinivasan Raju writes: > This introduces the pureLiFi LiFi driver for LiFi-X, LiFi-XC > and LiFi-XL USB devices. > > This driver implementation has been based on the zd1211rw driver. > > Driver is based on 802.11 softMAC Architecture and uses > native 802.11 for configuration and management. >

[PATCH] ubi: remove dead code in validate_vid_hdr()

2020-12-19 Thread Jubin Zhong
data_size is already checked against zero when vol_type matches UBI_VID_STATIC. Remove the following dead code. Signed-off-by: Jubin Zhong --- drivers/mtd/ubi/io.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/mtd/ubi/io.c b/drivers/mtd/ubi/io.c index

RE: [PATCH v16 1/3] scsi: ufs: Introduce HPB feature

2020-12-19 Thread Avri Altman
> > > On Sat, Dec 19, 2020 at 06:18:47PM +0900, Daejun Park wrote: > > +static int ufshpb_get_state(struct ufshpb_lu *hpb) > > +{ > > + return atomic_read(>hpb_state); > > +} > > + > > +static void ufshpb_set_state(struct ufshpb_lu *hpb, int state) > > +{ > > + atomic_set(>hpb_state,

[PATCH] dmaengine: mediatek: mtk-hsdma: Fix a resource leak in the error handling path of the probe function

2020-12-19 Thread Christophe JAILLET
'mtk_hsdma_hw_deinit()' should be called in the error handling path of the probe function to undo a previous 'mtk_hsdma_hw_init()' call, as already done in the remove function. Fixes: 548c4597e984 ("dmaengine: mediatek: Add MediaTek High-Speed DMA controller for MT7622 and MT7623 SoC")

Re: [PATCH backport] membarrier: Explicitly sync remote cores when SYNC_CORE is requested

2020-12-19 Thread Greg KH
On Mon, Dec 14, 2020 at 10:00:43AM -0800, Andy Lutomirski wrote: > commit 758c9373d84168dc7d039cf85a0e920046b17b41 upstream > > membarrier() does not explicitly sync_core() remote CPUs; instead, it > relies on the assumption that an IPI will result in a core sync. On x86, > this may be true in

[PATCH v1] drm/panel: simple: add SGD GKTW70SDAD1SD

2020-12-19 Thread Oliver Graute
Add support for the Solomon Goldentek Display Model: GKTW70SDAD1SD to panel-simple. The panel spec from Variscite can be found at: https://www.variscite.com/wp-content/uploads/2017/12/VLCD-CAP-GLD-RGB.pdf Signed-off-by: Oliver Graute --- panel-timing { clock-frequency =

Re: [PATCH] genksyms: Ignore module scoped _Static_assert()

2020-12-19 Thread Masahiro Yamada
On Fri, Dec 11, 2020 at 2:24 PM Andrew Morton wrote: > > On Thu, 10 Dec 2020 17:25:30 +0100 Marco Elver wrote: > > > On Thu, 10 Dec 2020 at 14:29, Miguel Ojeda > > wrote: > > > On Thu, Dec 10, 2020 at 11:35 AM Marco Elver wrote: > > > > > > > > It looks like there's no clear MAINTAINER for

Re: [PATCH 1/2] mm: Allow architectures to request 'old' entries when prefaulting

2020-12-19 Thread Kirill A. Shutemov
On Fri, Dec 18, 2020 at 10:56:55AM -0800, Linus Torvalds wrote: > No? Okay, but we only win the NULL check. xas_retry() and xa_is_value() has to be repeated in the beginning of the loop. >From b4f4c0d32e654b8459a1e439a453373499b8946a Mon Sep 17 00:00:00 2001 From: "Kirill A. Shutemov" Date:

Re: [PATCH v2 3/4] arm64: dts: imx8mq-librem5-devkit: Disable snvs_rtc

2020-12-19 Thread Krzysztof Kozlowski
On Thu, Dec 17, 2020 at 04:13:14PM +0100, Guido Günther wrote: > The board has it's own RTC chip which is backed by the (optional) > battery and hence preserves data/time on poweroff when that is inserted. > > Signed-off-by: Guido Günther > --- >

Re: [PATCH v2 2/4] arm64: dts: imx8mq-librem5-devkit: Tweak pmic regulators

2020-12-19 Thread Krzysztof Kozlowski
On Thu, Dec 17, 2020 at 04:13:13PM +0100, Guido Günther wrote: > BUCK3 needs a regulator-enable-ramp-delay since otherwise the board > freezes on etnaviv probe. With this pgc_gpu suspends and resumes as > expected. This must have been always broken since gpcv2 support was > enabled. > > We also

Re: [PATCH v2 4/4] arm64: dts: imx8mq-librem5-devkit: Drop custom clock settings

2020-12-19 Thread Krzysztof Kozlowski
On Thu, Dec 17, 2020 at 04:13:15PM +0100, Guido Günther wrote: > Otherwise the boot hangs early on and the resulting clock tree without > this already closely matches the selected rates (722534400 and > 786432000). > > audio_pll2 000 722534397 0

Re: [PATCH v2 1/4] arm64: defconfig: Enable Librem 5 devkit components

2020-12-19 Thread Krzysztof Kozlowski
On Thu, Dec 17, 2020 at 04:13:12PM +0100, Guido Günther wrote: > The Librem 5 devkit is based on NXP's i.MX8MQ. Schematics are at > https://source.puri.sm/Librem5/dvk-mx8m-bsb. > > This enables drivers for the following hardware components that aren't > yet enabled in defconfig: > > - Goodix

Re: [PATCH 3/4] arm64: dts: imx8mq-librem5: Move usdhc clocks assignment to board DT

2020-12-19 Thread Krzysztof Kozlowski
On Fri, Dec 18, 2020 at 11:31:30AM +0100, Martin Kepplinger wrote: > According to commit e045f044e84e ("arm64: dts: imx8mq: Move usdhc clocks > assignment to board DT") add the clocks assignment to imx8mq-librem5.dtsi > too. > > Signed-off-by: Martin Kepplinger This should go with Fixes tag as

Re: [PATCH 2/4] arm64: dts: imx8mq-librem5: add pinctrl for the touchscreen description

2020-12-19 Thread Krzysztof Kozlowski
On Fri, Dec 18, 2020 at 11:31:29AM +0100, Martin Kepplinger wrote: > Add the pinctrl description for the interrupt. Please describe why do you need to add it. From the patch contents I easily see what you are doing. But neither the commit title nor the message describe what you want to achieve

Re: [PATCH v8 3/4] arm64: dts: imx8m: add NVMEM provider and consumer to read soc unique ID

2020-12-19 Thread Krzysztof Kozlowski
On Fri, Dec 18, 2020 at 04:37:25PM +0800, Alice Guo (OSS) wrote: > From: Alice Guo > > In order to be able to use NVMEM APIs to read soc unique ID, add the > nvmem data cell and name for nvmem-cells to the "soc" node, and add a > nvmem node which provides soc unique ID to efuse@3035. > >

Re: [PATCH v8 4/4] soc: imx8m: change to use platform driver

2020-12-19 Thread Krzysztof Kozlowski
On Fri, Dec 18, 2020 at 04:37:26PM +0800, Alice Guo (OSS) wrote: > From: Alice Guo > > Directly reading ocotp register depends on that bootloader enables ocotp > clk, which is not always effective, so change to use nvmem API. Using > nvmem API requires to support driver defer probe and thus

Re: sparse annotation for error types?

2020-12-19 Thread Dan Carpenter
I've pushed my Smatch check for missing error codes. https://github.com/error27/smatch/commit/be18f90f05b684c12b80b9364b5bbc5dbef922da I ended up writing a slightly more tricky version of the check because there were some places that do: ret = 0; goto out; And I

Greetings to you.

2020-12-19 Thread Mr David Bernstein
Greetings to you. My name is Mr. David Bernstein the chairman of the British Red Cross, I brought news to you from the British Red Cross London, EC2 United Kingdom our aim and goal is to have every Humanitarian aid and have your good will’s in heart. My purpose for contacting you is that i have

Re: [PATCH] clk: vc5: Use "idt,voltage-microvolt" instead of "idt,voltage-microvolts"

2020-12-19 Thread Geert Uytterhoeven
Hi Luca, On Fri, Dec 18, 2020 at 11:18 PM Luca Ceresoli wrote: > On 18/12/20 13:52, Geert Uytterhoeven wrote: > > Commit 45c940184b501fc6 ("dt-bindings: clk: versaclock5: convert to > > yaml") accidentally changed "idt,voltage-microvolts" to > > "idt,voltage-microvolt" in the DT bindings, while

[RFC PATCH v1 3/4] arm64: dts: rockchip: add rga node to rk3328.dtsi

2020-12-19 Thread Johan Jonker
Add rga node to the rk3328.dtsi file. Signed-off-by: Johan Jonker --- arch/arm64/boot/dts/rockchip/rk3328.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi index 1e3e1086e..c4170dc19 100644

[RFC PATCH v1 2/4] arm64: dts: rockchip: add rga node to px30.dtsi

2020-12-19 Thread Johan Jonker
Add rga node to the px30.dtsi file. Signed-off-by: Johan Jonker --- arch/arm64/boot/dts/rockchip/px30.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/px30.dtsi b/arch/arm64/boot/dts/rockchip/px30.dtsi index 541785425..fac9b4120 100644 ---

[RFC PATCH v1 1/4] media: dt-bindings: rockchip-rga: add more rga compatible properties

2020-12-19 Thread Johan Jonker
Add more rga compatible properties. "rockchip,px30-rga", "rockchip,rk3288-rga" "rockchip,rk3328-rga", "rockchip,rk3288-rga" "rockchip,rk3368-rga", "rockchip,rk3288-rga" make ARCH=arm64 dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/media/rockchip-rga.yaml Signed-off-by:

[RFC PATCH v1 4/4] arm64: dts: rockchip: add rga node to rk3368.dtsi

2020-12-19 Thread Johan Jonker
Add rga node to the rk3368.dtsi file. Signed-off-by: Johan Jonker --- arch/arm64/boot/dts/rockchip/rk3368.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3368.dtsi b/arch/arm64/boot/dts/rockchip/rk3368.dtsi index 3746f23dc..dad1a00e6 100644

Re: [PATCH v2 16/18] arm64: dts: hi3660: Harmonize DWC USB3 DT nodes name

2020-12-19 Thread Krzysztof Kozlowski
On Fri, Dec 18, 2020 at 09:11:42PM -0800, John Stultz wrote: > On Wed, Nov 11, 2020 at 1:22 AM Serge Semin > wrote: > > > > In accordance with the DWC USB3 bindings the corresponding node > > name is suppose to comply with the Generic USB HCD DT schema, which > > requires the USB nodes to have

Re: [patch] zswap: fix zswap_frontswap_load() vs zsmalloc::map/unmap() might_sleep() splat

2020-12-19 Thread Mike Galbraith
(CC zsmalloc maintainers) On Sat, 2020-12-19 at 11:59 +0100, Mike Galbraith wrote: > On Sat, 2020-12-19 at 11:46 +0100, Vitaly Wool wrote: > > On Sat, 19 Dec 2020, 11:27 Mike Galbraith, wrote: > > > > > The kernel that generated that splat was NOT an RT kernel, it was plain > > > master.today

Re: [PATCH v2 41/48] memory: tegra20-emc: Use devm_tegra_core_dev_init_opp_table()

2020-12-19 Thread Krzysztof Kozlowski
On Thu, Dec 17, 2020 at 09:06:31PM +0300, Dmitry Osipenko wrote: > Use common devm_tegra_core_dev_init_opp_table() helper for the OPP table > initialization. > > Signed-off-by: Dmitry Osipenko > --- > drivers/memory/tegra/tegra20-emc.c | 57 +++--- > 1 file changed, 4

Re: [patch] zswap: fix zswap_frontswap_load() vs zsmalloc::map/unmap() might_sleep() splat

2020-12-19 Thread Mike Galbraith
On Sat, 2020-12-19 at 11:46 +0100, Vitaly Wool wrote: > On Sat, 19 Dec 2020, 11:27 Mike Galbraith, wrote: > > > The kernel that generated that splat was NOT an RT kernel, it was plain > > master.today with a PREEMPT config. > > > I see, thanks. I don't think it makes things better for zsmalloc >

[PATCH] nvmem: core: Fix a resource leak on error in nvmem_add_cells_from_of()

2020-12-19 Thread Dan Carpenter
This doesn't call of_node_put() on the error path so it leads to a memory leak. Fixes: 0749aa25af82 ("nvmem: core: fix regression in of_nvmem_cell_get()") Signed-off-by: Dan Carpenter --- The kfree_const() could just be replaced with kfree(). Someone got over excited converting things from

Re: [PATCH v2 07/48] dt-bindings: arm: tegra: Add binding for core power domain

2020-12-19 Thread Krzysztof Kozlowski
On Thu, Dec 17, 2020 at 09:05:57PM +0300, Dmitry Osipenko wrote: > All NVIDIA Tegra SoCs have a core power domain where majority of hardware > blocks reside. Add binding for the core power domain. > > Signed-off-by: Dmitry Osipenko > --- > .../arm/tegra/nvidia,tegra20-core-domain.yaml | 48

Re: [patch] zswap: fix zswap_frontswap_load() vs zsmalloc::map/unmap() might_sleep() splat

2020-12-19 Thread Vitaly Wool
On Sat, 19 Dec 2020, 11:27 Mike Galbraith, wrote: > > On Sat, 2020-12-19 at 11:20 +0100, Vitaly Wool wrote: > > Hi Mike, > > > > On Sat, Dec 19, 2020 at 11:12 AM Mike Galbraith wrote: > > > > > > (mailer partially munged formatting? resend) > > > > > > mm/zswap: fix zswap_frontswap_load() vs

Re: [kbuild-all] Re: [linux-next:master 13538/13785] /tmp/metronomefb-846872.s:300: Error: unrecognized opcode `zext.b a2,a2'

2020-12-19 Thread Philip Li
On Sat, Dec 19, 2020 at 06:28:20PM +0800, Philip Li wrote: > On Sat, Dec 19, 2020 at 08:56:06AM +0100, Pavel Machek wrote: > > Crazy robot, stop spamming. This report is obviously bogus, yet, you > > sent me 5 copies. > Thanks Pavel for input, sorry for the false positive. It tries to > bisect

Re: [PATCH v16 1/3] scsi: ufs: Introduce HPB feature

2020-12-19 Thread Greg KH
On Sat, Dec 19, 2020 at 06:18:47PM +0900, Daejun Park wrote: > +static int ufshpb_get_state(struct ufshpb_lu *hpb) > +{ > + return atomic_read(>hpb_state); > +} > + > +static void ufshpb_set_state(struct ufshpb_lu *hpb, int state) > +{ > + atomic_set(>hpb_state, state); > +} You have a

Re: [kbuild-all] Re: [linux-next:master 13538/13785] /tmp/metronomefb-846872.s:300: Error: unrecognized opcode `zext.b a2,a2'

2020-12-19 Thread Philip Li
On Sat, Dec 19, 2020 at 08:56:06AM +0100, Pavel Machek wrote: > Crazy robot, stop spamming. This report is obviously bogus, yet, you > sent me 5 copies. Thanks Pavel for input, sorry for the false positive. It tries to bisect error like below (the new error), but it may be related to assember

Re: [patch] zswap: fix zswap_frontswap_load() vs zsmalloc::map/unmap() might_sleep() splat

2020-12-19 Thread Mike Galbraith
On Sat, 2020-12-19 at 11:20 +0100, Vitaly Wool wrote: > Hi Mike, > > On Sat, Dec 19, 2020 at 11:12 AM Mike Galbraith wrote: > > > > (mailer partially munged formatting? resend) > > > > mm/zswap: fix zswap_frontswap_load() vs zsmalloc::map/unmap() might_sleep() > > splat > > > > zsmalloc

Re: [patch] zswap: fix zswap_frontswap_load() vs zsmalloc::map/unmap() might_sleep() splat

2020-12-19 Thread Vitaly Wool
Hi Mike, On Sat, Dec 19, 2020 at 11:12 AM Mike Galbraith wrote: > > (mailer partially munged formatting? resend) > > mm/zswap: fix zswap_frontswap_load() vs zsmalloc::map/unmap() might_sleep() > splat > > zsmalloc map/unmap methods use preemption disabling bit spinlocks. Take the > mutex

[PATCH] cpufreq: brcmstb-avs-cpufreq: Fix some resource leaks in the error handling path of the probe function

2020-12-19 Thread Christophe JAILLET
If 'cpufreq_register_driver()' fails, we must release the resources allocated in 'brcm_avs_prepare_init()' as already done in the remove function. To do that, introduce a new function 'brcm_avs_prepare_uninit()' in order to avoid code duplication. This also makes the code more readable (IMHO).

[tip:timers/urgent] BUILD SUCCESS f6f5cd840ae782680c5e94048c72420e4e6857f9

2020-12-19 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/urgent branch HEAD: f6f5cd840ae782680c5e94048c72420e4e6857f9 timekeeping: Fix spelling mistake in Kconfig "fullfill" -> "fulfill" elapsed time: 721m configs tested: 116 configs skipped: 2 The following configs

Re: [patch] zswap: fix zswap_frontswap_load() vs zsmalloc::map/unmap() might_sleep() splat

2020-12-19 Thread Mike Galbraith
(mailer partially munged formatting? resend) mm/zswap: fix zswap_frontswap_load() vs zsmalloc::map/unmap() might_sleep() splat zsmalloc map/unmap methods use preemption disabling bit spinlocks. Take the mutex outside of pool map/unmap methods in zswap_frontswap_load() as is done in

[patch] zswap: fix zswap_frontswap_load() vs zsmalloc::map/unmap() might_sleep() splat

2020-12-19 Thread Mike Galbraith
Greetings, Beating on zswap+zsmalloc leads to the splat below, possible patch below that. [ 139.794413] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:935 [ 139.794585] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 907, name: avahi-daemon [ 139.794608]

List of Enterprise Networking Devices Bought on 19 Dec 2020 Saturday and Earlier

2020-12-19 Thread Turritopsis Dohrnii Teo En Ming
Subject: List of Enterprise Networking Devices Bought on 19 Dec 2020 Saturday and Earlier Mr. Turritopsis Dohrnii Teo En Ming (42 year old Singapore Targeted Individual) bought the following enterprise networking devices on 19 Dec 2020 Saturday and earlier. (1) Refurbished Fortigate 60E

drivers/crypto/qat/qat_common/qat_algs.c:483: undefined reference to `aes_expandkey'

2020-12-19 Thread kernel test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 3644e2d2dda78e21edd8f5415b6d7ab03f5f54f3 commit: 5106dfeaeabea73d5132daab1d89d57b57fa98b7 crypto: qat - add AES-XTS support for QAT GEN4 devices date: 8 days ago config: i386-randconfig-m021-20201216

Re: upstream boot error: UBSAN: null-ptr-deref in corrupted

2020-12-19 Thread Dmitry Vyukov
On Fri, Dec 18, 2020 at 8:47 PM Kees Cook wrote: > > On Thu, Dec 17, 2020 at 11:38:30AM +0100, Dmitry Vyukov wrote: > > On Thu, Dec 17, 2020 at 11:14 AM syzbot > > wrote: > > > > > > Hello, > > > > > > syzbot found the following issue on: > > > > > > HEAD commit:accefff5 Merge tag

Re: [PATCH] inotify, memcg: account inotify instances to kmemcg

2020-12-19 Thread Amir Goldstein
On Sat, Dec 19, 2020 at 12:11 AM Shakeel Butt wrote: > > Currently the fs sysctl inotify/max_user_instances is used to limit the > number of inotify instances on the system. For systems running multiple > workloads, the per-user namespace sysctl max_inotify_instances can be > used to further

Re: kernel BUG at drivers/dma-buf/dma-buf.c:LINE!

2020-12-19 Thread Dmitry Vyukov
On Sat, Dec 19, 2020 at 3:50 AM syzbot wrote: > > syzbot suspects this issue was fixed by commit: > > commit e722a295cf493388dae474745d30e91e1a2ec549 > Author: Greg Kroah-Hartman > Date: Thu Aug 27 12:36:27 2020 + > > staging: ion: remove from the tree > > bisection log:

Re: [PATCH 3/5] dt-bindings: soc: add the required property 'additionalProperties'

2020-12-19 Thread Stafford Horne
On Fri, Dec 18, 2020 at 03:17:06PM -0600, Rob Herring wrote: > On Fri, 04 Dec 2020 17:38:11 +0800, Zhen Lei wrote: > > When I do dt_binding_check for any YAML file, below wanring is always > > reported: > > > > xxx/soc/litex/litex,soc-controller.yaml: 'additionalProperties' is a > > required

[PATCH] ia64: fix timer cleanup regression

2020-12-19 Thread Arnd Bergmann
From: Arnd Bergmann A cleanup patch from my legacy timer series broke ia64 and led to RCU stall errors and a fast system clock: [ 909.360108] INFO: task systemd-sysv-ge:200 blocked for more than 127 seconds. [ 909.360108] Not tainted 5.10.0+ #130 [ 909.360108] "echo 0 >

[PATCH v16 3/3] scsi: ufs: Prepare HPB read for cached sub-region

2020-12-19 Thread Daejun Park
This patch changes the read I/O to the HPB read I/O. If the logical address of the read I/O belongs to active sub-region, the HPB driver modifies the read I/O command to HPB read. It modifies the UPIU command of UFS instead of modifying the existing SCSI command. In the HPB version 1.0, the

[PATCH v16 2/3] scsi: ufs: L2P map management for HPB read

2020-12-19 Thread Daejun Park
This is a patch for managing L2P map in HPB module. The HPB divides logical addresses into several regions. A region consists of several sub-regions. The sub-region is a basic unit where L2P mapping is managed. The driver loads L2P mapping data of each sub-region. The loaded sub-region is called

[PATCH v16 1/3] scsi: ufs: Introduce HPB feature

2020-12-19 Thread Daejun Park
This is a patch for the HPB initialization and adds HPB function calls to UFS core driver. NAND flash-based storage devices, including UFS, have mechanisms to translate logical addresses of IO requests to the corresponding physical addresses of the flash storage. In UFS,

[PATCH v16 0/3] scsi: ufs: Add Host Performance Booster Support

2020-12-19 Thread Daejun Park
Changelog: v15 -> v16 1. Add missed sysfs ABI documentation. v14 -> v15 1. Remove duplicated sysfs ABI entries in documentation. 2. Add experiment result of HPB performance testing with iozone. v13 -> v14 1. Cleanup codes by commentted in Greg's review. 2. Add documentation for sysfs entries

RE: Re: [PATCH v15 1/3] scsi: ufs: Introduce HPB feature

2020-12-19 Thread Daejun Park
On Sat, Dec 19, 2020 at 12:30:39PM +0900, Daejun Park wrote: > > @@ -323,6 +325,8 @@ static struct attribute *ufs_sysfs_device_descriptor[] > > = { > > _attr_number_of_secure_wpa.attr, > > _attr_psa_max_data_size.attr, > > _attr_psa_state_timeout.attr, > > + _attr_hpb_version.attr,

[PATCH v2 0/1] device-dax: avoid an unnecessary check in alloc_dev_dax_range()

2020-12-19 Thread Zhen Lei
v1 --> v2: In v1, I use the "goto" statement to merge two identical __release_region() calls. However, the new patch https://lkml.org/lkml/2020/12/18/735 deletes one of them, the "goto" becomes worthless. So when krealloc() failed, directly call __release_region() and return error code. Zhen

[PATCH v2 1/1] device-dax: avoid an unnecessary check in alloc_dev_dax_range()

2020-12-19 Thread Zhen Lei
Swap the calling sequence of krealloc() and __request_region(), call the latter first. In this way, the value of dev_dax->nr_range does not need to be considered when __request_region() failed. Signed-off-by: Zhen Lei --- drivers/dax/bus.c | 20 ++-- 1 file changed, 6

<    1   2   3   4   5   >