ioat: ioat_alloc_ring() failure handling.
Subsystems (43)
Sasha Levin
maintainerPATCH 169/205 drm/radeon: fix bad DMA from INTERRUPT_CNTL2
In reply to Sasha LevinFrom: Sam Bobroff <[email protected]>
[ Upstream commit 62d91dd2851e8ae2ca552f1b090a3575a4edf759 ]
The INTERRUPT_CNTL2 register expects a valid DMA address, but is currently set with a GPU MC address. This can cause problems on systems that detect the resulting DMA read from an invalid address (found on a Power8 guest).
Instead, use the DMA address of the dummy page because it will always be safe.
--- drivers/gpu/drm/radeon/cik.c | 4 ++-- drivers/gpu/drm/radeon/r600.c | 4 ++-- drivers/gpu/drm/radeon/si.c | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-)
drivers/gpu/drm/radeon/cik.c +2 -2
@@ -6969,8 +6969,8 @@ static int cik_irq_init(struct radeon_device *rdev) }/* setup interrupt control */ -/* XXX this should actually be a bus address, not an MC address. same on older asics */ -WREG32 (INTERRUPT_CNTL2 , rdev->ih.gpu_addr >>8 ); +/* set dummy read address to dummy page address */ +WREG32 (INTERRUPT_CNTL2 , rdev->dummy_page.addr >>8 ); interrupt_cntl =RREG32 (INTERRUPT_CNTL );/* IH_DUMMY_RD_OVERRIDE=0 - dummy read disabled with msi, enabled without msi * IH_DUMMY_RD_OVERRIDE=1 - dummy read controlled by IH_DUMMY_RD_EN
drivers/gpu/drm/radeon/r600.c +2 -2
@@ -3696,8 +3696,8 @@ int r600_irq_init(struct radeon_device *rdev) }/* setup interrupt control */ -/* set dummy read address to ring address */ -WREG32 (INTERRUPT_CNTL2 , rdev->ih.gpu_addr >>8 ); +/* set dummy read address to dummy page address */ +WREG32 (INTERRUPT_CNTL2 , rdev->dummy_page.addr >>8 ); interrupt_cntl =RREG32 (INTERRUPT_CNTL );/* IH_DUMMY_RD_OVERRIDE=0 - dummy read disabled with msi, enabled without msi * IH_DUMMY_RD_OVERRIDE=1 - dummy read controlled by IH_DUMMY_RD_EN
drivers/gpu/drm/radeon/si.c +2 -2
@@ -5997,8 +5997,8 @@ static int si_irq_init(struct radeon_device *rdev) }/* setup interrupt control */ -/* set dummy read address to ring address */ -WREG32 (INTERRUPT_CNTL2 , rdev->ih.gpu_addr >>8 ); +/* set dummy read address to dummy page address */ +WREG32 (INTERRUPT_CNTL2 , rdev->dummy_page.addr >>8 ); interrupt_cntl =RREG32 (INTERRUPT_CNTL );/* IH_DUMMY_RD_OVERRIDE=0 - dummy read disabled with msi, enabled without msi * IH_DUMMY_RD_OVERRIDE=1 - dummy read controlled by IH_DUMMY_RD_EN
Signature · 6 lines
2.20.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Sasha Levin
maintainerPATCH 170/205 ASoC: rsnd: fix DALIGN register for SSIU
In reply to Sasha LevinFrom: Nilkanth Ahirrao <[email protected]>
[ Upstream commit ef8e14794308a428b194f8b06ad9ae06b43466e4 ]
The current driver only sets 0x76543210 and 0x67452301 for DALIGN. This doesn’t work well for TDM split and ex-split mode for all SSIU. This patch programs the DALIGN registers based on the SSIU number.
--- sound/soc/sh/rcar/core.c | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-)
sound/soc/sh/rcar/core.c +18 -2
@@ -376,6 +376,17 @@ u32 rsnd_get_adinr_bit(struct rsnd_mod *mod, struct rsnd_dai_stream *io)*/ u32 rsnd_get_dalign (struct rsnd_mod *mod,struct rsnd_dai_stream *io) { +static const u32 dalign_values[8 ][2 ] = { + {0x76543210 ,0x67452301 }, + {0x00000032 ,0x00000023 }, + {0x00007654 ,0x00006745 }, + {0x00000076 ,0x00000067 }, + {0xfedcba98 ,0xefcdab89 }, + {0x000000ba ,0x000000ab }, + {0x0000fedc ,0x0000efcd }, + {0x000000fe ,0x000000ef }, + }; +int id =0 , inv;struct rsnd_mod *ssiu =rsnd_io_to_mod_ssiu (io);struct rsnd_mod *target;struct snd_pcm_runtime *runtime =rsnd_io_to_runtime (io);
@@ -411,13 +422,18 @@ u32 rsnd_get_dalign(struct rsnd_mod *mod, struct rsnd_dai_stream *io) target = cmd ? cmd : ssiu; } +if (mod == ssiu) + id =rsnd_mod_id_sub (mod); +/* Non target mod or non 16bit needs normal DALIGN */ if ((snd_pcm_format_width (runtime->format) !=16 ) || (mod != target)) -return 0x76543210 ; + inv =0 ;/* Target mod needs inverted DALIGN when 16bit */ else -return 0x67452301 ; + inv =1 ; + +return dalign_values[id][inv]; }u32 rsnd_get_busif_shift (struct rsnd_dai_stream *io,struct rsnd_mod *mod)
Signature · 6 lines
2.20.1 _______________________________________________ Alsa-devel mailing list [email protected] https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Sasha Levin
maintainerPATCH 171/205 ice: fix stack leakage
In reply to Sasha LevinFrom: Jesse Brandeburg <[email protected]>
[ Upstream commit 949375de945f7042df2b6488228a1a2b36e69f35 ]
In the case of an invalid virtchannel request the driver would return uninitialized data to the VF from the PF stack which is a bug. Fix by initializing the stack variable earlier in the function before any return paths can be taken.
--- drivers/net/ethernet/intel/ice/ice_virtchnl_pf.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/net/ethernet/intel/ice/ice_virtchnl_pf.c +1 -2
@@ -1873,8 +1873,8 @@ static int ice_vc_get_stats_msg(struct ice_vf *vf, u8 *msg)enum virtchnl_status_code v_ret =VIRTCHNL_STATUS_SUCCESS ;struct virtchnl_queue_select *vqs = (struct virtchnl_queue_select *)msg; +struct ice_eth_stats stats = {0 };struct ice_pf *pf = vf->pf; -struct ice_eth_stats stats;struct ice_vsi *vsi;if (!test_bit (ICE_VF_STATE_ACTIVE , vf->vf_states)) {
@@ -1893,7 +1893,6 @@ static int ice_vc_get_stats_msg(struct ice_vf *vf, u8 *msg) goto error_param; } -memset (&stats,0 ,sizeof (struct ice_eth_stats ));ice_update_eth_stats (vsi); stats = vsi->eth_stats;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 172/205 xdp: Fix cleanup on map free for devmap_hash map type
In reply to Sasha LevinFrom: Toke Høiland-Jørgensen <[email protected]>
[ Upstream commit 071cdecec57fb5d5df78e6a12114ad7bccea5b0e ]
Tetsuo pointed out that it was not only the device unregister hook that was broken for devmap_hash types, it was also cleanup on map free. So better fix this as well.
While we're at it, there's no reason to allocate the netdev_map array for DEVMAP_HASH, so skip that and adjust the cost accordingly.
--- kernel/bpf/devmap.c | 74 ++++++++++++++++++++++++++++----------------- 1 file changed, 46 insertions(+), 28 deletions(-)
kernel/bpf/devmap.c +46 -28
@@ -74,7 +74,7 @@ struct bpf_dtab_netdev {struct bpf_dtab {struct bpf_map map; -struct bpf_dtab_netdev **netdev_map; +struct bpf_dtab_netdev **netdev_map;/* DEVMAP type only */ struct list_head __percpu *flush_list;struct list_head list;
@@ -101,6 +101,12 @@ static struct hlist_head *dev_map_create_hash(unsigned int entries)return hash; } +static inline struct hlist_head *dev_map_index_hash (struct bpf_dtab *dtab, +int idx) +{ +return &dtab->dev_index_head[idx & (dtab->n_buckets -1 )]; +} +static int dev_map_init_map (struct bpf_dtab *dtab,union bpf_attr *attr) {int err, cpu;
@@ -120,8 +126,7 @@ static int dev_map_init_map(struct bpf_dtab *dtab, union bpf_attr *attr)bpf_map_init_from_attr (&dtab->map, attr);/* make sure page count doesn't overflow */ - cost = (u64 ) dtab->map.max_entries *sizeof (struct bpf_dtab_netdev *); - cost +=sizeof (struct list_head ) *num_possible_cpus (); + cost = (u64 )sizeof (struct list_head ) *num_possible_cpus ();if (attr->map_type ==BPF_MAP_TYPE_DEVMAP_HASH ) { dtab->n_buckets =roundup_pow_of_two (dtab->map.max_entries);
@@ -129,6 +134,8 @@ static int dev_map_init_map(struct bpf_dtab *dtab, union bpf_attr *attr)if (!dtab->n_buckets)/* Overflow check */ return -EINVAL ; cost += (u64 )sizeof (struct hlist_head ) * dtab->n_buckets; + }else { + cost += (u64 ) dtab->map.max_entries *sizeof (struct bpf_dtab_netdev *); }/* if map size is larger than memlock limit, reject it */
@@ -143,24 +150,22 @@ static int dev_map_init_map(struct bpf_dtab *dtab, union bpf_attr *attr)for_each_possible_cpu (cpu)INIT_LIST_HEAD (per_cpu_ptr (dtab->flush_list, cpu)); - dtab->netdev_map =bpf_map_area_alloc (dtab->map.max_entries * -sizeof (struct bpf_dtab_netdev *), - dtab->map.numa_node); -if (!dtab->netdev_map) - goto free_percpu; -if (attr->map_type ==BPF_MAP_TYPE_DEVMAP_HASH ) { dtab->dev_index_head =dev_map_create_hash (dtab->n_buckets);if (!dtab->dev_index_head) - goto free_map_area; + goto free_percpu;spin_lock_init (&dtab->index_lock); + }else { + dtab->netdev_map =bpf_map_area_alloc (dtab->map.max_entries * +sizeof (struct bpf_dtab_netdev *), + dtab->map.numa_node); +if (!dtab->netdev_map) + goto free_percpu; }return 0 ; -free_map_area: -bpf_map_area_free (dtab->netdev_map); free_percpu:free_percpu (dtab->flush_list); free_charge:
@@ -228,21 +233,40 @@ static void dev_map_free(struct bpf_map *map)cond_resched (); } -for (i =0 ; i < dtab->map.max_entries; i++) { -struct bpf_dtab_netdev *dev; +if (dtab->map.map_type ==BPF_MAP_TYPE_DEVMAP_HASH ) { +for (i =0 ; i < dtab->n_buckets; i++) { +struct bpf_dtab_netdev *dev; +struct hlist_head *head; +struct hlist_node *next; - dev = dtab->netdev_map[i]; -if (!dev) -continue ; + head =dev_map_index_hash (dtab, i); -free_percpu (dev->bulkq); -dev_put (dev->dev); -kfree (dev); +hlist_for_each_entry_safe (dev, next, head, index_hlist) { +hlist_del_rcu (&dev->index_hlist); +free_percpu (dev->bulkq); +dev_put (dev->dev); +kfree (dev); + } + } + +kfree (dtab->dev_index_head); + }else { +for (i =0 ; i < dtab->map.max_entries; i++) { +struct bpf_dtab_netdev *dev; + + dev = dtab->netdev_map[i]; +if (!dev) +continue ; + +free_percpu (dev->bulkq); +dev_put (dev->dev); +kfree (dev); + } + +bpf_map_area_free (dtab->netdev_map); }free_percpu (dtab->flush_list); -bpf_map_area_free (dtab->netdev_map); -kfree (dtab->dev_index_head);kfree (dtab); }
@@ -263,12 +287,6 @@ static int dev_map_get_next_key(struct bpf_map *map, void *key, void *next_key)return 0 ; } -static inline struct hlist_head *dev_map_index_hash (struct bpf_dtab *dtab, -int idx) -{ -return &dtab->dev_index_head[idx & (dtab->n_buckets -1 )]; -} -struct bpf_dtab_netdev *__dev_map_hash_lookup_elem (struct bpf_map *map,u32 key) { struct bpf_dtab *dtab = container_of(map, struct bpf_dtab, map);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 173/205 ARM: dts: Fix sgx sysconfig register for omap4
In reply to Sasha LevinFrom: Tony Lindgren <[email protected]>
[ Upstream commit 3e5c3c41ae925458150273e2f74ffbf999530c5f ]
Looks like we've had the sgx sysconfig register and revision register always wrong for omap4, including the old platform data. Let's fix the offsets to what the TRM says. Otherwise the sgx module may never idle depending on the state of the real sysconfig register.
--- arch/arm/boot/dts/omap4.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/boot/dts/omap4.dtsi +2 -2
@@ -330,8 +330,8 @@ target-module@56000000 { compatible = "ti,sysc-omap4", "ti,sysc"; - reg = <0x5601fc00 0x4>, - <0x5601fc10 0x4>; + reg = <0x5600fe00 0x4>, + <0x5600fe10 0x4>; reg-names = "rev", "sysc"; ti,sysc-midle = <SYSC_IDLE_FORCE>, <SYSC_IDLE_NO>,
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 174/205 arm64: dts: juno: Fix UART frequency
In reply to Sasha LevinFrom: Andre Przywara <[email protected]>
[ Upstream commit 39a1a8941b27c37f79508426e27a2ec29829d66c ]
Older versions of the Juno *SoC* TRM [1] recommended that the UART clock source should be 7.2738 MHz, whereas the *system* TRM [2] stated a more correct value of 7.3728 MHz. Somehow the wrong value managed to end up in our DT.
Doing a prime factorisation, a modulo divide by 115200 and trying to buy a 7.2738 MHz crystal at your favourite electronics dealer suggest that the old value was actually a typo. The actual UART clock is driven by a PLL, configured via a parameter in some board.txt file in the firmware, which reads 7.37 MHz (sic!).
Fix this to correct the baud rate divisor calculation on the Juno board.
[1] http://infocenter.arm.com/help/topic/com.arm.doc.ddi0515b.b/DDI0515B_b_juno_arm_development_platform_soc_trm.pdf
[2] http://infocenter.arm.com/help/topic/com.arm.doc.100113_0000_07_en/arm_versatile_express_juno_development_platform_(v2m_juno)_technical_reference_manual_100113_0000_07_en.pdf
--- arch/arm64/boot/dts/arm/juno-clocks.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm64/boot/dts/arm/juno-clocks.dtsi +2 -2
@@ -8,10 +8,10 @@ */ / { /* SoC fixed clocks */ - soc_uartclk: refclk7273800hz { + soc_uartclk: refclk7372800hz { compatible = "fixed-clock"; #clock-cells = <0>; - clock-frequency = <7273800>; + clock-frequency = <7372800>; clock-output-names = "juno:uartclk"; };
Signature · 7 lines
2.20.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Sasha Levin
maintainerPATCH 175/205 um: Don't trace irqflags during shutdown
In reply to Sasha LevinFrom: Johannes Berg <[email protected]>
[ Upstream commit 5c1f33e2a03c0b8710b5d910a46f1e1fb0607679 ]
In the main() code, we eventually enable signals just before exec() or exit(), in order to to not have signals pending and delivered *after* the exec().
I've observed SIGSEGV loops at this point, and the reason seems to be the irqflags tracing; this makes sense as the kernel is no longer really functional at this point. Since there's really no reason to use unblock_signals_trace() here (I had just done a global search & replace), use the plain unblock_signals() in this case to avoid going into the no longer functional kernel.
--- arch/um/os-Linux/main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/um/os-Linux/main.c +1 -1
@@ -170,7 +170,7 @@ int __init main(int argc, char **argv, char **envp)* that they won't be delivered after the exec, when * they are definitely not expected. */ -unblock_signals_trace (); +unblock_signals ();os_info ("\n" );/* Reboot */
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 176/205 um: virtio_uml: Disallow modular build
In reply to Sasha LevinFrom: Johannes Berg <[email protected]>
[ Upstream commit bf9f80cf0ccab5f346f7d3cdc445da8fcfe6ce34 ]
This driver *can* be a module, but then its parameters (socket path) are untrusted data from inside the VM, and that isn't allowed. Allow the code to only be built-in to avoid that.
--- arch/um/drivers/Kconfig | 2 +- arch/um/drivers/virtio_uml.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
arch/um/drivers/Kconfig +1 -1
@@ -337,7 +337,7 @@ config UML_NET_SLIRP endmenu config VIRTIO_UML - tristate "UML driver for virtio devices" + bool "UML driver for virtio devices" select VIRTIO help This driver provides support for virtio based paravirtual device
arch/um/drivers/virtio_uml.c +2 -2
@@ -4,12 +4,12 @@* * Copyright(c) 2019 Intel Corporation * -* This module allows virtio devices to be used over a vhost-user socket. +* This driver allows virtio devices to be used over a vhost-user socket. * * Guest devices can be instantiated by kernel module or command line * parameters. One device will be created for each parameter. Syntax: * -* [virtio_uml.]device=<socket>:<virtio_id>[:<platform_id>] +* virtio_uml.device=<socket>:<virtio_id>[:<platform_id>] * where: * <socket> := vhost-user socket path to connect * <virtio_id> := virtio device id (as in virtio_ids.h)
Signature · 7 lines
2.20.1 _______________________________________________ linux-um mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-um
Sasha Levin
maintainerPATCH 177/205 scsi: qla2xxx: fix rports not being mark as lost in sync fabric scan
In reply to Sasha LevinFrom: Martin Wilck <[email protected]>
[ Upstream commit d341e9a8f2cffe4000c610225c629f62c7489c74 ]
In qla2x00_find_all_fabric_devs(), fcport->flags & FCF_LOGIN_NEEDED is a necessary condition for logging into new rports, but not for dropping lost ones.
--- drivers/scsi/qla2xxx/qla_init.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/scsi/qla2xxx/qla_init.c +3 -3
@@ -5891,8 +5891,7 @@ qla2x00_find_all_fabric_devs(scsi_qla_host_t *vha)if (test_bit (LOOP_RESYNC_NEEDED , &vha->dpc_flags))break ; -if ((fcport->flags &FCF_FABRIC_DEVICE ) ==0 || - (fcport->flags &FCF_LOGIN_NEEDED ) ==0 ) +if ((fcport->flags &FCF_FABRIC_DEVICE ) ==0 )continue ;if (fcport->scan_state ==QLA_FCPORT_SCAN ) {
@@ -5915,7 +5914,8 @@ qla2x00_find_all_fabric_devs(scsi_qla_host_t *vha) } } -if (fcport->scan_state ==QLA_FCPORT_FOUND ) +if (fcport->scan_state ==QLA_FCPORT_FOUND && + (fcport->flags &FCF_LOGIN_NEEDED ) !=0 )qla24xx_fcport_handle_login (vha, fcport); }return (rval);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 178/205 scsi: qla2xxx: Fix qla2x00_request_irqs() for MSI
In reply to Sasha LevinFrom: Huacai Chen <[email protected]>
[ Upstream commit 45dc8f2d9c94ed74a5e31e63e9136a19a7e16081 ]
Commit 4fa183455988 ("scsi: qla2xxx: Utilize pci_alloc_irq_vectors/ pci_free_irq_vectors calls.") use pci_alloc_irq_vectors() to replace pci_enable_msi() but it didn't handle the return value correctly. This bug make qla2x00 always fail to setup MSI if MSI-X fail, so fix it.
BTW, improve the log message of return value in qla2x00_request_irqs() to avoid confusion.
--- drivers/scsi/qla2xxx/qla_isr.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/scsi/qla2xxx/qla_isr.c +3 -3
@@ -3625,7 +3625,7 @@ qla2x00_request_irqs(struct qla_hw_data *ha, struct rsp_que *rsp) skip_msix:ql_log (ql_log_info, vha,0x0037 , -"Falling back-to MSI mode -%d.\n" , ret); +"Falling back-to MSI mode -- ret=%d.\n" , ret); if (!IS_QLA24XX(ha) && !IS_QLA2532(ha) && !IS_QLA8432(ha) && !IS_QLA8001(ha) && !IS_P3P_TYPE(ha) && !IS_QLAFX00(ha) &&
@@ -3633,13 +3633,13 @@ qla2x00_request_irqs(struct qla_hw_data *ha, struct rsp_que *rsp) goto skip_msi; ret =pci_alloc_irq_vectors (ha->pdev,1 ,1 ,PCI_IRQ_MSI ); -if (!ret) { +if (ret >0 ) {ql_dbg (ql_dbg_init, vha,0x0038 ,"MSI: Enabled.\n" ); ha->flags.msi_enabled =1 ; }else ql_log (ql_log_warn, vha,0x0039 , -"Falling back-to INTa mode -- %d.\n" , ret); +"Falling back-to INTa mode -- ret=%d.\n" , ret); skip_msi:/* Skip INTx on ISP82xx. */
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 179/205 bpf: Support pre-2.25-binutils objcopy for vmlinux BTF
In reply to Sasha LevinFrom: Stanislav Fomichev <[email protected]>
[ Upstream commit da5fb18225b49b97bb37c51bcbbb2990a507c364 ]
If vmlinux BTF generation fails, but CONFIG_DEBUG_INFO_BTF is set, .BTF section of vmlinux is empty and kernel will prohibit BPF loading and return "in-kernel BTF is malformed".
--dump-section argument to binutils' objcopy was added in version 2.25. When using pre-2.25 binutils, BTF generation silently fails. Convert to --only-section which is present on pre-2.25 binutils.
Documentation/process/changes.rst states that binutils 2.21+ is supported, not sure those standards apply to BPF subsystem.
v2:
* exit and print an error if gen_btf fails (John Fastabend)
v3:
* resend with Andrii's Acked-by/Tested-by tags
--- scripts/link-vmlinux.sh | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
scripts/link-vmlinux.sh +6 -1
@@ -127,7 +127,8 @@ gen_btf() cut -d, -f1 | cut -d' ' -f2) bin_format=$(LANG=C ${OBJDUMP} -f ${1} | grep 'file format' | \ awk '{print $4}') - ${OBJCOPY} --dump-section .BTF=.btf.vmlinux.bin ${1} 2>/dev/null + ${OBJCOPY} --set-section-flags .BTF=alloc -O binary \ + --only-section=.BTF ${1} .btf.vmlinux.bin 2>/dev/null ${OBJCOPY} -I binary -O ${bin_format} -B ${bin_arch} \ --rename-section .data=.BTF .btf.vmlinux.bin ${2} }
@@ -253,6 +254,10 @@ btf_vmlinux_bin_o="" if [ -n "${CONFIG_DEBUG_INFO_BTF}" ]; then if gen_btf .tmp_vmlinux.btf .btf.vmlinux.bin.o ; then btf_vmlinux_bin_o=.btf.vmlinux.bin.o + else + echo >&2 "Failed to generate BTF for vmlinux" + echo >&2 "Try to disable CONFIG_DEBUG_INFO_BTF" + exit 1 fi fi
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 180/205 libbpf: Fix Makefile' libbpf symbol mismatch diagnostic
In reply to Sasha LevinFrom: Andrii Nakryiko <[email protected]>
[ Upstream commit b568405856906ee4d9ba6284fd36f2928653a623 ]
Fix Makefile's diagnostic diff output when there is LIBBPF_API-versioned symbols mismatch.
--- tools/lib/bpf/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/lib/bpf/Makefile +1 -1
@@ -215,7 +215,7 @@ check_abi: $(OUTPUT)libbpf.so "versioned symbols in $^ ($(VERSIONED_SYM_COUNT))." \ "Please make sure all LIBBPF_API symbols are" \ "versioned in $(VERSION_SCRIPT)." >&2; \ - readelf -s --wide $(OUTPUT)libbpf-in.o | \ + readelf -s --wide $(BPF_IN_SHARED) | \ cut -d "@" -f1 | sed 's/_v[0-9]_[0-9]_[0-9].*//' | \ awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$8}'| \ sort -u > $(OUTPUT)libbpf_global_syms.tmp; \
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 181/205 ath9k: use iowrite32 over __raw_writel
In reply to Sasha LevinFrom: Christian Lamparter <[email protected]>
[ Upstream commit 22d0d5ae7a089967e9295a06694aa3e8a812b15e ]
This patch changes the ath9k_pci_owl_loader to use the same iowrite32 memory accessor that ath9k_pci is using to communicate with the PCI(e) chip.
This will fix endian issues that came up during testing with loaned AVM Fritz!Box 7360 (Lantiq MIPS SoCs + AR9287).
--- drivers/net/wireless/ath/ath9k/ath9k_pci_owl_loader.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/wireless/ath/ath9k/ath9k_pci_owl_loader.c +1 -1
@@ -84,7 +84,7 @@ static int ath9k_pci_fixup(struct pci_dev *pdev, const u16 *cal_data, val =swahb32 (val); } -__raw_writel (val, mem + reg); +iowrite32 (val, mem + reg);usleep_range (100 ,120 ); }
Signature · 7 lines
2.20.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Sasha Levin
maintainerPATCH 182/205 Revert "arm64: dts: juno: add dma-ranges property"
In reply to Sasha LevinFrom: Sudeep Holla <[email protected]>
[ Upstream commit 54fb3fe0f211d4729a2551cf9497bd612189af9d ]
This reverts commit 193d00a2b35ee3353813b4006a18131122087205.
Commit 951d48855d86 ("of: Make of_dma_get_range() work on bus nodes") reworked the logic such that of_dma_get_range() works correctly starting from a bus node containing "dma-ranges".
Since on Juno we don't have a SoC level bus node and "dma-ranges" is present only in the root node, we get the following error:
OF: translation of DMA address(0) to CPU address failed node(/sram@2e000000)
OF: translation of DMA address(0) to CPU address failed node(/uart@7ff80000)
...
OF: translation of DMA address(0) to CPU address failed node(/mhu@2b1f0000)
OF: translation of DMA address(0) to CPU address failed node(/iommu@2b600000)
OF: translation of DMA address(0) to CPU address failed node(/iommu@2b600000)
OF: translation of DMA address(0) to CPU address failed node(/iommu@2b600000)
So let's fix it by dropping the "dma-ranges" property for now. This should be fine since it doesn't represent any kind of device-visible restriction; it was only there for completeness, and we've since given in to the assumption that missing "dma-ranges" implies a 1:1 mapping anyway.
We can add it later with a proper SoC bus node and moving all the devices that belong there along with the "dma-ranges" if required.
--- arch/arm64/boot/dts/arm/juno-base.dtsi | 1 - 1 file changed, 1 deletion(-)
arch/arm64/boot/dts/arm/juno-base.dtsi +0 -1
@@ -6,7 +6,6 @@ /* * Devices shared by all Juno boards */ - dma-ranges = <0 0 0 0 0x100 0>; memtimer: timer@2a810000 { compatible = "arm,armv7-timer-mem";
Signature · 7 lines
2.20.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Sasha Levin
maintainerPATCH 183/205 tipc: fix potential memory leak in __tipc_sendmsg()
In reply to Sasha LevinFrom: Tung Nguyen <[email protected]>
[ Upstream commit 2fe97a578d7bad3116a89dc8a6692a51e6fc1d9c ]
When initiating a connection message to a server side, the connection message is cloned and added to the socket write queue. However, if the cloning is failed, only the socket write queue is purged. It causes memory leak because the original connection message is not freed.
This commit fixes it by purging the list of connection message when it cannot be cloned.
--- net/tipc/socket.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
net/tipc/socket.c +3 -1
@@ -1392,8 +1392,10 @@ static int __tipc_sendmsg(struct socket *sock, struct msghdr *m, size_t dlen) rc =tipc_msg_build (hdr, m,0 , dlen, mtu, &pkts);if (unlikely (rc != dlen))return rc; -if (unlikely (syn && !tipc_msg_skb_clone (&pkts, &sk->sk_write_queue))) +if (unlikely (syn && !tipc_msg_skb_clone (&pkts, &sk->sk_write_queue))) { +__skb_queue_purge (&pkts);return -ENOMEM ; + }trace_tipc_sk_sendmsg (sk,skb_peek (&pkts),TIPC_DUMP_SK_SNDQ ," " ); rc =tipc_node_xmit (net, &pkts, dnode, tsk->portid);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 184/205 tipc: fix wrong socket reference counter after tipc_sk_timeout() returns
In reply to Sasha LevinFrom: Tung Nguyen <[email protected]>
[ Upstream commit 91a4a3eb433e4d786420c41f3c08d1d16c605962 ]
When tipc_sk_timeout() is executed but user space is grabbing ownership, this function rearms itself and returns. However, the socket reference counter is not reduced. This causes potential unexpected behavior.
This commit fixes it by calling sock_put() before tipc_sk_timeout() returns in the above-mentioned case.
--- net/tipc/socket.c | 1 + 1 file changed, 1 insertion(+)
net/tipc/socket.c +1 -0
@@ -2683,6 +2683,7 @@ static void tipc_sk_timeout(struct timer_list *t)if (sock_owned_by_user (sk)) {sk_reset_timer (sk, &sk->sk_timer, jiffies +HZ /20 );bh_unlock_sock (sk); +sock_put (sk);return ; }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 185/205 tipc: fix wrong timeout input for tipc_wait_for_cond()
In reply to Sasha LevinFrom: Tung Nguyen <[email protected]>
[ Upstream commit 12db3c8083fcab4270866a88191933f2d9f24f89 ]
In function __tipc_shutdown(), the timeout value passed to tipc_wait_for_cond() is not jiffies.
This commit fixes it by converting that value from milliseconds to jiffies.
--- net/tipc/socket.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/tipc/socket.c +1 -1
@@ -504,7 +504,7 @@ static void __tipc_shutdown(struct socket *sock, int error)struct sock *sk = sock->sk;struct tipc_sock *tsk =tipc_sk (sk);struct net *net =sock_net (sk); -long timeout =CONN_TIMEOUT_DEFAULT ; +long timeout =msecs_to_jiffies (CONN_TIMEOUT_DEFAULT );u32 dnode =tsk_peer_node (tsk);struct sk_buff *skb;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 186/205 bpf: Force .BTF section start to zero when dumping from vmlinux
In reply to Sasha LevinFrom: Stanislav Fomichev <[email protected]>
[ Upstream commit df786c9b947639aedbc7bb44b5dae2a7824af360 ]
While trying to figure out why fentry_fexit selftest doesn't pass for me (old pahole, broken BTF), I found out that my latest patch can break vmlinux .BTF generation. objcopy preserves section start when doing --only-section, so there is a chance (depending on where pahole inserts .BTF section) to have leading empty zeroes. Let's explicitly force section offset to zero.
Before:
$ objcopy --set-section-flags .BTF=alloc -O binary \ --only-section=.BTF vmlinux .btf.vmlinux.bin $ xxd .btf.vmlinux.bin | head -n1 00000000: 0000 0000 0000 0000 0000 0000 0000 0000 ................
After:
$ objcopy --change-section-address .BTF=0 \
--set-section-flags .BTF=alloc -O binary \
--only-section=.BTF vmlinux .btf.vmlinux.bin
$ xxd .btf.vmlinux.bin | head -n1
00000000: 9feb 0100 1800 0000 0000 0000 80e1 1c00 ................
^BTF magicAs part of this change, I'm also dropping '2>/dev/null' from objcopy invocation to be able to catch possible other issues (objcopy doesn't produce any warnings for me anymore, it did before with --dump-section).
--- scripts/link-vmlinux.sh | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
scripts/link-vmlinux.sh +3 -2
@@ -127,8 +127,9 @@ gen_btf() cut -d, -f1 | cut -d' ' -f2) bin_format=$(LANG=C ${OBJDUMP} -f ${1} | grep 'file format' | \ awk '{print $4}') - ${OBJCOPY} --set-section-flags .BTF=alloc -O binary \ - --only-section=.BTF ${1} .btf.vmlinux.bin 2>/dev/null + ${OBJCOPY} --change-section-address .BTF=0 \ + --set-section-flags .BTF=alloc -O binary \ + --only-section=.BTF ${1} .btf.vmlinux.bin ${OBJCOPY} -I binary -O ${bin_format} -B ${bin_arch} \ --rename-section .data=.BTF .btf.vmlinux.bin ${2} }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 187/205 platform/chrome: wilco_ec: fix use after free issue
In reply to Sasha LevinFrom: Wen Yang <[email protected]>
[ Upstream commit 856a0a6e2d09d31fd8f00cc1fc6645196a509d56 ]
This is caused by dereferencing 'dev_data' after put_device() in the telem_device_remove() function.
This patch just moves the put_device() down a bit to avoid this issue.
--- drivers/platform/chrome/wilco_ec/telemetry.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/platform/chrome/wilco_ec/telemetry.c +1 -1
@@ -406,8 +406,8 @@ static int telem_device_remove(struct platform_device *pdev)struct telem_device_data *dev_data =platform_get_drvdata (pdev);cdev_device_del (&dev_data->cdev, &dev_data->dev); -put_device (&dev_data->dev);ida_simple_remove (&telem_ida,MINOR (dev_data->dev.devt)); +put_device (&dev_data->dev);return 0 ; }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 188/205 sch_cake: Add missing NLA policy entry TCA_CAKE_SPLIT_GSO
In reply to Sasha LevinFrom: Victorien Molle <[email protected]>
[ Upstream commit b3c424eb6a1a3c485de64619418a471dee6ce849 ]
This field has never been checked since introduction in mainline kernel
--- net/sched/sch_cake.c | 1 + 1 file changed, 1 insertion(+)
net/sched/sch_cake.c +1 -0
@@ -2184,6 +2184,7 @@ static const struct nla_policy cake_policy[TCA_CAKE_MAX + 1] = { [TCA_CAKE_MPU] = { .type = NLA_U32 }, [TCA_CAKE_INGRESS] = { .type = NLA_U32 }, [TCA_CAKE_ACK_FILTER] = { .type = NLA_U32 }, + [TCA_CAKE_SPLIT_GSO] = { .type = NLA_U32 }, [TCA_CAKE_FWMARK] = { .type = NLA_U32 }, };
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 189/205 powerpc/kasan: Fix boot failure with RELOCATABLE && FSL_BOOKE
In reply to Sasha LevinFrom: Christophe Leroy <[email protected]>
[ Upstream commit 71eb40fc53371bc247c8066ae76ad9e22ae1e18d ]
When enabling CONFIG_RELOCATABLE and CONFIG_KASAN on FSL_BOOKE, the kernel doesn't boot.
relocate_init() requires KASAN early shadow area to be set up because it needs access to the device tree through generic functions.
Call kasan_early_init() before calling relocate_init()
--- arch/powerpc/kernel/head_fsl_booke.S | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/powerpc/kernel/head_fsl_booke.S +3 -3
@@ -238,6 +238,9 @@ set_ivor: bl early_init +#ifdef CONFIG_KASAN + bl kasan_early_init +#endif #ifdef CONFIG_RELOCATABLE mr r3,r30 mr r4,r31
@@ -264,9 +267,6 @@ set_ivor: /* * Decide what sort of machine this is and initialize the MMU. */ -#ifdef CONFIG_KASAN - bl kasan_early_init -#endif mr r3,r30 mr r4,r31 bl machine_init
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 190/205 powerpc/archrandom: fix arch_get_random_seed_int()
In reply to Sasha LevinFrom: Ard Biesheuvel <[email protected]>
[ Upstream commit b6afd1234cf93aa0d71b4be4788c47534905f0be ]
Commit 01c9348c7620ec65
powerpc: Use hardware RNG for arch_get_random_seed_* not arch_get_random_*
updated arch_get_random_[int|long]() to be NOPs, and moved the hardware RNG backing to arch_get_random_seed_[int|long]() instead. However, it failed to take into account that arch_get_random_int() was implemented in terms of arch_get_random_long(), and so we ended up with a version of the former that is essentially a NOP as well.
Fix this by calling arch_get_random_seed_long() from arch_get_random_seed_int() instead.
--- arch/powerpc/include/asm/archrandom.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/powerpc/include/asm/archrandom.h +1 -1
@@ -28,7 +28,7 @@ static inline int arch_get_random_seed_int(unsigned int *v)unsigned long val;int rc; - rc =arch_get_random_long (&val); + rc =arch_get_random_seed_long (&val);if (rc) *v = val;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 191/205 samples/bpf: Fix broken xdp_rxq_info due to map order assumptions
In reply to Sasha LevinFrom: Jesper Dangaard Brouer <[email protected]>
[ Upstream commit edbca120a8cdfa5a5793707e33497aa5185875ca ]
In the days of using bpf_load.c the order in which the 'maps' sections were defines in BPF side (*_kern.c) file, were used by userspace side to identify the map via using the map order as an index. In effect the order-index is created based on the order the maps sections are stored in the ELF-object file, by the LLVM compiler.
This have also carried over in libbpf via API bpf_map__next(NULL, obj) to extract maps in the order libbpf parsed the ELF-object file.
When BTF based maps were introduced a new section type ".maps" were created. I found that the LLVM compiler doesn't create the ".maps" sections in the order they are defined in the C-file. The order in the ELF file is based on the order the map pointer is referenced in the code.
This combination of changes lead to xdp_rxq_info mixing up the map file-descriptors in userspace, resulting in very broken behaviour, but without warning the user.
This patch fix issue by instead using bpf_object__find_map_by_name() to find maps via their names. (Note, this is the ELF name, which can be longer than the name the kernel retains).
--- samples/bpf/xdp_rxq_info_user.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
samples/bpf/xdp_rxq_info_user.c +3 -3
@@ -489,9 +489,9 @@ int main(int argc, char **argv)if (bpf_prog_load_xattr (&prog_load_attr, &obj, &prog_fd))return EXIT_FAIL ; - map =bpf_map__next (NULL , obj); - stats_global_map =bpf_map__next (map, obj); - rx_queue_index_map =bpf_map__next (stats_global_map, obj); + map =bpf_object__find_map_by_name (obj,"config_map" ); + stats_global_map =bpf_object__find_map_by_name (obj,"stats_global_map" ); + rx_queue_index_map =bpf_object__find_map_by_name (obj,"rx_queue_index_map" );if (!map || !stats_global_map || !rx_queue_index_map) {printf ("finding a map in obj file failed\n" );return EXIT_FAIL ;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 192/205 soc: aspeed: Fix snoop_file_poll()'s return type
In reply to Sasha LevinFrom: Luc Van Oostenryck <[email protected]>
[ Upstream commit a4e55ccd4392e70f296d12e81b93c6ca96ee21d5 ]
snoop_file_poll() is defined as returning 'unsigned int' but the .poll method is declared as returning '__poll_t', a bitwise type.
Fix this by using the proper return type and using the EPOLL constants instead of the POLL ones, as required for __poll_t.
--- drivers/soc/aspeed/aspeed-lpc-snoop.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/soc/aspeed/aspeed-lpc-snoop.c +2 -2
@@ -97,13 +97,13 @@ static ssize_t snoop_file_read(struct file *file, char __user *buffer,return ret ? ret : copied; } -static unsigned int snoop_file_poll (struct file *file, +static __poll_t snoop_file_poll (struct file *file,struct poll_table_struct *pt) {struct aspeed_lpc_snoop_channel *chan =snoop_file_to_chan (file);poll_wait (file, &chan->wq, pt); -return !kfifo_is_empty (&chan->fifo) ?POLLIN :0 ; +return !kfifo_is_empty (&chan->fifo) ?EPOLLIN :0 ; }static const struct file_operations snoop_fops = {
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 193/205 block: fix memleak of bio integrity data
In reply to Sasha LevinFrom: Justin Tee <[email protected]>
[ Upstream commit ece841abbed2da71fa10710c687c9ce9efb6bf69 ]
7c20f11680a4 ("bio-integrity: stop abusing bi_end_io") moves bio_integrity_free from bio_uninit() to bio_integrity_verify_fn() and bio_endio(). This way looks wrong because bio may be freed without calling bio_endio(), for example, blk_rq_unprep_clone() is called from dm_mq_queue_rq() when the underlying queue of dm-mpath is busy.
So memory leak of bio integrity data is caused by commit 7c20f11680a4.
Fixes this issue by re-adding bio_integrity_free() to bio_uninit().
Signed-off-by Justin Tee <[email protected]>
Add commit log, and simplify/fix the original patch wroten by Justin.
--- block/bio-integrity.c | 2 +- block/bio.c | 3 +++ block/blk.h | 4 ++++ 3 files changed, 8 insertions(+), 1 deletion(-)
block/bio-integrity.c +1 -1
@@ -87,7 +87,7 @@ EXPORT_SYMBOL(bio_integrity_alloc);* Description: Used to free the integrity portion of a bio. Usually * called from bio_free(). */ -static void bio_integrity_free (struct bio *bio) +void bio_integrity_free (struct bio *bio) {struct bio_integrity_payload *bip =bio_integrity (bio);struct bio_set *bs = bio->bi_pool;
block/bio.c +3 -0
@@ -233,6 +233,9 @@ struct bio_vec *bvec_alloc(gfp_t gfp_mask, int nr, unsigned long *idx,void bio_uninit (struct bio *bio) {bio_disassociate_blkg (bio); + +if (bio_integrity (bio)) +bio_integrity_free (bio); }EXPORT_SYMBOL (bio_uninit);
block/blk.h +4 -0
@@ -122,6 +122,7 @@ static inline void blk_rq_bio_prep(struct request *rq, struct bio *bio,#ifdef CONFIG_BLK_DEV_INTEGRITY void blk_flush_integrity (void );bool __bio_integrity_endio (struct bio *); +void bio_integrity_free (struct bio *bio);static inline bool bio_integrity_endio (struct bio *bio) {if (bio_integrity (bio))
@@ -167,6 +168,9 @@ static inline bool bio_integrity_endio(struct bio *bio) {return true; } +static inline void bio_integrity_free (struct bio *bio) +{ +}#endif /* CONFIG_BLK_DEV_INTEGRITY */ unsigned long blk_rq_timeout (unsigned long timeout);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 194/205 s390/qeth: fix dangling IO buffers after halt/clear
In reply to Sasha LevinFrom: Julian Wiedmann <[email protected]>
[ Upstream commit f9e50b02a99c3ebbaa30690e8d5be28a5c2624eb ]
The cio layer's intparm logic does not align itself well with how qeth manages cmd IOs. When an active IO gets terminated via halt/clear, the corresponding IRQ's intparm does not reflect the cmd buffer but rather the intparm that was passed to ccw_device_halt() / ccw_device_clear(). This behaviour was recently clarified in
commit b91d9e67e50b ("s390/cio: fix intparm documentation").
As a result, qeth_irq() currently doesn't cancel a cmd that was terminated via halt/clear. This primarily causes us to leak card->read_cmd after the qeth device is removed, since our IO path still holds a refcount for this cmd.
For qeth this means that we need to keep track of which IO is pending on a device ('active_cmd'), and use this as the intparm when calling halt/clear. Otherwise qeth_irq() can't match the subsequent IRQ to its cmd buffer.
Since we now keep track of the _expected_ intparm, we can also detect any mismatch; this would constitute a bug somewhere in the lower layers. In this case cancel the active cmd - we effectively "lost" the IRQ and should not expect any further notification for this IO.
--- drivers/s390/net/qeth_core.h | 3 ++ drivers/s390/net/qeth_core_main.c | 71 ++++++++++++++++++++++--------- drivers/s390/net/qeth_core_mpc.h | 14 ------ drivers/s390/net/qeth_l2_main.c | 12 +++--- drivers/s390/net/qeth_l3_main.c | 13 +++--- 5 files changed, 67 insertions(+), 46 deletions(-)
drivers/s390/net/qeth_core.h +3 -0
@@ -620,6 +620,7 @@ struct qeth_ipato {struct qeth_channel {struct ccw_device *ccwdev; +struct qeth_cmd_buffer *active_cmd;enum qeth_channel_states state;atomic_t irq_pending; };
@@ -1024,6 +1025,8 @@ int qeth_do_run_thread(struct qeth_card *, unsigned long);void qeth_clear_thread_start_bit (struct qeth_card *,unsigned long );void qeth_clear_thread_running_bit (struct qeth_card *,unsigned long );int qeth_core_hardsetup_card (struct qeth_card *card,bool *carrier_ok); +int qeth_stop_channel (struct qeth_channel *channel); +void qeth_print_status_message (struct qeth_card *);int qeth_init_qdio_queues (struct qeth_card *); int qeth_send_ipa_cmd(struct qeth_card *, struct qeth_cmd_buffer *,
drivers/s390/net/qeth_core_main.c +51 -20
135 lines not on this page · raw message
drivers/s390/net/qeth_core_mpc.h +0 -14
@@ -28,20 +28,6 @@ extern unsigned char IPA_PDU_HEADER[];#define QETH_TIMEOUT (10 * HZ)#define QETH_IPA_TIMEOUT (45 * HZ) -#define QETH_CLEAR_CHANNEL_PARM -10 -#define QETH_HALT_CHANNEL_PARM -11 - -static inline bool qeth_intparm_is_iob (unsigned long intparm) -{ -switch (intparm) { -case QETH_CLEAR_CHANNEL_PARM : -case QETH_HALT_CHANNEL_PARM : -case 0 : -return false; - } -return true; -} -/*****************************************************************************/ /* IP Assist related definitions */ /*****************************************************************************/
drivers/s390/net/qeth_l2_main.c +6 -6
@@ -877,9 +877,9 @@ static int qeth_l2_set_online(struct ccwgroup_device *gdev) out_remove:qeth_l2_stop_card (card); -ccw_device_set_offline (CARD_DDEV (card)); -ccw_device_set_offline (CARD_WDEV (card)); -ccw_device_set_offline (CARD_RDEV (card)); +qeth_stop_channel (&card->data); +qeth_stop_channel (&card->write); +qeth_stop_channel (&card->read);qdio_free (CARD_DDEV (card));mutex_unlock (&card->conf_mutex);
@@ -910,9 +910,9 @@ static int __qeth_l2_set_offline(struct ccwgroup_device *cgdev,rtnl_unlock ();qeth_l2_stop_card (card); - rc =ccw_device_set_offline (CARD_DDEV (card)); - rc2 =ccw_device_set_offline (CARD_WDEV (card)); - rc3 =ccw_device_set_offline (CARD_RDEV (card)); + rc =qeth_stop_channel (&card->data); + rc2 =qeth_stop_channel (&card->write); + rc3 =qeth_stop_channel (&card->read);if (!rc) rc = (rc2) ? rc2 : rc3;if (rc)
drivers/s390/net/qeth_l3_main.c +7 -6
@@ -2383,9 +2383,9 @@ static int qeth_l3_set_online(struct ccwgroup_device *gdev)return 0 ; out_remove:qeth_l3_stop_card (card); -ccw_device_set_offline (CARD_DDEV (card)); -ccw_device_set_offline (CARD_WDEV (card)); -ccw_device_set_offline (CARD_RDEV (card)); +qeth_stop_channel (&card->data); +qeth_stop_channel (&card->write); +qeth_stop_channel (&card->read);qdio_free (CARD_DDEV (card));mutex_unlock (&card->conf_mutex);
@@ -2421,9 +2421,10 @@ static int __qeth_l3_set_offline(struct ccwgroup_device *cgdev,call_netdevice_notifiers (NETDEV_REBOOT , card->dev);rtnl_unlock (); } - rc =ccw_device_set_offline (CARD_DDEV (card)); - rc2 =ccw_device_set_offline (CARD_WDEV (card)); - rc3 =ccw_device_set_offline (CARD_RDEV (card)); + + rc =qeth_stop_channel (&card->data); + rc2 =qeth_stop_channel (&card->write); + rc3 =qeth_stop_channel (&card->read);if (!rc) rc = (rc2) ? rc2 : rc3;if (rc)
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 195/205 net/mlx5e: Fix free peer_flow when refcount is 0
In reply to Sasha LevinFrom: Roi Dayan <[email protected]>
[ Upstream commit eb252c3a24fc5856fa62140c2f8269ddce6ce4e5 ]
It could be neigh update flow took a refcount on peer flow so sometimes we cannot release peer flow even if parent flow is being freed now.
--- drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/net/ethernet/mellanox/mlx5/core/en_tc.c +5 -2
@@ -1615,8 +1615,11 @@ static void __mlx5e_tc_del_fdb_peer_flow(struct mlx5e_tc_flow *flow)flow_flag_clear (flow,DUP ); -mlx5e_tc_del_fdb_flow (flow->peer_flow->priv, flow->peer_flow); -kfree (flow->peer_flow); +if (refcount_dec_and_test (&flow->peer_flow->refcnt)) { +mlx5e_tc_del_fdb_flow (flow->peer_flow->priv, flow->peer_flow); +kfree (flow->peer_flow); + } + flow->peer_flow =NULL ; }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 196/205 ARM: 8943/1: Fix topology setup in case of CPU hotplug for CONFIG_SCHED_MC
In reply to Sasha LevinFrom: Dietmar Eggemann <[email protected]>
[ Upstream commit ff98a5f624d2910de050f1fc7f2a32769da86b51 ]
Commit ca74b316df96 ("arm: Use common cpu_topology structure and functions.") changed cpu_coregroup_mask() from the ARM32 specific implementation in arch/arm/include/asm/topology.h to the one shared with ARM64 and RISCV in drivers/base/arch_topology.c.
Currently on ARM32 (TC2 w/ CONFIG_SCHED_MC) the task scheduler setup code (w/ CONFIG_SCHED_DEBUG) shows this during CPU hotplug:
ERROR: groups don't span domain->span
It happens to CPUs of the cluster of the CPU which gets hot-plugged out on scheduler domain MC.
Turns out that the shared cpu_coregroup_mask() requires that the hot-plugged CPU is removed from the core_sibling mask via remove_cpu_topology(). Otherwise the 'is core_sibling subset of cpumask_of_node()' doesn't work. In this case the task scheduler has to deal with cpumask_of_node instead of core_sibling which is wrong on scheduler domain MC.
e.g. CPU3 hot-plugged out on TC2 [cluster0: 0,3-4 cluster1: 1-2]:
cpu_coregroup_mask(): CPU3 cpumask_of_node=0-2,4 core_sibling=0,3-4
^
should be:
cpu_coregroup_mask(): CPU3 cpumask_of_node=0-2,4 core_sibling=0,4
Add remove_cpu_topology() to __cpu_disable() to remove the CPU from the topology masks in case of a CPU hotplug out operation.
At the same time tweak store_cpu_topology() slightly so it will call update_siblings_masks() in case of CPU hotplug in operation via secondary_start_kernel()->smp_store_cpu_info().
This aligns the ARM32 implementation with the ARM64 one.
Guarding remove_cpu_topology() with CONFIG_GENERIC_ARCH_TOPOLOGY is necessary since some Arm32 defconfigs (aspeed_g5_defconfig, milbeaut_m10v_defconfig, spear13xx_defconfig) specify an explicit
# CONFIG_ARM_CPU_TOPOLOGY is not set
w/ ./arch/arm/Kconfig: select GENERIC_ARCH_TOPOLOGY if ARM_CPU_TOPOLOGY
--- arch/arm/kernel/smp.c | 4 ++++ arch/arm/kernel/topology.c | 10 +++++----- 2 files changed, 9 insertions(+), 5 deletions(-)
arch/arm/kernel/smp.c +4 -0
@@ -240,6 +240,10 @@ int __cpu_disable(void)if (ret)return ret; +#ifdef CONFIG_GENERIC_ARCH_TOPOLOGY +remove_cpu_topology (cpu); +#endif +/* * Take this CPU offline. Once we clear this, we can't return, * and we must not schedule until we're ready to give up the cpu.
arch/arm/kernel/topology.c +5 -5
@@ -196,9 +196,8 @@ void store_cpu_topology(unsigned int cpuid)struct cpu_topology *cpuid_topo = &cpu_topology[cpuid];unsigned int mpidr; -/* If the cpu topology has been already set, just return */ -if (cpuid_topo->core_id !=-1 ) -return ; +if (cpuid_topo->package_id !=-1 ) + goto topology_populated; mpidr =read_cpuid_mpidr ();
@@ -231,14 +230,15 @@ void store_cpu_topology(unsigned int cpuid) cpuid_topo->package_id =-1 ; } -update_siblings_masks (cpuid); -update_cpu_capacity (cpuid);pr_info ("CPU%u: thread %d, cpu %d, socket %d, mpidr %x\n" , cpuid, cpu_topology[cpuid].thread_id, cpu_topology[cpuid].core_id, cpu_topology[cpuid].package_id, mpidr); + +topology_populated: +update_siblings_masks (cpuid); }static inline int cpu_corepower_flags (void )
Signature · 7 lines
2.20.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Sasha Levin
maintainerPATCH 197/205 net-sysfs: Call dev_hold always in netdev_queue_add_kobject
In reply to Sasha LevinFrom: Jouni Hogander <[email protected]>
[ Upstream commit e0b60903b434a7ee21ba8d8659f207ed84101e89 ]
Dev_hold has to be called always in netdev_queue_add_kobject. Otherwise usage count drops below 0 in case of failure in kobject_init_and_add.
--- net/core/net-sysfs.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
net/core/net-sysfs.c +5 -2
@@ -1462,14 +1462,17 @@ static int netdev_queue_add_kobject(struct net_device *dev, int index)struct kobject *kobj = &queue->kobj;int error =0 ; +/* Kobject_put later will trigger netdev_queue_release call +* which decreases dev refcount: Take that reference here +*/ +dev_hold (queue->dev); + kobj->kset = dev->queues_kset; error =kobject_init_and_add (kobj, &netdev_queue_ktype,NULL ,"tx-%u" , index);if (error) goto err; -dev_hold (queue->dev); -#ifdef CONFIG_BQL error =sysfs_create_group (kobj, &dql_group);if (error)
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 198/205 NFSD fixing possible null pointer derefering in copy offload
In reply to Sasha LevinFrom: Olga Kornievskaia <[email protected]>
[ Upstream commit 18f428d4e2f7eff162d80b2b21689496c4e82afd ]
Static checker revealed possible error path leading to possible NULL pointer dereferencing.
--- fs/nfsd/nfs4proc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/nfsd/nfs4proc.c +2 -1
@@ -1298,7 +1298,8 @@ nfsd4_copy(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate, out:return status; out_err: -cleanup_async_copy (async_copy); +if (async_copy) +cleanup_async_copy (async_copy); goto out; }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 199/205 nfsd: depend on CRYPTO_MD5 for legacy client tracking
In reply to Sasha LevinFrom: Patrick Steinhardt <[email protected]>
[ Upstream commit 38a2204f5298620e8a1c3b1dc7b831425106dbc0 ]
The legacy client tracking infrastructure of nfsd makes use of MD5 to derive a client's recovery directory name. As the nfsd module doesn't declare any dependency on CRYPTO_MD5, though, it may fail to allocate the hash if the kernel was compiled without it. As a result, generation of client recovery directories will fail with the following error:
NFSD: unable to generate recoverydir name
The explicit dependency on CRYPTO_MD5 was removed as redundant back in 6aaa67b5f3b9 (NFSD: Remove redundant "select" clauses in fs/Kconfig 2008-02-11) as it was already implicitly selected via RPCSEC_GSS_KRB5. This broke when RPCSEC_GSS_KRB5 was made optional for NFSv4 in commit df486a25900f (NFS: Fix the selection of security flavours in Kconfig) at a later point.
Fix the issue by adding back an explicit dependency on CRYPTO_MD5.
--- fs/nfsd/Kconfig | 1 + 1 file changed, 1 insertion(+)
fs/nfsd/Kconfig +1 -0
@@ -73,6 +73,7 @@ config NFSD_V4 select NFSD_V3 select FS_POSIX_ACL select SUNRPC_GSS + select CRYPTO_MD5 select CRYPTO_SHA256 select GRACE_PERIOD help
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 200/205 scsi: ufs: Give an unique ID to each ufs-bsg
In reply to Sasha LevinFrom: Can Guo <[email protected]>
[ Upstream commit 8c850a0296004409e7bcb9464712fb2807da656a ]
Considering there can be multiple UFS hosts in SoC, give each ufs-bsg an unique ID by appending the scsi host number to its device name.
--- drivers/scsi/ufs/ufs_bsg.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/scsi/ufs/ufs_bsg.c +1 -1
@@ -202,7 +202,7 @@ int ufs_bsg_probe(struct ufs_hba *hba) bsg_dev->parent =get_device (parent); bsg_dev->release = ufs_bsg_node_release; -dev_set_name (bsg_dev,"ufs-bsg" ); +dev_set_name (bsg_dev,"ufs-bsg%u" , shost->host_no); ret =device_add (bsg_dev);if (ret)
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 201/205 tipc: fix potential hanging after b/rcast changing
In reply to Sasha LevinFrom: Tuong Lien <[email protected]>
[ Upstream commit dca4a17d24ee9d878836ce5eb8dc25be1ffa5729 ]
In commit c55c8edafa91 ("tipc: smooth change between replicast and broadcast"), we allow instant switching between replicast and broadcast by sending a dummy 'SYN' packet on the last used link to synchronize packets on the links. The 'SYN' message is an object of link congestion also, so if that happens, a 'SOCK_WAKEUP' will be scheduled to be sent back to the socket...
However, in that commit, we simply use the same socket 'cong_link_cnt' counter for both the 'SYN' & normal payload message sending. Therefore, if both the replicast & broadcast links are congested, the counter will be not updated correctly but overwritten by the latter congestion. Later on, when the 'SOCK_WAKEUP' messages are processed, the counter is reduced one by one and eventually overflowed. Consequently, further activities on the socket will only wait for the false congestion signal to disappear but never been met.
Because sending the 'SYN' message is vital for the mechanism, it should be done anyway. This commit fixes the issue by marking the message with an error code e.g. 'TIPC_ERR_NO_PORT', so its sending should not face a link congestion, there is no need to touch the socket 'cong_link_cnt' either. In addition, in the event of any error (e.g. -ENOBUFS), we will purge the entire payload message queue and make a return immediately.
--- net/tipc/bcast.c | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-)
net/tipc/bcast.c +15 -9
@@ -305,17 +305,17 @@ static int tipc_rcast_xmit(struct net *net, struct sk_buff_head *pkts,* @skb: socket buffer to copy * @method: send method to be used * @dests: destination nodes for message. -* @cong_link_cnt: returns number of encountered congested destination links * Returns 0 if success, otherwise errno */ static int tipc_mcast_send_sync (struct net *net,struct sk_buff *skb,struct tipc_mc_method *method, -struct tipc_nlist *dests, -u16 *cong_link_cnt) +struct tipc_nlist *dests) {struct tipc_msg *hdr, *_hdr;struct sk_buff_head tmpq;struct sk_buff *_skb; +u16 cong_link_cnt; +int rc =0 ;/* Is a cluster supporting with new capabilities ? */ if (!(tipc_net (net)->capabilities &TIPC_MCAST_RBCTL ))
@@ -343,18 +343,19 @@ static int tipc_mcast_send_sync(struct net *net, struct sk_buff *skb, _hdr =buf_msg (_skb);msg_set_size (_hdr,MCAST_H_SIZE );msg_set_is_rcast (_hdr, !msg_is_rcast (hdr)); +msg_set_errcode (_hdr,TIPC_ERR_NO_PORT );__skb_queue_head_init (&tmpq);__skb_queue_tail (&tmpq, _skb);if (method->rcast) -tipc_bcast_xmit (net, &tmpq, cong_link_cnt); + rc =tipc_bcast_xmit (net, &tmpq, &cong_link_cnt);else -tipc_rcast_xmit (net, &tmpq, dests, cong_link_cnt); + rc =tipc_rcast_xmit (net, &tmpq, dests, &cong_link_cnt);/* This queue should normally be empty by now */ __skb_queue_purge (&tmpq); -return 0 ; +return rc; }/* tipc_mcast_xmit - deliver message to indicated destination nodes
@@ -396,9 +397,14 @@ int tipc_mcast_xmit(struct net *net, struct sk_buff_head *pkts,msg_set_is_rcast (hdr, method->rcast);/* Switch method ? */ -if (rcast != method->rcast) -tipc_mcast_send_sync (net, skb, method, - dests, cong_link_cnt); +if (rcast != method->rcast) { + rc =tipc_mcast_send_sync (net, skb, method, dests); +if (unlikely (rc)) { +pr_err ("Unable to send SYN: method %d, rc %d\n" , + rcast, rc); + goto exit; + } + }if (method->rcast) rc =tipc_rcast_xmit (net, pkts, dests, cong_link_cnt);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 202/205 tipc: fix retrans failure due to wrong destination
In reply to Sasha LevinFrom: Tuong Lien <[email protected]>
[ Upstream commit abc9b4e0549b93fdaff56e9532bc49a2d7b04955 ]
When a user message is sent, TIPC will check if the socket has faced a congestion at link layer. If that happens, it will make a sleep to wait for the congestion to disappear. This leaves a gap for other users to take over the socket (e.g. multi threads) since the socket is released as well. Also, in case of connectionless (e.g. SOCK_RDM), user is free to send messages to various destinations (e.g. via 'sendto()'), then the socket's preformatted header has to be updated correspondingly prior to the actual payload message building.
Unfortunately, the latter action is done before the first action which causes a condition issue that the destination of a certain message can be modified incorrectly in the middle, leading to wrong destination when that message is built. Consequently, when the message is sent to the link layer, it gets stuck there forever because the peer node will simply reject it. After a number of retransmission attempts, the link is eventually taken down and the retransmission failure is reported.
This commit fixes the problem by rearranging the order of actions to prevent the race condition from occurring, so the message building is 'atomic' and its header will not be modified by anyone.
--- net/tipc/socket.c | 32 ++++++++++++++++++-------------- 1 file changed, 18 insertions(+), 14 deletions(-)
net/tipc/socket.c +18 -14
@@ -1306,8 +1306,8 @@ static int __tipc_sendmsg(struct socket *sock, struct msghdr *m, size_t dlen)struct tipc_msg *hdr = &tsk->phdr;struct tipc_name_seq *seq;struct sk_buff_head pkts; -u32 dport, dnode =0 ; -u32 type, inst; +u32 dport =0 , dnode =0 ; +u32 type =0 , inst =0 ;int mtu, rc;if (unlikely (dlen >TIPC_MAX_USER_MSG_SIZE ))
@@ -1360,23 +1360,11 @@ static int __tipc_sendmsg(struct socket *sock, struct msghdr *m, size_t dlen) type = dest->addr.name.name.type; inst = dest->addr.name.name.instance; dnode = dest->addr.name.domain; -msg_set_type (hdr,TIPC_NAMED_MSG ); -msg_set_hdr_sz (hdr,NAMED_H_SIZE ); -msg_set_nametype (hdr, type); -msg_set_nameinst (hdr, inst); -msg_set_lookup_scope (hdr,tipc_node2scope (dnode)); dport =tipc_nametbl_translate (net, type, inst, &dnode); -msg_set_destnode (hdr, dnode); -msg_set_destport (hdr, dport);if (unlikely (!dport && !dnode))return -EHOSTUNREACH ; }else if (dest->addrtype ==TIPC_ADDR_ID ) { dnode = dest->addr.id.node; -msg_set_type (hdr,TIPC_DIRECT_MSG ); -msg_set_lookup_scope (hdr,0 ); -msg_set_destnode (hdr, dnode); -msg_set_destport (hdr, dest->addr.id.ref); -msg_set_hdr_sz (hdr,BASIC_H_SIZE ); }else {return -EINVAL ; }
@@ -1387,6 +1375,22 @@ static int __tipc_sendmsg(struct socket *sock, struct msghdr *m, size_t dlen)if (unlikely (rc))return rc; +if (dest->addrtype ==TIPC_ADDR_NAME ) { +msg_set_type (hdr,TIPC_NAMED_MSG ); +msg_set_hdr_sz (hdr,NAMED_H_SIZE ); +msg_set_nametype (hdr, type); +msg_set_nameinst (hdr, inst); +msg_set_lookup_scope (hdr,tipc_node2scope (dnode)); +msg_set_destnode (hdr, dnode); +msg_set_destport (hdr, dport); + }else {/* TIPC_ADDR_ID */ +msg_set_type (hdr,TIPC_DIRECT_MSG ); +msg_set_lookup_scope (hdr,0 ); +msg_set_destnode (hdr, dnode); +msg_set_destport (hdr, dest->addr.id.ref); +msg_set_hdr_sz (hdr,BASIC_H_SIZE ); + } +__skb_queue_head_init (&pkts); mtu =tipc_node_get_mtu (net, dnode, tsk->portid); rc =tipc_msg_build (hdr, m,0 , dlen, mtu, &pkts);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 203/205 gpio: aspeed: avoid return type warning
In reply to Sasha LevinFrom: Arnd Bergmann <[email protected]>
[ Upstream commit 11e299de3aced4ea23a9fb1fef6c983c8d516302 ]
gcc has a hard time tracking whether BUG_ON(1) ends execution or not:
drivers/gpio/gpio-aspeed-sgpio.c: In function 'bank_reg':drivers/gpio/gpio-aspeed-sgpio.c:112:1: error: control reaches end of non-void function [-Werror=return-type]
Use the simpler BUG() that gcc knows cannot continue.
--- drivers/gpio/sgpio-aspeed.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpio/sgpio-aspeed.c +1 -1
@@ -107,7 +107,7 @@ static void __iomem *bank_reg(struct aspeed_sgpio *gpio,return gpio->base + bank->irq_regs +GPIO_IRQ_STATUS ;default :/* acturally if code runs to here, it's an error case */ -BUG_ON (1 ); +BUG (); } }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 204/205 scsi: mpt3sas: Fix double free in attach error handling
In reply to Sasha LevinFrom: Dan Carpenter <[email protected]>
[ Upstream commit ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb ]
The caller also calls _base_release_memory_pools() on error so it leads to a number of double frees:
drivers/scsi/mpt3sas/mpt3sas_base.c:7207 mpt3sas_base_attach() warn: 'ioc->chain_dma_pool' double freed drivers/scsi/mpt3sas/mpt3sas_base.c:7207 mpt3sas_base_attach() warn: 'ioc->hpr_lookup' double freed drivers/scsi/mpt3sas/mpt3sas_base.c:7207 mpt3sas_base_attach() warn: 'ioc->internal_lookup' double freed drivers/scsi/mpt3sas/mpt3sas_base.c:7207 mpt3sas_base_attach() warn: 'ioc->pcie_sgl_dma_pool' double freed drivers/scsi/mpt3sas/mpt3sas_base.c:7207 mpt3sas_base_attach() warn: 'ioc->reply_dma_pool' double freed drivers/scsi/mpt3sas/mpt3sas_base.c:7207 mpt3sas_base_attach() warn: 'ioc->reply_free_dma_pool' double freed drivers/scsi/mpt3sas/mpt3sas_base.c:7207 mpt3sas_base_attach() warn: 'ioc->reply_post_free_array_dma_pool' double freed drivers/scsi/mpt3sas/mpt3sas_base.c:7207 mpt3sas_base_attach() warn: 'ioc->reply_post_free_dma_pool' double freed drivers/scsi/mpt3sas/mpt3sas_base.c:7207 mpt3sas_base_attach() warn: 'ioc->sense_dma_pool' double freed
--- drivers/scsi/mpt3sas/mpt3sas_base.c | 1 - 1 file changed, 1 deletion(-)
drivers/scsi/mpt3sas/mpt3sas_base.c +0 -1
@@ -5234,7 +5234,6 @@ _base_allocate_memory_pools(struct MPT3SAS_ADAPTER *ioc) &ct->chain_buffer_dma);if (!ct->chain_buffer) {ioc_err (ioc,"chain_lookup: pci_pool_alloc failed\n" ); -_base_release_memory_pools (ioc); goto out; } }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 205/205 phy/rockchip: inno-hdmi: round clock rate down to closest 1000 Hz
In reply to Sasha LevinFrom: Jonas Karlman <[email protected]>
[ Upstream commit 4f510aa10468954b1da4e94689c38ac6ea8d3627 ]
Commit 287422a95fe2 ("drm/rockchip: Round up _before_ giving to the clock framework") changed what rate clk_round_rate() is called with, an additional 999 Hz added to the requsted mode clock. This has caused a regression on RK3328 and presumably also on RK3228 because the inno-hdmi-phy clock requires an exact match of the requested rate in the pre pll config table.
When an exact match is not found the parent clock rate (24MHz) is returned to the clk_round_rate() caller. This cause wrong pixel clock to be used and result in no-signal when configuring a mode on RK3328.
Fix this by rounding the rate down to closest 1000 Hz in round_rate func, this allows an exact match to be found in pre pll config table.
--- drivers/phy/rockchip/phy-rockchip-inno-hdmi.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/phy/rockchip/phy-rockchip-inno-hdmi.c +4 -0
@@ -603,6 +603,8 @@ static long inno_hdmi_phy_rk3228_clk_round_rate(struct clk_hw *hw, {const struct pre_pll_config *cfg = pre_pll_cfg_table; + rate = (rate /1000 ) *1000 ; +for (; cfg->pixclock !=0 ; cfg++)if (cfg->pixclock == rate && !cfg->fracdiv)break ;
@@ -755,6 +757,8 @@ static long inno_hdmi_phy_rk3328_clk_round_rate(struct clk_hw *hw, {const struct pre_pll_config *cfg = pre_pll_cfg_table; + rate = (rate /1000 ) *1000 ; +for (; cfg->pixclock !=0 ; cfg++)if (cfg->pixclock == rate)break ;
Signature · 1 line
2.20.1