Re: linux-next: build failure after merge of the hwmon-staging tree

On 8/23/20 5:28 PM, Stephen Rothwell wrote: > Hi all, > > After merging the hwmon-staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/hwmon/pmbus/adm1266.c: In function 'adm1266_probe': > drivers/hwmon/pmbus/adm1266.c:478:31: error: passing argument 2 of

Re: [PATCH 02/22] dt-bindings: gpio: fsl-imx-gpio: Add gpio-ranges property

On Mon, Aug 24, 2020 at 08:58:01AM +0200, Sascha Hauer wrote: > On Mon, Aug 24, 2020 at 08:38:06AM +0200, Krzysztof Kozlowski wrote: > > On Mon, Aug 24, 2020 at 07:24:46AM +0200, Sascha Hauer wrote: > > > On Sun, Aug 23, 2020 at 06:15:30PM +0200, Krzysztof Kozlowski wrote: > > > > The GPIO controll

RE: [PATCH] blk-mq: use BLK_MQ_NO_TAG for no tag

Hi Jens Sorry to trouble you, I am very sorry for taking it for granted for the patch compile. I checked, compile for the two changed files are OK: block/blk-core.c block/blk-mq-sched.c Compile failed for the function in below header file: include/linux/blk-mq.h: request_to_qc_t() - if (rq

Re: [PATCH v2 1/2] thermal: qcom-spmi-temp-alarm: Don't suppress negative temp

On 29/07/2020 18:52, Guru Das Srinagesh wrote: > From: Veera Vegivada > > Currently driver is suppressing the negative temperature > readings from the vadc. Consumers of the thermal zones need > to read the negative temperature too. Don't suppress the > readings. > > Fixes: c610afaa21d3c6e ("the

[PATCH] arm64: dts: imx8mm-beacon-baseboard: Correct LED default state

There is no LED default state "none". leds-gpio driver maps it to "off", so correct them to fix dtbs_check warnings like: arch/arm64/boot/dts/freescale/imx8mm-beacon-kit.dt.yaml: leds: led0:default-state:0: 'none' is not one of ['on', 'off', 'keep'] Signed-off-by: Krzysztof Kozlowski ---

RE: [PATCH v8 0/3] drm: Add support for Cadence MHDP DPI/DP bridge and J721E wrapper.

Hi Guido, > -Original Message- > From: Guido Günther > Sent: Wednesday, August 12, 2020 7:27 PM > To: Tomi Valkeinen > Cc: Swapnil Kashinath Jakhade ; airl...@linux.ie; > dan...@ffwll.ch; laurent.pinch...@ideasonboard.com; robh...@kernel.org; > a.ha...@samsung.com; narmstr...@baylibre.co

Re: [GIT PULL] tee subsystem pin_user_pages for v5.8

On 8/23/20 11:51 PM, Jens Wiklander wrote: On Fri, Aug 21, 2020 at 11:19 PM Olof Johansson wrote: On Fri, Aug 21, 2020 at 12:58 PM John Hubbard wrote: On 8/21/20 11:49 AM, Olof Johansson wrote: On Tue, May 26, 2020 at 03:12:59PM +0200, Jens Wiklander wrote: Hello arm-soc maintainers, Ple

Re: linux-next: Signed-off-by missing for commits in the arm-soc-fixes tree

On 21. 08. 20 18:18, Olof Johansson wrote: > Hi, > > On Thu, Aug 20, 2020 at 10:19 PM Stephen Rothwell > wrote: >> >> Hi all, >> >> Commits >> >> 8d53ecfbf231 ("arm64: dts: xilinx: Align IOMMU nodename with dtschema") >> b4b6fb8de8dc ("arm64: dts: zynqmp: Add GTR transceivers") >> >> are

Re: [PATCH] drivers: thermal: Kconfig: fix spelling mistake "acces" -> "access"

On 10/08/2020 10:27, Colin King wrote: > From: Colin Ian King > > There is a spelling mistake in the Kconfig text, fix it. > > Signed-off-by: Colin Ian King > --- Applied, thanks -- Linaro.org │ Open source software for ARM SoCs Follow Linaro:

Re: [PATCH 1/2] thermal: imx: Use dev_err_probe() to simplify error handling

On 11/08/2020 04:58, Anson Huang wrote: > dev_err_probe() can reduce code size, uniform error handling and record the > defer probe reason etc., use it to simplify the code. > > Signed-off-by: Anson Huang > --- Applied, thanks -- Linaro.org │ Open source software for

Re: [PATCH] mmc: tegra: Add Runtime PM callbacks

[...] > @@ -1622,7 +1699,6 @@ static int sdhci_tegra_probe(struct platform_device > *pdev) > > goto err_clk_get; > } > - clk_prepare_enable(clk); > pltfm_host->clk = clk; > > tegra_host->rst = devm_reset_control_get_exclusive(&pdev->dev, > @@ -1645,16

Re: [PATCH v3 2/2] regulator: mt6360: Add DT binding documentation

⊕ Mark Brown 於 2020年8月20日 週四 下午7:30寫道： > > On Thu, Aug 20, 2020 at 03:53:42PM +0800, Gene Chen wrote: > > > +properties: > > + compatible: > > +const: mediatek,mt6360-regulator > > + > > + LDO_VIN3-supply: > > +description: Input supply phandle(s) for LDO3 > > + > > Only LDO3 needs a su

[PATCH] HID: elan: Fix memleak in elan_input_configured

When input_mt_init_slots() fails, input should be freed to prevent memleak. Fixes: 9a6a4193d65b8 ("HID: Add driver for USB ELAN Touchpad") Signed-off-by: Dinghao Liu --- drivers/hid/hid-elan.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/hid/hid-elan.c b/drivers/hid/hid-elan.c ind

Re: [PATCH 1/2] drm/virtio: fix unblank

On 18. 08. 20, 9:25, Gerd Hoffmann wrote: > When going through a disable/enable cycle without changing the > framebuffer the optimization added by commit 3954ff10e06e ("drm/virtio: > skip set_scanout if framebuffer didn't change") causes the screen stay > blank. Add a bool to force an update to fi

Re: [PATCH v1 1/6] mfd: Add driver for Embedded Controller found on Acer Iconia Tab A500

On Sun, 23 Aug 2020, Dmitry Osipenko wrote: > 23.08.2020 21:16, Lubomir Rintel пишет: > > Hello, > ... > >> +config MFD_ACER_A500_EC > >> + tristate "Embedded Controller driver for Acer Iconia Tab A500" > >> + depends on (I2C_TEGRA && ARCH_TEGRA_2x_SOC) || COMPILE_TEST > > > > This seems to als

Re: [PATCH 2/3] block: fix locking for struct block_device size updates

On 8/23/20 11:10 AM, Christoph Hellwig wrote: > Two different callers use two different mutexes for updating the > block device size, which obviously doesn't help to actually protect > against concurrent updates from the different callers. In addition > one of the locks, bd_mutex is rather prone t

Re: [PATCH 4/5] bio: introduce BIO_FOLL_PIN flag

On 8/22/20 11:57 PM, John Hubbard wrote: On 8/22/20 11:25 PM, Christoph Hellwig wrote: On Fri, Aug 21, 2020 at 09:20:58PM -0700, John Hubbard wrote: Add a new BIO_FOLL_PIN flag to struct bio, whose "short int" flags field was full, thuse triggering an expansion of the field from 16, to 32 bits.

Re: [PATCH 3/3] nvme: don't call revalidate_disk from nvme_set_queue_dying

On 8/23/20 11:10 AM, Christoph Hellwig wrote: > In nvme_set_queue_dying we really just want to ensure the disk and bdev > sizes are set to zero. Going through revalidate_disk leads to a somewhat > arcance and complex callchain relying on special behavior in a few > places. Instead just lift the s

Re: [PATCH v5 1/3] dmaengine: ptdma: Initial driver for the AMD PTDMA controller

Apologies for my delayed response. On 7/3/2020 12:48 PM, Vinod Koul wrote: > [CAUTION: External Email] > > On 16-06-20, 20:11, Sanjay R Mehta wrote: > >> +static int pt_core_execute_cmd(struct ptdma_desc *desc, >> +struct pt_cmd_queue *cmd_q) >> +{ >> + __le32 *mp

Re: [PATCH v8 1/4] power: supply: core: add quick charge type property

On Mon, Aug 24, 2020 at 08:54:56AM +0800, Qiwu Huang wrote: > On Tue, Aug 18, 2020 at 2:07 PM Greg KH wrote: > > > > On Tue, Aug 18, 2020 at 09:56:28AM +0800, Qiwu Huang wrote: > > > On Fri, Aug 14, 2020 at 2:09 PM Greg KH > > > wrote: > > > > > > > > On Fri, Aug 14, 2020 at 11:46:54AM +0800, Qi

Re: [PATCH v5 00/16] Allwinner A100 Initial support

ping..

Re: [PATCH] memory: samsung: exynos5422-dmc: propagate error from exynos5_counters_get()

Hi, On 17.08.2020 14:27, Lukasz Luba wrote: > On 8/17/20 1:07 PM, Krzysztof Kozlowski wrote: >> On Tue, Aug 04, 2020 at 01:38:11PM +0100, Lukasz Luba wrote: >>> On 8/4/20 1:19 PM, Marek Szyprowski wrote: On 04.08.2020 11:11, Lukasz Luba wrote: > On 8/4/20 7:12 AM, Marek Szyprowski wrote:

Re: [GIT PULL] tee subsystem pin_user_pages for v5.8

On Mon, Aug 24, 2020 at 9:18 AM John Hubbard wrote: > > On 8/23/20 11:51 PM, Jens Wiklander wrote: > > On Fri, Aug 21, 2020 at 11:19 PM Olof Johansson wrote: > >> > >> On Fri, Aug 21, 2020 at 12:58 PM John Hubbard wrote: > >>> > >>> On 8/21/20 11:49 AM, Olof Johansson wrote: > On Tue, May 2

Re: [PATCH v4] dt-binding: phy: convert ti,omap-usb2 to YAML

Hi, On 21/08/2020 11:11, Roger Quadros wrote: Move ti,omap-usb2 to its own YAML schema. Signed-off-by: Roger Quadros Reviewed-by: Rob Herring --- v4 - fix example to fix dt_binding_check warnings - '#phy-cells' -> "#phy-cells" - Add 'oneOf' to compatible logic to allow just "ti,omap-usb2" as

[PATCH 0/1] convert l2 cache dt bindings to YAML format

The patch is created on mainline linux v5.8.rc-7 commit 92ed30191993 ("Linux 5.8-rc7") Following is the log for dt_binding_check and dtbs_check linux> make DT_SCHEMA_FLAGS="-u" DT_SCHEMA_FILES="Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml" dt_binding_check HOSTCC scripts/dtc/

[PATCH v6 0/2] phy: omap-usb2-phy: Errata and coding style fix

Hi, This series addresses silicon errata i2075 - "USB2PHY: USB2PHY Charger Detect is Enabled by Default Without VBUS Presence" It also fixes coding style issues. cheers, -roger Changelog: v6 - move coding style fixes to separate patch v5 - don't use dt property to enable workaround. Use soc

[PATCH 1/1] dt-bindings: riscv: sifive-l2-cache: convert bindings to json-schema

Convert the device tree bindings for the SiFive's FU540-C000 SoC's L2 Cache controller to YAML format. Signed-off-by: Sagar Kadam --- .../devicetree/bindings/riscv/sifive-l2-cache.txt | 51 .../devicetree/bindings/riscv/sifive-l2-cache.yaml | 93 ++ 2 files chan

[PATCH v6 2/2] phy: omap-usb2-phy: fix coding style issues

Fix checkpatch warnings and sort the include files alphabetically. Signed-off-by: Roger Quadros --- drivers/phy/ti/phy-omap-usb2.c | 36 -- 1 file changed, 17 insertions(+), 19 deletions(-) diff --git a/drivers/phy/ti/phy-omap-usb2.c b/drivers/phy/ti/phy-omap-usb

[PATCH v6 1/2] phy: omap-usb2-phy: disable PHY charger detect

AM654x PG1.0 has a silicon bug that D+ is pulled high after POR, which could cause enumeration failure with some USB hubs. Disabling the USB2_PHY Charger Detect function will put D+ into the normal state. This addresses Silicon Errata: i2075 - "USB2PHY: USB2PHY Charger Detect is Enabled by Defaul

Re: [PATCH] ARM: dts: imx6sx-sdb: Add headphone detection for sound card

Hi Shawn, Fabio > > > > > I would like to know your opinion, should I move headphone detect > > > GPIO To audmux group? > > > > What about adding a dedicated pinctrl_hp for the headphone detect pin > > like it is done at: > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit. >

[PATCH v2 0/3] Add headphone detection for sound card

Add headphone detection for sound card and add audio sound card node for imx6sll. Shengjiu Wang (3): ARM: dts: imx6sx-sdb: Add headphone detection for sound card ARM: dts: imx6sl-evk: Add headphone detection for sound card ARM: dts: imx6sll-evk: Add audio sound card node changes in v2 - add

[PATCH v2 3/3] ARM: dts: imx6sll-evk: Add audio sound card node

Add audio sound card node, which depends on codec node, SSI node, audmux node. Signed-off-by: Shengjiu Wang --- arch/arm/boot/dts/imx6sll-evk.dts | 73 +++ 1 file changed, 73 insertions(+) diff --git a/arch/arm/boot/dts/imx6sll-evk.dts b/arch/arm/boot/dts/imx6sll-ev

[PATCH v2 2/3] ARM: dts: imx6sl-evk: Add headphone detection for sound card

Headphone detection is triggered by GPIO, then driver can switch between speaker and headphone. Signed-off-by: Shengjiu Wang --- arch/arm/boot/dts/imx6sl-evk.dts | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm/boot/dts/imx6sl-evk.dts b/arch/arm/boot/dts/imx6sl-evk.dts index

[PATCH v2 1/3] ARM: dts: imx6sx-sdb: Add headphone detection for sound card

Headphone detection is triggered by GPIO, then driver can switch between speaker and headphone. Signed-off-by: Shengjiu Wang --- arch/arm/boot/dts/imx6sx-sdb.dtsi | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm/boot/dts/imx6sx-sdb.dtsi b/arch/arm/boot/dts/imx6sx-sdb.dtsi i

Re: [PATCH v3 6/6] sdhci: tegra: Add missing TMCLK for data timeout

On Thu, 6 Aug 2020 at 02:32, Sowjanya Komatineni wrote: > > commit b5a84ecf025a ("mmc: tegra: Add Tegra210 support") > > Tegra210 and later has a separate sdmmc_legacy_tm (TMCLK) used by Tegra > SDMMC hawdware for data timeout to achive better timeout than using > SDCLK and using TMCLK is recommen

Re: [PATCH v4 1/2] selinux: add tracepoint on audited events

> Merged into selinux/next, thanks! Thanks everyone for the reviews and constructive feedback!

Re: [PATCH v5 00/16] Allwinner A100 Initial support

On Mon, 24 Aug 2020, Frank Lee wrote: > ping.. "Please don't send content free pings and please allow a reasonable time for review. People get busy, go on holiday, attend conferences and so on so unless there is some reason for urgency (like critical bug fixes) please allow at least a cou

[PATCH RESEND] ASoC: fsl_sai: Add -EPROBE_DEFER check for regmap init

Regmap initialization may return -EPROBE_DEFER for clock may not be ready, so check -EPROBE_DEFER error type before start another Regmap initialization. Signed-off-by: Shengjiu Wang Acked-by: Nicolin Chen --- sound/soc/fsl/fsl_sai.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --

Re: KASAN: use-after-free Write in vcs_read

On 22. 08. 20, 9:34, Jiri Slaby wrote: > On 22. 08. 20, 9:31, syzbot wrote: >> syzbot has bisected this issue to: >> >> commit b1c32fcfadf5593ab7a63261cc8a5747c36e627e >> Author: Jiri Slaby >> Date: Tue Aug 18 08:57:05 2020 + >> >> vc_screen: extract vcs_read_buf_header > > It's like 7t

[PATCH v2 0/6] kasan: add workqueue and timer stack for generic KASAN

Syzbot reports many UAF issues for workqueue or timer, see [1] and [2]. In some of these access/allocation happened in process_one_work(), we see the free stack is useless in KASAN report, it doesn't help programmers to solve UAF on workqueue. The same may stand for times. This patchset improves K

Re: linux-next: build failure after merge of the net-next tree

On 2020-08-22 08:16 +0200, Sven Joachim wrote: > On 2020-08-21 09:23 -0700, Brian Vazquez wrote: > >> Hi Sven, >> >> Sorry for the late reply, did you still see this after: >> https://patchwork.ozlabs.org/project/netdev/patch/20200803131948.41736-1-yuehaib...@huawei.com/ >> ?? > > That patch is ap

Re: (EXT) Re: [PATCH net-next 2/2] net: phy: dp83867: apply ti, led-function and ti, led-ctrl to registers

On Sat, 2020-08-22 at 18:08 +0200, Andrew Lunn wrote: > On Fri, Aug 21, 2020 at 09:21:46AM +0200, Matthias Schiffer wrote: > > These DT bindings are already in use by the imx7-mba7 DTS, but they > > were > > not supported by the PHY driver so far. > > > > Signed-off-by: Matthias Schiffer > > > >

[PATCH v2 1/6] timer: kasan: record timer stack

When analyze use-after-free or double-free issue, recording the timer stacks is helpful to to preserve usage history which potentially gives a hint about the affected code. Record the most recent two timer init calls in KASAN which are printed on failure in the KASAN report. For timers it has tur

[PATCH v2 2/6] workqueue: kasan: record workqueue stack

Records the last two enqueuing work call stacks in order to print them in KASAN report. It is useful for programmers to solve use-after-free or double-free memory workqueue issue. For workqueue it has turned out to be useful to record the enqueuing work call stacks. Because user can see KASAN repo

[PATCH v2 3/6] kasan: print timer and workqueue stack

The aux_stack[2] is reused to record the call_rcu() call stack, timer init call stack, and enqueuing work call stacks. So that we need to change the auxiliary stack title for common title, print them in KASAN report. Signed-off-by: Walter Wu Suggested-by: Marco Elver Cc: Andrey Ryabinin Cc: Dmi

[PATCH v2 4/6] kasan: add tests for timer stack recording

Adds a test to verify timer stack recording and print it in KASAN report. The KASAN report was as follows(cleaned up slightly): BUG: KASAN: use-after-free in kasan_timer_uaf Freed by task 0: kasan_save_stack+0x24/0x50 kasan_set_track+0x24/0x38 kasan_set_free_info+0x20/0x40 __kasan_sla

[PATCH v2 6/6] kasan: update documentation for generic kasan

Generic KASAN support to record the last two timer and workqueue stacks and print them in KASAN report. So that need to update documentation. Signed-off-by: Walter Wu Cc: Andrey Ryabinin Cc: Dmitry Vyukov Cc: Alexander Potapenko Cc: Jonathan Corbet --- Documentation/dev-tools/kasan.rst | 4 +

[PATCH v2 5/6] kasan: add tests for workqueue stack recording

Adds a test to verify workqueue stack recording and print it in KASAN report. The KASAN report was as follows(cleaned up slightly): BUG: KASAN: use-after-free in kasan_workqueue_uaf Freed by task 54: kasan_save_stack+0x24/0x50 kasan_set_track+0x24/0x38 kasan_set_free_info+0x20/0x40 __k

Re: [PATCH 00/32] Set 2: Rid W=1 warnings in Wireless

On Sat, 22 Aug 2020, Christian Lamparter wrote: > On 2020-08-21 09:16, Lee Jones wrote: > > This set is part of a larger effort attempting to clean-up W=1 > > kernel builds, which are currently overwhelmingly riddled with > > niggly little warnings. > > > I see that after our discussion about the

Re: [PATCH v10 2/2] Add PWM fan controller driver for LGM SoC

On Mon, Aug 24, 2020 at 11:36:37AM +0800, Rahul Tanwar wrote: > Intel Lightning Mountain(LGM) SoC contains a PWM fan controller. > This PWM controller does not have any other consumer, it is a > dedicated PWM controller for fan attached to the system. Add > driver for this PWM fan controller. ...

Re: stable-rc 4.14: arm64: Internal error: Oops: clk_reparent __clk_set_parent_before on db410c

On Thu, Aug 13, 2020 at 07:30:40PM +0530, Naresh Kamboju wrote: > On Wed, 12 Aug 2020 at 23:14, Stephen Boyd wrote: > > > > Quoting Stephen Boyd (2020-07-23 03:26:02) > > > Quoting Naresh Kamboju (2020-07-23 03:10:37) > > > > On Thu, 23 Jul 2020 at 13:36, Stephen Boyd wrote: > > > > > > > > > > I

RE: Lockdep warning caused by "driver core: Fix sleeping in invalid context during device link deletion"

> From: Saravana Kannan > Sent: Saturday, August 22, 2020 2:28 AM > > On Thu, Aug 20, 2020 at 8:50 PM Dong Aisheng > wrote: > > > > Hi ALL, > > > > We met the below WARNING during system suspend on an iMX6Q SDB board > > with the latest linus/master branch (v5.9-rc1+) and next-20200820. > > v5.8

Re: [PATCH v3] firmware_loader: fix memory leak for paged buffer

On Thu, 20 Aug 2020 22:57:50 +0200, Prateek Sood wrote: > > vfree() is being called on paged buffer allocated > using alloc_page() and mapped using vmap(). > > Freeing of pages in vfree() relies on nr_pages of > struct vm_struct. vmap() does not update nr_pages. > It can lead to memory leaks. >

Re: [PATCH v3] firmware_loader: fix memory leak for paged buffer

On Mon, Aug 24, 2020 at 10:19:50AM +0200, Takashi Iwai wrote: > On Thu, 20 Aug 2020 22:57:50 +0200, > Prateek Sood wrote: > > > > vfree() is being called on paged buffer allocated > > using alloc_page() and mapped using vmap(). > > > > Freeing of pages in vfree() relies on nr_pages of > > struct

Re: [PATCH] mtd: spi-nor: intel-spi: Do not try to make the SPI flash chip writable

On Sat, Aug 22, 2020 at 06:06:03PM +0200, Arnd Bergmann wrote: > On Wed, Aug 19, 2020 at 11:11 AM Mika Westerberg > wrote: > > On Wed, Aug 19, 2020 at 10:38:24AM +0200, Arnd Bergmann wrote: > > > On Wed, Aug 19, 2020 at 8:57 AM Mika Westerberg > > > wrote: > > > > > > Actually thinking about thi

Re: KASAN: use-after-free Write in vcs_read

On Mon, Aug 24, 2020 at 10:03:54AM +0200, Jiri Slaby wrote: > On 22. 08. 20, 9:34, Jiri Slaby wrote: > > On 22. 08. 20, 9:31, syzbot wrote: > >> syzbot has bisected this issue to: > >> > >> commit b1c32fcfadf5593ab7a63261cc8a5747c36e627e > >> Author: Jiri Slaby > >> Date: Tue Aug 18 08:57:05 202

Re: [PATCH v5 3/3] dmaengine: ptdma: Add debugfs entries for PTDMA information

> > On 16-06-20, 20:11, Sanjay R Mehta wrote: >> From: Sanjay R Mehta >> >> Expose data about the configuration and operation of the >> PTDMA through debugfs entries: device name, capabilities, >> configuration, statistics. >> >> Signed-off-by: Sanjay R Mehta >> --- >> drivers/dma/ptdma/Makef

[PATCH] dt-bindings: mmc: Add missing description for clk_in/out_sd1

The commit a8fdb80f4d47 ("arm64: zynqmp: Add ZynqMP SDHCI compatible string") added clock-output-names for both SDHCIs before DT binding yaml conversion. But only clk_in/out_sd0 clock names have been covered by DT binding which ends up with dt yaml checking warnings as: >From schema: .../Documentat

[PATCH] watchdog: sbsa_gwdt: add shutdown hook to driver

From: Zhao Qiang Kexec maybe need more time than timeout of wdt(sbsa) which will reset the system. So it is necessary to add shutdown hook to disable the wdt when run kexec. Signed-off-by: Zhao Qiang --- drivers/watchdog/sbsa_gwdt.c | 9 + 1 file changed, 9 insertions(+) diff --git a/

Re: [PATCH 1/3] block: replace bd_set_size with bd_set_nr_sectors

Reviewed-by: Sagi Grimberg

Re: [PATCH 3/3] nvme: don't call revalidate_disk from nvme_set_queue_dying

Reviewed-by: Sagi Grimberg

RE: [PATCH v5] kernel/trace: Add DISALLOW_TRACE_PRINTK make option

From: Nicolas Boichat > Sent: 24 August 2020 03:59 > > trace_printk is meant as a debugging tool, and should not be > compiled into production code without specific debug Kconfig > options enabled, or source code changes, as indicated by the > warning that shows up on boot if any trace_printk is c

Re: [PATCH 2/3] block: fix locking for struct block_device size updates

Reviewed-by: Sagi Grimberg

Re: [PATCH v1] brcmfmac: increase F2 watermark for BCM4329

On 8/23/2020 4:20 PM, Dmitry Osipenko wrote: This patch fixes SDHCI CRC errors during of RX throughput testing on BCM4329 chip if SDIO BUS is clocked above 25MHz. In particular the checksum problem is observed on NVIDIA Tegra20 SoCs. The good watermark value is borrowed from downstream BCMDHD

[PATCH] arm64: dts: zynqmp: Remove undocumented u-boot properties

u-boot, DT properties are not documented anywhere in Linux DT binding that's why remove them. Signed-off-by: Michal Simek --- arch/arm64/boot/dts/xilinx/zynqmp-clk-ccf.dtsi | 5 - arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 1 - 2 files changed, 6 deletions(-) diff --git a/arch/arm64/

RE: [PATCH RESEND 04/10] crypto: hisilicon/zip - replace 'sprintf' with 'scnprintf'

From: Yang Shen > Sent: 24 August 2020 04:12 > > Replace 'sprintf' with 'scnprintf' to avoid overrun. > > Signed-off-by: Yang Shen > Reviewed-by: Zhou Wang > --- > drivers/crypto/hisilicon/zip/zip_main.c | 11 +++ > 1 file changed, 7 insertions(+), 4 deletions(-) > > diff --git a/driv

[PATCH 5.8 001/148] drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()

From: Chris Wilson [ Upstream commit 119c53d2d4044c59c450c4f5a568d80b9d861856 ] drm_gem_dumb_map_offset() now exists and does everything vgem_gem_dump_map does and *ought* to do. In particular, vgem_gem_dumb_map() was trying to reject mmapping an imported dmabuf by checking the existence of obj

[PATCH 5.8 014/148] romfs: fix uninitialized memory leak in romfs_dev_read()

From: Jann Horn commit bcf85fcedfdd17911982a3e3564fcfec7b01eebd upstream. romfs has a superblock field that limits the size of the filesystem; data beyond that limit is never accessed. romfs_dev_read() fetches a caller-supplied number of bytes from the backing device. It returns 0 on success o

[PATCH 5.8 017/148] squashfs: avoid bio_alloc() failure with 1Mbyte blocks

From: Phillip Lougher commit f26044c83e6e473a61917f5db411d1417327d425 upstream. This is a regression introduced by the patch "migrate from ll_rw_block usage to BIO". Bio_alloc() is limited to 256 pages (1 Mbyte). This can cause a failure when reading 1 Mbyte block filesystems. The problem is

[PATCH 5.8 015/148] kernel/relay.c: fix memleak on destroy relay channel

From: Wei Yongjun commit 71e843295c680898959b22dc877ae3839cc22470 upstream. kmemleak report memory leak as follows: unreferenced object 0x607ee4e5f948 (size 8): comm "syz-executor.1", pid 2098, jiffies 4295031601 (age 288.468s) hex dump (first 8 bytes): 00 00 00 00 00 00 00 00

[PATCH 5.8 013/148] mm/vunmap: add cond_resched() in vunmap_pmd_range

From: Aneesh Kumar K.V commit e47110e90584a22e9980510b00d0dfad3a83354e upstream. Like zap_pte_range add cond_resched so that we can avoid softlockups as reported below. On non-preemptible kernel with large I/O map region (like the one we get when using persistent memory with sector mode), an un

[PATCH 5.8 002/148] drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel

From: Paul Cercueil [ Upstream commit bad20a2dbfdfaf01560026909506b6ed69d65ba2 ] The FRD350H54004 panel was marked as having active-high VSYNC and HSYNC signals, which sorts-of worked, but resulted in the picture fading out under certain circumstances. Fix this issue by marking VSYNC and HSYNC

[PATCH 5.8 010/148] can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated

From: Oleksij Rempel commit af804b7826350d5af728dca4715e473338fbd7e5 upstream. This patch adds check to ensure that the struct net_device::ml_priv is allocated, as it is used later by the j1939 stack. The allocation is done by all mainline CAN network drivers, but when using bond or team device

[PATCH 5.8 034/148] s390/pci: ignore stale configuration request event

From: Niklas Schnelle commit b76fee1bc56c31a9d2a49592810eba30cc06d61a upstream. A configuration request event may be stale, that is the event may reference a zdev which was already configured. This can happen when a hotplug happens during boot such that the device is discovered and configured in

[PATCH 5.8 008/148] ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion

From: Mike Pozulp commit e17f02d0559c174cf1f6435e45134490111eaa37 upstream. The Galaxy Book Ion uses the same ALC298 codec as other Samsung laptops which have the no headphone sound bug, like my Samsung Notebook. The Galaxy Book owner confirmed that this patch fixes the bug. BugLink: https://bu

[PATCH 5.8 009/148] can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in j1939_tp_txtimer()

From: Oleksij Rempel commit cd3b3636c99fcac52c598b64061f3fe4413c6a12 upstream. The current stack implementation do not support ECTS requests of not aligned TP sized blocks. If ECTS will request a block with size and offset spanning two TP blocks, this will cause memcpy() to read beyond the queu

[PATCH 5.8 005/148] khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()

From: Hugh Dickins [ Upstream commit f3f99d63a8156c7a4a6b20aac22b53c5579c7dc1 ] syzbot crashes on the VM_BUG_ON_MM(khugepaged_test_exit(mm), mm) in __khugepaged_enter(): yes, when one thread is about to dump core, has set core_state, and is waiting for others, another might do something calling

[PATCH 5.8 039/148] drm/amd/display: Fix EDID parsing after resume from suspend

From: Stylon Wang commit b24bdc37d03a0478189e20a50286092840f414fa upstream. [Why] Resuming from suspend, CEA blocks from EDID are not parsed and no video modes can support YUV420. When this happens, output bpc cannot go over 8-bit with 4K modes on HDMI. [How] In amdgpu_dm_update_connector_after

[PATCH 5.8 032/148] s390/pci: re-introduce zpci_remove_device()

From: Niklas Schnelle commit 2f0230b2f2d5fd287a85583eefb5aed35b6fe510 upstream. For fixing the PF to VF link removal we need to perform some action on every removal of a zdev from the common PCI subsystem. So in preparation re-introduce zpci_remove_device() and use that instead of directly calli

[PATCH 5.8 020/148] ASoC: amd: renoir: restore two more registers during resume

From: Hui Wang commit ccff7bd468d5e0595176656a051ef67c01f01968 upstream. Recently we found an issue about the suspend and resume. If dmic is recording the sound, and we run suspend and resume, after the resume, the dmic can't work well anymore. we need to close the app and reopen the app, then t

[PATCH 5.8 004/148] drm/ast: Initialize DRAM type before posting GPU

From: Thomas Zimmermann [ Upstream commit 244d012801dae30c91983b360457c78d481584b0 ] Posting the GPU requires the correct DRAM type to be stored in struct ast_private. Therefore first initialize the DRAM info and then post the GPU. This restores the original order of instructions in this functio

[PATCH 5.8 006/148] ALSA: hda: avoid reset of sdo_limit

From: Sameer Pujar commit b90b925fd52c75ee7531df739d850a1f7c58ef06 upstream. By default 'sdo_limit' is initialized with a default value of '8' as per spec. This is overridden in cases where a different value is required. However this is getting reset when snd_hdac_bus_init_chip() is called again

[PATCH 5.8 031/148] s390/pci: fix zpci_bus_link_virtfn()

From: Niklas Schnelle commit 3cddb79afc60bcdb5fd9dd7a1c64a8d03bdd460f upstream. We were missing the pci_dev_put() for candidate PFs. Furhtermore in discussion with upstream it turns out that somewhat counterintuitively some common code, in particular the vfio-pci driver, assumes that pdev->is_v

[PATCH 5.8 021/148] RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request

From: Kaike Wan commit b25e8e85e75a61af1ddc88c4798387dd3132dd43 upstream. The following message occurs when running an AI application with TID RDMA enabled: hfi1 :7f:00.0: hfi1_0: [QP74] hfi1_tid_timeout 4084 hfi1 :7f:00.0: hfi1_0: [QP70] hfi1_tid_timeout 4084 The issue happens when TI

[PATCH 5.8 037/148] drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal

From: Daniel Kolesa commit f41ed88cbd6f025f7a683a11a74f901555fba11c upstream. GFP_KERNEL may and will sleep, and this is being executed in a non-preemptible context; this will mess things up since it's called inbetween DC_FP_START/END, and rescheduling will result in the DC_FP_END later being ca

[PATCH 5.8 048/148] media: coda: jpeg: add NULL check after kmalloc

From: Chen Zhou [ Upstream commit 20171723144ca0d057b72e852536992fd371369a ] Fixes coccicheck warning: ./drivers/media/platform/coda/coda-jpeg.c:331:3-31: alloc with no test, possible model on line 354 Add NULL check after kmalloc. Signed-off-by: Chen Zhou Signed-off-by: Hans Verkuil

[PATCH 5.8 023/148] opp: Put opp table in dev_pm_opp_set_rate() for empty tables

From: Stephen Boyd commit 8979ef70850eb469e1094279259d1ef393ffe85f upstream. We get the opp_table pointer at the top of the function and so we should put the pointer at the end of the function like all other exit paths from this function do. Cc: v5.7+ # v5.7+ Fixes: aca48b61f963 ("opp: Manage

[PATCH 5.8 024/148] opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails

From: Stephen Boyd commit d4ec88d205583ac4f9482cf3e89128589bd881d2 upstream. We get the opp_table pointer at the top of the function and so we should put the pointer at the end of the function like all other exit paths from this function do. Cc: v5.8+ # v5.8+ Fixes: b00e667a6d8b ("opp: Remove

[PATCH 5.8 042/148] drm/amd/display: fix pow() crashing when given base 0

From: Krunoslav Kovac commit d2e59d0ff4c44d1f6f8ed884a5bea7d1bb7fd98c upstream. [Why&How] pow(a,x) is implemented as exp(x*log(a)). log(0) will crash. So return 0^x = 0, unless x=0, convention seems to be 0^0 = 1. Cc: sta...@vger.kernel.org Signed-off-by: Krunoslav Kovac Reviewed-by: Anthony K

[PATCH 5.8 049/148] f2fs: fix to check page dirty status before writeback

From: Chao Yu [ Upstream commit eb1353cfa9c1e9415b03dc117f8399969fa02102 ] In f2fs_write_raw_pages(), we need to check page dirty status before writeback, because there could be a racer (e.g. reclaimer) helps writebacking the dirty page. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim Signe

[PATCH 5.8 043/148] drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON

From: Pankaj Bharadiya [ Upstream commit bf07f6ebffefce2bbf3c318f9ce2f987774ea983 ] struct drm_device specific drm_WARN* macros include device information in the backtrace, so we know what device the warnings originate from. Prefer drm_WARN_ON over WARN_ON. Signed-off-by: Pankaj Bharadiya Sig

[PATCH 5.8 025/148] ext4: do not block RWF_NOWAIT dio write on unallocated space

From: Jan Kara commit 0b3171b6d195637f84ddf8b59bae818ea20bc8ac upstream. Since commit 378f32bab371 ("ext4: introduce direct I/O write using iomap infrastructure") we don't properly bail out of RWF_NOWAIT direct IO write if underlying blocks are not allocated. Also ext4_dio_write_checks() does no

[PATCH 5.8 022/148] opp: Enable resources again if they were disabled earlier

From: Rajendra Nayak commit a4501bac0e553bed117b7e1b166d49731caf7260 upstream. dev_pm_opp_set_rate() can now be called with freq = 0 in order to either drop performance or bandwidth votes or to disable regulators on platforms which support them. In such cases, a subsequent call to dev_pm_opp_se

[PATCH 5.8 044/148] drm/i915: Provide the perf pmu.module

From: Chris Wilson [ Upstream commit df3ab3cb7eae63c6eb7c9aebcc196a75d59f65dd ] Rather than manually implement our own module reference counting for perf pmu events, finally realise that there is a module parameter to struct pmu for this very purpose. Signed-off-by: Chris Wilson Cc: Tvrtko Urs

[PATCH 5.8 046/148] scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM

From: Bodo Stroesser [ Upstream commit 3145550a7f8b08356c8ff29feaa6c56aca12901d ] This patch fixes the following crash (see https://bugzilla.kernel.org/show_bug.cgi?id=208045) Process iscsi_trx (pid: 7496, stack limit = 0x10dd111a) CPU: 0 PID: 7496 Comm: iscsi_trx Not tainted 4.19.118

[PATCH 5.8 069/148] alpha: fix annotation of io{read,write}{16,32}be()

From: Luc Van Oostenryck [ Upstream commit bd72866b8da499e60633ff28f8a4f6e09ca78efe ] These accessors must be used to read/write a big-endian bus. The value returned or written is native-endian. However, these accessors are defined using be{16,32}_to_cpu() or cpu_to_be{16,32}() to make the end

[PATCH 5.8 052/148] f2fs: should avoid inode eviction in synchronous path

From: Jaegeuk Kim [ Upstream commit b0f3b87fb3abc42c81d76c6c5795f26dbdb2f04b ] https://bugzilla.kernel.org/show_bug.cgi?id=208565 PID: 257TASK: ecdd CPU: 0 COMMAND: "init" #0 [] (__schedule) from [] #1 [] (schedule) from [] #2 [] (rwsem_down_read_failed) from [] #3 [] (down_r

[PATCH 5.8 067/148] tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null pointer dereference

From: Gaurav Singh [ Upstream commit d830020656c5b68ced962ed3cb51a90e0a89d4c4 ] Haven't reproduced this issue. This PR is does a minor code cleanup. Signed-off-by: Gaurav Singh Signed-off-by: Andrew Morton Reviewed-by: Andrew Morton Cc: Shuah Khan Cc: Tejun Heo Cc: Michal Koutn Cc: Roman

[PATCH 5.8 078/148] ASoC: q6afe-dai: mark all widgets registers as SND_SOC_NOPM

From: Srinivas Kandagatla [ Upstream commit 56235e4bc5ae58cb8fcd9314dba4e9ab077ddda8 ] Looks like the q6afe-dai dapm widget registers are set as "0", which is a not correct. As this registers will be read by ASoC core during startup which will throw up errors, Fix this by making the registers a

Re: [PATCH] PM: sleep: core: Fix the handling of pending runtime resume requests

Hi, On Fri, Aug 21, 2020 at 03:34:42PM -0400, Alan Stern wrote: > This means that the code could be simplified to just: > > pm_runtime_barrier(dev); > > Will this fix the reported bug? It seems likely to me that the actual > problem with the failure scenario in the patch description was

  1   2   3   4   5   6   7   8   9   10   >