spi: spi-cadence: Fix SPI CS gets toggling sporadically
Subsystems (21)
Sasha Levin
maintainerPATCH 1/53 spi: spi-cadence: Fix SPI CS gets toggling sporadically
From: Sai Krishna Potthuri <[email protected]>
[ Upstream commit 21b511ddee09a78909035ec47a6a594349fe3296 ]
As part of unprepare_transfer_hardware, SPI controller will be disabled which will indirectly deassert the CS line. This will create a problem in some of the devices where message will be transferred with cs_change flag set(CS should not be deasserted).
As per SPI controller implementation, if SPI controller is disabled then all output enables are inactive and all pins are set to input mode which means CS will go to default state high(deassert). This leads to an issue when core explicitly ask not to deassert the CS (cs_change = 1). This patch fix the above issue by checking the Slave select status bits from configuration register before disabling the SPI.
--- drivers/spi/spi-cadence.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
drivers/spi/spi-cadence.c +8 -2
@@ -69,6 +69,7 @@#define CDNS_SPI_BAUD_DIV_SHIFT 3/* Baud rate divisor shift in CR */ #define CDNS_SPI_SS_SHIFT 10/* Slave Select field shift in CR */ #define CDNS_SPI_SS0 0x1/* Slave Select zero */ +#define CDNS_SPI_NOSS 0x3C/* No Slave select */ /* * SPI Interrupt Registers bit Masks
@@ -449,15 +450,20 @@ static int cdns_prepare_transfer_hardware(struct spi_master *master)* @master: Pointer to the spi_master structure which provides * information about the controller. * -* This function disables the SPI master controller. +* This function disables the SPI master controller when no slave selected. * * Return: 0 always */ static int cdns_unprepare_transfer_hardware (struct spi_master *master) {struct cdns_spi *xspi =spi_master_get_devdata (master); +u32 ctrl_reg; -cdns_spi_write (xspi,CDNS_SPI_ER ,CDNS_SPI_ER_DISABLE ); +/* Disable the SPI if slave is deselected */ + ctrl_reg =cdns_spi_read (xspi,CDNS_SPI_CR ); + ctrl_reg = (ctrl_reg &CDNS_SPI_CR_SSCTRL ) >>CDNS_SPI_SS_SHIFT ; +if (ctrl_reg ==CDNS_SPI_NOSS ) +cdns_spi_write (xspi,CDNS_SPI_ER ,CDNS_SPI_ER_DISABLE );return 0 ; }
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 2/53 spi: cadence: Detect transmit FIFO depth
From: Lars-Peter Clausen <[email protected]>
[ Upstream commit 7b40322f7183a92c4303457528ae7cda571c60b9 ]
The depth of the transmit FIFO for the Cadence SPI controller is currently hardcoded to 128. But the depth is a synthesis configuration parameter of the core and can vary between different SoCs.
If the configured FIFO size is less than 128 the driver will busy loop in the cdns_spi_fill_tx_fifo() function waiting for FIFO space to become available.
Depending on the length and speed of the transfer it can spin for a significant amount of time. The cdns_spi_fill_tx_fifo() function is called from the drivers interrupt handler, so it can leave interrupts disabled for a prolonged amount of time.
In addition the read FIFO will also overflow and data will be discarded.
To avoid this detect the actual size of the FIFO and use that rather than the hardcoded value.
To detect the FIFO size the FIFO threshold register is used. The register is sized so that it can hold FIFO size - 1 as its maximum value. Bits that are not needed to hold the threshold value will always read 0. By writing 0xffff to the register and then reading back the value in the register we get the FIFO size.
--- drivers/spi/spi-cadence.c | 27 +++++++++++++++++++++++---- 1 file changed, 23 insertions(+), 4 deletions(-)
drivers/spi/spi-cadence.c +23 -4
@@ -93,9 +93,6 @@#define CDNS_SPI_ER_ENABLE 0x00000001/* SPI Enable Bit Mask */ #define CDNS_SPI_ER_DISABLE 0x0/* SPI Disable Bit Mask */ -/* SPI FIFO depth in bytes */ -#define CDNS_SPI_FIFO_DEPTH 128 -/* Default number of chip select lines */ #define CDNS_SPI_DEFAULT_NUM_CS 4
@@ -111,6 +108,7 @@* @rx_bytes: Number of bytes requested * @dev_busy: Device busy flag * @is_decoded_cs: Flag for decoder property set or not +* @tx_fifo_depth: Depth of the TX FIFO */ struct cdns_spi {void __iomem *regs;
@@ -124,6 +122,7 @@ struct cdns_spi {int rx_bytes;u8 dev_busy;u32 is_decoded_cs; +unsigned int tx_fifo_depth; };/* Macros for the SPI controller read/write */
@@ -305,7 +304,7 @@ static void cdns_spi_fill_tx_fifo(struct cdns_spi *xspi) {unsigned long trans_cnt =0 ; -while ((trans_cnt <CDNS_SPI_FIFO_DEPTH ) && +while ((trans_cnt < xspi->tx_fifo_depth) && (xspi->tx_bytes >0 )) {/* When xspi in busy condition, bytes may send failed,
@@ -468,6 +467,24 @@ static int cdns_unprepare_transfer_hardware(struct spi_master *master)return 0 ; } +/** +* cdns_spi_detect_fifo_depth - Detect the FIFO depth of the hardware +* @xspi: Pointer to the cdns_spi structure +* +* The depth of the TX FIFO is a synthesis configuration parameter of the SPI +* IP. The FIFO threshold register is sized so that its maximum value can be the +* FIFO size - 1. This is used to detect the size of the FIFO. +*/ +static void cdns_spi_detect_fifo_depth (struct cdns_spi *xspi) +{ +/* The MSBs will get truncated giving us the size of the FIFO */ +cdns_spi_write (xspi,CDNS_SPI_THLD ,0xffff ); + xspi->tx_fifo_depth =cdns_spi_read (xspi,CDNS_SPI_THLD ) +1 ; + +/* Reset to default */ +cdns_spi_write (xspi,CDNS_SPI_THLD ,0x1 ); +} +/** * cdns_spi_probe - Probe method for the SPI driver * @pdev: Pointer to the platform_device structure
@@ -540,6 +557,8 @@ static int cdns_spi_probe(struct platform_device *pdev)if (ret <0 ) xspi->is_decoded_cs =0 ; +cdns_spi_detect_fifo_depth (xspi); +/* SPI controller initializations */ cdns_spi_init_hw (xspi);
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 3/53 spi: spi-mem: Fix spi_mem_poll_status()
In reply to Sasha LevinFrom: Patrice Chotard <[email protected]>
[ Upstream commit 2283679f4c468df367830b7eb8f22d48a6940e19 ]
In spi_mem_exec_op(), in case cs_gpiod descriptor is set, exec_op() callback can't be used.
The same must be applied in spi_mem_poll_status(), poll_status() callback can't be used, we must use the legacy path using read_poll_timeout().
Tested on STM32mp257c-ev1 specific evaluation board on which a spi-nand was mounted instead of a spi-nor.
--- drivers/spi/spi-mem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/spi/spi-mem.c +1 -1
@@ -799,7 +799,7 @@ int spi_mem_poll_status(struct spi_mem *mem, op->data.dir != SPI_MEM_DATA_IN)return -EINVAL ; -if (ctlr->mem_ops && ctlr->mem_ops->poll_status) { +if (ctlr->mem_ops && ctlr->mem_ops->poll_status && !mem->spi->cs_gpiod) { ret =spi_mem_access_start (mem);if (ret)return ret;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 4/53 arm64: s32g2: Pass unit name to soc node
In reply to Sasha LevinFrom: Fabio Estevam <[email protected]>
[ Upstream commit 4266e2f70d4388b8c6a95056169954ff049ced94 ]
Pass unit name to soc node to fix the following W=1 build warning:
arch/arm64/boot/dts/freescale/s32g2.dtsi:82.6-123.4: Warning (unit_address_vs_reg): /soc: node has a reg or ranges property, but no unit name
--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/freescale/s32g2.dtsi +1 -1
@@ -79,7 +79,7 @@ psci { }; }; - soc { + soc@0 { compatible = "simple-bus"; #address-cells = <1>; #size-cells = <1>;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 5/53 regulator: qcom_smd: correct MP5496 ranges
In reply to Sasha LevinFrom: Robert Marko <[email protected]>
[ Upstream commit 122e951eb8045338089b086c8bd9b0b9afb04a92 ]
Currently set MP5496 Buck and LDO ranges dont match its datasheet[1]. According to the datasheet:
Buck range is 0.6-2.1875V with a 12.5mV step
LDO range is 0.8-3.975V with a 25mV step.
So, correct the ranges according to the datasheet[1].
--- drivers/regulator/qcom_smd-regulator.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/regulator/qcom_smd-regulator.c +4 -4
@@ -723,19 +723,19 @@ static const struct regulator_desc pms405_pldo600 = {static const struct regulator_desc mp5496_smpa2 = { .linear_ranges = (struct linear_range []) { -REGULATOR_LINEAR_RANGE (725000 ,0 ,27 ,12500 ), +REGULATOR_LINEAR_RANGE (600000 ,0 ,127 ,12500 ), }, .n_linear_ranges =1 , - .n_voltages =28 , + .n_voltages =128 , .ops = &rpm_mp5496_ops, };static const struct regulator_desc mp5496_ldoa2 = { .linear_ranges = (struct linear_range []) { -REGULATOR_LINEAR_RANGE (1800000 ,0 ,60 ,25000 ), +REGULATOR_LINEAR_RANGE (800000 ,0 ,127 ,25000 ), }, .n_linear_ranges =1 , - .n_voltages =61 , + .n_voltages =128 , .ops = &rpm_mp5496_ops, };
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 6/53 ALSA: usb-audio: US16x08: Move overflow check before array access
In reply to Sasha LevinFrom: Daniil Dementev <[email protected]>
[ Upstream commit 3ddbe35d9a2ebd4924d458e0246b4ba6c13bb456 ]
Buffer overflow could occur in the loop "while", due to accessing an array element before checking the index.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
--- sound/usb/mixer_us16x08.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
sound/usb/mixer_us16x08.c +3 -3
@@ -637,10 +637,10 @@ static int snd_get_meter_comp_index(struct snd_us16x08_meter_store *store) } }else {/* skip channels with no compressor active */ -while (!store->comp_store->val[ +while (store->comp_index <=SND_US16X08_MAX_CHANNELS + && !store->comp_store->val[COMP_STORE_IDX (SND_US16X08_ID_COMP_SWITCH )] - [store->comp_index -1 ] - && store->comp_index <=SND_US16X08_MAX_CHANNELS ) { + [store->comp_index -1 ]) { store->comp_index++; } ret = store->comp_index++;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 7/53 bus: bt1-apb: Don't print error on -EPROBE_DEFER
In reply to Sasha LevinFrom: Serge Semin <[email protected]>
[ Upstream commit be5cddef05f519a321a543906f255ac247246074 ]
The Baikal-T1 APB bus driver correctly handles the deferred probe situation, but still pollutes the system log with a misleading error message. Let's fix that by using the dev_err_probe() method to print the log message in case of the clocks/resets request errors.
--- drivers/bus/bt1-apb.c | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-)
drivers/bus/bt1-apb.c +6 -8
@@ -175,10 +175,9 @@ static int bt1_apb_request_rst(struct bt1_apb *apb)int ret; apb->prst =devm_reset_control_get_optional_exclusive (apb->dev,"prst" ); -if (IS_ERR (apb->prst)) { -dev_warn (apb->dev,"Couldn't get reset control line\n" ); -return PTR_ERR (apb->prst); - } +if (IS_ERR (apb->prst)) +return dev_err_probe (apb->dev,PTR_ERR (apb->prst), +"Couldn't get reset control line\n" ); ret =reset_control_deassert (apb->prst);if (ret)
@@ -199,10 +198,9 @@ static int bt1_apb_request_clk(struct bt1_apb *apb)int ret; apb->pclk =devm_clk_get (apb->dev,"pclk" ); -if (IS_ERR (apb->pclk)) { -dev_err (apb->dev,"Couldn't get APB clock descriptor\n" ); -return PTR_ERR (apb->pclk); - } +if (IS_ERR (apb->pclk)) +return dev_err_probe (apb->dev,PTR_ERR (apb->pclk), +"Couldn't get APB clock descriptor\n" ); ret =clk_prepare_enable (apb->pclk);if (ret) {
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 8/53 bus: bt1-axi: Don't print error on -EPROBE_DEFER
In reply to Sasha LevinFrom: Serge Semin <[email protected]>
[ Upstream commit 5e93207e962a6d23893ff4405f6c5d4396fb5934 ]
The Baikal-T1 AXI bus driver correctly handles the deferred probe situation, but still pollutes the system log with a misleading error message. Let's fix that by using the dev_err_probe() method to print the log message in case of the clocks/resets request errors.
--- drivers/bus/bt1-axi.c | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-)
drivers/bus/bt1-axi.c +6 -8
@@ -135,10 +135,9 @@ static int bt1_axi_request_rst(struct bt1_axi *axi)int ret; axi->arst =devm_reset_control_get_optional_exclusive (axi->dev,"arst" ); -if (IS_ERR (axi->arst)) { -dev_warn (axi->dev,"Couldn't get reset control line\n" ); -return PTR_ERR (axi->arst); - } +if (IS_ERR (axi->arst)) +return dev_err_probe (axi->dev,PTR_ERR (axi->arst), +"Couldn't get reset control line\n" ); ret =reset_control_deassert (axi->arst);if (ret)
@@ -159,10 +158,9 @@ static int bt1_axi_request_clk(struct bt1_axi *axi)int ret; axi->aclk =devm_clk_get (axi->dev,"aclk" ); -if (IS_ERR (axi->aclk)) { -dev_err (axi->dev,"Couldn't get AXI Interconnect clock\n" ); -return PTR_ERR (axi->aclk); - } +if (IS_ERR (axi->aclk)) +return dev_err_probe (axi->dev,PTR_ERR (axi->aclk), +"Couldn't get AXI Interconnect clock\n" ); ret =clk_prepare_enable (axi->aclk);if (ret) {
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 9/53 selftests: Fix clang cross compilation
In reply to Sasha LevinFrom: Mark Brown <[email protected]>
[ Upstream commit 795285ef242543bb636556b7225f20adb7d3795c ]
Unlike GCC clang uses a single compiler image to support multiple target architectures meaning that we can't simply rely on CROSS_COMPILE to select the output architecture. Instead we must pass --target to the compiler to tell it what to output, kselftest was not doing this so cross compilation of kselftest using clang resulted in kselftest being built for the host architecture.
More work is required to fix tests using custom rules but this gets the bulk of things building.
--- tools/testing/selftests/lib.mk | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-)
tools/testing/selftests/lib.mk +23 -2
@@ -7,10 +7,31 @@ else ifneq ($(filter -%,$(LLVM)),) LLVM_SUFFIX := $(LLVM) endif -CC := $(LLVM_PREFIX)clang$(LLVM_SUFFIX) +CLANG_TARGET_FLAGS_arm := arm-linux-gnueabi +CLANG_TARGET_FLAGS_arm64 := aarch64-linux-gnu +CLANG_TARGET_FLAGS_hexagon := hexagon-linux-musl +CLANG_TARGET_FLAGS_m68k := m68k-linux-gnu +CLANG_TARGET_FLAGS_mips := mipsel-linux-gnu +CLANG_TARGET_FLAGS_powerpc := powerpc64le-linux-gnu +CLANG_TARGET_FLAGS_riscv := riscv64-linux-gnu +CLANG_TARGET_FLAGS_s390 := s390x-linux-gnu +CLANG_TARGET_FLAGS_x86 := x86_64-linux-gnu +CLANG_TARGET_FLAGS := $(CLANG_TARGET_FLAGS_$(ARCH)) + +ifeq ($(CROSS_COMPILE),) +ifeq ($(CLANG_TARGET_FLAGS),) +$(error Specify CROSS_COMPILE or add '--target=' option to lib.mk +else +CLANG_FLAGS += --target=$(CLANG_TARGET_FLAGS) +endif # CLANG_TARGET_FLAGS +else +CLANG_FLAGS += --target=$(notdir $(CROSS_COMPILE:%-=%)) +endif # CROSS_COMPILE + +CC := $(LLVM_PREFIX)clang$(LLVM_SUFFIX) $(CLANG_FLAGS) -fintegrated-as else CC := $(CROSS_COMPILE)gcc -endif +endif # LLVM ifeq (0,$(MAKELEVEL)) ifeq ($(OUTPUT),)
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 10/53 drm/vc4: plane: Prevent async update if we don't have a dlist
In reply to Sasha LevinFrom: Maxime Ripard <[email protected]>
[ Upstream commit cb468c7d84d174ab9cd638be9f5b3f1ba2b311a0 ]
The vc4 planes are setup in hardware by creating a hardware descriptor in a dedicated RAM. As part of the process to setup a plane in KMS, we thus need to allocate some part of that dedicated RAM to store our descriptor there.
The async update path will just reuse the descriptor already allocated for that plane and will modify it directly in RAM to match whatever has been asked for.
In order to do that, it will compare the descriptor for the old plane state and the new plane state, will make sure they fit in the same size, and check that only the position or buffer address have changed.
--- drivers/gpu/drm/vc4/vc4_plane.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/gpu/drm/vc4/vc4_plane.c +4 -0
@@ -1321,6 +1321,10 @@ static int vc4_plane_atomic_async_check(struct drm_plane *plane, old_vc4_state =to_vc4_plane_state (plane->state); new_vc4_state =to_vc4_plane_state (new_plane_state); + +if (!new_vc4_state->hw_dlist) +return -EINVAL ; + if (old_vc4_state->dlist_count != new_vc4_state->dlist_count || old_vc4_state->pos0_offset != new_vc4_state->pos0_offset || old_vc4_state->pos2_offset != new_vc4_state->pos2_offset ||
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 11/53 drm/vc4: crtc: Use an union to store the page flip callback
In reply to Sasha LevinFrom: Maxime Ripard <[email protected]>
[ Upstream commit 2523e9dcc3be91bf9fdc0d1e542557ca00bbef42 ]
We'll need to extend the vc4_async_flip_state structure to rely on another callback implementation, so let's move the current one into a union.
--- drivers/gpu/drm/vc4/vc4_crtc.c | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-)
drivers/gpu/drm/vc4/vc4_crtc.c +14 -6
@@ -769,17 +769,17 @@ struct vc4_async_flip_state {struct drm_framebuffer *old_fb;struct drm_pending_vblank_event *event; -struct vc4_seqno_cb cb; +union { +struct vc4_seqno_cb seqno; + } cb; };/* Called when the V3D execution for the BO being flipped to is done, so that * we can actually update the plane's address to point to it. */ static void -vc4_async_page_flip_complete (struct vc4_seqno_cb *cb) +vc4_async_page_flip_complete (struct vc4_async_flip_state *flip_state) { -struct vc4_async_flip_state *flip_state = - container_of(cb, struct vc4_async_flip_state, cb);struct drm_crtc *crtc = flip_state->crtc;struct drm_device *dev = crtc->dev;struct drm_plane *plane = crtc->primary;
@@ -815,6 +815,14 @@ vc4_async_page_flip_complete(struct vc4_seqno_cb *cb)kfree (flip_state); } +static void vc4_async_page_flip_seqno_complete (struct vc4_seqno_cb *cb) +{ +struct vc4_async_flip_state *flip_state = + container_of(cb, struct vc4_async_flip_state, cb.seqno); + +vc4_async_page_flip_complete (flip_state); +} +/* Implements async (non-vblank-synced) page flips. * * The page flip ioctl needs to return immediately, so we grab the
@@ -875,8 +883,8 @@ static int vc4_async_page_flip(struct drm_crtc *crtc,*/ drm_atomic_set_fb_for_plane (plane->state, fb); -vc4_queue_seqno_cb (dev, &flip_state->cb, bo->seqno, - vc4_async_page_flip_complete); +vc4_queue_seqno_cb (dev, &flip_state->cb.seqno, bo->seqno, + vc4_async_page_flip_seqno_complete);/* Driver takes ownership of state on successful async commit. */ return 0 ;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 12/53 drm/vc4: crtc: Move the BO handling out of common page-flip callback
In reply to Sasha LevinFrom: Maxime Ripard <[email protected]>
[ Upstream commit 4d12c36fb73b5c49fe2f95d06515fd9846010fd2 ]
We'll soon introduce another completion callback source that won't need to use the BO reference counting, so let's move it around to create a function we will be able to share between both callbacks.
--- drivers/gpu/drm/vc4/vc4_crtc.c | 34 ++++++++++++++++++++-------------- 1 file changed, 20 insertions(+), 14 deletions(-)
drivers/gpu/drm/vc4/vc4_crtc.c +20 -14
@@ -796,21 +796,8 @@ vc4_async_page_flip_complete(struct vc4_async_flip_state *flip_state)drm_crtc_vblank_put (crtc);drm_framebuffer_put (flip_state->fb); -/* Decrement the BO usecnt in order to keep the inc/dec calls balanced -* when the planes are updated through the async update path. -* FIXME: we should move to generic async-page-flip when it's -* available, so that we can get rid of this hand-made cleanup_fb() -* logic. -*/ -if (flip_state->old_fb) { -struct drm_gem_cma_object *cma_bo; -struct vc4_bo *bo; - - cma_bo =drm_fb_cma_get_gem_obj (flip_state->old_fb,0 ); - bo =to_vc4_bo (&cma_bo->base); -vc4_bo_dec_usecnt (bo); +if (flip_state->old_fb)drm_framebuffer_put (flip_state->old_fb); - }kfree (flip_state); }
@@ -819,8 +806,27 @@ static void vc4_async_page_flip_seqno_complete(struct vc4_seqno_cb *cb) {struct vc4_async_flip_state *flip_state = container_of(cb, struct vc4_async_flip_state, cb.seqno); +struct vc4_bo *bo =NULL ; + +if (flip_state->old_fb) { +struct drm_gem_cma_object *cma_bo = +drm_fb_cma_get_gem_obj (flip_state->old_fb,0 ); + bo =to_vc4_bo (&cma_bo->base); + }vc4_async_page_flip_complete (flip_state); + +/* +* Decrement the BO usecnt in order to keep the inc/dec +* calls balanced when the planes are updated through +* the async update path. +* +* FIXME: we should move to generic async-page-flip when +* it's available, so that we can get rid of this +* hand-made cleanup_fb() logic. +*/ +if (bo) +vc4_bo_dec_usecnt (bo); }/* Implements async (non-vblank-synced) page flips.
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 13/53 selftests: vm: Fix resource leak when return error
In reply to Sasha LevinFrom: Ding Xiang <[email protected]>
[ Upstream commit 3084a4ec7f9bb1ec90036cfd01b1abadc5dd4fb2 ]
When return on an error path, file handle need to be closed to prevent resource leak
--- tools/testing/selftests/vm/ksm_tests.c | 2 ++ 1 file changed, 2 insertions(+)
tools/testing/selftests/vm/ksm_tests.c +2 -0
@@ -54,6 +54,7 @@ static int ksm_write_sysfs(const char *file_path, unsigned long val) }if (fprintf (f,"%lu" , val) <0 ) {perror ("fprintf" ); +fclose (f);return 1 ; }fclose (f);
@@ -72,6 +73,7 @@ static int ksm_read_sysfs(const char *file_path, unsigned long *val) }if (fscanf (f,"%lu" , val) !=1 ) {perror ("fscanf" ); +fclose (f);return 1 ; }fclose (f);
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 14/53 scsi: ufs: Simplify ufshcd_clear_cmd()
In reply to Sasha LevinFrom: Bart Van Assche <[email protected]>
[ Upstream commit da8badd7d3583f447eac2ab65a332f2d773deca1 ]
Remove the local variable 'err'. This patch does not change any functionality.
--- drivers/scsi/ufs/ufshcd.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)
drivers/scsi/ufs/ufshcd.c +2 -6
@@ -2856,7 +2856,6 @@ static int ufshcd_compose_dev_cmd(struct ufs_hba *hba,static int ufshcd_clear_cmd (struct ufs_hba *hba,int tag) { -int err =0 ;unsigned long flags;u32 mask =1 << tag;
@@ -2869,11 +2868,8 @@ ufshcd_clear_cmd(struct ufs_hba *hba, int tag)* wait for h/w to clear corresponding bit in door-bell. * max. wait is 1 sec. */ - err =ufshcd_wait_for_register (hba, -REG_UTP_TRANSFER_REQ_DOOR_BELL , - mask, ~mask,1000 ,1000 ); - -return err; +return ufshcd_wait_for_register (hba,REG_UTP_TRANSFER_REQ_DOOR_BELL , + mask, ~mask,1000 ,1000 ); } static int
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 15/53 scsi: ufs: Support clearing multiple commands at once
In reply to Sasha LevinFrom: Bart Van Assche <[email protected]>
[ Upstream commit d1a7644648b7cdacaf8d1013a4285001911e9bc8 ]
Modify ufshcd_clear_cmd() such that it supports clearing multiple commands at once instead of one command at a time. This change will be used in a later patch to reduce the time spent in the reset handler.
--- drivers/scsi/ufs/ufshcd.c | 42 ++++++++++++++++++++++++++------------- 1 file changed, 28 insertions(+), 14 deletions(-)
drivers/scsi/ufs/ufshcd.c +28 -14
@@ -734,17 +734,28 @@ static enum utp_ocs ufshcd_get_tr_ocs(struct ufshcd_lrb *lrbp) }/** -* ufshcd_utrl_clear - Clear a bit in UTRLCLR register +* ufshcd_utrl_clear() - Clear requests from the controller request list. * @hba: per adapter instance -* @pos: position of the bit to be cleared +* @mask: mask with one bit set for each request to be cleared */ -static inline void ufshcd_utrl_clear (struct ufs_hba *hba,u32 pos) +static inline void ufshcd_utrl_clear (struct ufs_hba *hba,u32 mask) {if (hba->quirks &UFSHCI_QUIRK_BROKEN_REQ_LIST_CLR ) -ufshcd_writel (hba, (1 << pos),REG_UTP_TRANSFER_REQ_LIST_CLEAR ); -else -ufshcd_writel (hba, ~(1 << pos), -REG_UTP_TRANSFER_REQ_LIST_CLEAR ); + mask = ~mask; +/* +* From the UFSHCI specification: "UTP Transfer Request List CLear +* Register (UTRLCLR): This field is bit significant. Each bit +* corresponds to a slot in the UTP Transfer Request List, where bit 0 +* corresponds to request slot 0. A bit in this field is set to ‘0’ +* by host software to indicate to the host controller that a transfer +* request slot is cleared. The host controller +* shall free up any resources associated to the request slot +* immediately, and shall set the associated bit in UTRLDBR to ‘0’. The +* host software indicates no change to request slots by setting the +* associated bits in this field to ‘1’. Bits in this field shall only +* be set ‘1’ or ‘0’ by host software when UTRLRSR is set to ‘1’." +*/ +ufshcd_writel (hba, ~mask,REG_UTP_TRANSFER_REQ_LIST_CLEAR ); }/**
@@ -2853,15 +2864,18 @@ static int ufshcd_compose_dev_cmd(struct ufs_hba *hba,return ufshcd_compose_devman_upiu (hba, lrbp); } -static int -ufshcd_clear_cmd (struct ufs_hba *hba,int tag) +/* +* Clear all the requests from the controller for which a bit has been set in +* @mask and wait until the controller confirms that these requests have been +* cleared. +*/ +static int ufshcd_clear_cmds (struct ufs_hba *hba,u32 mask) {unsigned long flags; -u32 mask =1 << tag;/* clear outstanding transaction before retry */ spin_lock_irqsave (hba->host->host_lock, flags); -ufshcd_utrl_clear (hba, tag); +ufshcd_utrl_clear (hba, mask);spin_unlock_irqrestore (hba->host->host_lock, flags);/*
@@ -2949,7 +2963,7 @@ static int ufshcd_wait_for_dev_cmd(struct ufs_hba *hba, err = -ETIMEDOUT ;dev_dbg (hba->dev,"%s: dev_cmd request timedout, tag %d\n" , __func__, lrbp->task_tag); -if (!ufshcd_clear_cmd (hba, lrbp->task_tag)) +if (!ufshcd_clear_cmds (hba,1U << lrbp->task_tag))/* successfully cleared the command, retry if needed */ err = -EAGAIN ;/*
@@ -6984,7 +6998,7 @@ static int ufshcd_eh_device_reset_handler(struct scsi_cmnd *cmd)/* clear the commands that were pending for corresponding LUN */ for_each_set_bit (pos, &hba->outstanding_reqs, hba->nutrs) {if (hba->lrb[pos].lun == lun) { - err =ufshcd_clear_cmd (hba, pos); + err =ufshcd_clear_cmds (hba,1U << pos);if (err)break ;__ufshcd_transfer_req_compl (hba,1U << pos);
@@ -7086,7 +7100,7 @@ static int ufshcd_try_to_abort_task(struct ufs_hba *hba, int tag) goto out; } - err =ufshcd_clear_cmd (hba, tag); + err =ufshcd_clear_cmds (hba,1U << tag);if (err)dev_err (hba->dev,"%s: Failed clearing cmd at tag %d, err %d\n" , __func__, tag, err);
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 16/53 scsi: ufs: Fix a race between the interrupt handler and the reset handler
In reply to Sasha LevinFrom: Bart Van Assche <[email protected]>
[ Upstream commit 2acd76e7b8596e307fcec8fc6bc5fe5ab174749a ]
Prevent that both the interrupt handler and the reset handler try to complete a request at the same time. This patch is the result of an analysis of the following crash:
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000120 CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 5.10.107-android13-4-00051-g1e48e8970cca-ab8664745 #1 pc : ufshcd_release_scsi_cmd+0x30/0x46c lr : __ufshcd_transfer_req_compl+0x4fc/0x9c0 Call trace: ufshcd_release_scsi_cmd+0x30/0x46c __ufshcd_transfer_req_compl+0x4fc/0x9c0 ufshcd_poll+0xf0/0x208 ufshcd_sl_intr+0xb8/0xf0 ufshcd_intr+0x168/0x2f4 __handle_irq_event_percpu+0xa0/0x30c handle_irq_event+0x84/0x178 handle_fasteoi_irq+0x150/0x2e8 __handle_domain_irq+0x114/0x1e4 gic_handle_irq.31846+0x58/0x300 el1_irq+0xe4/0x1c0 cpuidle_enter_state+0x3ac/0x8c4 do_idle+0x2fc/0x55c cpu_startup_entry+0x84/0x90 kernel_init+0x0/0x310 start_kernel+0x0/0x608 start_kernel+0x4ec/0x608
--- drivers/scsi/ufs/ufshcd.c | 28 +++++++++++++++++++--------- 1 file changed, 19 insertions(+), 9 deletions(-)
drivers/scsi/ufs/ufshcd.c +19 -9
@@ -6970,14 +6970,14 @@ int ufshcd_exec_raw_upiu_cmd(struct ufs_hba *hba, }/** -* ufshcd_eh_device_reset_handler - device reset handler registered to -* scsi layer. +* ufshcd_eh_device_reset_handler() - Reset a single logical unit. * @cmd: SCSI command pointer * * Returns SUCCESS/FAILED */ static int ufshcd_eh_device_reset_handler (struct scsi_cmnd *cmd) { +unsigned long flags, pending_reqs =0 , not_cleared =0 ;struct Scsi_Host *host;struct ufs_hba *hba;u32 pos;
@@ -6996,14 +6996,24 @@ static int ufshcd_eh_device_reset_handler(struct scsi_cmnd *cmd) }/* clear the commands that were pending for corresponding LUN */ -for_each_set_bit (pos, &hba->outstanding_reqs, hba->nutrs) { -if (hba->lrb[pos].lun == lun) { - err =ufshcd_clear_cmds (hba,1U << pos); -if (err) -break ; -__ufshcd_transfer_req_compl (hba,1U << pos); - } +spin_lock_irqsave (&hba->outstanding_lock, flags); +for_each_set_bit (pos, &hba->outstanding_reqs, hba->nutrs) +if (hba->lrb[pos].lun == lun) +__set_bit (pos, &pending_reqs); + hba->outstanding_reqs &= ~pending_reqs; +spin_unlock_irqrestore (&hba->outstanding_lock, flags); + +if (ufshcd_clear_cmds (hba, pending_reqs) <0 ) { +spin_lock_irqsave (&hba->outstanding_lock, flags); + not_cleared = pending_reqs & +ufshcd_readl (hba,REG_UTP_TRANSFER_REQ_DOOR_BELL ); + hba->outstanding_reqs |= not_cleared; +spin_unlock_irqrestore (&hba->outstanding_lock, flags); + +dev_err (hba->dev,"%s: failed to clear requests %#lx\n" , + __func__, not_cleared); } +__ufshcd_transfer_req_compl (hba, pending_reqs & ~not_cleared); out: hba->req_abort_count =0 ;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 17/53 selftests/bpf: Shuffle cookies symbols in kprobe multi test
In reply to Sasha LevinFrom: Jiri Olsa <[email protected]>
[ Upstream commit ad8848535e97f4a5374fc68f7a5d16e2565940cc ]
There's a kernel bug that causes cookies to be misplaced and the reason we did not catch this with this test is that we provide bpf_fentry_test* functions already sorted by name.
Shuffling function bpf_fentry_test2 deeper in the list and keeping the current cookie values as before will trigger the bug.
The kernel fix is coming in following changes.
--- .../selftests/bpf/prog_tests/bpf_cookie.c | 78 +++++++++---------- .../selftests/bpf/progs/kprobe_multi.c | 24 +++--- 2 files changed, 51 insertions(+), 51 deletions(-)
tools/testing/selftests/bpf/prog_tests/bpf_cookie.c +39 -39
@@ -118,24 +118,24 @@ static void kprobe_multi_link_api_subtest(void) })GET_ADDR ("bpf_fentry_test1" , addrs[0 ]); -GET_ADDR ("bpf_fentry_test2" , addrs[1 ]); -GET_ADDR ("bpf_fentry_test3" , addrs[2 ]); -GET_ADDR ("bpf_fentry_test4" , addrs[3 ]); -GET_ADDR ("bpf_fentry_test5" , addrs[4 ]); -GET_ADDR ("bpf_fentry_test6" , addrs[5 ]); -GET_ADDR ("bpf_fentry_test7" , addrs[6 ]); +GET_ADDR ("bpf_fentry_test3" , addrs[1 ]); +GET_ADDR ("bpf_fentry_test4" , addrs[2 ]); +GET_ADDR ("bpf_fentry_test5" , addrs[3 ]); +GET_ADDR ("bpf_fentry_test6" , addrs[4 ]); +GET_ADDR ("bpf_fentry_test7" , addrs[5 ]); +GET_ADDR ("bpf_fentry_test2" , addrs[6 ]);GET_ADDR ("bpf_fentry_test8" , addrs[7 ]);#undef GET_ADDR - cookies[0 ] =1 ; - cookies[1 ] =2 ; - cookies[2 ] =3 ; - cookies[3 ] =4 ; - cookies[4 ] =5 ; - cookies[5 ] =6 ; - cookies[6 ] =7 ; - cookies[7 ] =8 ; + cookies[0 ] =1 ;/* bpf_fentry_test1 */ + cookies[1 ] =2 ;/* bpf_fentry_test3 */ + cookies[2 ] =3 ;/* bpf_fentry_test4 */ + cookies[3 ] =4 ;/* bpf_fentry_test5 */ + cookies[4 ] =5 ;/* bpf_fentry_test6 */ + cookies[5 ] =6 ;/* bpf_fentry_test7 */ + cookies[6 ] =7 ;/* bpf_fentry_test2 */ + cookies[7 ] =8 ;/* bpf_fentry_test8 */ opts.kprobe_multi.addrs = (const unsigned long *) &addrs; opts.kprobe_multi.cnt =ARRAY_SIZE (addrs);
@@ -146,14 +146,14 @@ static void kprobe_multi_link_api_subtest(void)if (!ASSERT_GE (link1_fd,0 ,"link1_fd" )) goto cleanup; - cookies[0 ] =8 ; - cookies[1 ] =7 ; - cookies[2 ] =6 ; - cookies[3 ] =5 ; - cookies[4 ] =4 ; - cookies[5 ] =3 ; - cookies[6 ] =2 ; - cookies[7 ] =1 ; + cookies[0 ] =8 ;/* bpf_fentry_test1 */ + cookies[1 ] =7 ;/* bpf_fentry_test3 */ + cookies[2 ] =6 ;/* bpf_fentry_test4 */ + cookies[3 ] =5 ;/* bpf_fentry_test5 */ + cookies[4 ] =4 ;/* bpf_fentry_test6 */ + cookies[5 ] =3 ;/* bpf_fentry_test7 */ + cookies[6 ] =2 ;/* bpf_fentry_test2 */ + cookies[7 ] =1 ;/* bpf_fentry_test8 */ opts.kprobe_multi.flags =BPF_F_KPROBE_MULTI_RETURN ; prog_fd =bpf_program__fd (skel->progs.test_kretprobe);
@@ -178,12 +178,12 @@ static void kprobe_multi_attach_api_subtest(void)struct kprobe_multi *skel =NULL ;const char *syms[8 ] = {"bpf_fentry_test1" , -"bpf_fentry_test2" ,"bpf_fentry_test3" ,"bpf_fentry_test4" ,"bpf_fentry_test5" ,"bpf_fentry_test6" ,"bpf_fentry_test7" , +"bpf_fentry_test2" ,"bpf_fentry_test8" , };__u64 cookies[8 ];
@@ -195,14 +195,14 @@ static void kprobe_multi_attach_api_subtest(void) skel->bss->pid =getpid (); skel->bss->test_cookie = true; - cookies[0 ] =1 ; - cookies[1 ] =2 ; - cookies[2 ] =3 ; - cookies[3 ] =4 ; - cookies[4 ] =5 ; - cookies[5 ] =6 ; - cookies[6 ] =7 ; - cookies[7 ] =8 ; + cookies[0 ] =1 ;/* bpf_fentry_test1 */ + cookies[1 ] =2 ;/* bpf_fentry_test3 */ + cookies[2 ] =3 ;/* bpf_fentry_test4 */ + cookies[3 ] =4 ;/* bpf_fentry_test5 */ + cookies[4 ] =5 ;/* bpf_fentry_test6 */ + cookies[5 ] =6 ;/* bpf_fentry_test7 */ + cookies[6 ] =7 ;/* bpf_fentry_test2 */ + cookies[7 ] =8 ;/* bpf_fentry_test8 */ opts.syms = syms; opts.cnt =ARRAY_SIZE (syms);
@@ -213,14 +213,14 @@ static void kprobe_multi_attach_api_subtest(void)if (!ASSERT_OK_PTR (link1,"bpf_program__attach_kprobe_multi_opts" )) goto cleanup; - cookies[0 ] =8 ; - cookies[1 ] =7 ; - cookies[2 ] =6 ; - cookies[3 ] =5 ; - cookies[4 ] =4 ; - cookies[5 ] =3 ; - cookies[6 ] =2 ; - cookies[7 ] =1 ; + cookies[0 ] =8 ;/* bpf_fentry_test1 */ + cookies[1 ] =7 ;/* bpf_fentry_test3 */ + cookies[2 ] =6 ;/* bpf_fentry_test4 */ + cookies[3 ] =5 ;/* bpf_fentry_test5 */ + cookies[4 ] =4 ;/* bpf_fentry_test6 */ + cookies[5 ] =3 ;/* bpf_fentry_test7 */ + cookies[6 ] =2 ;/* bpf_fentry_test2 */ + cookies[7 ] =1 ;/* bpf_fentry_test8 */ opts.retprobe = true;
tools/testing/selftests/bpf/progs/kprobe_multi.c +12 -12
@@ -54,21 +54,21 @@ static void kprobe_multi_check(void *ctx, bool is_return)if (is_return) {SET (kretprobe_test1_result, &bpf_fentry_test1,8 ); -SET (kretprobe_test2_result, &bpf_fentry_test2,7 ); -SET (kretprobe_test3_result, &bpf_fentry_test3,6 ); -SET (kretprobe_test4_result, &bpf_fentry_test4,5 ); -SET (kretprobe_test5_result, &bpf_fentry_test5,4 ); -SET (kretprobe_test6_result, &bpf_fentry_test6,3 ); -SET (kretprobe_test7_result, &bpf_fentry_test7,2 ); +SET (kretprobe_test2_result, &bpf_fentry_test2,2 ); +SET (kretprobe_test3_result, &bpf_fentry_test3,7 ); +SET (kretprobe_test4_result, &bpf_fentry_test4,6 ); +SET (kretprobe_test5_result, &bpf_fentry_test5,5 ); +SET (kretprobe_test6_result, &bpf_fentry_test6,4 ); +SET (kretprobe_test7_result, &bpf_fentry_test7,3 );SET (kretprobe_test8_result, &bpf_fentry_test8,1 ); }else {SET (kprobe_test1_result, &bpf_fentry_test1,1 ); -SET (kprobe_test2_result, &bpf_fentry_test2,2 ); -SET (kprobe_test3_result, &bpf_fentry_test3,3 ); -SET (kprobe_test4_result, &bpf_fentry_test4,4 ); -SET (kprobe_test5_result, &bpf_fentry_test5,5 ); -SET (kprobe_test6_result, &bpf_fentry_test6,6 ); -SET (kprobe_test7_result, &bpf_fentry_test7,7 ); +SET (kprobe_test2_result, &bpf_fentry_test2,7 ); +SET (kprobe_test3_result, &bpf_fentry_test3,2 ); +SET (kprobe_test4_result, &bpf_fentry_test4,3 ); +SET (kprobe_test5_result, &bpf_fentry_test5,4 ); +SET (kprobe_test6_result, &bpf_fentry_test6,5 ); +SET (kprobe_test7_result, &bpf_fentry_test7,6 );SET (kprobe_test8_result, &bpf_fentry_test8,8 ); }
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 18/53 ALSA: x86: intel_hdmi_audio: enable pm_runtime and set autosuspend delay
In reply to Sasha LevinFrom: Pierre-Louis Bossart <[email protected]>
[ Upstream commit e87c65aeb46ca4f5b7dc08531200bcb8a426c62e ]
The existing code uses pm_runtime_get_sync/put_autosuspend, but pm_runtime was not explicitly enabled. The autosuspend delay was not set either, the value is set to 5s since HDMI is rather painful to resume.
--- sound/x86/intel_hdmi_audio.c | 5 +++++ 1 file changed, 5 insertions(+)
sound/x86/intel_hdmi_audio.c +5 -0
@@ -33,6 +33,8 @@#include <drm/intel_lpe_audio.h> #include "intel_hdmi_audio.h" +#define INTEL_HDMI_AUDIO_SUSPEND_DELAY_MS 5000 +#define for_each_pipe (card_ctx, pipe) \ for ((pipe) = 0; (pipe) < (card_ctx)->num_pipes; (pipe)++)#define for_each_port (card_ctx, port) \
@@ -1802,8 +1804,11 @@ static int __hdmi_lpe_audio_probe(struct platform_device *pdev) pdata->notify_audio_lpe = notify_audio_lpe;spin_unlock_irq (&pdata->lpe_audio_slock); +pm_runtime_set_autosuspend_delay (&pdev->dev,INTEL_HDMI_AUDIO_SUSPEND_DELAY_MS );pm_runtime_use_autosuspend (&pdev->dev); +pm_runtime_enable (&pdev->dev);pm_runtime_mark_last_busy (&pdev->dev); +pm_runtime_idle (&pdev->dev);dev_dbg (&pdev->dev,"%s: handle pending notification\n" , __func__);for_each_port (card_ctx, port) {
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 19/53 ALSA: x86: intel_hdmi_audio: use pm_runtime_resume_and_get()
In reply to Sasha LevinFrom: Pierre-Louis Bossart <[email protected]>
[ Upstream commit bb30b453fedac277d66220431fd7063d9ddc10d8 ]
The current code does not check for errors and does not release the reference on errors.
--- sound/x86/intel_hdmi_audio.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
sound/x86/intel_hdmi_audio.c +8 -2
@@ -1068,7 +1068,9 @@ static int had_pcm_open(struct snd_pcm_substream *substream) intelhaddata =snd_pcm_substream_chip (substream); runtime = substream->runtime; -pm_runtime_get_sync (intelhaddata->dev); + retval =pm_runtime_resume_and_get (intelhaddata->dev); +if (retval <0 ) +return retval;/* set the runtime hw parameter with local snd_pcm_hardware struct */ runtime->hw = had_pcm_hardware;
@@ -1536,8 +1538,12 @@ static void had_audio_wq(struct work_struct *work) container_of(work, struct snd_intelhad, hdmi_audio_wq);struct intel_hdmi_lpe_audio_pdata *pdata = ctx->dev->platform_data;struct intel_hdmi_lpe_audio_port_pdata *ppdata = &pdata->port[ctx->port]; +int ret; + + ret =pm_runtime_resume_and_get (ctx->dev); +if (ret <0 ) +return ; -pm_runtime_get_sync (ctx->dev);mutex_lock (&ctx->mutex);if (ppdata->pipe <0 ) { dev_dbg(ctx->dev, "%s: Event: HAD_NOTIFY_HOT_UNPLUG : port = %d\n",
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 20/53 hamradio: 6pack: fix array-index-out-of-bounds in decode_std_command()
In reply to Sasha LevinFrom: Xu Jia <[email protected]>
[ Upstream commit 2b04495e21cdb9b45c28c6aeb2da560184de20a3 ]
Hulk Robot reports incorrect sp->rx_count_cooked value in decode_std_command(). This should be caused by the subtracting from sp->rx_count_cooked before. It seems that sp->rx_count_cooked value is changed to 0, which bypassed the previous judgment.
The situation is shown below:
(Thread 1) | (Thread 2) decode_std_command() | resync_tnc() ... | if (rest == 2) | sp->rx_count_cooked -= 2; | else if (rest == 3) | ... | sp->rx_count_cooked = 0; sp->rx_count_cooked -= 1; | for (i = 0; i < sp->rx_count_cooked; i++) // report error checksum += sp->cooked_buf[i];
sp->rx_count_cooked is a shared variable but is not protected by a lock. The same applies to sp->rx_count. This patch adds a lock to fix the bug.
The fail log is shown below:
=======================================================================
UBSAN: array-index-out-of-bounds in drivers/net/hamradio/6pack.c:925:31 index 400 is out of range for type 'unsigned char [400]' CPU: 3 PID: 7433 Comm: kworker/u10:1 Not tainted 5.18.0-rc5-00163-g4b97bac0756a #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Workqueue: events_unbound flush_to_ldisc Call Trace: <TASK> dump_stack_lvl+0xcd/0x134 ubsan_epilogue+0xb/0x50 __ubsan_handle_out_of_bounds.cold+0x62/0x6c sixpack_receive_buf+0xfda/0x1330 tty_ldisc_receive_buf+0x13e/0x180 tty_port_default_receive_buf+0x6d/0xa0 flush_to_ldisc+0x213/0x3f0 process_one_work+0x98f/0x1620 worker_thread+0x665/0x1080 kthread+0x2e9/0x3a0 ret_from_fork+0x1f/0x30 ...
--- drivers/net/hamradio/6pack.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
drivers/net/hamradio/6pack.c +8 -1
@@ -99,6 +99,7 @@ struct sixpack {unsigned int rx_count;unsigned int rx_count_cooked; +spinlock_t rxlock;int mtu;/* Our mtu (to spot changes!) */ int buffsize;/* Max buffers sizes */
@@ -565,6 +566,7 @@ static int sixpack_open(struct tty_struct *tty) sp->dev = dev;spin_lock_init (&sp->lock); +spin_lock_init (&sp->rxlock);refcount_set (&sp->refcnt,1 );init_completion (&sp->dead);
@@ -913,6 +915,7 @@ static void decode_std_command(struct sixpack *sp, unsigned char cmd) sp->led_state =0x60 ;/* fill trailing bytes with zeroes */ sp->tty->ops->write (sp->tty, &sp->led_state,1 ); +spin_lock_bh (&sp->rxlock); rest = sp->rx_count;if (rest !=0 )for (i = rest; i <=3 ; i++)
@@ -930,6 +933,7 @@ static void decode_std_command(struct sixpack *sp, unsigned char cmd)sp_bump (sp,0 ); } sp->rx_count_cooked =0 ; +spin_unlock_bh (&sp->rxlock); }break ;case SIXP_TX_URUN :printk (KERN_DEBUG "6pack: TX underrun\n" );
@@ -959,8 +963,11 @@ sixpack_decode(struct sixpack *sp, const unsigned char *pre_rbuff, int count)decode_prio_command (sp, inbyte); else if ((inbyte & SIXP_STD_CMD_MASK) != 0) decode_std_command(sp, inbyte); - else if ((sp->status & SIXP_RX_DCD_MASK) == SIXP_RX_DCD_MASK) + else if ((sp->status & SIXP_RX_DCD_MASK) == SIXP_RX_DCD_MASK) { +spin_lock_bh (&sp->rxlock);decode_data (sp, inbyte); +spin_unlock_bh (&sp->rxlock); + } } }
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 21/53 block: serialize all debugfs operations using q->debugfs_mutex
In reply to Sasha LevinFrom: Christoph Hellwig <[email protected]>
[ Upstream commit 5cf9c91ba927119fc6606b938b1895bb2459d3bc ]
Various places like I/O schedulers or the QOS infrastructure try to register debugfs files on demans, which can race with creating and removing the main queue debugfs directory. Use the existing debugfs_mutex to serialize all debugfs operations that rely on q->debugfs_dir or the directories hanging off it.
To make the teardown code a little simpler declare all debugfs dentry pointers and not just the main one uncoditionally in blkdev.h.
Move debugfs_mutex next to the dentries that it protects and document what it is used for.
--- block/blk-mq-debugfs.c | 25 ++++++++++++++++++++----- block/blk-mq-debugfs.h | 5 ----- block/blk-mq-sched.c | 11 +++++++++++ block/blk-rq-qos.c | 2 ++ block/blk-rq-qos.h | 7 ++++++- block/blk-sysfs.c | 20 +++++++++----------- include/linux/blkdev.h | 8 ++++---- kernel/trace/blktrace.c | 3 --- 8 files changed, 52 insertions(+), 29 deletions(-)
block/blk-mq-debugfs.c +20 -5
@@ -713,11 +713,6 @@ void blk_mq_debugfs_register(struct request_queue *q) } } -void blk_mq_debugfs_unregister (struct request_queue *q) -{ - q->sched_debugfs_dir =NULL ; -} -static void blk_mq_debugfs_register_ctx (struct blk_mq_hw_ctx *hctx,struct blk_mq_ctx *ctx) {
@@ -748,6 +743,8 @@ void blk_mq_debugfs_register_hctx(struct request_queue *q,void blk_mq_debugfs_unregister_hctx (struct blk_mq_hw_ctx *hctx) { +if (!hctx->queue->debugfs_dir) +return ;debugfs_remove_recursive (hctx->debugfs_dir); hctx->sched_debugfs_dir =NULL ; hctx->debugfs_dir =NULL ;
@@ -775,6 +772,8 @@ void blk_mq_debugfs_register_sched(struct request_queue *q) {struct elevator_type *e = q->elevator->type; +lockdep_assert_held (&q->debugfs_mutex); +/* * If the parent directory has not been created yet, return, we will be * called again later on and the directory/files will be created then.
@@ -792,6 +791,8 @@ void blk_mq_debugfs_register_sched(struct request_queue *q)void blk_mq_debugfs_unregister_sched (struct request_queue *q) { +lockdep_assert_held (&q->debugfs_mutex); +debugfs_remove_recursive (q->sched_debugfs_dir); q->sched_debugfs_dir =NULL ; }
@@ -813,6 +814,10 @@ static const char *rq_qos_id_to_name(enum rq_qos_id id)void blk_mq_debugfs_unregister_rqos (struct rq_qos *rqos) { +lockdep_assert_held (&rqos->q->debugfs_mutex); + +if (!rqos->q->debugfs_dir) +return ;debugfs_remove_recursive (rqos->debugfs_dir); rqos->debugfs_dir =NULL ; }
@@ -822,6 +827,8 @@ void blk_mq_debugfs_register_rqos(struct rq_qos *rqos)struct request_queue *q = rqos->q;const char *dir_name =rq_qos_id_to_name (rqos->id); +lockdep_assert_held (&q->debugfs_mutex); +if (rqos->debugfs_dir || !rqos->ops->debugfs_attrs)return ;
@@ -837,6 +844,8 @@ void blk_mq_debugfs_register_rqos(struct rq_qos *rqos)void blk_mq_debugfs_unregister_queue_rqos (struct request_queue *q) { +lockdep_assert_held (&q->debugfs_mutex); +debugfs_remove_recursive (q->rqos_debugfs_dir); q->rqos_debugfs_dir =NULL ; }
@@ -846,6 +855,8 @@ void blk_mq_debugfs_register_sched_hctx(struct request_queue *q, {struct elevator_type *e = q->elevator->type; +lockdep_assert_held (&q->debugfs_mutex); +/* * If the parent debugfs directory has not been created yet, return; * We will be called again later on with appropriate parent debugfs
@@ -865,6 +876,10 @@ void blk_mq_debugfs_register_sched_hctx(struct request_queue *q,void blk_mq_debugfs_unregister_sched_hctx (struct blk_mq_hw_ctx *hctx) { +lockdep_assert_held (&hctx->queue->debugfs_mutex); + +if (!hctx->queue->debugfs_dir) +return ;debugfs_remove_recursive (hctx->sched_debugfs_dir); hctx->sched_debugfs_dir =NULL ; }
block/blk-mq-debugfs.h +0 -5
@@ -21,7 +21,6 @@ int __blk_mq_debugfs_rq_show(struct seq_file *m, struct request *rq);int blk_mq_debugfs_rq_show (struct seq_file *m,void *v);void blk_mq_debugfs_register (struct request_queue *q); -void blk_mq_debugfs_unregister (struct request_queue *q);void blk_mq_debugfs_register_hctx (struct request_queue *q,struct blk_mq_hw_ctx *hctx);void blk_mq_debugfs_unregister_hctx (struct blk_mq_hw_ctx *hctx);
@@ -42,10 +41,6 @@ static inline void blk_mq_debugfs_register(struct request_queue *q) { } -static inline void blk_mq_debugfs_unregister (struct request_queue *q) -{ -} -static inline void blk_mq_debugfs_register_hctx (struct request_queue *q,struct blk_mq_hw_ctx *hctx) {
block/blk-mq-sched.c +11 -0
@@ -593,7 +593,9 @@ int blk_mq_init_sched(struct request_queue *q, struct elevator_type *e)if (ret) goto err_free_map_and_rqs; +mutex_lock (&q->debugfs_mutex);blk_mq_debugfs_register_sched (q); +mutex_unlock (&q->debugfs_mutex);queue_for_each_hw_ctx (q, hctx, i) {if (e->ops.init_hctx) {
@@ -606,7 +608,9 @@ int blk_mq_init_sched(struct request_queue *q, struct elevator_type *e)return ret; } } +mutex_lock (&q->debugfs_mutex);blk_mq_debugfs_register_sched_hctx (q, hctx); +mutex_unlock (&q->debugfs_mutex); }return 0 ;
@@ -647,14 +651,21 @@ void blk_mq_exit_sched(struct request_queue *q, struct elevator_queue *e)unsigned int flags =0 ;queue_for_each_hw_ctx (q, hctx, i) { +mutex_lock (&q->debugfs_mutex);blk_mq_debugfs_unregister_sched_hctx (hctx); +mutex_unlock (&q->debugfs_mutex); +if (e->type->ops.exit_hctx && hctx->sched_data) { e->type->ops.exit_hctx (hctx, i); hctx->sched_data =NULL ; } flags = hctx->flags; } + +mutex_lock (&q->debugfs_mutex);blk_mq_debugfs_unregister_sched (q); +mutex_unlock (&q->debugfs_mutex); +if (e->type->ops.exit_sched) e->type->ops.exit_sched (e);blk_mq_sched_tags_teardown (q, flags);
block/blk-rq-qos.c +2 -0
@@ -294,7 +294,9 @@ void rq_qos_wait(struct rq_wait *rqw, void *private_data,void rq_qos_exit (struct request_queue *q) { +mutex_lock (&q->debugfs_mutex);blk_mq_debugfs_unregister_queue_rqos (q); +mutex_unlock (&q->debugfs_mutex);while (q->rq_qos) {struct rq_qos *rqos = q->rq_qos;
block/blk-rq-qos.h +6 -1
@@ -104,8 +104,11 @@ static inline void rq_qos_add(struct request_queue *q, struct rq_qos *rqos)blk_mq_unfreeze_queue (q); -if (rqos->ops->debugfs_attrs) +if (rqos->ops->debugfs_attrs) { +mutex_lock (&q->debugfs_mutex);blk_mq_debugfs_register_rqos (rqos); +mutex_unlock (&q->debugfs_mutex); + } }static inline void rq_qos_del (struct request_queue *q,struct rq_qos *rqos)
@@ -129,7 +132,9 @@ static inline void rq_qos_del(struct request_queue *q, struct rq_qos *rqos)blk_mq_unfreeze_queue (q); +mutex_lock (&q->debugfs_mutex);blk_mq_debugfs_unregister_rqos (rqos); +mutex_unlock (&q->debugfs_mutex); }typedef bool (acquire_inflight_cb_t )(struct rq_wait *rqw,void *private_data);
block/blk-sysfs.c +9 -11
@@ -779,14 +779,13 @@ static void blk_release_queue(struct kobject *kobj)if (queue_is_mq (q))blk_mq_release (q); -blk_trace_shutdown (q);mutex_lock (&q->debugfs_mutex); +blk_trace_shutdown (q);debugfs_remove_recursive (q->debugfs_dir); + q->debugfs_dir =NULL ; + q->sched_debugfs_dir =NULL ;mutex_unlock (&q->debugfs_mutex); -if (queue_is_mq (q)) -blk_mq_debugfs_unregister (q); -bioset_exit (&q->bio_split);if (blk_queue_has_srcu (q))
@@ -836,17 +835,16 @@ int blk_register_queue(struct gendisk *disk) goto unlock; } +if (queue_is_mq (q)) +__blk_mq_register_dev (dev, q); +mutex_lock (&q->sysfs_lock); +mutex_lock (&q->debugfs_mutex); q->debugfs_dir =debugfs_create_dir (kobject_name (q->kobj.parent), blk_debugfs_root); -mutex_unlock (&q->debugfs_mutex); - -if (queue_is_mq (q)) { -__blk_mq_register_dev (dev, q); +if (queue_is_mq (q))blk_mq_debugfs_register (q); - } - -mutex_lock (&q->sysfs_lock); +mutex_unlock (&q->debugfs_mutex); ret =disk_register_independent_access_ranges (disk,NULL );if (ret)
include/linux/blkdev.h +4 -4
@@ -466,7 +466,6 @@ struct request_queue {#endif /* CONFIG_BLK_DEV_ZONED */ int node; -struct mutex debugfs_mutex;#ifdef CONFIG_BLK_DEV_IO_TRACE struct blk_trace __rcu *blk_trace;#endif
@@ -510,11 +509,12 @@ struct request_queue {struct bio_set bio_split;struct dentry *debugfs_dir; - -#ifdef CONFIG_BLK_DEBUG_FS struct dentry *sched_debugfs_dir;struct dentry *rqos_debugfs_dir; -#endif +/* +* Serializes all debugfs metadata operations using the above dentries. +*/ +struct mutex debugfs_mutex;bool mq_sysfs_init_done;
kernel/trace/blktrace.c +0 -3
@@ -770,14 +770,11 @@ int blk_trace_ioctl(struct block_device *bdev, unsigned cmd, char __user *arg)**/ void blk_trace_shutdown (struct request_queue *q) { -mutex_lock (&q->debugfs_mutex);if (rcu_dereference_protected (q->blk_trace,lockdep_is_held (&q->debugfs_mutex))) {__blk_trace_startstop (q,0 );__blk_trace_remove (q); } - -mutex_unlock (&q->debugfs_mutex); }#ifdef CONFIG_BLK_CGROUP
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 22/53 block: remove per-disk debugfs files in blk_unregister_queue
In reply to Sasha LevinFrom: Christoph Hellwig <[email protected]>
[ Upstream commit 99d055b4fd4bbb309c6cdb51a0d420669f777944 ]
The block debugfs files are created in blk_register_queue, which is called by add_disk and use a naming scheme based on the disk_name. After del_gendisk returns that name can be reused and thus we must not leave these debugfs files around, otherwise the kernel is unhappy and spews messages like:
Directory XXXXX with parent 'block' already present!
and the newly created devices will not have working debugfs files.
Move the unregistration to blk_unregister_queue instead (which matches the sysfs unregistration) to make sure the debugfs life time rules match those of the disk name.
As part of the move also make sure the whole debugfs unregistration is inside a single debugfs_mutex critical section.
Note that this breaks blktests block/002, which checks that the debugfs directory has not been removed while blktests is running, but that particular check should simply be removed from the test case.
--- block/blk-mq-debugfs.c | 8 -------- block/blk-mq-debugfs.h | 5 ----- block/blk-rq-qos.c | 4 ---- block/blk-sysfs.c | 16 ++++++++-------- 4 files changed, 8 insertions(+), 25 deletions(-)
block/blk-mq-debugfs.c +0 -8
@@ -842,14 +842,6 @@ void blk_mq_debugfs_register_rqos(struct rq_qos *rqos)debugfs_create_files (rqos->debugfs_dir, rqos, rqos->ops->debugfs_attrs); } -void blk_mq_debugfs_unregister_queue_rqos (struct request_queue *q) -{ -lockdep_assert_held (&q->debugfs_mutex); - -debugfs_remove_recursive (q->rqos_debugfs_dir); - q->rqos_debugfs_dir =NULL ; -} -void blk_mq_debugfs_register_sched_hctx (struct request_queue *q,struct blk_mq_hw_ctx *hctx) {
block/blk-mq-debugfs.h +0 -5
@@ -35,7 +35,6 @@ void blk_mq_debugfs_unregister_sched_hctx(struct blk_mq_hw_ctx *hctx);void blk_mq_debugfs_register_rqos (struct rq_qos *rqos);void blk_mq_debugfs_unregister_rqos (struct rq_qos *rqos); -void blk_mq_debugfs_unregister_queue_rqos (struct request_queue *q);#else static inline void blk_mq_debugfs_register (struct request_queue *q) {
@@ -82,10 +81,6 @@ static inline void blk_mq_debugfs_register_rqos(struct rq_qos *rqos)static inline void blk_mq_debugfs_unregister_rqos (struct rq_qos *rqos) { } - -static inline void blk_mq_debugfs_unregister_queue_rqos (struct request_queue *q) -{ -}#endif #ifdef CONFIG_BLK_DEBUG_FS_ZONED
block/blk-rq-qos.c +0 -4
@@ -294,10 +294,6 @@ void rq_qos_wait(struct rq_wait *rqw, void *private_data,void rq_qos_exit (struct request_queue *q) { -mutex_lock (&q->debugfs_mutex); -blk_mq_debugfs_unregister_queue_rqos (q); -mutex_unlock (&q->debugfs_mutex); -while (q->rq_qos) {struct rq_qos *rqos = q->rq_qos; q->rq_qos = rqos->next;
block/blk-sysfs.c +8 -8
@@ -779,13 +779,6 @@ static void blk_release_queue(struct kobject *kobj)if (queue_is_mq (q))blk_mq_release (q); -mutex_lock (&q->debugfs_mutex); -blk_trace_shutdown (q); -debugfs_remove_recursive (q->debugfs_dir); - q->debugfs_dir =NULL ; - q->sched_debugfs_dir =NULL ; -mutex_unlock (&q->debugfs_mutex); -bioset_exit (&q->bio_split);if (blk_queue_has_srcu (q))
@@ -946,8 +939,15 @@ void blk_unregister_queue(struct gendisk *disk)/* Now that we've deleted all child objects, we can delete the queue. */ kobject_uevent (&q->kobj,KOBJ_REMOVE );kobject_del (&q->kobj); -mutex_unlock (&q->sysfs_dir_lock); +mutex_lock (&q->debugfs_mutex); +blk_trace_shutdown (q); +debugfs_remove_recursive (q->debugfs_dir); + q->debugfs_dir =NULL ; + q->sched_debugfs_dir =NULL ; + q->rqos_debugfs_dir =NULL ; +mutex_unlock (&q->debugfs_mutex); +kobject_put (&disk_to_dev (disk)->kobj); }
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 23/53 block: freeze the queue earlier in del_gendisk
In reply to Sasha LevinFrom: Christoph Hellwig <[email protected]>
[ Upstream commit a09b314005f3a0956ebf56e01b3b80339df577cc ]
Freeze the queue earlier in del_gendisk so that the state does not change while we remove debugfs and sysfs files.
Ming mentioned that being able to observer request in debugfs might be useful while the queue is being frozen in del_gendisk, which is made possible by this change.
--- block/genhd.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
block/genhd.c +1 -2
@@ -623,6 +623,7 @@ void del_gendisk(struct gendisk *disk)* Prevent new I/O from crossing bio_queue_enter(). */ blk_queue_start_drain (q); +blk_mq_freeze_queue_wait (q);if (!(disk->flags &GENHD_FL_HIDDEN )) {sysfs_remove_link (&disk_to_dev (disk)->kobj,"bdi" );
@@ -646,8 +647,6 @@ void del_gendisk(struct gendisk *disk)pm_runtime_set_memalloc_noio (disk_to_dev (disk), false);device_del (disk_to_dev (disk)); -blk_mq_freeze_queue_wait (q); -blk_throtl_cancel_bios (disk->queue);blk_sync_queue (q);
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 24/53 drivers/net/ethernet/neterion/vxge: Fix a use-after-free bug in vxge-main.c
In reply to Sasha LevinFrom: Wentao_Liang <[email protected]>
[ Upstream commit 8fc74d18639a2402ca52b177e990428e26ea881f ]
The pointer vdev points to a memory region adjacent to a net_device structure ndev, which is a field of hldev. At line 4740, the invocation to vxge_device_unregister unregisters device hldev, and it also releases the memory region pointed by vdev->bar0. At line 4743, the freed memory region is referenced (i.e., iounmap(vdev->bar0)), resulting in a use-after-free vulnerability. We can fix the bug by calling iounmap before vxge_device_unregister.
4721. static void vxge_remove(struct pci_dev *pdev)
4722. {
4723. struct __vxge_hw_device *hldev;
4724. struct vxgedev *vdev;
…
4731. vdev = netdev_priv(hldev->ndev);
…
4740. vxge_device_unregister(hldev);
4741. /* Do not call pci_disable_sriov here, as it
will break child devices */
4742. vxge_hw_device_terminate(hldev);
4743. iounmap(vdev->bar0);
…
4749 vxge_debug_init(vdev->level_trace, "%s:%d
Device unregistered",
4750 __func__, __LINE__);
4751 vxge_debug_entryexit(vdev->level_trace, "%s:%d
Exiting...", __func__,
4752 __LINE__);
4753. }
This is the screenshot when the vulnerability is triggered by using KASAN. We can see that there is a use-after-free reported by KASAN.
/***************************start**************************/
root@kernel:~# echo 1 > /sys/bus/pci/devices/0000:00:03.0/remove [ 178.296316] vxge_remove [ 182.057081] ================================================================== [ 182.057548] BUG: KASAN: use-after-free in vxge_remove+0xe0/0x15c [ 182.057760] Read of size 8 at addr ffff888006c76598 by task bash/119 [ 182.057983] [ 182.058747] CPU: 0 PID: 119 Comm: bash Not tainted 5.18.0 #5 [ 182.058919] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [ 182.059463] Call Trace: [ 182.059726] <TASK> [ 182.060017] dump_stack_lvl+0x34/0x44 [ 182.060316] print_report.cold+0xb2/0x6b7 [ 182.060401] ? kfree+0x89/0x290 [ 182.060478] ? vxge_remove+0xe0/0x15c [ 182.060545] kasan_report+0xa9/0x120 [ 182.060629] ? vxge_remove+0xe0/0x15c [ 182.060706] vxge_remove+0xe0/0x15c [ 182.060793] pci_device_remove+0x5d/0xe0 [ 182.060968] device_release_driver_internal+0xf1/0x180 [ 182.061063] pci_stop_bus_device+0xae/0xe0 [ 182.061150] pci_stop_and_remove_bus_device_locked+0x11/0x20 [ 182.061236] remove_store+0xc6/0xe0 [ 182.061297] ? subordinate_bus_number_show+0xc0/0xc0 [ 182.061359] ? __mutex_lock_slowpath+0x10/0x10 [ 182.061438] ? sysfs_kf_write+0x6d/0xa0 [ 182.061525] kernfs_fop_write_iter+0x1b0/0x260 [ 182.061610] ? sysfs_kf_bin_read+0xf0/0xf0 [ 182.061695] new_sync_write+0x209/0x310 [ 182.061789] ? new_sync_read+0x310/0x310 [ 182.061865] ? cgroup_rstat_updated+0x5c/0x170 [ 182.061937] ? preempt_count_sub+0xf/0xb0 [ 182.061995] ? pick_next_entity+0x13a/0x220 [ 182.062063] ? __inode_security_revalidate+0x44/0x80 [ 182.062155] ? security_file_permission+0x46/0x2a0 [ 182.062230] vfs_write+0x33f/0x3e0 [ 182.062303] ksys_write+0xb4/0x150 [ 182.062369] ? __ia32_sys_read+0x40/0x40 [ 182.062451] do_syscall_64+0x3b/0x90 [ 182.062531] entry_SYSCALL_64_after_hwframe+0x46/0xb0 [ 182.062894] RIP: 0033:0x7f3f37d17274 [ 182.063558] Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b3 0f 1f 80 00 00 00 00 48 8d 05 89 54 0d 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 41 54 49 89 d4 55 48 89 f5 53 [ 182.063797] RSP: 002b:00007ffd5ba9e178 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 182.064117] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f3f37d17274 [ 182.064219] RDX: 0000000000000002 RSI: 000055bbec327180 RDI: 0000000000000001 [ 182.064315] RBP: 000055bbec327180 R08: 000000000000000a R09: 00007f3f37de7cf0 [ 182.064414] R10: 000000000000000a R11: 0000000000000246 R12: 00007f3f37de8760 [ 182.064513] R13: 0000000000000002 R14: 00007f3f37de3760 R15: 0000000000000002 [ 182.064691] </TASK> [ 182.064916] [ 182.065224] The buggy address belongs to the physical page: [ 182.065804] page:00000000ef31e4f4 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x6c76 [ 182.067419] flags: 0x100000000000000(node=0|zone=1) [ 182.068997] raw: 0100000000000000 0000000000000000 ffffea00001b1d88 0000000000000000 [ 182.069118] raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 [ 182.069294] page dumped because: kasan: bad access detected [ 182.069331] [ 182.069360] Memory state around the buggy address: [ 182.070006] ffff888006c76480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 182.070136] ffff888006c76500: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 182.070230] >ffff888006c76580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 182.070305] ^ [ 182.070456] ffff888006c76600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 182.070505] ffff888006c76680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 182.070606] ================================================================== [ 182.071374] Disabling lock debugging due to kernel taint
/*****************************end*****************************/
After fixing the bug as done in the patch, we can find KASAN do not report
the bug and the device(00:03.0) has been successfully removed.
/*****************************start***************************/
root@kernel:~# echo 1 > /sys/bus/pci/devices/0000:00:03.0/remove root@kernel:~#
/******************************end****************************/
--- drivers/net/ethernet/neterion/vxge/vxge-main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/neterion/vxge/vxge-main.c +1 -1
@@ -4737,10 +4737,10 @@ static void vxge_remove(struct pci_dev *pdev)for (i =0 ; i < vdev->no_of_vpath; i++)vxge_free_mac_add_list (&vdev->vpaths[i]); +iounmap (vdev->bar0);vxge_device_unregister (hldev);/* Do not call pci_disable_sriov here, as it will break child devices */ vxge_hw_device_terminate (hldev); -iounmap (vdev->bar0);pci_release_region (pdev,0 );pci_disable_device (pdev); driver_config->config_dev_cnt--;
Signature · 1 line
2.35.1
Jakub Kicinski
maintainerRe: [PATCH AUTOSEL 5.18 24/53] drivers/net/ethernet/neterion/vxge: Fix a use-after-free bug in vxge-main.c
Quoted 11 lines · On Mon, 27 Jun 2022 22:18:10 -0400 Sasha Levin wrote:
From:
Wentao_Liang<[email protected]>[ Upstream commit
8fc74d18639a2402ca52b177e990428e26ea881f]The pointer vdev points to a memory region adjacent to a
net_devicestructure ndev, which is a field of hldev. At line 4740, the invocation tovxge_device_unregisterunregisters device hldev, and it also releases the memory region pointed byvdev->bar0. At line 4743, the freed memory region is referenced (i.e.,iounmap(vdev->bar0)), resulting in a use-after-free vulnerability. We can fix the bug by calling iounmap beforevxge_device_unregister.
This is a dud see commit 877fe9d49b74 ("Revert "drivers/net/ethernet/neterion/vxge: Fix a use-after-free bug in vxge-main.c"")
Sasha Levin
maintainerPATCH 25/53 powerpc/prom_init: Fix build failure with GCC_PLUGIN_STRUCTLEAK_BYREF_ALL and KASAN
In reply to Sasha LevinFrom: Christophe Leroy <[email protected]>
[ Upstream commit ca5dabcff1df6bc8c413922b5fa63cc602858803 ]
When CONFIG_KASAN is selected, we expect prom_init to use __memset() because it is too early to use memset().
But with CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL, the compiler adds calls to memset() to clear objects on stack, hence the following failure:
PROMCHK arch/powerpc/kernel/prom_init_check
Error: External symbol 'memset' referenced from prom_init.c
make[2]: *** [arch/powerpc/kernel/Makefile:204 : arch/powerpc/kernel/prom_init_check] Erreur 1
prom_find_machine_type() is called from prom_init() and is called only once, so lets put compat[] in BSS instead of stack to avoid that.
--- arch/powerpc/kernel/prom_init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/powerpc/kernel/prom_init.c +1 -1
@@ -2300,7 +2300,7 @@ static void __init prom_init_stdout(void)static int __init prom_find_machine_type (void ) { -char compat[256 ]; + static char compat[256] __prombss;int len, i =0 ;#ifdef CONFIG_PPC64 phandle rtas;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 26/53 libperf evsel: Open shouldn't leak fd on failure
In reply to Sasha LevinFrom: Ian Rogers <[email protected]>
[ Upstream commit 94725994cfd768b9ee1bd06f15c252694b1e9b89 ]
If perf_event_open() fails the fd is opened but it is only freed by closing (not by delete).
Typically when an open fails you don't call close and so this results in a memory leak. To avoid this, add a close when open fails.
--- tools/lib/perf/evsel.c | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-)
tools/lib/perf/evsel.c +12 -5
@@ -149,23 +149,30 @@ int perf_evsel__open(struct perf_evsel *evsel, struct perf_cpu_map *cpus,int fd, group_fd, *evsel_fd; evsel_fd =FD (evsel, idx, thread); -if (evsel_fd ==NULL ) -return -EINVAL ; +if (evsel_fd ==NULL ) { + err = -EINVAL ; + goto out; + } err =get_group_fd (evsel, idx, thread, &group_fd);if (err <0 ) -return err; + goto out; fd =sys_perf_event_open (&evsel->attr, threads->map[thread].pid, cpu, group_fd,0 ); -if (fd <0 ) -return -errno; +if (fd <0 ) { + err = -errno; + goto out; + } *evsel_fd = fd; } } +out: +if (err) +perf_evsel__close (evsel);return err; }
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 27/53 drm: panel-orientation-quirks: Add quirk for Aya Neo Next
In reply to Sasha LevinFrom: Maya Matuszczyk <[email protected]>
[ Upstream commit be33d52ef5b4bdfec04cfdad39368c343bac97a3 ]
The device is identified by "NEXT" in board name, however there are different versions of it, "Next Advance" and "Next Pro", that have different DMI board names.
Due to a production error a batch or two have their board names prefixed by "AYANEO", this makes it 6 different DMI board names. To save some space in final kernel image DMI_MATCH is used instead of DMI_EXACT_MATCH.
--- drivers/gpu/drm/drm_panel_orientation_quirks.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/gpu/drm/drm_panel_orientation_quirks.c +6 -0
@@ -152,6 +152,12 @@ static const struct dmi_system_id orientation_data[] = { DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "AYA NEO 2021"), }, .driver_data = (void *)&lcd800x1280_rightside_up, + }, { /* AYA NEO NEXT */ + .matches = { +DMI_EXACT_MATCH (DMI_BOARD_VENDOR ,"AYANEO" ), + DMI_MATCH(DMI_BOARD_NAME, "NEXT"), + }, + .driver_data = (void *)&lcd800x1280_rightside_up, }, { /* Chuwi HiBook (CWI514) */ .matches = { DMI_MATCH(DMI_BOARD_VENDOR, "Hampoo"),
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 28/53 iio: freq: admv1014: Fix warning about dubious x & !y and improve readability
In reply to Sasha LevinFrom: Antoniu Miclaus <[email protected]>
[ Upstream commit 6f6bd7591945c679b7f595119ea997b19f5794db ]
The warning comes from __BF_FIELD_CHECK()
specifically
BUILD_BUG_ON_MSG(__builtin_constant_p(_val) ? \ ~((_mask) >> __bf_shf(_mask)) & (_val) : 0, \ _pfx "value too large for the field"); \
The code was using !(enum value) which is not particularly easy to follow so replace that with explicit matching and use of ? 0 : 1; or ? 1 : 0; to improve readability.
--- drivers/iio/frequency/admv1014.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/iio/frequency/admv1014.c +4 -2
@@ -700,8 +700,10 @@ static int admv1014_init(struct admv1014_state *st)ADMV1014_DET_EN_MSK ; enable_reg =FIELD_PREP (ADMV1014_P1DB_COMPENSATION_MSK , st->p1db_comp ?3 :0 ) | -FIELD_PREP (ADMV1014_IF_AMP_PD_MSK , !(st->input_mode)) | -FIELD_PREP (ADMV1014_BB_AMP_PD_MSK , st->input_mode) | +FIELD_PREP (ADMV1014_IF_AMP_PD_MSK , + (st->input_mode ==ADMV1014_IF_MODE ) ?0 :1 ) | +FIELD_PREP (ADMV1014_BB_AMP_PD_MSK , + (st->input_mode ==ADMV1014_IF_MODE ) ?1 :0 ) |FIELD_PREP (ADMV1014_DET_EN_MSK , st->det_en);return __admv1014_spi_update_bits (st,ADMV1014_REG_ENABLE , enable_reg_msk, enable_reg);
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 29/53 spi: rockchip: Unmask IRQ at the final to avoid preemption
In reply to Sasha LevinFrom: Jon Lin <[email protected]>
[ Upstream commit 419bc8f681a0dc63588cee693b6d45e7caa6006c ]
Avoid pio_write process is preempted, resulting in abnormal state.
--- drivers/spi/spi-rockchip.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
drivers/spi/spi-rockchip.c +7 -4
@@ -381,15 +381,18 @@ static int rockchip_spi_prepare_irq(struct rockchip_spi *rs, rs->tx_left = rs->tx ? xfer->len / rs->n_bytes :0 ; rs->rx_left = xfer->len / rs->n_bytes; -if (rs->cs_inactive) -writel_relaxed (INT_RF_FULL |INT_CS_INACTIVE , rs->regs +ROCKCHIP_SPI_IMR ); -else -writel_relaxed (INT_RF_FULL , rs->regs +ROCKCHIP_SPI_IMR ); +writel_relaxed (0xffffffff , rs->regs +ROCKCHIP_SPI_ICR ); +spi_enable_chip (rs, true);if (rs->tx_left)rockchip_spi_pio_writer (rs); +if (rs->cs_inactive) +writel_relaxed (INT_RF_FULL |INT_CS_INACTIVE , rs->regs +ROCKCHIP_SPI_IMR ); +else +writel_relaxed (INT_RF_FULL , rs->regs +ROCKCHIP_SPI_IMR ); +/* 1 means the transfer is in progress */ return 1 ; }
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 30/53 video: fbdev: skeletonfb: Fix syntax errors in comments
In reply to Sasha LevinFrom: Xiang wangx <[email protected]>
[ Upstream commit fc378794a2f7a19cf26010dc33b89ba608d4c70f ]
Delete the redundant word 'its'.
--- drivers/video/fbdev/skeletonfb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/video/fbdev/skeletonfb.c +1 -1
@@ -96,7 +96,7 @@ static const struct fb_fix_screeninfo xxxfb_fix = {/* * Modern graphical hardware not only supports pipelines but some -* also support multiple monitors where each display can have its +* also support multiple monitors where each display can have * its own unique data. In this case each display could be * represented by a separate framebuffer device thus a separate * struct fb_info. Now the struct xxx_par represents the graphics
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 31/53 video: fbdev: intelfb: Use aperture size from pci_resource_len
In reply to Sasha LevinFrom: Petr Cvek <[email protected]>
[ Upstream commit 25c9a15fb7bbfafb94dd3b4e3165c18b8e1bd039 ]
Aperture size for i9x5 variants is determined from PCI base address.
if (pci_resource_start(pdev, 2) & 0x08000000) *aperture_size = MB(128); ...
This condition is incorrect as 128 MiB address can have the address set as 0x?8000000 or 0x?0000000. Also the code can be simplified to just use pci_resource_len().
The true settings of the aperture size is in the MSAC register, which could be used instead. However the value is used only as an info message, so it doesn't matter.
--- drivers/video/fbdev/intelfb/intelfbhw.c | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-)
drivers/video/fbdev/intelfb/intelfbhw.c +5 -7
@@ -201,13 +201,11 @@ int intelfbhw_get_memory(struct pci_dev *pdev, int *aperture_size,case PCI_DEVICE_ID_INTEL_945GME :case PCI_DEVICE_ID_INTEL_965G :case PCI_DEVICE_ID_INTEL_965GM : -/* 915, 945 and 965 chipsets support a 256MB aperture. -Aperture size is determined by inspected the -base address of the aperture. */ -if (pci_resource_start (pdev,2 ) &0x08000000 ) - *aperture_size =MB (128 ); -else - *aperture_size =MB (256 ); +/* +* 915, 945 and 965 chipsets support 64MB, 128MB or 256MB +* aperture. Determine size from PCI resource length. +*/ + *aperture_size =pci_resource_len (pdev,2 );break ;default :if ((tmp &INTEL_GMCH_MEM_MASK ) ==INTEL_GMCH_MEM_64M )
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 32/53 io_uring: mark reissue requests with REQ_F_PARTIAL_IO
In reply to Sasha LevinFrom: Jens Axboe <[email protected]>
[ Upstream commit 1bacd264d3c3a05de4afdd1712c9dd6ccebb9490 ]
If we mark for reissue, we assume that the buffer will remain stable. Hence if are using a provided buffer, we need to ensure that we stick with it for the duration of that request.
This only affects block devices that use provided buffers, as those are the only ones that get marked with REQ_F_REISSUE.
--- fs/io_uring.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/io_uring.c +2 -2
@@ -3009,7 +3009,7 @@ static bool __io_complete_rw_common(struct io_kiocb *req, long res)if (unlikely (res != req->result)) {if ((res == -EAGAIN || res == -EOPNOTSUPP ) &&io_rw_should_reissue (req)) { - req->flags |=REQ_F_REISSUE ; + req->flags |=REQ_F_REISSUE |REQ_F_PARTIAL_IO ;return true; }req_set_fail (req);
@@ -3059,7 +3059,7 @@ static void io_complete_rw_iopoll(struct kiocb *kiocb, long res)kiocb_end_write (req);if (unlikely (res != req->result)) {if (res == -EAGAIN &&io_rw_should_reissue (req)) { - req->flags |=REQ_F_REISSUE ; + req->flags |=REQ_F_REISSUE |REQ_F_PARTIAL_IO ;return ; } req->result = res;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 33/53 video: fbdev: pxa3xx-gcu: Fix integer overflow in pxa3xx_gcu_write
In reply to Sasha LevinFrom: Hyunwoo Kim <[email protected]>
[ Upstream commit a09d2d00af53b43c6f11e6ab3cb58443c2cac8a7 ]
In pxa3xx_gcu_write, a count parameter of type size_t is passed to words of type int. Then, copy_from_user() may cause a heap overflow because it is used as the third argument of copy_from_user().
--- drivers/video/fbdev/pxa3xx-gcu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/video/fbdev/pxa3xx-gcu.c +1 -1
@@ -381,7 +381,7 @@ pxa3xx_gcu_write(struct file *file, const char *buff,struct pxa3xx_gcu_batch *buffer;struct pxa3xx_gcu_priv *priv =to_pxa3xx_gcu_priv (file); -int words = count /4 ; +size_t words = count /4 ;/* Does not need to be atomic. There's a lock in user space, * but anyhow, this is just for statistics. */
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 34/53 video: fbdev: simplefb: Check before clk_put() not needed
In reply to Sasha LevinFrom: Yihao Han <[email protected]>
[ Upstream commit 5491424d17bdeb7b7852a59367858251783f8398 ]
clk_put() already checks the clk ptr using !clk and IS_ERR() so there is no need to check it again before calling it.
--- drivers/video/fbdev/simplefb.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/video/fbdev/simplefb.c +1 -2
@@ -237,8 +237,7 @@ static int simplefb_clocks_get(struct simplefb_par *par,if (IS_ERR (clock)) {if (PTR_ERR (clock) == -EPROBE_DEFER ) {while (--i >=0 ) { -if (par->clks[i]) -clk_put (par->clks[i]); +clk_put (par->clks[i]); }kfree (par->clks);return -EPROBE_DEFER ;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 35/53 btrfs: add missing inode updates on each iteration when replacing extents
In reply to Sasha LevinFrom: Filipe Manana <[email protected]>
[ Upstream commit 983d8209c6803345c9958f4cc358d1155f93a099 ]
When replacing file extents, called during fallocate, hole punching, clone and deduplication, we may not be able to replace/drop all the target file extent items with a single transaction handle. We may get -ENOSPC while doing it, in which case we release the transaction handle, balance the dirty pages of the btree inode, flush delayed items and get a new transaction handle to operate on what's left of the target range.
By dropping and replacing file extent items we have effectively modified the inode, so we should bump its iversion and update its mtime/ctime before we update the inode item. This is because if the transaction we used for partially modifying the inode gets committed by someone after we release it and before we finish the rest of the range, a power failure happens, then after mounting the filesystem our inode has an outdated iversion and mtime/ctime, corresponding to the values it had before we changed it.
So add the missing iversion and mtime/ctime updates.
--- fs/btrfs/ctree.h | 2 ++ fs/btrfs/file.c | 19 +++++++++++++++++++ fs/btrfs/inode.c | 1 + fs/btrfs/reflink.c | 1 + 4 files changed, 23 insertions(+)
fs/btrfs/ctree.h +2 -0
@@ -1331,6 +1331,8 @@ struct btrfs_replace_extent_info {* existing extent into a file range. */ bool is_new_extent; +/* Indicate if we should update the inode's mtime and ctime. */ +bool update_times;/* Meaningful only if is_new_extent is true. */ int qgroup_reserved;/*
fs/btrfs/file.c +19 -0
@@ -2850,6 +2850,25 @@ int btrfs_replace_file_extents(struct btrfs_inode *inode, extent_info->file_offset += replace_len; } +/* +* We are releasing our handle on the transaction, balance the +* dirty pages of the btree inode and flush delayed items, and +* then get a new transaction handle, which may now point to a +* new transaction in case someone else may have committed the +* transaction we used to replace/drop file extent items. So +* bump the inode's iversion and update mtime and ctime except +* if we are called from a dedupe context. This is because a +* power failure/crash may happen after the transaction is +* committed and before we finish replacing/dropping all the +* file extent items we need. +*/ +inode_inc_iversion (&inode->vfs_inode); + +if (!extent_info || extent_info->update_times) { + inode->vfs_inode.i_mtime =current_time (&inode->vfs_inode); + inode->vfs_inode.i_ctime = inode->vfs_inode.i_mtime; + } + ret =btrfs_update_inode (trans, root, inode);if (ret)break ;
fs/btrfs/inode.c +1 -0
@@ -9916,6 +9916,7 @@ static struct btrfs_trans_handle *insert_prealloc_file_extent( extent_info.file_offset = file_offset; extent_info.extent_buf = (char *)&stack_fi; extent_info.is_new_extent = true; + extent_info.update_times = true; extent_info.qgroup_reserved = qgroup_released; extent_info.insertions =0 ;
fs/btrfs/reflink.c +1 -0
@@ -489,6 +489,7 @@ static int btrfs_clone(struct inode *src, struct inode *inode, clone_info.file_offset = new_key.offset; clone_info.extent_buf = buf; clone_info.is_new_extent = false; + clone_info.update_times = !no_time_update; ret =btrfs_replace_file_extents (BTRFS_I (inode), path, drop_start, new_key.offset + datal -1 , &clone_info, &trans);
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 36/53 btrfs: do not BUG_ON() on failure to migrate space when replacing extents
In reply to Sasha LevinFrom: Filipe Manana <[email protected]>
[ Upstream commit 650c9caba32a0167a018cca0fab32a2965d23513 ]
At btrfs_replace_file_extents(), if we fail to migrate reserved metadata space from the transaction block reserve into the local block reserve, we trigger a BUG_ON(). This is because it should not be possible to have a failure here, as we reserved more space when we started the transaction than the space we want to migrate. However having a BUG_ON() is way too drastic, we can perfectly handle the failure and return the error to the caller. So just do that instead, and add a WARN_ON() to make it easier to notice the failure if it ever happens (which is particularly useful for fstests, and the warning will trigger a failure of a test case).
--- fs/btrfs/file.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
fs/btrfs/file.c +4 -2
@@ -2766,7 +2766,8 @@ int btrfs_replace_file_extents(struct btrfs_inode *inode, ret =btrfs_block_rsv_migrate (&fs_info->trans_block_rsv, rsv, min_size, false); -BUG_ON (ret); +if (WARN_ON (ret)) + goto out_trans; trans->block_rsv = rsv; cur_offset = start;
@@ -2885,7 +2886,8 @@ int btrfs_replace_file_extents(struct btrfs_inode *inode, ret =btrfs_block_rsv_migrate (&fs_info->trans_block_rsv, rsv, min_size, false); -BUG_ON (ret);/* shouldn't happen */ +if (WARN_ON (ret)) +break ; trans->block_rsv = rsv; cur_offset = drop_args.drop_end;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 37/53 io_uring: fix merge error in checking send/recv addr2 flags
In reply to Sasha LevinFrom: Jens Axboe <[email protected]>
[ Upstream commit b60cac14bb3c88cff2a7088d9095b01a80938c41 ]
With the dropping of the IOPOLL checking in the per-opcode handlers, we inadvertently left two checks in the recv/recvmsg and send/sendmsg prep handlers for the same thing, and one of them includes addr2 which holds the flags for these opcodes.
Fix it up and kill the redundant checks.
--- fs/io_uring.c | 4 ---- 1 file changed, 4 deletions(-)
fs/io_uring.c +0 -4
@@ -5252,8 +5252,6 @@ static int io_sendmsg_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)if (unlikely (req->ctx->flags &IORING_SETUP_IOPOLL ))return -EINVAL ; -if (unlikely (sqe->addr2 || sqe->file_index)) -return -EINVAL ; sr->umsg =u64_to_user_ptr (READ_ONCE (sqe->addr)); sr->len =READ_ONCE (sqe->len);
@@ -5465,8 +5463,6 @@ static int io_recvmsg_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)if (unlikely (req->ctx->flags &IORING_SETUP_IOPOLL ))return -EINVAL ; -if (unlikely (sqe->addr2 || sqe->file_index)) -return -EINVAL ; sr->umsg =u64_to_user_ptr (READ_ONCE (sqe->addr)); sr->len =READ_ONCE (sqe->len);
Signature · 1 line
2.35.1
Jens Axboe
maintainerRe: [PATCH AUTOSEL 5.18 37/53] io_uring: fix merge error in checking send/recv addr2 flags
Quoted 32 lines · Sasha Levin
From: Jens Axboe <[email protected]>
[ Upstream commit
b60cac14bb3c88cff2a7088d9095b01a80938c41]With the dropping of the IOPOLL checking in the per-opcode handlers, we inadvertently left two checks in the recv/recvmsg and send/sendmsg prep handlers for the same thing, and one of them includes addr2 which holds the flags for these opcodes.
Fix it up and kill the redundant checks.
Signed-off-by Jens Axboe <[email protected]>Signed-off-by Sasha Levin <[email protected]>--- fs/io_uring.c | 4 ---- 1 file changed, 4 deletions(-)fs/io_uring.c +0
-2@@ -5252,8 +5252,6 @@ static int io_sendmsg_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)if (unlikely (req->ctx->flags &IORING_SETUP_IOPOLL ))return -EINVAL ; -if (unlikely (sqe->addr2 || sqe->file_index)) -return -EINVAL ; sr->umsg =u64_to_user_ptr (READ_ONCE (sqe->addr)); sr->len =READ_ONCE (sqe->len);
fs/io_uring.c static int io_recvmsg_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe) · line 5468
Quoted 8 lines
fs/io_uring.c +0
-2@@ -5465,8 +5463,6 @@ static int io_recvmsg_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)if (unlikely (req->ctx->flags &IORING_SETUP_IOPOLL ))return -EINVAL ; -if (unlikely (sqe->addr2 || sqe->file_index)) -return -EINVAL ; sr->umsg =u64_to_user_ptr (READ_ONCE (sqe->addr)); sr->len =READ_ONCE (sqe->len);
This doesn't look right, and cannot be as the problem was added with a 5.19 merge issue. Please drop this patch from 5.18-stable, thanks.
Signature · 1 line
Jens Axboe
Sasha Levin
maintainerPATCH 38/53 drm/xen: Add missing VM_DONTEXPAND flag in mmap callback
In reply to Sasha LevinFrom: Oleksandr Tyshchenko <[email protected]>
[ Upstream commit ca6969013d13282b42cb5edcc13db731a08e0ad8 ]
With Xen PV Display driver in use the "expected" VM_DONTEXPAND flag is not set (neither explicitly nor implicitly), so the driver hits the code path in drm_gem_mmap_obj() which triggers the WARNING.
--- drivers/gpu/drm/xen/xen_drm_front_gem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/xen/xen_drm_front_gem.c +1 -1
@@ -71,7 +71,7 @@ static int xen_drm_front_gem_object_mmap(struct drm_gem_object *gem_obj,* the whole buffer. */ vma->vm_flags &= ~VM_PFNMAP ; - vma->vm_flags |=VM_MIXEDMAP ; + vma->vm_flags |=VM_MIXEDMAP |VM_DONTEXPAND ; vma->vm_pgoff =0 ;/*
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 39/53 arch: mips: generic: Add missing of_node_put() in board-ranchu.c
In reply to Sasha LevinFrom: Liang He <[email protected]>
[ Upstream commit 4becf6417bbdc293734a590fe4ed38437bbcea2c ]
In ranchu_measure_hpt_freq(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_put_node() when it is not used anymore.
--- arch/mips/generic/board-ranchu.c | 1 + 1 file changed, 1 insertion(+)
arch/mips/generic/board-ranchu.c +1 -0
@@ -44,6 +44,7 @@ static __init unsigned int ranchu_measure_hpt_freq(void) __func__); rtc_base =of_iomap (np,0 ); +of_node_put (np);if (!rtc_base)panic ("%s(): Failed to ioremap Goldfish RTC base!" , __func__);
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 40/53 mips: mti-malta: Fix refcount leak in malta-time.c
In reply to Sasha LevinFrom: Liang He <[email protected]>
[ Upstream commit 608d94cb84c42585058d692f2fe5d327f8868cdb ]
In update_gic_frequency_dt(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.
--- arch/mips/mti-malta/malta-time.c | 2 ++ 1 file changed, 2 insertions(+)
arch/mips/mti-malta/malta-time.c +2 -0
@@ -214,6 +214,8 @@ static void update_gic_frequency_dt(void)if (of_update_property (node, &gic_frequency_prop) <0 )pr_err ("error updating gic frequency property\n" ); + + of_node_put(node); }#endif
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 41/53 mips: ralink: Fix refcount leak in of.c
In reply to Sasha LevinFrom: Liang He <[email protected]>
[ Upstream commit 48ca54e39173d1ed4c4dc8cf045484014bb26eaf ]
In plat_of_remap_node(), plat_of_remap_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.
--- arch/mips/ralink/of.c | 2 ++ 1 file changed, 2 insertions(+)
arch/mips/ralink/of.c +2 -0
@@ -40,6 +40,8 @@ __iomem void *plat_of_remap_node(const char *node)if (of_address_to_resource (np,0 , &res))panic ("Failed to get resource for %s" , node); +of_node_put (np); +if (!request_mem_region (res.start,resource_size (&res), res.name))
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 42/53 mips: lantiq: falcon: Fix refcount leak bug in sysctrl
In reply to Sasha LevinFrom: Liang He <[email protected]>
[ Upstream commit 72a2af539fff975caadd9a4db3f99963569bd9c9 ]
In ltq_soc_init(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.
--- arch/mips/lantiq/falcon/sysctrl.c | 6 ++++++ 1 file changed, 6 insertions(+)
arch/mips/lantiq/falcon/sysctrl.c +6 -0
@@ -208,6 +208,12 @@ void __init ltq_soc_init(void) of_address_to_resource(np_sysgpe, 0, &res_sys[2]))panic ("Failed to get core resources" ); +of_node_put (np_status); +of_node_put (np_ebu); +of_node_put (np_sys1); +of_node_put (np_syseth); +of_node_put (np_sysgpe); + if ((request_mem_region(res_status.start, resource_size(&res_status), res_status.name) < 0) || (request_mem_region(res_ebu.start, resource_size(&res_ebu),
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 43/53 mips: lantiq: xway: Fix refcount leak bug in sysctrl
In reply to Sasha LevinFrom: Liang He <[email protected]>
[ Upstream commit 76695592711ef1e215cc24ed3e1cd857d7fc3098 ]
In ltq_soc_init(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.
--- arch/mips/lantiq/xway/sysctrl.c | 4 ++++ 1 file changed, 4 insertions(+)
arch/mips/lantiq/xway/sysctrl.c +4 -0
@@ -441,6 +441,10 @@ void __init ltq_soc_init(void) of_address_to_resource(np_ebu, 0, &res_ebu))panic ("Failed to get core resources" ); +of_node_put (np_pmu); +of_node_put (np_cgu); +of_node_put (np_ebu); +if (!request_mem_region (res_pmu.start,resource_size (&res_pmu), res_pmu.name) || !request_mem_region(res_cgu.start, resource_size(&res_cgu),
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 44/53 mips/pic32/pic32mzda: Fix refcount leak bugs
In reply to Sasha LevinFrom: Liang He <[email protected]>
[ Upstream commit eb9e9bc4fa5fb489c92ec588b3fb35f042ba6d86 ]
of_find_matching_node(), of_find_compatible_node() and of_find_node_by_path() will return node pointers with refcout incremented. We should call of_node_put() when they are not used anymore.
--- arch/mips/pic32/pic32mzda/init.c | 7 ++++++- arch/mips/pic32/pic32mzda/time.c | 3 +++ 2 files changed, 9 insertions(+), 1 deletion(-)
arch/mips/pic32/pic32mzda/init.c +6 -1
@@ -98,13 +98,18 @@ static int __init pic32_of_prepare_platform_data(struct of_dev_auxdata *lookup) np =of_find_compatible_node (NULL ,NULL , lookup->compatible);if (np) { lookup->name = (char *)np->name; -if (lookup->phys_addr) +if (lookup->phys_addr) { +of_node_put (np);continue ; + }if (!of_address_to_resource (np,0 , &res)) lookup->phys_addr = res.start; +of_node_put (np); } } +of_node_put (root); +return 0 ; }
arch/mips/pic32/pic32mzda/time.c +3 -0
@@ -32,6 +32,9 @@ static unsigned int pic32_xlate_core_timer_irq(void) goto default_map; irq =irq_of_parse_and_map (node,0 ); + +of_node_put (node); +if (!irq) goto default_map;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 45/53 mips: dts: ingenic: Add TCU clock to x1000/x1830 tcu device node
In reply to Sasha LevinFrom: Aidan MacDonald <[email protected]>
[ Upstream commit db30dc1a5226eb74d52f748989e9a06451333678 ]
This clock is a gate for the TCU hardware block on these SoCs, but it wasn't included in the device tree since the ingenic-tcu driver erroneously did not request it.
--- arch/mips/boot/dts/ingenic/x1000.dtsi | 5 +++-- arch/mips/boot/dts/ingenic/x1830.dtsi | 5 +++-- 2 files changed, 6 insertions(+), 4 deletions(-)
arch/mips/boot/dts/ingenic/x1000.dtsi +3 -2
@@ -111,8 +111,9 @@ tcu: timer@10002000 { clocks = <&cgu X1000_CLK_RTCLK>, <&cgu X1000_CLK_EXCLK>, - <&cgu X1000_CLK_PCLK>; - clock-names = "rtc", "ext", "pclk"; + <&cgu X1000_CLK_PCLK>, + <&cgu X1000_CLK_TCU>; + clock-names = "rtc", "ext", "pclk", "tcu"; interrupt-controller; #interrupt-cells = <1>;
arch/mips/boot/dts/ingenic/x1830.dtsi +3 -2
@@ -104,8 +104,9 @@ tcu: timer@10002000 { clocks = <&cgu X1830_CLK_RTCLK>, <&cgu X1830_CLK_EXCLK>, - <&cgu X1830_CLK_PCLK>; - clock-names = "rtc", "ext", "pclk"; + <&cgu X1830_CLK_PCLK>, + <&cgu X1830_CLK_TCU>; + clock-names = "rtc", "ext", "pclk", "tcu"; interrupt-controller; #interrupt-cells = <1>;
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 46/53 mips: lantiq: Add missing of_node_put() in irq.c
In reply to Sasha LevinFrom: Liang He <[email protected]>
[ Upstream commit 3748d2185ac4c2c6f80989672253aad909ecaf95 ]
In icu_of_init(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.
--- arch/mips/lantiq/irq.c | 1 + 1 file changed, 1 insertion(+)
arch/mips/lantiq/irq.c +1 -0
@@ -408,6 +408,7 @@ int __init icu_of_init(struct device_node *node, struct device_node *parent)if (!ltq_eiu_membase)panic ("Failed to remap eiu memory" ); } +of_node_put (eiu_node);return 0 ; }
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 47/53 drm/sun4i: Add DMA mask and segment size
In reply to Sasha LevinFrom: Jernej Skrabec <[email protected]>
[ Upstream commit f5aa16807aa4f99293044944590dde81364f434f ]
Kernel occasionally complains that there is mismatch in segment size when trying to render HW decoded videos and rendering them directly with sun4i DRM driver. Following message can be observed on H6 SoC:
[ 184.298308] ------------[ cut here ]------------ [ 184.298326] DMA-API: sun4i-drm display-engine: mapping sg segment longer than device claims to support [len=6144000] [max=65536] [ 184.298364] WARNING: CPU: 1 PID: 382 at kernel/dma/debug.c:1162 debug_dma_map_sg+0x2b0/0x350 [ 184.322997] CPU: 1 PID: 382 Comm: ffmpeg Not tainted 5.19.0-rc1+ #1331 [ 184.329533] Hardware name: Tanix TX6 (DT) [ 184.333544] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 184.340512] pc : debug_dma_map_sg+0x2b0/0x350 [ 184.344882] lr : debug_dma_map_sg+0x2b0/0x350 [ 184.349250] sp : ffff800009f33a50 [ 184.352567] x29: ffff800009f33a50 x28: 0000000000010000 x27: ffff000001b86c00 [ 184.359725] x26: ffffffffffffffff x25: ffff000005d8cc80 x24: 0000000000000000 [ 184.366879] x23: ffff80000939ab18 x22: 0000000000000001 x21: 0000000000000001 [ 184.374031] x20: 0000000000000000 x19: ffff0000018a7410 x18: ffffffffffffffff [ 184.381186] x17: 0000000000000000 x16: 0000000000000000 x15: ffffffffffffffff [ 184.388338] x14: 0000000000000001 x13: ffff800009534e86 x12: 6f70707573206f74 [ 184.395493] x11: 20736d69616c6320 x10: 000000000000000a x9 : 0000000000010000 [ 184.402647] x8 : ffff8000093b6d40 x7 : ffff800009f33850 x6 : 000000000000000c [ 184.409800] x5 : ffff0000bf997940 x4 : 0000000000000000 x3 : 0000000000000027 [ 184.416953] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000003960e80 [ 184.424106] Call trace: [ 184.426556] debug_dma_map_sg+0x2b0/0x350 [ 184.430580] __dma_map_sg_attrs+0xa0/0x110 [ 184.434687] dma_map_sgtable+0x28/0x4c [ 184.438447] vb2_dc_dmabuf_ops_map+0x60/0xcc [ 184.442729] __map_dma_buf+0x2c/0xd4 [ 184.446321] dma_buf_map_attachment+0xa0/0x130 [ 184.450777] drm_gem_prime_import_dev+0x7c/0x18c [ 184.455410] drm_gem_prime_fd_to_handle+0x1b8/0x214 [ 184.460300] drm_prime_fd_to_handle_ioctl+0x2c/0x40 [ 184.465190] drm_ioctl_kernel+0xc4/0x174 [ 184.469123] drm_ioctl+0x204/0x420 [ 184.472534] __arm64_sys_ioctl+0xac/0xf0 [ 184.476474] invoke_syscall+0x48/0x114 [ 184.480240] el0_svc_common.constprop.0+0x44/0xec [ 184.484956] do_el0_svc+0x2c/0xc0 [ 184.488283] el0_svc+0x2c/0x84 [ 184.491354] el0t_64_sync_handler+0x11c/0x150 [ 184.495723] el0t_64_sync+0x18c/0x190 [ 184.499397] ---[ end trace 0000000000000000 ]---
Fix that by setting DMA mask and segment size.
--- drivers/gpu/drm/sun4i/sun4i_drv.c | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/gpu/drm/sun4i/sun4i_drv.c +8 -0
@@ -7,6 +7,7 @@*/ #include <linux/component.h> +#include <linux/dma-mapping.h> #include <linux/kfifo.h> #include <linux/module.h> #include <linux/of_graph.h>
@@ -367,6 +368,13 @@ static int sun4i_drv_probe(struct platform_device *pdev)INIT_KFIFO (list.fifo); +/* +* DE2 and DE3 cores actually supports 40-bit addresses, but +* driver does not. +*/ +dma_set_mask_and_coherent (&pdev->dev,DMA_BIT_MASK (32 )); +dma_set_max_seg_size (&pdev->dev,UINT_MAX ); +for (i =0 ;; i++) { struct device_node *pipeline = of_parse_phandle(np, "allwinner,pipelines",
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 48/53 drm/sun4i: Return if frontend is not present
In reply to Sasha LevinFrom: Saud Farooqui <[email protected]>
[ Upstream commit 85016f66af8506cb601fd4f4fde23ed327a266be ]
Added return statement in sun4i_layer_format_mod_supported() in case frontend is not present.
--- drivers/gpu/drm/sun4i/sun4i_layer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/sun4i/sun4i_layer.c +1 -1
@@ -117,7 +117,7 @@ static bool sun4i_layer_format_mod_supported(struct drm_plane *plane,struct sun4i_layer *layer =plane_to_sun4i_layer (plane);if (IS_ERR_OR_NULL (layer->backend->frontend)) -sun4i_backend_format_is_supported (format, modifier); +return sun4i_backend_format_is_supported (format, modifier);return sun4i_backend_format_is_supported (format, modifier) ||sun4i_frontend_format_is_supported (format, modifier);
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 49/53 hinic: Replace memcpy() with direct assignment
In reply to Sasha LevinFrom: Kees Cook <[email protected]>
[ Upstream commit 1e70212e031528918066a631c9fdccda93a1ffaa ]
Under CONFIG_FORTIFY_SOURCE=y and CONFIG_UBSAN_BOUNDS=y, Clang is bugged here for calculating the size of the destination buffer (0x10 instead of 0x14). This copy is a fixed size (sizeof(struct fw_section_info_st)), with the source and dest being struct fw_section_info_st, so the memcpy should be safe, assuming the index is within bounds, which is UBSAN_BOUNDS's responsibility to figure out.
Avoid the whole thing and just do a direct assignment. This results in no change to the executable code.
[This is a duplicate of commit 2c0ab32b73cf ("hinic: Replace memcpy()
with direct assignment") which was applied to net-next.]
--- drivers/net/ethernet/huawei/hinic/hinic_devlink.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/net/ethernet/huawei/hinic/hinic_devlink.c +1 -3
@@ -43,9 +43,7 @@ static bool check_image_valid(struct hinic_devlink_priv *priv, const u8 *buf,for (i =0 ; i < fw_image->fw_info.fw_section_cnt; i++) { len += fw_image->fw_section_info[i].fw_section_len; -memcpy (&host_image->image_section_info[i], - &fw_image->fw_section_info[i], -sizeof (struct fw_section_info_st )); + host_image->image_section_info[i] = fw_image->fw_section_info[i]; } if (len != fw_image->fw_len ||
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 50/53 drm/amdgpu: Adjust logic around GTT size (v3)
In reply to Sasha LevinFrom: Alex Deucher <[email protected]>
[ Upstream commit f15345a377c6ea9c7cc74f079616af8856aff37f ]
Certain GL unit tests for large textures can cause problems with the OOM killer since there is no way to link this memory to a process. This was originally mitigated (but not necessarily eliminated) by limiting the GTT size. The problem is this limit is often too low for many modern games so just make the limit 1/2 of system memory. The OOM accounting needs to be addressed, but we shouldn't prevent common 3D applications from being usable just to potentially mitigate that corner case.
Set default GTT size to max(3G, 1/2 of system ram) by default.
v2: drop previous logic and default to 3/4 of ram
v3: default to half of ram to align with ttm
v4: fix spelling in comment (Kent)
--- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c +14 -6
@@ -1798,18 +1798,26 @@ int amdgpu_ttm_init(struct amdgpu_device *adev)DRM_INFO ("amdgpu: %uM of VRAM memory ready\n" , (unsigned ) (adev->gmc.real_vram_size / (1024 *1024 ))); -/* Compute GTT size, either bsaed on 3/4th the size of RAM size +/* Compute GTT size, either based on 1/2 the size of RAM size * or whatever the user passed on module init */ if (amdgpu_gtt_size ==-1 ) {struct sysinfo si;si_meminfo (&si); - gtt_size =min (max ((AMDGPU_DEFAULT_GTT_SIZE_MB <<20 ), - adev->gmc.mc_vram_size), - ((uint64_t )si.totalram * si.mem_unit *3 /4 )); - } -else +/* Certain GL unit tests for large textures can cause problems +* with the OOM killer since there is no way to link this memory +* to a process. This was originally mitigated (but not necessarily +* eliminated) by limiting the GTT size. The problem is this limit +* is often too low for many modern games so just make the limit 1/2 +* of system memory which aligns with TTM. The OOM accounting needs +* to be addressed, but we shouldn't prevent common 3D applications +* from being usable just to potentially mitigate that corner case. +*/ + gtt_size =max ((AMDGPU_DEFAULT_GTT_SIZE_MB <<20 ), + (u64 )si.totalram * si.mem_unit /2 ); + }else { gtt_size = (uint64_t )amdgpu_gtt_size <<20 ; + }/* Initialize GTT memory pool */ r =amdgpu_gtt_mgr_init (adev, gtt_size);
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 51/53 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH
In reply to Sasha LevinFrom: Leo Savernik <[email protected]>
[ Upstream commit 41f38043f884c66af4114a7109cf540d6222f450 ]
The Micron MTFDKBA2T0TFH device reports the same subsysem NQN for all devices. Add a quick to ignore it.
--- drivers/nvme/host/pci.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/nvme/host/pci.c +2 -0
@@ -3441,6 +3441,8 @@ static const struct pci_device_id nvme_id_table[] = { { PCI_DEVICE(0x1cc1, 0x8201), /* ADATA SX8200PNP 512GB */ .driver_data =NVME_QUIRK_NO_DEEPEST_PS | NVME_QUIRK_IGNORE_DEV_SUBNQN, }, + { PCI_DEVICE(0x1344, 0x5407), /* Micron Technology Inc NVMe SSD */ + .driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN }, { PCI_DEVICE(0x1c5c, 0x1504), /* SK Hynix PC400 */ .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, }, { PCI_DEVICE(0x15b7, 0x2001), /* Sandisk Skyhawk */
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 52/53 gpio: grgpio: Fix device removing
In reply to Sasha LevinFrom: Uwe Kleine-König <[email protected]>
[ Upstream commit c1c2a15c2b5379ea8e44dcdcc298e3de42076ba0 ]
If a platform device's remove callback returns non-zero, the device core emits a warning and still removes the device and calls the devm cleanup callbacks.
So it's not save to not unregister the gpiochip because on the next request to a GPIO the driver accesses kfree()'d memory. Also if an IRQ triggers, the freed memory is accessed.
Instead rely on the GPIO framework to ensure that after gpiochip_remove() all GPIOs are freed and so the corresponding IRQs are unmapped.
This is a preparation for making platform remove callbacks return void.
--- drivers/gpio/gpio-grgpio.c | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-)
drivers/gpio/gpio-grgpio.c +1 -13
@@ -434,25 +434,13 @@ static int grgpio_probe(struct platform_device *ofdev)static int grgpio_remove (struct platform_device *ofdev) {struct grgpio_priv *priv =platform_get_drvdata (ofdev); -int i; -int ret =0 ; - -if (priv->domain) { -for (i =0 ; i <GRGPIO_MAX_NGPIO ; i++) { -if (priv->uirqs[i].refcnt !=0 ) { - ret = -EBUSY ; - goto out; - } - } - }gpiochip_remove (&priv->gc);if (priv->domain)irq_domain_remove (priv->domain); -out: -return ret; +return 0 ; }static const struct of_device_id grgpio_match[] = {
Signature · 1 line
2.35.1
Sasha Levin
maintainerPATCH 53/53 arm: mach-spear: Add missing of_node_put() in time.c
In reply to Sasha LevinFrom: Liang He <[email protected]>
[ Upstream commit 2c629dd2d14fd7f64a553f809eda6d0b3a4f615a ]
In spear_setup_of_timer(), of_find_matching_node() will return a node pointer with refcount incrementd. We should use of_node_put() in each fail path or when it is not used anymore.
--- arch/arm/mach-spear/time.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
arch/arm/mach-spear/time.c +6 -2
@@ -218,13 +218,13 @@ void __init spear_setup_of_timer(void) irq =irq_of_parse_and_map (np,0 );if (!irq) {pr_err ("%s: No irq passed for timer via DT\n" , __func__); -return ; + goto err_put_np; } gpt_base =of_iomap (np,0 );if (!gpt_base) {pr_err ("%s: of iomap failed\n" , __func__); -return ; + goto err_put_np; } gpt_clk =clk_get_sys ("gpt0" ,NULL );
@@ -239,6 +239,8 @@ void __init spear_setup_of_timer(void) goto err_prepare_enable_clk; } +of_node_put (np); +spear_clockevent_init (irq);spear_clocksource_init ();
@@ -248,4 +250,6 @@ void __init spear_setup_of_timer(void)clk_put (gpt_clk); err_iomap:iounmap (gpt_base); +err_put_np: +of_node_put (np); }
Signature · 1 line
2.35.1