7.1.5-rc1 review
Subsystems (15)
Greg Kroah-Hartman
maintainerPATCH 115/2077 watchdog: sama5d4_wdt: Fix WDDIS detection on SAM9X60 and SAMA7G5
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Balakrishnan Sambath <[email protected]>
[ Upstream commit e8bc610b14a99d24b0916635102cc52ba41def9b ]
The driver hardcoded AT91_WDT_WDDIS (bit 15) in wdt_enabled and the probe initial state readout. SAM9X60 and SAMA7G5 use bit 12 (AT91_SAM9X60_WDDIS), causing incorrect WDDIS detection.
Introduce a per-device wddis_mask field to select the correct WDDIS bit based on the compatible string.
--- drivers/watchdog/sama5d4_wdt.c | 48 +++++++++++++++------------------- 1 file changed, 21 insertions(+), 27 deletions(-)
drivers/watchdog/sama5d4_wdt.c +21 -27
@@ -30,6 +30,7 @@ struct sama5d4_wdt {void __iomem *reg_base;u32 mr;u32 ir; +u32 wddis_mask;unsigned long last_ping;bool need_irq;bool sam9x60_support;
@@ -48,7 +49,10 @@ MODULE_PARM_DESC(nowayout,"Watchdog cannot be stopped once started (default=" __MODULE_STRING(WATCHDOG_NOWAYOUT) ")"); -#define wdt_enabled (!(wdt->mr & AT91_WDT_WDDIS)) +static inline bool wdt_enabled (struct sama5d4_wdt *wdt) +{ +return !(wdt->mr & wdt->wddis_mask); +}#define wdt_read (wdt, field) \ readl_relaxed((wdt)->reg_base + (field))
@@ -81,12 +85,9 @@ static int sama5d4_wdt_start(struct watchdog_device *wdd) {struct sama5d4_wdt *wdt =watchdog_get_drvdata (wdd); -if (wdt->sam9x60_support) { +if (wdt->sam9x60_support)writel_relaxed (wdt->ir, wdt->reg_base +AT91_SAM9X60_IER ); - wdt->mr &= ~AT91_SAM9X60_WDDIS ; - }else { - wdt->mr &= ~AT91_WDT_WDDIS ; - } + wdt->mr &= ~wdt->wddis_mask;wdt_write (wdt,AT91_WDT_MR , wdt->mr);return 0 ;
@@ -96,12 +97,9 @@ static int sama5d4_wdt_stop(struct watchdog_device *wdd) {struct sama5d4_wdt *wdt =watchdog_get_drvdata (wdd); -if (wdt->sam9x60_support) { +if (wdt->sam9x60_support)writel_relaxed (wdt->ir, wdt->reg_base +AT91_SAM9X60_IDR ); - wdt->mr |=AT91_SAM9X60_WDDIS ; - }else { - wdt->mr |=AT91_WDT_WDDIS ; - } + wdt->mr |= wdt->wddis_mask;wdt_write (wdt,AT91_WDT_MR , wdt->mr);return 0 ;
@@ -117,7 +115,7 @@ static int sama5d4_wdt_ping(struct watchdog_device *wdd) }static int sama5d4_wdt_set_timeout (struct watchdog_device *wdd, -unsigned int timeout) +unsigned int timeout) {struct sama5d4_wdt *wdt =watchdog_get_drvdata (wdd);u32 value =WDT_SEC2TICKS (timeout);
@@ -140,8 +138,8 @@ static int sama5d4_wdt_set_timeout(struct watchdog_device *wdd,* If the watchdog is enabled, then the timeout can be updated. Else, * wait that the user enables it. */ -if (wdt_enabled) -wdt_write (wdt,AT91_WDT_MR , wdt->mr & ~AT91_WDT_WDDIS ); +if (wdt_enabled (wdt)) +wdt_write (wdt,AT91_WDT_MR , wdt->mr & ~wdt->wddis_mask); wdd->timeout = timeout;
@@ -184,10 +182,7 @@ static int of_sama5d4_wdt_init(struct device_node *np, struct sama5d4_wdt *wdt) {const char *tmp; -if (wdt->sam9x60_support) - wdt->mr =AT91_SAM9X60_WDDIS ; -else - wdt->mr =AT91_WDT_WDDIS ; + wdt->mr = wdt->wddis_mask;if (!of_property_read_string (np,"atmel,watchdog-type" , &tmp) && !strcmp (tmp,"software" ))
@@ -213,15 +208,11 @@ static int sama5d4_wdt_init(struct sama5d4_wdt *wdt)* If the watchdog is already running, we can safely update it. * Else, we have to disable it properly. */ -if (!wdt_enabled) { +if (!wdt_enabled (wdt)) { reg =wdt_read (wdt,AT91_WDT_MR ); -if (wdt->sam9x60_support && (!(reg &AT91_SAM9X60_WDDIS ))) -wdt_write_nosleep (wdt,AT91_WDT_MR , - reg |AT91_SAM9X60_WDDIS ); -else if (!wdt->sam9x60_support && - (!(reg &AT91_WDT_WDDIS ))) +if (!(reg & wdt->wddis_mask))wdt_write_nosleep (wdt,AT91_WDT_MR , - reg |AT91_WDT_WDDIS ); + reg | wdt->wddis_mask); }if (wdt->sam9x60_support) {
@@ -273,6 +264,9 @@ static int sama5d4_wdt_probe(struct platform_device *pdev) of_device_is_compatible(dev->of_node, "microchip,sama7g5-wdt")) wdt->sam9x60_support = true; + wdt->wddis_mask = wdt->sam9x60_support ?AT91_SAM9X60_WDDIS + :AT91_WDT_WDDIS ; +watchdog_set_drvdata (wdd, wdt); regs =devm_platform_ioremap_resource (pdev,0 );
@@ -306,8 +300,8 @@ static int sama5d4_wdt_probe(struct platform_device *pdev)watchdog_init_timeout (wdd, wdt_timeout, dev); reg =wdt_read (wdt,AT91_WDT_MR ); -if (!(reg &AT91_WDT_WDDIS )) { - wdt->mr &= ~AT91_WDT_WDDIS ; +if (!(reg & wdt->wddis_mask)) { + wdt->mr &= ~wdt->wddis_mask;set_bit (WDOG_HW_RUNNING , &wdd->status); }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 116/2077 watchdog: sprd_wdt: Remove redundant sprd_wdt_disable() on register failure
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Felix Gu <[email protected]>
[ Upstream commit 96b3cfc3b8ad0524d12fed1e08bc5df3ff345f64 ]
The driver uses devm_add_action_or_reset() to register sprd_wdt_disable() as a managed cleanup action.
When devm_watchdog_register_device() fails, the devm core will invoke the cleanup action automatically.
The explicit sprd_wdt_disable() call in the error path is therefore redundant and results in adouble cleanup.
--- drivers/watchdog/sprd_wdt.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
drivers/watchdog/sprd_wdt.c +2 -3
@@ -320,10 +320,9 @@ static int sprd_wdt_probe(struct platform_device *pdev)watchdog_init_timeout (&wdt->wdd,0 , dev); ret =devm_watchdog_register_device (dev, &wdt->wdd); -if (ret) { -sprd_wdt_disable (wdt); +if (ret)return ret; - } +platform_set_drvdata (pdev, wdt);return 0 ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 117/2077 media: cedrus: Fix failure to clean up hardware on probe failure
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Samuel Holland <[email protected]>
[ Upstream commit f0a22f1d602ed499a192284de5e811a73421f0c7 ]
If V4L2 device fails to register, then SRAM still be claimed and as a result driver will not be able to probe again.
cedrus 1c0e000.video-codec: Failed to claim SRAM
cedrus 1c0e000.video-codec: Failed to probe hardware
cedrus 1c0e000.video-codec: probe with driver cedrus failed with error -16
cedrus_hw_remove undoes everything that was previously done by cedrus_hw_probe, such as disabling runtime power management and releasing the claimed SRAM and reserved memory region.
--- drivers/staging/media/sunxi/cedrus/cedrus.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/staging/media/sunxi/cedrus/cedrus.c +3 -1
@@ -476,7 +476,7 @@ static int cedrus_probe(struct platform_device *pdev) ret =v4l2_device_register (&pdev->dev, &dev->v4l2_dev);if (ret) {dev_err (&pdev->dev,"Failed to register V4L2 device\n" ); -return ret; + goto err_hw; } vfd = &dev->vfd;
@@ -537,6 +537,8 @@ static int cedrus_probe(struct platform_device *pdev)v4l2_m2m_release (dev->m2m_dev); err_v4l2:v4l2_device_unregister (&dev->v4l2_dev); +err_hw: +cedrus_hw_remove (dev);return ret; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 118/2077 media: v4l2-common: Add YUV24 format info
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nas Chung <[email protected]>
[ Upstream commit 968b741872914a15363af0daf24ed2e82ec355f3 ]
The YUV24 format is missing an entry in the v4l2_format_info(). The YUV24 format is the packed YUV 4:4:4 formats with 8 bits per component.
--- drivers/media/v4l2-core/v4l2-common.c | 1 + 1 file changed, 1 insertion(+)
drivers/media/v4l2-core/v4l2-common.c +1 -0
@@ -281,6 +281,7 @@ const struct v4l2_format_info *v4l2_format_info(u32 format) { .format = V4L2_PIX_FMT_Y212, .pixel_enc = V4L2_PIXEL_ENC_YUV, .mem_planes = 1, .comp_planes = 1, .bpp = { 4, 0, 0, 0 }, .bpp_div = { 1, 1, 1, 1 }, .hdiv = 2, .vdiv = 1 }, { .format = V4L2_PIX_FMT_Y216, .pixel_enc = V4L2_PIXEL_ENC_YUV, .mem_planes = 1, .comp_planes = 1, .bpp = { 4, 0, 0, 0 }, .bpp_div = { 1, 1, 1, 1 }, .hdiv = 2, .vdiv = 1 }, { .format = V4L2_PIX_FMT_YUV48_12, .pixel_enc = V4L2_PIXEL_ENC_YUV, .mem_planes = 1, .comp_planes = 1, .bpp = { 6, 0, 0, 0 }, .bpp_div = { 1, 1, 1, 1 }, .hdiv = 1, .vdiv = 1 }, + { .format = V4L2_PIX_FMT_YUV24, .pixel_enc = V4L2_PIXEL_ENC_YUV, .mem_planes = 1, .comp_planes = 1, .bpp = { 3, 0, 0, 0 }, .bpp_div = { 1, 1, 1, 1 }, .hdiv = 1, .vdiv = 1 }, { .format = V4L2_PIX_FMT_MT2110T, .pixel_enc = V4L2_PIXEL_ENC_YUV, .mem_planes = 2, .comp_planes = 2, .bpp = { 5, 10, 0, 0 }, .bpp_div = { 4, 4, 1, 1 }, .hdiv = 2, .vdiv = 2, .block_w = { 16, 8, 0, 0 }, .block_h = { 32, 16, 0, 0 }}, { .format = V4L2_PIX_FMT_MT2110R, .pixel_enc = V4L2_PIXEL_ENC_YUV, .mem_planes = 2, .comp_planes = 2, .bpp = { 5, 10, 0, 0 }, .bpp_div = { 4, 4, 1, 1 }, .hdiv = 2, .vdiv = 2,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 119/2077 drm: verisilicon: call atomic helpers plane state check even if no CRTC
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Icenowy Zheng <[email protected]>
[ Upstream commit eae3903e33797a28d0d37e693d4314d58338918e ]
The drm_atomic_helper_check_plane_state() helper function needs to be called even if the plane is bound to no CRTCs.
Remove the early return in the primary plane's atomic_check, and use NULL for crtc_state in this situation.
--- drivers/gpu/drm/verisilicon/vs_primary_plane.c | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-)
drivers/gpu/drm/verisilicon/vs_primary_plane.c +3 -7
@@ -26,14 +26,10 @@ static int vs_primary_plane_atomic_check(struct drm_plane *plane,struct drm_plane_state *new_plane_state =drm_atomic_get_new_plane_state (state, plane);struct drm_crtc *crtc = new_plane_state->crtc; -struct drm_crtc_state *crtc_state; +struct drm_crtc_state *crtc_state =NULL ; -if (!crtc) -return 0 ; - - crtc_state =drm_atomic_get_new_crtc_state (state, crtc); -if (WARN_ON (!crtc_state)) -return -EINVAL ; +if (crtc) + crtc_state =drm_atomic_get_new_crtc_state (state, crtc); return drm_atomic_helper_check_plane_state(new_plane_state, crtc_state,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 120/2077 memory: tegra: Wire up system sleep PM ops
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ashish Mhetre <[email protected]>
[ Upstream commit 2411c8d1e3e09910e94bab0d0a2c071fbc8a9e7b ]
The tegra-mc platform driver does not register any dev_pm_ops, so the SoC-specific ->resume() is never invoked (e.g. tegra186_mc_resume) on system wake. On Tegra186 and later this means MC client Stream-ID override registers are not reprogrammed, and clients behind the ARM SMMU fault on the first DMA after resume.
Register a dev_pm_ops on the tegra-mc driver and route the system resume callback into mc->soc->ops->resume() so the existing SID restore path runs again on wake.
No suspend callback is needed as the resume path reprograms all MC state from the static SoC tables, so there is nothing to save.
--- drivers/memory/tegra/mc.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
drivers/memory/tegra/mc.c +14 -0
@@ -13,6 +13,7 @@#include <linux/of.h> #include <linux/of_platform.h> #include <linux/platform_device.h> +#include <linux/pm.h> #include <linux/slab.h> #include <linux/sort.h> #include <linux/tegra-icc.h>
@@ -1010,10 +1011,23 @@ static void tegra_mc_sync_state(struct device *dev)icc_sync_state (dev); } +static int tegra_mc_resume (struct device *dev) +{ +struct tegra_mc *mc =dev_get_drvdata (dev); + +if (mc->soc->ops && mc->soc->ops->resume) + mc->soc->ops->resume (mc); + +return 0 ; +} + +static DEFINE_SIMPLE_DEV_PM_OPS(tegra_mc_pm_ops, NULL, tegra_mc_resume); +static struct platform_driver tegra_mc_driver = { .driver = { .name ="tegra-mc" , .of_match_table = tegra_mc_of_match, + .pm =pm_sleep_ptr (&tegra_mc_pm_ops), .suppress_bind_attrs = true, .sync_state = tegra_mc_sync_state, },
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 121/2077 objtool/klp: Fix is_uncorrelated_static_local() for Clang
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Joe Lawrence <[email protected]>
[ Upstream commit 84c304a534b844703d3437811e8f072166e3f116 ]
For naming function-local static locals, GCC uses <var>.<id>, e.g. __already_done.15, while Clang uses <func>.<var> with optional .<id>, e.g. create_worker.__already_done.111
The existing is_uncorrelated_static_local() check only matches the GCC convention where the variable name is a prefix. Handle both cases by checking for a prefix match (GCC) and by checking after the first dot separator (Clang).
--- tools/objtool/klp-diff.c | 33 +++++++++++++++++++++++---------- 1 file changed, 23 insertions(+), 10 deletions(-)
tools/objtool/klp-diff.c +23 -10
@@ -242,16 +242,17 @@ static struct symbol *next_file_symbol(struct elf *elf, struct symbol *sym)static bool is_uncorrelated_static_local (struct symbol *sym) {static const char *const vars[] = { -"__already_done." , -"__func__." , -"__key." , -"__warned." , -"_entry." , -"_entry_ptr." , -"_rs." , -"descriptor." , -"CSWTCH." , +"__already_done" , +"__func__" , +"__key" , +"__warned" , +"_entry" , +"_entry_ptr" , +"_rs" , +"descriptor" , +"CSWTCH" , }; +const char *dot;if (!is_object_sym (sym) || !is_local_sym (sym))return false;
@@ -259,8 +260,20 @@ static bool is_uncorrelated_static_local(struct symbol *sym)if (!strcmp (sym->sec->name,".data.once" ))return true; + dot =strchr (sym->name,'.' ); +if (!dot) +return false; +for (int i =0 ; i <ARRAY_SIZE (vars); i++) { -if (strstarts (sym->name, vars[i])) +size_t len =strlen (vars[i]); + +/* GCC: <var>.<id> */ +if (strstarts (sym->name, vars[i]) && (sym->name[len] =='.' )) +return true; + +/* Clang: <func>.<var>[.<id>] */ +if (strstarts (dot +1 , vars[i]) && + (dot[1 + len] =='.' || dot[1 + len] =='\0' ))return true; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 122/2077 objtool/klp: Fix .data..once static local non-correlation
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Poimboeuf <[email protected]>
[ Upstream commit ff529864e738f447ff4c019956319930fc274a23 ]
While there was once a section named .data.once, it has since been renamed to .data..once with commit dbefa1f31a91 ("Rename .data.once to .data..once to fix resetting WARN*_ONCE"). Fix it.
--- tools/objtool/klp-diff.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
tools/objtool/klp-diff.c +2 -1
@@ -257,7 +257,8 @@ static bool is_uncorrelated_static_local(struct symbol *sym)if (!is_object_sym (sym) || !is_local_sym (sym))return false; -if (!strcmp (sym->sec->name,".data.once" )) +/* WARN_ONCE, etc */ +if (!strcmp (sym->sec->name,".data..once" ))return true; dot =strchr (sym->name,'.' );
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 123/2077 objtool/klp: Fix create_fake_symbols() skipping entsize-based sections
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Joe Lawrence <[email protected]>
[ Upstream commit 3de711fba73ad93b8b3fbe09cf681cefed5d573d ]
create_fake_symbols() has two phases: creating symbols from ANNOTATE_DATA_SPECIAL entries, and a fallback that uses sh_entsize for special sections like .static_call_sites.
When .discard.annotate_data is absent, the function returns early, skipping the entsize fallback and silently allowing unsupported module-local static call keys through.
Fix it by jumping to the entsize phase instead of returning early.
--- tools/objtool/klp-diff.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/objtool/klp-diff.c +2 -2
@@ -1348,7 +1348,7 @@ static int create_fake_symbols(struct elf *elf) sec =find_section_by_name (elf,".discard.annotate_data" );if (!sec || !sec->rsec) -return 0 ; + goto entsize;for_each_reloc (sec->rsec, reloc) {unsigned long offset, size;
@@ -1380,7 +1380,7 @@ static int create_fake_symbols(struct elf *elf)/* * 2) Make symbols for sh_entsize, and simple arrays of pointers: */ - +entsize:for_each_sec (elf, sec) {unsigned int entry_size;unsigned long offset;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 124/2077 objtool/klp: Fix handling of zero-length .altinstr_replacement sections
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Poimboeuf <[email protected]>
[ Upstream commit c4c02d4450b5b7e2fbde578252f71a5697180112 ]
When a section is empty (e.g. only zero-length alternative replacements), there are no symbols to convert a section symbol reference to. Skip the reloc instead of erroring out.
--- tools/objtool/klp-diff.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)
tools/objtool/klp-diff.c +12 -1
@@ -993,6 +993,13 @@ static int convert_reloc_secsym_to_sym(struct elf *elf, struct reloc *reloc)/* No dedicated section; find the symbol manually */ sym =find_symbol_containing (sec,arch_adjusted_addend (reloc));if (!sym) { +/* +* This is presumably an .altinstr_replacement section which is +* empty due to it only having zero-length replacement(s). +*/ +if (!sec_size (sec)) +return 1 ; +/* * This can happen for special section references to weak code * whose symbol has been stripped by the linker.
@@ -1253,6 +1260,7 @@ static int clone_sym_relocs(struct elfs *e, struct symbol *patched_sym)for_each_reloc (patched_rsec, patched_reloc) {unsigned long offset; +int ret;if (reloc_offset (patched_reloc) < start ||reloc_offset (patched_reloc) >= end)
@@ -1266,12 +1274,15 @@ static int clone_sym_relocs(struct elfs *e, struct symbol *patched_sym) !strcmp(patched_reloc->sym->sec->name, ".altinstr_aux")) continue; -if (convert_reloc_sym (e->patched, patched_reloc)) { + ret =convert_reloc_sym (e->patched, patched_reloc); +if (ret <0 ) {ERROR_FUNC (patched_rsec->base,reloc_offset (patched_reloc),"failed to convert reloc sym '%s' to its proper format" , patched_reloc->sym->name);return -1 ; } +if (ret >0 ) +continue ; offset = out_sym->offset + (reloc_offset (patched_reloc) - patched_sym->offset);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 125/2077 objtool/klp: Fix cloning of zero-length section symbols
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Poimboeuf <[email protected]>
[ Upstream commit 98377f3ba7c02d6eb34e203c9f9823bc62b0d231 ]
Fix NULL dereference when cloning a symbol from an empty section. sec->data is only populated for sections with non-zero size.
--- tools/objtool/klp-diff.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/objtool/klp-diff.c +1 -1
@@ -669,7 +669,7 @@ static struct symbol *__clone_symbol(struct elf *elf, struct symbol *patched_symsize_t size;/* bss doesn't have data */ -if (patched_sym->sec->data->d_buf) +if (patched_sym->sec->data && patched_sym->sec->data->d_buf) data = patched_sym->sec->data->d_buf + patched_sym->offset;if (is_sec_sym (patched_sym))
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 126/2077 objtool/klp: Fix extraction of text annotations for alternatives
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Poimboeuf <[email protected]>
[ Upstream commit 62a7a01fde87c99926cd7e9670b4226c4c79ebaf ]
Objtool is failing to extract text annotations which reference .altinstr_replacement instructions:
1) Alternative replacement fake symbols are NOTYPE rather than FUNC,
and they don't have sym->included set, thus they aren't recognized
by should_keep_special_sym().2) .discard.annotate_insn gets processed before .altinstr_replacement, so the referenced (fake) symbols don't have clones yet.
Fix the first issue by checking for a valid clone instead of sym->included and by accepting NOTYPE symbols when processing .discard.annotate_insn.
Fix the second issue by deferring text annotation processing until after the other special sections have been cloned.
--- tools/objtool/klp-diff.c | 33 ++++++++++++++++++++++++++++----- 1 file changed, 28 insertions(+), 5 deletions(-)
tools/objtool/klp-diff.c +28 -5
@@ -1425,6 +1425,7 @@ static int create_fake_symbols(struct elf *elf)/* Keep a special section entry if it references an included function */ static bool should_keep_special_sym (struct elf *elf,struct symbol *sym) { +bool annotate_insn = !strcmp (sym->sec->name,".discard.annotate_insn" );struct reloc *reloc;if (is_sec_sym (sym) || !sym->sec->rsec)
@@ -1434,7 +1435,16 @@ static bool should_keep_special_sym(struct elf *elf, struct symbol *sym)if (convert_reloc_sym (elf, reloc))continue ; -if (is_func_sym (reloc->sym) && reloc->sym->included) +if (!reloc->sym->clone ||is_undef_sym (reloc->sym->clone)) +continue ; + +/* +* Keep special section references to cloned functions. +* In some cases annotate_insn can also reference cloned alt +* replacement fake symbols; keep those references as well. +*/ +if (is_func_sym (reloc->sym) || + (annotate_insn &&is_notype_sym (reloc->sym)))return true; }
@@ -1578,15 +1588,28 @@ static int clone_special_section(struct elfs *e, struct section *patched_sec)/* Extract only the needed bits from special sections */ static int clone_special_sections (struct elfs *e) { -struct section *patched_sec; +struct section *sec, *annotate_insn =NULL ; -for_each_sec (e->patched, patched_sec) { -if (is_special_section (patched_sec)) { -if (clone_special_section (e, patched_sec)) +for_each_sec (e->patched, sec) { +if (is_special_section (sec)) { +if (!strcmp (sec->name,".discard.annotate_insn" )) { + annotate_insn = sec; +continue ; + } +if (clone_special_section (e, sec))return -1 ; } } +/* +* Do .discard.annotate_insn last, it can reference other special +* sections (alt replacements) so they need to be cloned first. +*/ +if (annotate_insn) { +if (clone_special_section (e, annotate_insn)) +return -1 ; + } +return 0 ; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 127/2077 objtool/klp: Fix relocation conversion failures for R_X86_64_NONE
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Poimboeuf <[email protected]>
[ Upstream commit 3787e82a4e3a0a04aeb5543580ee90bed3a36e55 ]
Objtool has some hacks which NOP out certain calls/jumps and replace their relocations with R_X86_64_NONE. The klp-diff relocation extraction code will error out when trying to copy these relocations due to their negative addend, which would only makes sense for a PC-relative branch instruction. Just ignore them.
--- tools/objtool/klp-diff.c | 3 +++ 1 file changed, 3 insertions(+)
tools/objtool/klp-diff.c +3 -0
@@ -1020,6 +1020,9 @@ static int convert_reloc_secsym_to_sym(struct elf *elf, struct reloc *reloc)*/ static int convert_reloc_sym (struct elf *elf,struct reloc *reloc) { +if (reloc_type (reloc) ==R_NONE ) +return 1 ; +if (is_reloc_allowed (reloc))return 0 ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 128/2077 objtool: Replace iterator callback with for_each_sym_by_mangled_name()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Poimboeuf <[email protected]>
[ Upstream commit 0333b7399587ee0aaa863ed0d13a00a6c7c64068 ]
Convert the callback-based iterate_sym_by_demangled_name() with a new for_each_sym_by_demangled_name() macro. This eliminates the callback struct/function and makes the code more compact and readable.
Stable-dep-of: a375e327b63e ("objtool: Fix reloc hash collision in find_reloc_by_dest_range()")
--- tools/objtool/elf.c | 68 ++++++++--------------------- tools/objtool/include/objtool/elf.h | 32 ++++++++++++-- tools/objtool/klp-diff.c | 42 ++++++------------ 3 files changed, 60 insertions(+), 82 deletions(-)
tools/objtool/elf.c +17 -51
@@ -27,27 +27,16 @@static ssize_t demangled_name_len (const char *name); -static inline u32 str_hash (const char *str) -{ -return jhash (str,strlen (str),0 ); -} - -static inline u32 str_hash_demangled (const char *str) +u32 str_hash_demangled (const char *str) {return jhash (str,demangled_name_len (str),0 ); } -#define __elf_table (name) (elf->name##_hash) -#define __elf_bits (name) (elf->name##_bits) - -#define __elf_table_entry (name, key) \ - __elf_table(name)[hash_min(key, __elf_bits(name))] -#define elf_hash_add (name, node, key) \ ({ \ struct elf_hash_node *__node = node; \ - __node->next = __elf_table_entry(name, key); \ - __elf_table_entry(name, key) = __node; \ + __node->next = __elf_table_entry(elf, name, key); \ + __elf_table_entry(elf, name, key) = __node; \ }) static inline void __elf_hash_del(struct elf_hash_node *node,
@@ -69,30 +58,20 @@ static inline void __elf_hash_del(struct elf_hash_node *node, }#define elf_hash_del (name, node, key) \ - __elf_hash_del(node, &__elf_table_entry(name, key)) - -#define elf_list_entry (ptr, type, member) \ -({ \ - typeof(ptr) __ptr = (ptr); \ - __ptr ? container_of(__ptr, type, member) : NULL; \ -}) - -#define elf_hash_for_each_possible (name, obj, member, key) \ - for (obj = elf_list_entry(__elf_table_entry(name, key), typeof(*obj), member); \ - obj; \ - obj = elf_list_entry(obj->member.next, typeof(*(obj)), member)) + __elf_hash_del(node, &__elf_table_entry(elf, name, key))#define elf_alloc_hash (name, size) \ ({ \ - __elf_bits(name) = max(10, ilog2(size)); \ - __elf_table(name) = mmap(NULL, sizeof(struct elf_hash_node *) << __elf_bits(name), \ + __elf_bits(elf, name) = max(10, ilog2(size)); \ + __elf_table(elf, name) = mmap(NULL, \ + sizeof(struct elf_hash_node *) << __elf_bits(elf, name), \ PROT_READ|PROT_WRITE, \ MAP_PRIVATE|MAP_ANON, -1, 0); \ - if (__elf_table(name) == (void *)-1L) { \ + if (__elf_table(elf, name) == (void *)-1L) { \ ERROR_GLIBC("mmap fail " #name); \ - __elf_table(name) = NULL; \ + __elf_table(elf, name) = NULL; \ } \ - __elf_table(name); \ + __elf_table(elf, name); \ })static inline unsigned long __sym_start (struct symbol *s)
@@ -141,7 +120,7 @@ struct section *find_section_by_name(const struct elf *elf, const char *name) {struct section *sec; -elf_hash_for_each_possible (section_name, sec, name_hash,str_hash (name)) { +elf_hash_for_each_possible (elf, section_name, sec, name_hash,str_hash (name)) {if (!strcmp (sec->name, name))return sec; }
@@ -154,7 +133,7 @@ static struct section *find_section_by_index(struct elf *elf, {struct section *sec; -elf_hash_for_each_possible (section, sec, hash, idx) { +elf_hash_for_each_possible (elf, section, sec, hash, idx) {if (sec->idx == idx)return sec; }
@@ -166,7 +145,7 @@ static struct symbol *find_symbol_by_index(struct elf *elf, unsigned int idx) {struct symbol *sym; -elf_hash_for_each_possible (symbol, sym, hash, idx) { +elf_hash_for_each_possible (elf, symbol, sym, hash, idx) {if (sym->idx == idx)return sym; }
@@ -285,7 +264,7 @@ struct symbol *find_symbol_by_name(const struct elf *elf, const char *name) {struct symbol *sym; -elf_hash_for_each_possible (symbol_name, sym, name_hash,str_hash (name)) { +elf_hash_for_each_possible (elf, symbol_name, sym, name_hash,str_hash (name)) {if (!strcmp (sym->name, name))return sym; }
@@ -300,7 +279,7 @@ static struct symbol *find_local_symbol_by_file_and_name(const struct elf *elf, {struct symbol *sym; -elf_hash_for_each_possible (symbol_name, sym, name_hash,str_hash_demangled (name)) { +elf_hash_for_each_possible (elf, symbol_name, sym, name_hash,str_hash_demangled (name)) {if (sym->bind ==STB_LOCAL && sym->file == file && !strcmp (sym->name, name)) {return sym;
@@ -314,7 +293,7 @@ struct symbol *find_global_symbol_by_name(const struct elf *elf, const char *nam {struct symbol *sym; -elf_hash_for_each_possible (symbol_name, sym, name_hash,str_hash_demangled (name)) { +elf_hash_for_each_possible (elf, symbol_name, sym, name_hash,str_hash_demangled (name)) {if (!strcmp (sym->name, name) && !is_local_sym (sym))return sym; }
@@ -322,19 +301,6 @@ struct symbol *find_global_symbol_by_name(const struct elf *elf, const char *namreturn NULL ; } -void iterate_global_symbol_by_demangled_name (const struct elf *elf, -const char *demangled_name, -void (*process)(struct symbol *sym,void *data), -void *data) -{ -struct symbol *sym; - -elf_hash_for_each_possible (symbol_name, sym, name_hash,str_hash (demangled_name)) { -if (!strcmp (sym->demangled_name, demangled_name) && !is_local_sym (sym)) -process (sym, data); - } -} -struct reloc *find_reloc_by_dest_range (const struct elf *elf,struct section *sec,unsigned long offset,unsigned int len) {
@@ -347,7 +313,7 @@ struct reloc *find_reloc_by_dest_range(const struct elf *elf, struct section *sereturn NULL ; for_offset_range(o, offset, offset + len) { -elf_hash_for_each_possible (reloc, reloc, hash, +elf_hash_for_each_possible (elf, reloc, reloc, hash,sec_offset_hash (rsec, o)) {if (reloc->sec != rsec)continue ;
tools/objtool/include/objtool/elf.h +29 -3
@@ -21,6 +21,13 @@#define SEC_NAME_LEN 1024#define SYM_NAME_LEN 512 +static inline u32 str_hash (const char *str) +{ +return jhash (str,strlen (str),0 ); +} + +u32 str_hash_demangled (const char *str); +#define bswap_if_needed (elf, val) __bswap_if_needed(&elf->ehdr, val)#ifdef LIBELF_USE_DEPRECATED
@@ -130,6 +137,23 @@ struct elf {struct symbol *symbol_data; }; +#define __elf_table (elf, name) ((elf)->name##_hash) +#define __elf_bits (elf, name) ((elf)->name##_bits) + +#define __elf_table_entry (elf, name, key) \ + __elf_table(elf, name)[hash_min(key, __elf_bits(elf, name))] + +#define elf_list_entry (ptr, type, member) \ +({ \ + typeof(ptr) __ptr = (ptr); \ + __ptr ? container_of(__ptr, type, member) : NULL; \ +}) + +#define elf_hash_for_each_possible (elf, name, obj, member, key) \ + for (obj = elf_list_entry(__elf_table_entry(elf, name, key), typeof(*obj), member); \ + obj; \ + obj = elf_list_entry(obj->member.next, typeof(*(obj)), member)) +struct elf *elf_open_read (const char *name,int flags);struct elf *elf_create_file (GElf_Ehdr *ehdr,const char *name);
@@ -186,9 +210,6 @@ struct symbol *find_func_by_offset(struct section *sec, unsigned long offset);struct symbol *find_symbol_by_offset (struct section *sec,unsigned long offset);struct symbol *find_symbol_by_name (const struct elf *elf,const char *name);struct symbol *find_global_symbol_by_name (const struct elf *elf,const char *name); -void iterate_global_symbol_by_demangled_name (const struct elf *elf,const char *demangled_name, -void (*process)(struct symbol *sym,void *data), -void *data);struct symbol *find_symbol_containing (const struct section *sec,unsigned long offset);int find_symbol_hole_containing (const struct section *sec,unsigned long offset);struct reloc *find_reloc_by_dest (const struct elf *elf,struct section *sec,unsigned long offset);
@@ -468,6 +489,11 @@ static inline void set_sym_next_reloc(struct reloc *reloc, struct reloc *next)#define for_each_sym_continue (elf, sym) \ list_for_each_entry_continue(sym, &elf->symbols, global_list) +#define for_each_sym_by_demangled_name (elf, name, sym) \ + elf_hash_for_each_possible(elf, symbol_name, sym, name_hash, \ + str_hash(name)) \ + if (strcmp(sym->demangled_name, name)) {} else +#define rsec_next_reloc (rsec, reloc) \ reloc_idx(reloc) < sec_num_entries(rsec) - 1 ? reloc + 1 : NULL
tools/objtool/klp-diff.c +14 -28
63 lines not on this page · raw message
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 129/2077 objtool: Fix reloc hash collision in find_reloc_by_dest_range()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Poimboeuf <[email protected]>
[ Upstream commit a375e327b63e0da29b82a92b569bfdf4628fa38a ]
In find_reloc_by_dest_range(), hash collisions can cause a high-offset relocation to appear when probing a low-offset hash bucket.
Only return early when the best match found so far genuinely belongs to the current bucket (its offset is within the bucket's stride range). Otherwise, continue scanning later buckets which may contain lower-offset matches.
This ensures the first reloc in the range gets returned.
--- tools/objtool/elf.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
tools/objtool/elf.c +4 -3
@@ -301,8 +301,9 @@ struct symbol *find_global_symbol_by_name(const struct elf *elf, const char *namreturn NULL ; } +/* If there are multiple matches, return the first one in the range */ struct reloc *find_reloc_by_dest_range (const struct elf *elf,struct section *sec, -unsigned long offset,unsigned int len) +unsigned long offset,unsigned int len) {struct reloc *reloc, *r =NULL ;struct section *rsec;
@@ -324,11 +325,11 @@ struct reloc *find_reloc_by_dest_range(const struct elf *elf, struct section *se r = reloc; } } -if (r) +if (r && (reloc_offset (r) &OFFSET_STRIDE_MASK ) == o)return r; } -return NULL ; +return r; }struct reloc *find_reloc_by_dest (const struct elf *elf,struct section *sec,unsigned long offset)
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 130/2077 klp-build: Fix hang on out-of-date .config
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Poimboeuf <[email protected]>
[ Upstream commit cc39ccce7d5bc623100f07dcda070cef1bf690f6 ]
If .config is out of date with the kernel source, 'make syncconfig' hangs while waiting for user input on new config options. Detect the mismatch and return an error.
--- scripts/livepatch/klp-build | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
scripts/livepatch/klp-build +6 -1
@@ -306,7 +306,12 @@ set_kernelversion() { stash_file "$file" - kernelrelease="$(cd "$SRC" && make syncconfig &>/dev/null && make -s kernelrelease)" + if [[ -n "$(make -s listnewconfig 2>/dev/null)" ]]; then + die ".config mismatch, check your .config or run 'make olddefconfig'" + fi + make syncconfig &>/dev/null || die "make syncconfig failed" + + kernelrelease="$(make -s kernelrelease)" [[ -z "$kernelrelease" ]] && die "failed to get kernel version" sed -i "2i echo $kernelrelease; exit 0" scripts/setlocalversion
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 131/2077 klp-build: Fix checksum comparison for changed offsets
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Poimboeuf <[email protected]>
[ Upstream commit ba77fe55781a2464f68b6c13b4b31d05abd2abcf ]
The klp-build -f/--show-first-changed feature uses diff to compare checksum log lines between original and patched objects. However, diff compares entire lines, including the offset field. When a function is at a different section offset, the offset field differs even though the instruction checksum is identical, causing the wrong instruction to be printed.
Only compare the checksum field when looking for the first changed instruction. Also print both the original and patched offsets when they differ.
--- scripts/livepatch/klp-build | 30 +++++++++++++++++++++++------- 1 file changed, 23 insertions(+), 7 deletions(-)
scripts/livepatch/klp-build +23 -7
@@ -727,13 +727,29 @@ diff_checksums() { ) for func in ${funcs[$file]}; do - diff <( grep0 -E "^DEBUG: .*checksum: $func " "$orig_log" | sed "s|$ORIG_DIR/||") \ - <( grep0 -E "^DEBUG: .*checksum: $func " "$patched_log" | sed "s|$PATCHED_DIR/||") \ - | gawk '/^< DEBUG: / { - gsub(/:/, "") - printf "%s: %s: %s\n", $3, $5, $6 - exit - }' || true + local -a orig patched + paste <(grep0 -E "^DEBUG: .*checksum: $func " "$orig_log") \ + <(grep0 -E "^DEBUG: .*checksum: $func " "$patched_log") | + while IFS= read -r line; do + read -ra orig <<< "${line%%$'\t'*}" + read -ra patched <<< "${line#*$'\t'}" + + if [[ ${#patched[@]} -eq 0 ]]; then + printf "%s: %s: %s (removed)\n" "${orig[1]%:}" "${orig[3]}" "${orig[-2]}" + break + elif [[ ${#orig[@]} -eq 0 ]]; then + printf "%s: %s: %s (added)\n" "${patched[1]%:}" "${patched[3]}" "${patched[-2]}" + break + fi + + [[ "${orig[-1]}" == "${patched[-1]}" ]] && continue + + printf "%s: %s: %s" "${orig[1]%:}" "${orig[3]}" "${orig[-2]}" + [[ "${orig[-2]}" != "${patched[-2]}" ]] && \ + printf " (patched: %s)" "${patched[-2]}" + printf "\n" + break + done || true done done }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 132/2077 klp-build: Fix patch cleanup on interrupt
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Poimboeuf <[email protected]>
[ Upstream commit f3048888ea62ac1c573db91e74e0dcabe058e89f ]
If a build error occurs and the user hits Ctrl-C while a large patch is being reverted during cleanup, the cleanup EXIT trap gets re-triggered and tries to re-revert the already partially-reverted patch. That causes 'patch -R' to repeatedly prompt
"Unreversed patch detected! Ignore -R? [n]"
for each already-reverted hunk, with no way to break out.
Fix it by adding '--force' to the patch revert command in revert_patch(), which causes it to silently ignore already-reverted hunks. And ignore errors, as the cleanup is always best-effort.
For similar reasons, add to APPLIED_PATCHES before (rather than after) applying the patch in apply_patch() so an interrupted apply will also get cleaned up.
--- scripts/livepatch/klp-build | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
scripts/livepatch/klp-build +2 -2
@@ -381,15 +381,15 @@ apply_patch() { warn "${patch} applied with fuzz" fi - patch -d "$SRC" -p1 --no-backup-if-mismatch -r /dev/null "${extra_args[@]}" --silent < "$patch" APPLIED_PATCHES+=("$patch") + patch -d "$SRC" -p1 --no-backup-if-mismatch -r /dev/null "${extra_args[@]}" --silent < "$patch" } revert_patch() { local patch="$1" local tmp=() - patch -d "$SRC" -p1 -R --silent --no-backup-if-mismatch -r /dev/null < "$patch" + patch -d "$SRC" -p1 -R --force --no-backup-if-mismatch -r /dev/null &> /dev/null < "$patch" || true for p in "${APPLIED_PATCHES[@]}"; do [[ "$p" == "$patch" ]] && continue
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 133/2077 crypto: qat - fix heartbeat error injection
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Damian Muszynski <[email protected]>
[ Upstream commit 2e96024632b386c86860aa78639940fc96d6fcc9 ]
The current implementation of the heartbeat error injection uses adf_disable_arb_thd() to stop a specific accelerator engine thread from processing requests. This does not reliably prevent the device from generating responses.
Fix the error injection by disabling the device arbiter through exit_arb() instead. This properly simulates a device failure by stopping all arbitration, which results in missing responses for sent requests.
Remove the now unused adf_disable_arb_thd() function and its declaration.
--- .../intel/qat/qat_common/adf_common_drv.h | 1 - .../qat/qat_common/adf_heartbeat_inject.c | 6 ++--- .../intel/qat/qat_common/adf_hw_arbiter.c | 25 ------------------- 3 files changed, 2 insertions(+), 30 deletions(-)
drivers/crypto/intel/qat/qat_common/adf_common_drv.h +0 -1
@@ -90,7 +90,6 @@ void adf_exit_aer(void);int adf_init_arb (struct adf_accel_dev *accel_dev);void adf_exit_arb (struct adf_accel_dev *accel_dev);void adf_update_ring_arb (struct adf_etr_ring_data *ring); -int adf_disable_arb_thd (struct adf_accel_dev *accel_dev,u32 ae,u32 thr);int adf_dev_get (struct adf_accel_dev *accel_dev);void adf_dev_put (struct adf_accel_dev *accel_dev);
drivers/crypto/intel/qat/qat_common/adf_heartbeat_inject.c +2 -4
@@ -64,10 +64,8 @@ int adf_heartbeat_inject_error(struct adf_accel_dev *accel_dev)if (ret)return ret; -/* Configure worker threads to stop processing any packet */ - ret =adf_disable_arb_thd (accel_dev, rand_ae, rand_thr); -if (ret) -return ret; +/* Disable arbiter to stop processing any packet */ + hw_device->exit_arb (accel_dev);/* Change HB counters memory to simulate a hang */ adf_set_hb_counters_fail (accel_dev, rand_ae, rand_thr);
drivers/crypto/intel/qat/qat_common/adf_hw_arbiter.c +0 -25
@@ -99,28 +99,3 @@ void adf_exit_arb(struct adf_accel_dev *accel_dev) csr_ops->write_csr_ring_srv_arb_en (csr, i,0 ); }EXPORT_SYMBOL_GPL (adf_exit_arb); - -int adf_disable_arb_thd (struct adf_accel_dev *accel_dev,u32 ae,u32 thr) -{ -void __iomem *csr = accel_dev->transport->banks[0 ].csr_addr; -struct adf_hw_device_data *hw_data = accel_dev->hw_device; -const u32 *thd_2_arb_cfg; -struct arb_info info; -u32 ae_thr_map; - -if (ADF_AE_STRAND0_THREAD == thr ||ADF_AE_STRAND1_THREAD == thr) - thr =ADF_AE_ADMIN_THREAD ; - - hw_data->get_arb_info (&info); - thd_2_arb_cfg = hw_data->get_arb_mapping (accel_dev); -if (!thd_2_arb_cfg) -return -EFAULT ; - -/* Disable scheduling for this particular AE and thread */ - ae_thr_map = *(thd_2_arb_cfg + ae); - ae_thr_map &= ~(GENMASK (3 ,0 ) << (thr *BIT (2 ))); - -WRITE_CSR_ARB_WT2SAM (csr, info.arb_offset, info.wt2sam_offset, ae, - ae_thr_map); -return 0 ; -}
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 134/2077 lib/vsprintf: Fix to check field_width and precision
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Masami Hiramatsu (Google) <[email protected]>
[ Upstream commit 71876dffab295b6e25d4209f0424da8fc5020e12 ]
Check the field_width and presition correctly. Previously it depends on the bitfield conversion from int to check out-of-range error. However, commit 938df695e98d ("vsprintf: associate the format state with the format pointer") changed those fields to int.
We need to check the out-of-range correctly without bitfield conversion.
--- lib/vsprintf.c | 36 ++++++++++++++---------------------- 1 file changed, 14 insertions(+), 22 deletions(-)
lib/vsprintf.c +14 -22
@@ -2640,6 +2640,18 @@ static unsigned char spec_flag(unsigned char c)return (c <sizeof (spec_flag_array)) ? spec_flag_array[c] :0 ; } +static void set_field_width (struct printf_spec *spec,int width) +{ + spec->field_width =clamp (width, -FIELD_WIDTH_MAX ,FIELD_WIDTH_MAX ); +WARN_ONCE (spec->field_width != width,"field width %d out of range" , width); +} + +static void set_precision (struct printf_spec *spec,int prec) +{ + spec->precision =clamp (prec,0 ,PRECISION_MAX ); +WARN_ONCE (spec->precision < prec,"precision %d too large" , prec); +} +/* * Helper function to decode printf style format. * Each call decode a token from the format and return the
@@ -2710,7 +2722,7 @@ struct fmt format_decode(struct fmt fmt, struct printf_spec *spec) spec->field_width =-1 ;if (isdigit (*fmt.str)) - spec->field_width =skip_atoi (&fmt.str); +set_field_width (spec,skip_atoi (&fmt.str));else if (unlikely (*fmt.str =='*' )) {/* it's the next argument */ fmt.state =FORMAT_STATE_WIDTH ;
@@ -2724,9 +2736,7 @@ struct fmt format_decode(struct fmt fmt, struct printf_spec *spec)if (unlikely (*fmt.str =='.' )) { fmt.str++;if (isdigit (*fmt.str)) { - spec->precision =skip_atoi (&fmt.str); -if (spec->precision <0 ) - spec->precision =0 ; +set_precision (spec,skip_atoi (&fmt.str)); }else if (*fmt.str =='*' ) {/* it's the next argument */ fmt.state =FORMAT_STATE_PRECISION ;
@@ -2799,24 +2809,6 @@ struct fmt format_decode(struct fmt fmt, struct printf_spec *spec)return fmt; } -static void -set_field_width (struct printf_spec *spec,int width) -{ - spec->field_width = width; -if (WARN_ONCE (spec->field_width != width,"field width %d too large" , width)) { - spec->field_width =clamp (width, -FIELD_WIDTH_MAX ,FIELD_WIDTH_MAX ); - } -} - -static void -set_precision (struct printf_spec *spec,int prec) -{ - spec->precision = prec; -if (WARN_ONCE (spec->precision != prec,"precision %d too large" , prec)) { - spec->precision =clamp (prec,0 ,PRECISION_MAX ); - } -} -/* * Turn a 1/2/4-byte value into a 64-bit one for printing: truncate * as necessary and deal with signedness.
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 135/2077 dts: spacemit: set console baud rate on bpif3
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Conor Dooley <[email protected]>
[ Upstream commit 24c12ca43b12c104389d9a159207d0b25779d0af ]
Because the default console's baud rate is not set, defconfig kernels do not have any serial output on this platform. Set the baud rate to 115200, matching what is used by U-Boot etc on this platform.
--- arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -1
@@ -19,7 +19,7 @@ aliases { }; chosen { - stdout-path = "serial0"; + stdout-path = "serial0:115200n8"; }; leds {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 136/2077 pinctrl: sunxi: fix regulator leak in sunxi_pmx_request() error path
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Felix Gu <[email protected]>
[ Upstream commit 334f7bcbdc79dc8e5b938ac3372453a5368221cf ]
In the error path of sunxi_pmx_request(), the code calls regulator_put(s_reg->regulator) to release the regulator. However, s_reg->regulator is only assigned after a successful regulator_enable(). This causes a memory leak: the regulator obtained via regulator_get() is never properly released when regulator_enable() fails.
--- drivers/pinctrl/sunxi/pinctrl-sunxi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pinctrl/sunxi/pinctrl-sunxi.c +1 -1
@@ -925,7 +925,7 @@ static int sunxi_pmx_request(struct pinctrl_dev *pctldev, unsigned offset)return 0 ; out: -regulator_put (s_reg->regulator); +regulator_put (reg);return ret; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 137/2077 riscv: dts: microchip: gpio controllers on mpfs need 2 interrupt cells
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Conor Dooley <[email protected]>
[ Upstream commit 79b731da340f1c9703e28665d49a865aa6956278 ]
The platform has variable interrupt types for GPIO interrupts, in addition to having multiple lines per GPIO controller. Two interrupt cells are required.
--- arch/riscv/boot/dts/microchip/mpfs.dtsi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/riscv/boot/dts/microchip/mpfs.dtsi +3 -3
@@ -499,7 +499,7 @@ gpio0: gpio@20120000 { reg = <0x0 0x20120000 0x0 0x1000>; interrupt-parent = <&irqmux>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; interrupts = <0>, <1>, <2>, <3>, <4>, <5>, <6>, <7>, <8>, <9>, <10>, <11>,
@@ -516,7 +516,7 @@ gpio1: gpio@20121000 { reg = <0x0 0x20121000 0x0 0x1000>; interrupt-parent = <&irqmux>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; interrupts = <32>, <33>, <34>, <35>, <36>, <37>, <38>, <39>, <40>, <41>, <42>, <43>,
@@ -535,7 +535,7 @@ gpio2: gpio@20122000 { reg = <0x0 0x20122000 0x0 0x1000>; interrupt-parent = <&irqmux>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; interrupts = <64>, <65>, <66>, <67>, <68>, <69>, <70>, <71>, <72>, <73>, <74>, <75>,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 138/2077 riscv: dts: microchip: remove gpio hogs from beaglev-fire
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Conor Dooley <[email protected]>
[ Upstream commit 7ab032833b2f0dd3b51d71e6756ebe7efc61eed4 ]
sd-det-hog should be cd-gpios, but when the mmc-spi-slot was added, the "cd-" prefix was omitted and the collision with the hog was not noticed.
vio-enable-hog is just a regulator that can be modelled as such.
--- .../boot/dts/microchip/mpfs-beaglev-fire.dts | 25 ++++++++----------- 1 file changed, 10 insertions(+), 15 deletions(-)
arch/riscv/boot/dts/microchip/mpfs-beaglev-fire.dts +10 -15
@@ -77,6 +77,15 @@ imx219_vddl: fixedregulator-2 { regulator-max-microvolt = <1200000>; }; + regulator-1v8-syzygy { + compatible = "regulator-fixed"; + gpios = <&gpio2 30 GPIO_ACTIVE_HIGH>; + regulator-name = "syzygy_1v8"; + regulator-min-microvolt = <1800000>; + regulator-max-microvolt = <1800000>; + regulator-always-on; + enable-active-high; + }; }; &gpio0 {
@@ -118,20 +127,6 @@ &gpio2 { "P8_PIN27", "P8_PIN28", "P8_PIN29", "P8_PIN30", "M2_W_DISABLE1", "M2_W_DISABLE2", "VIO_ENABLE", "SD_DET"; status = "okay"; - - vio-enable-hog { - gpio-hog; - gpios = <30 30>; - output-high; - line-name = "VIO_ENABLE"; - }; - - sd-det-hog { - gpio-hog; - gpios = <31 31>; - input; - line-name = "SD_DET"; - }; }; &i2c0 {
@@ -316,7 +311,7 @@ channel@7 { mmc@1 { compatible = "mmc-spi-slot"; reg = <1>; - gpios = <&gpio2 31 1>; + cd-gpios = <&gpio2 31 GPIO_ACTIVE_LOW>; voltage-ranges = <3300 3300>; spi-max-frequency = <5000000>; disable-wp;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 139/2077 dt-bindings: vendor-prefixes: Add Displaytech Ltd.
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marek Vasut <[email protected]>
[ Upstream commit 42112cff8cb78ff6120983ba71bd14d52ce9dccd ]
Add "displaytech" vendor prefix for Displaytech Ltd. .
--- Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++ 1 file changed, 2 insertions(+)
Documentation/devicetree/bindings/vendor-prefixes.yaml +2 -0
@@ -437,6 +437,8 @@ patternProperties: description: Diodes, Inc. "^dioo,.*": description: Dioo Microcircuit Co., Ltd + "^displaytech,.*": + description: Displaytech Ltd. "^djn,.*": description: Shenzhen DJN Optronics Technology Co., Ltd "^dlc,.*":
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 140/2077 drm/gpuvm: take refcount on DRM device
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alice Ryhl <[email protected]>
[ Upstream commit c2d72717e0a9dd01c6a1bac61a1462a8e04bd179 ]
Currently GPUVM relies on the owner implicitly holding a refcount to the drm device, and it does not implicitly take a refcount on the drm device. This design is error-prone, so take a refcount on the device.
--- drivers/gpu/drm/drm_gpuvm.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/gpu/drm/drm_gpuvm.c +5 -1
@@ -25,6 +25,7 @@* */ +#include <drm/drm_drv.h> #include <drm/drm_gpuvm.h> #include <drm/drm_print.h>
@@ -1117,6 +1118,7 @@ drm_gpuvm_init(struct drm_gpuvm *gpuvm, const char *name, gpuvm->drm = drm; gpuvm->r_obj = r_obj; +drm_dev_get (drm);drm_gem_object_get (r_obj);drm_gpuvm_warn_check_overflow (gpuvm, start_offset, range);
@@ -1160,13 +1162,15 @@ static void drm_gpuvm_free(struct kref *kref) { struct drm_gpuvm *gpuvm = container_of(kref, struct drm_gpuvm, kref); +struct drm_device *drm = gpuvm->drm;drm_gpuvm_fini (gpuvm); -if (drm_WARN_ON (gpuvm->drm, !gpuvm->ops->vm_free)) +if (drm_WARN_ON (drm, !gpuvm->ops->vm_free))return ; gpuvm->ops->vm_free (gpuvm); +drm_dev_put (drm); }/**
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 141/2077 wifi: cfg80211: restrict LMR feedback check to TB and non-TB ranging
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peddolla Harshavardhan Reddy <[email protected]>
[ Upstream commit bef9d5e378f07ccdf967b929897de84a9931d1e3 ]
The lmr_feedback field is only applicable to TB and non-TB ranging. Currently, pmsr_parse_ftm() enforces lmr_feedback for all RSTA requests, incorrectly rejecting valid EDCA-based RSTA requests.
Fix this by limiting the lmr_feedback requirement to TB and non-TB ranging only.
--- net/wireless/pmsr.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
net/wireless/pmsr.c +3 -1
@@ -195,7 +195,9 @@ static int pmsr_parse_ftm(struct cfg80211_registered_device *rdev,return -EOPNOTSUPP ; } -if (out->ftm.rsta && !out->ftm.lmr_feedback) { +if (out->ftm.rsta && + (out->ftm.non_trigger_based || out->ftm.trigger_based) && + !out->ftm.lmr_feedback) {NL_SET_ERR_MSG_ATTR (info->extack, tb[NL80211_PMSR_FTM_REQ_ATTR_RSTA ],"FTM: RSTA set without LMR feedback" );
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 142/2077 drm/panel: Clean up SOFEF00 config dependencies
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marijn Suijten <[email protected]>
[ Upstream commit e87e2357292f80d10e1a43cb910454313a5cb448 ]
As per the config name this Display IC features a DSI command-mode interface (or the command to switch to video mode is not known/documented) and does not use any of the video-mode helper utilities, hence should not select VIDEOMODE_HELPERS. In addition it uses devm_gpiod_get() and related functions from GPIOLIB.
--- drivers/gpu/drm/panel/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/panel/Kconfig +1 -1
@@ -982,10 +982,10 @@ config DRM_PANEL_SAMSUNG_S6E8FC0 config DRM_PANEL_SAMSUNG_SOFEF00 tristate "Samsung SOFEF00 DSI panel controller" + depends on GPIOLIB depends on OF depends on DRM_MIPI_DSI depends on BACKLIGHT_CLASS_DEVICE - select VIDEOMODE_HELPERS help Say Y or M here if you want to enable support for the Samsung AMOLED panel SOFEF00 DDIC and connected panel.
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 143/2077 drm/panel: Clean up S6E3FC2X01 config dependencies
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Heidelberg <[email protected]>
[ Upstream commit faf497d2f1ff15756981c6e65a9c3d8bf192a969 ]
As per the config name this Display IC features a DSI command-mode interface (or the command to switch to video mode is not known/documented) and does not use any of the video-mode helper utilities, hence should not select VIDEOMODE_HELPERS. In addition it uses devm_gpiod_get() and related functions from GPIOLIB.
--- drivers/gpu/drm/panel/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/panel/Kconfig +1 -1
@@ -890,10 +890,10 @@ config DRM_PANEL_SAMSUNG_S6D7AA0 config DRM_PANEL_SAMSUNG_S6E3FC2X01 tristate "Samsung S6E3FC2X01 DSI panel controller" + depends on GPIOLIB depends on OF depends on DRM_MIPI_DSI depends on BACKLIGHT_CLASS_DEVICE - select VIDEOMODE_HELPERS help Say Y or M here if you want to enable support for the Samsung S6E3FC2 DDIC and connected MIPI DSI panel.
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 144/2077 drm/panel: Clean up S6E3HA2 config dependencies and fill help text
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Heidelberg <[email protected]>
[ Upstream commit 632a8aa96d0717aa92cb63e3939d09b896223b4c ]
As per the config name this Display IC features a DSI command-mode interface (or the command to switch to video mode is not known/documented) and does not use any of the video-mode helper utilities, hence should not select VIDEOMODE_HELPERS. In addition it uses devm_gpiod_get() and related functions from GPIOLIB.
--- drivers/gpu/drm/panel/Kconfig | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
drivers/gpu/drm/panel/Kconfig +8 -1
@@ -910,11 +910,18 @@ config DRM_PANEL_SAMSUNG_S6E3HA2 config DRM_PANEL_SAMSUNG_S6E3HA8 tristate "Samsung S6E3HA8 DSI video mode panel" + depends on GPIOLIB depends on OF depends on DRM_MIPI_DSI depends on BACKLIGHT_CLASS_DEVICE select DRM_DISPLAY_DSC_HELPER - select VIDEOMODE_HELPERS + help + Say Y or M here if you want to enable support for the + Samsung S6E3HA8 DDIC and connected MIPI DSI panel. + Currently supported panels: + + Samsung AMB577PX01 (found in the Samsung S9 smartphone) + config DRM_PANEL_SAMSUNG_S6E63J0X03 tristate "Samsung S6E63J0X03 DSI command mode panel"
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 145/2077 riscv: dts: microchip: update pic64gx gpio interrupts to better match the SoC
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Conor Dooley <[email protected]>
[ Upstream commit 4ce4a46cdb2404bcd53ca58a18aeda673f37fbe9 ]
Just like PolarFire SoC, the same issues with GPIO interrupts exist in the pic64gx, due to their similarity. Yoinking from the commit message for the same change for PolarFire SoC:
There are 3 GPIO controllers on this SoC, of which:
- GPIO controller 0 has 14 GPIOs
- GPIO controller 1 has 24 GPIOs
- GPIO controller 2 has 32 GPIOs
All GPIOs are capable of generating interrupts, for a total of 70. There are only 41 IRQs available however, so a configurable mux is used to ensure all GPIOs can be used for interrupt generation.
38 of the 41 interrupts are in what the documentation calls "direct mode", as they provide an exclusive connection from a GPIO to the PLIC. The 3 remaining interrupts are used to mux the interrupts which do not have a exclusive connection, one for each GPIO controller.
The mux was overlooked when the bindings and driver were originally written for the GPIO controllers on Polarfire SoC, and the interrupts property in the GPIO nodes used to try and convey what the mapping was. Instead, the mux should be a device in its own right, and the GPIO controllers should be connected to it, rather than to the PLIC. Now that a binding exists for that mux, fix the inaccurate description of the interrupt controller hierarchy.
Stable-dep-of: 48c7771b3c79 ("riscv: dts: microchip: fix pic64gx gpio interrupt-cells")
--- .../dts/microchip/pic64gx-curiosity-kit.dts | 47 ++++++++++++------- arch/riscv/boot/dts/microchip/pic64gx.dtsi | 32 +++++++++++-- 2 files changed, 58 insertions(+), 21 deletions(-)
arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dts +29 -18
@@ -63,10 +63,6 @@ hss: hss-buffer@bfc00000 { }; &gpio0 { - interrupts = <13>, <14>, <15>, <16>, - <17>, <18>, <19>, <20>, - <21>, <22>, <23>, <24>, - <25>, <26>; status ="okay"; gpio-line-names = "", "", "", "", "", "", "", "",
@@ -74,12 +70,6 @@ &gpio0 { }; &gpio1 { - interrupts = <27>, <28>, <29>, <30>, - <31>, <32>, <33>, <34>, - <35>, <36>, <37>, <38>, - <39>, <40>, <41>, <42>, - <43>, <44>, <45>, <46>, - <47>, <48>, <49>, <50>; status ="okay"; gpio-line-names = "", "", "LED1", "LED2", "LED3", "LED4", "LED5", "LED6",
@@ -88,14 +78,6 @@ &gpio1 { }; &gpio2 { - interrupts = <53>, <53>, <53>, <53>, - <53>, <53>, <53>, <53>, - <53>, <53>, <53>, <53>, - <53>, <53>, <53>, <53>, - <53>, <53>, <53>, <53>, - <53>, <53>, <53>, <53>, - <53>, <53>, <53>, <53>, - <53>, <53>, <53>, <53>; pinctrl-names = "default"; pinctrl-0 = <&mdio1_gpio>, <&spi0_gpio>, <&can0_gpio>, <&pcie_gpio>, <&qspi_gpio>, <&uart3_gpio>, <&uart4_gpio>, <&can1_gpio>;
@@ -107,6 +89,35 @@ &gpio2 { "DIP4", "USR_IO11", "", "", "SWITCH1", "", "", ""; }; +&irqmux { + interrupt-map = <0 &plic 13>, <1 &plic 14>, <2 &plic 15>, + <3 &plic 16>, <4 &plic 17>, <5 &plic 18>, + <6 &plic 19>, <7 &plic 20>, <8 &plic 21>, + <9 &plic 22>, <10 &plic 23>, <11 &plic 24>, + <12 &plic 25>, <13 &plic 26>, + + <32 &plic 27>, <33 &plic 28>, <34 &plic 29>, + <35 &plic 30>, <36 &plic 31>, <37 &plic 32>, + <38 &plic 33>, <39 &plic 34>, <40 &plic 35>, + <41 &plic 36>, <42 &plic 37>, <43 &plic 38>, + <44 &plic 39>, <45 &plic 40>, <46 &plic 41>, + <47 &plic 42>, <48 &plic 43>, <49 &plic 44>, + <50 &plic 45>, <51 &plic 46>, <52 &plic 47>, + <53 &plic 48>, <54 &plic 49>, <55 &plic 50>, + + <64 &plic 53>, <65 &plic 53>, <66 &plic 53>, + <67 &plic 53>, <68 &plic 53>, <69 &plic 53>, + <70 &plic 53>, <71 &plic 53>, <72 &plic 53>, + <73 &plic 53>, <74 &plic 53>, <75 &plic 53>, + <76 &plic 53>, <77 &plic 53>, <78 &plic 53>, + <79 &plic 53>, <80 &plic 53>, <81 &plic 53>, + <82 &plic 53>, <83 &plic 53>, <84 &plic 53>, + <85 &plic 53>, <86 &plic 53>, <87 &plic 53>, + <88 &plic 53>, <89 &plic 53>, <90 &plic 53>, + <91 &plic 53>, <92 &plic 53>, <93 &plic 53>, + <94 &plic 53>, <95 &plic 53>; +}; + &mac0 { status = "okay"; phy-mode = "sgmii";
arch/riscv/boot/dts/microchip/pic64gx.dtsi +29 -3
@@ -295,6 +295,14 @@ mss_top_sysreg: syscon@20002000 { #size-cells = <1>; #reset-cells = <1>; + irqmux: interrupt-controller@54 { + compatible = "microchip,pic64gx-irqmux", "microchip,mpfs-irqmux"; + reg = <0x54 0x4>; + #address-cells = <0>; + #interrupt-cells = <1>; + interrupt-map-mask = <0x7f>; + }; + iomux0: pinctrl@200 { compatible = "microchip,pic64gx-pinctrl-iomux0", "microchip,mpfs-pinctrl-iomux0";
@@ -484,9 +492,13 @@ mac1: ethernet@20112000 { gpio0: gpio@20120000 { compatible = "microchip,pic64gx-gpio", "microchip,mpfs-gpio"; reg = <0x0 0x20120000 0x0 0x1000>; - interrupt-parent = <&plic>; + interrupt-parent = <&irqmux>; interrupt-controller; #interrupt-cells = <1>; + interrupts = <0>, <1>, <2>, <3>, + <4>, <5>, <6>, <7>, + <8>, <9>, <10>, <11>, + <12>, <13>; clocks = <&clkcfg CLK_GPIO0>; gpio-controller; #gpio-cells = <2>;
@@ -497,9 +509,15 @@ gpio0: gpio@20120000 { gpio1: gpio@20121000 { compatible = "microchip,pic64gx-gpio", "microchip,mpfs-gpio"; reg = <0x0 0x20121000 0x0 0x1000>; - interrupt-parent = <&plic>; + interrupt-parent = <&irqmux>; interrupt-controller; #interrupt-cells = <1>; + interrupts = <32>, <33>, <34>, <35>, + <36>, <37>, <38>, <39>, + <40>, <41>, <42>, <43>, + <44>, <45>, <46>, <47>, + <48>, <49>, <50>, <51>, + <52>, <53>, <54>, <55>; clocks = <&clkcfg CLK_GPIO1>; gpio-controller; #gpio-cells = <2>;
@@ -510,9 +528,17 @@ gpio1: gpio@20121000 { gpio2: gpio@20122000 { compatible = "microchip,pic64gx-gpio", "microchip,mpfs-gpio"; reg = <0x0 0x20122000 0x0 0x1000>; - interrupt-parent = <&plic>; + interrupt-parent = <&irqmux>; interrupt-controller; #interrupt-cells = <1>; + interrupts = <64>, <65>, <66>, <67>, + <68>, <69>, <70>, <71>, + <72>, <73>, <74>, <75>, + <76>, <77>, <78>, <79>, + <80>, <81>, <82>, <83>, + <84>, <85>, <86>, <87>, + <88>, <89>, <90>, <91>, + <92>, <93>, <94>, <95>; clocks = <&clkcfg CLK_GPIO2>; gpio-controller; #gpio-cells = <2>;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 146/2077 riscv: dts: microchip: fix pic64gx gpio interrupt-cells
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Conor Dooley <[email protected]>
[ Upstream commit 48c7771b3c792b153872a2eff67e4cbcb77e4054 ]
As the pic64gx devicetree files got added in parallel to the GPIO interrupt-cells being fixed for PolarFire SoC, they didn't get changed to the correct values. Fix them now.
--- arch/riscv/boot/dts/microchip/pic64gx.dtsi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/riscv/boot/dts/microchip/pic64gx.dtsi +3 -3
@@ -494,7 +494,7 @@ gpio0: gpio@20120000 { reg = <0x0 0x20120000 0x0 0x1000>; interrupt-parent = <&irqmux>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; interrupts = <0>, <1>, <2>, <3>, <4>, <5>, <6>, <7>, <8>, <9>, <10>, <11>,
@@ -511,7 +511,7 @@ gpio1: gpio@20121000 { reg = <0x0 0x20121000 0x0 0x1000>; interrupt-parent = <&irqmux>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; interrupts = <32>, <33>, <34>, <35>, <36>, <37>, <38>, <39>, <40>, <41>, <42>, <43>,
@@ -530,7 +530,7 @@ gpio2: gpio@20122000 { reg = <0x0 0x20122000 0x0 0x1000>; interrupt-parent = <&irqmux>; interrupt-controller; - #interrupt-cells = <1>; + #interrupt-cells = <2>; interrupts = <64>, <65>, <66>, <67>, <68>, <69>, <70>, <71>, <72>, <73>, <74>, <75>,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 147/2077 arm64: dts: marvell: samsung-coreprimevelte: Increase touchscreen voltage
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Duje Mihanović <[email protected]>
[ Upstream commit 4da515eca1b8de56c9e8a17866626f99d9bccbc7 ]
The old 1.9V setting was found to be insufficient in certain environments (in my case cold ones), causing the touchscreen to register ghost touches and mostly ignore actual touches. Increase the voltage to 2.5V to correct the issue.
--- .../boot/dts/marvell/mmp/pxa1908-samsung-coreprimevelte.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/marvell/mmp/pxa1908-samsung-coreprimevelte.dts +1 -1
@@ -460,7 +460,7 @@ pmic@30 { regulators { ldo2: ldo2 { - regulator-min-microvolt = <1900000>; + regulator-min-microvolt = <2500000>; regulator-max-microvolt = <3100000>; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 148/2077 ARM: dts: rockchip: Add #{address,size}-cells to Chromium-based /firmware
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Brian Norris <[email protected]>
[ Upstream commit 98461edf564a35ee00a97a64f5463eaece586546 ]
Chromium/Depthcharge bootloaders may dynamically add a few device nodes to a system's DTB under a /firmware node. A typical DT looks something like the following:
/ {
firmware {
ranges;
coreboot {
compatible = "coreboot";
reg = <...>;
...;
};
};
};Notably, the /firmware node has an empty 'ranges', but does not have address/size-cells.
Commit 6e5773d52f4a ("of/address: Fix WARN when attempting translating non-translatable addresses") started requiring #address-cells for a device's parent if we want to use the reg resource in a device node. This leads to errors like the following:
[ 7.763870] coreboot_table firmware:coreboot: probe with driver coreboot_table failed with error -22
Add appropriate #{address,size}-cells to work around the problem.
Note that Google has also patched the Depthcharge bootloader source to add {address,size}-cells [1], but bootloader updates are typically delivered only via Google OS updates. Not all users install Google software updates, and even if they do, Google may not produce updated binaries for all/older devices.
[1] https://lore.kernel.org/all/[email protected]/
https://crrev.com/c/6051580 ("coreboot: Insert #address-cells and #size-cells for firmware node")
[On RK288-based Chromebooks there is no real other way than to load the
DTB together with its kernel when running a mainline kernel and as the whole line is EOL, there also won't be any updates to the bootloader that could fix that issue there.]
--- arch/arm/boot/dts/rockchip/rk3288-veyron.dtsi | 5 +++++ 1 file changed, 5 insertions(+)
arch/arm/boot/dts/rockchip/rk3288-veyron.dtsi +5 -0
@@ -18,6 +18,11 @@ chosen { stdout-path = "serial2:115200n8"; }; + firmware { + #address-cells = <1>; + #size-cells = <1>; + }; + /* * The default coreboot on veyron devices ignores memory@0 nodes * and would instead create another memory node.
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 149/2077 arm64: dts: rockchip: Add #{address,size}-cells to Chromium-based /firmware
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Brian Norris <[email protected]>
[ Upstream commit 0b74f1a037672980c477bbe6b3848fb5341eb4f1 ]
Chromium/Depthcharge bootloaders may dynamically add a few device nodes to a system's DTB under a /firmware node. A typical DT looks something like the following:
## From a RK3399 Gru/Kevin Chromebook:
# find /sys/firmware/devicetree/base/firmware /sys/firmware/devicetree/base/firmware /sys/firmware/devicetree/base/firmware/coreboot /sys/firmware/devicetree/base/firmware/coreboot/ram-code /sys/firmware/devicetree/base/firmware/coreboot/compatible /sys/firmware/devicetree/base/firmware/coreboot/board-id /sys/firmware/devicetree/base/firmware/coreboot/reg /sys/firmware/devicetree/base/firmware/coreboot/name /sys/firmware/devicetree/base/firmware/chromeos /sys/firmware/devicetree/base/firmware/chromeos/readonly-firmware-version /sys/firmware/devicetree/base/firmware/chromeos/active-ec-firmware /sys/firmware/devicetree/base/firmware/chromeos/firmware-version /sys/firmware/devicetree/base/firmware/chromeos/nonvolatile-context-storage /sys/firmware/devicetree/base/firmware/chromeos/vboot-shared-data /sys/firmware/devicetree/base/firmware/chromeos/nonvolatile-context-size /sys/firmware/devicetree/base/firmware/chromeos/nonvolatile-context-offset /sys/firmware/devicetree/base/firmware/chromeos/hardware-id /sys/firmware/devicetree/base/firmware/chromeos/compatible /sys/firmware/devicetree/base/firmware/chromeos/firmware-type /sys/firmware/devicetree/base/firmware/chromeos/fmap-offset /sys/firmware/devicetree/base/firmware/chromeos/name /sys/firmware/devicetree/base/firmware/ranges /sys/firmware/devicetree/base/firmware/name
The /firmware node has an empty 'ranges', but does not have address/size-cells.
Commit 6e5773d52f4a ("of/address: Fix WARN when attempting translating non-translatable addresses") started requiring #address-cells for a device's parent if we want to use the reg resource in a device node. This leads to errors like the following:
[ 7.763870] coreboot_table firmware:coreboot: probe with driver coreboot_table failed with error -22
Add appropriate #{address,size}-cells to work around the problem.
Note that Google has also patched the Depthcharge bootloader source to add {address,size}-cells [1], but bootloader updates are typically delivered only via Google OS updates. Not all users install Google software updates, and even if they do, Google may not produce updated binaries for all/older devices.
[1] https://lore.kernel.org/all/[email protected]/
https://crrev.com/c/6051580 ("coreboot: Insert #address-cells and #size-cells for firmware node")
[On RK3399-based Chromebooks there is no real other way than to load the
DTB together with its kernel when running a mainline kernel and as the whole line is EOL, there also won't be any updates to the bootloader that could fix that issue there.]
--- arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 5 +++++ 1 file changed, 5 insertions(+)
arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi +5 -0
@@ -18,6 +18,11 @@ chosen { stdout-path = "serial2:115200n8"; }; + firmware { + #address-cells = <2>; + #size-cells = <2>; + }; + /* * Power Tree *
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 150/2077 arm64: dts: rockchip: fix rk809 interrupt pin on rk3566-roc-pc
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Weixin Guo <[email protected]>
[ Upstream commit 460bac478c5fe69054ffc60d607bba03bcaf909b ]
The RK809 PMIC interrupt pin on the Firefly ROC-RK3566-PC (Station M2) is physically connected to GPIO0_A3 (RK_PA3) according to the board's schematic.
Currently, the PMIC node incorrectly specifies RK_PA7 for the interrupt, which prevents the PMIC from correctly signaling interrupts. (Note that the pinctrl node 'pmic_int' correctly configures RK_PA3).
Fix this by updating the interrupts property to use RK_PA3.
--- arch/arm64/boot/dts/rockchip/rk3566-roc-pc.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/rockchip/rk3566-roc-pc.dts +1 -1
@@ -245,7 +245,7 @@ rk809: pmic@20 { compatible = "rockchip,rk809"; reg = <0x20>; interrupt-parent = <&gpio0>; - interrupts = <RK_PA7 IRQ_TYPE_LEVEL_LOW>; + interrupts = <RK_PA3 IRQ_TYPE_LEVEL_LOW>; clock-output-names = "rk808-clkout1", "rk808-clkout2"; assigned-clocks = <&cru I2S1_MCLKOUT_TX>; assigned-clock-parents = <&cru CLK_I2S1_8CH_TX>;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 151/2077 arm64: dts: imx8x-colibri: Correct SODIMM PAD settings
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peng Fan <[email protected]>
[ Upstream commit 0a03ee38a262cab0d9754e9947d565e089a9f7a5 ]
SION is BIT(30), not BIT(26). Correct it.
--- arch/arm64/boot/dts/freescale/imx8x-colibri.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm64/boot/dts/freescale/imx8x-colibri.dtsi +2 -2
@@ -631,12 +631,12 @@ pinctrl_adc0: adc0grp { */ pinctrl_atmel_adap: atmeladaptergrp { fsl,pins = <IMX8QXP_UART1_RX_LSIO_GPIO0_IO22 0x21>, /* SODIMM 30 */ - <IMX8QXP_UART1_TX_LSIO_GPIO0_IO21 0x4000021>; /* SODIMM 28 */ + <IMX8QXP_UART1_TX_LSIO_GPIO0_IO21 0x40000021>; /* SODIMM 28 */ }; /* Atmel MXT touchsceen + boards with built-in Capacitive Touch Connector */ pinctrl_atmel_conn: atmelconnectorgrp { - fsl,pins = <IMX8QXP_QSPI0B_DATA2_LSIO_GPIO3_IO20 0x4000021>, /* SODIMM 107 */ + fsl,pins = <IMX8QXP_QSPI0B_DATA2_LSIO_GPIO3_IO20 0x40000021>, /* SODIMM 107 */ <IMX8QXP_QSPI0B_SS1_B_LSIO_GPIO3_IO24 0x21>; /* SODIMM 106 */ };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 152/2077 arm64: dts: imx8mn-vhip4-evalboard-v1: Correct interrupt flags
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Krzysztof Kozlowski <[email protected]>
[ Upstream commit 895e7756cdc1ba6467eb37eba31c1358243f6ad9 ]
GPIO_ACTIVE_x flags are not correct in the context of interrupt flags. These are simple defines so they could be used in DTS but they will not have the same meaning:
1. GPIO_ACTIVE_HIGH = 0 => IRQ_TYPE_NONE
2. GPIO_ACTIVE_LOW = 1 => IRQ_TYPE_EDGE_RISING
Correct the interrupt flags, assuming the author of the code wanted the same logical behavior behind the name "ACTIVE_xxx", this is:ACTIVE_LOW => IRQ_TYPE_LEVEL_LOW
--- arch/arm64/boot/dts/freescale/imx8mn-vhip4-evalboard-v1.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/freescale/imx8mn-vhip4-evalboard-v1.dts +1 -1
@@ -112,7 +112,7 @@ &i2c3 { &ifm_pmic { interrupt-parent = <&gpio2>; - interrupts = <0 GPIO_ACTIVE_LOW>; + interrupts = <0 IRQ_TYPE_LEVEL_LOW>; }; &iomuxc {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 153/2077 arm64: dts: imx8mn-vhip4-evalboard-v2: Correct interrupt flags
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Krzysztof Kozlowski <[email protected]>
[ Upstream commit 7263f1acdd33169e1558064ee9a98758921f3bec ]
GPIO_ACTIVE_x flags are not correct in the context of interrupt flags. These are simple defines so they could be used in DTS but they will not have the same meaning:
1. GPIO_ACTIVE_HIGH = 0 => IRQ_TYPE_NONE
2. GPIO_ACTIVE_LOW = 1 => IRQ_TYPE_EDGE_RISING
Correct the interrupt flags, assuming the author of the code wanted the same logical behavior behind the name "ACTIVE_xxx", this is:ACTIVE_LOW => IRQ_TYPE_LEVEL_LOW
--- arch/arm64/boot/dts/freescale/imx8mn-vhip4-evalboard-v2.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/freescale/imx8mn-vhip4-evalboard-v2.dts +1 -1
@@ -99,7 +99,7 @@ &i2c3 { &ifm_pmic { interrupt-parent = <&gpio5>; - interrupts = <17 GPIO_ACTIVE_LOW>; + interrupts = <17 IRQ_TYPE_LEVEL_LOW>; }; &iomuxc {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 154/2077 arm64: dts: imx8mp-ab2: Correct interrupt flags
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Krzysztof Kozlowski <[email protected]>
[ Upstream commit eb27f9b9a4b2965f8d497a3c565cfbc2473c184b ]
GPIO_ACTIVE_x flags are not correct in the context of interrupt flags. These are simple defines so they could be used in DTS but they will not have the same meaning:
1. GPIO_ACTIVE_HIGH = 0 => IRQ_TYPE_NONE
2. GPIO_ACTIVE_LOW = 1 => IRQ_TYPE_EDGE_RISING
Correct the interrupt flags, assuming the author of the code wanted the same logical behavior behind the name "ACTIVE_xxx", this is:ACTIVE_LOW => IRQ_TYPE_LEVEL_LOW
--- arch/arm64/boot/dts/freescale/imx8mp-ab2.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/freescale/imx8mp-ab2.dts +1 -1
@@ -281,7 +281,7 @@ pca9450: pmic@25 { compatible = "nxp,pca9450c"; reg = <0x25>; interrupt-parent = <&gpio1>; - interrupts = <3 GPIO_ACTIVE_LOW>; + interrupts = <3 IRQ_TYPE_LEVEL_LOW>; pinctrl-0 = <&pinctrl_pmic>; regulators {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 155/2077 Revert "arm64: dts: imx8mm-kontron: Add support for reading SD_VSEL signal"
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peng Fan <[email protected]>
[ Upstream commit aa907ee010e396c0c0d31d60495ace6e531ceec9 ]
This reverts commit 8472751c4d96b558d60d0f6aede6b24b64bcb3c9.
The board uses SDHC VSELECT to automatically switch between 1.8v and 3.3v. It does not use GPIO to control the PMIC SD_VSEL signal. The original commit intends to read back SD_VSEL value from GPIO, but it is wrong. When MUX is configured as SDHC VSELECT, it is impossible to read back the value from GPIO controller. Setting SION could only enable the input path for the mux function. It could not redirect the input to GPIO.
And value "0x40000d0" is wrong, SION is BIT30, not BIT26.
--- arch/arm64/boot/dts/freescale/imx8mm-kontron-bl.dts | 10 +++------- .../arm64/boot/dts/freescale/imx8mm-kontron-osm-s.dtsi | 7 +++---- 2 files changed, 6 insertions(+), 11 deletions(-)
arch/arm64/boot/dts/freescale/imx8mm-kontron-bl.dts +3 -7
@@ -254,10 +254,6 @@ &pwm2 { status = "okay"; }; -®_nvcc_sd { - sd-vsel-gpios = <&gpio1 4 GPIO_ACTIVE_HIGH>; -}; - &uart1 { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_uart1>;
@@ -466,7 +462,7 @@ MX8MM_IOMUXC_SD2_DATA1_USDHC2_DATA1 0x1d0 MX8MM_IOMUXC_SD2_DATA2_USDHC2_DATA2 0x1d0 MX8MM_IOMUXC_SD2_DATA3_USDHC2_DATA3 0x1d0 MX8MM_IOMUXC_SD2_CD_B_GPIO2_IO12 0x19 - MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0x40000d0 + MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0xd0 >; };
@@ -479,7 +475,7 @@ MX8MM_IOMUXC_SD2_DATA1_USDHC2_DATA1 0x1d4 MX8MM_IOMUXC_SD2_DATA2_USDHC2_DATA2 0x1d4 MX8MM_IOMUXC_SD2_DATA3_USDHC2_DATA3 0x1d4 MX8MM_IOMUXC_SD2_CD_B_GPIO2_IO12 0x19 - MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0x40000d0 + MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0xd0 >; };
@@ -492,7 +488,7 @@ MX8MM_IOMUXC_SD2_DATA1_USDHC2_DATA1 0x1d6 MX8MM_IOMUXC_SD2_DATA2_USDHC2_DATA2 0x1d6 MX8MM_IOMUXC_SD2_DATA3_USDHC2_DATA3 0x1d6 MX8MM_IOMUXC_SD2_CD_B_GPIO2_IO12 0x19 - MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0x40000d0 + MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0xd0 >; }; };
arch/arm64/boot/dts/freescale/imx8mm-kontron-osm-s.dtsi +3 -4
@@ -342,7 +342,6 @@ reg_nvcc_sd: LDO5 { regulator-name = "NVCC_SD (LDO5)"; regulator-min-microvolt = <1800000>; regulator-max-microvolt = <3300000>; - sd-vsel-gpios = <&gpio1 4 GPIO_ACTIVE_HIGH>; }; }; };
@@ -795,7 +794,7 @@ MX8MM_IOMUXC_SD2_DATA1_USDHC2_DATA1 0x1d0 /* SDIO_A_D1 */ MX8MM_IOMUXC_SD2_DATA2_USDHC2_DATA2 0x1d0 /* SDIO_A_D2 */ MX8MM_IOMUXC_SD2_DATA3_USDHC2_DATA3 0x1d0 /* SDIO_A_D3 */ MX8MM_IOMUXC_SD2_WP_USDHC2_WP 0x400000d6 /* SDIO_A_WP */ - MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0x40000090 + MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0x90 >; };
@@ -808,7 +807,7 @@ MX8MM_IOMUXC_SD2_DATA1_USDHC2_DATA1 0x1d4 /* SDIO_A_D1 */ MX8MM_IOMUXC_SD2_DATA2_USDHC2_DATA2 0x1d4 /* SDIO_A_D2 */ MX8MM_IOMUXC_SD2_DATA3_USDHC2_DATA3 0x1d4 /* SDIO_A_D3 */ MX8MM_IOMUXC_SD2_WP_USDHC2_WP 0x400000d6 /* SDIO_A_WP */ - MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0x40000090 + MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0x90 >; };
@@ -821,7 +820,7 @@ MX8MM_IOMUXC_SD2_DATA1_USDHC2_DATA1 0x1d6 /* SDIO_A_D1 */ MX8MM_IOMUXC_SD2_DATA2_USDHC2_DATA2 0x1d6 /* SDIO_A_D2 */ MX8MM_IOMUXC_SD2_DATA3_USDHC2_DATA3 0x1d6 /* SDIO_A_D3 */ MX8MM_IOMUXC_SD2_WP_USDHC2_WP 0x400000d6 /* SDIO_A_WP */ - MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0x40000090 + MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0x90 >; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 156/2077 Revert "arm64: dts: imx8mp-kontron: Add support for reading SD_VSEL signal"
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peng Fan <[email protected]>
[ Upstream commit 22465a195af370ed6311be3adee479fb7c683685 ]
This reverts commit 39e4189d9d63a0b6fc15458ce0136e99ecdfb1b8.
The board uses SDHC VSELECT to automatically switch between 1.8v and 3.3v. It does not use GPIO to control the PMIC SD_VSEL signal. The original commit intends to read back SD_VSEL value from GPIO, but it is wrong. When MUX is configured as SDHC VSELECT, it is impossible to read back the value from GPIO controller. Setting SION could only enable the input path for the mux function. It could not redirect the input to GPIO.
--- arch/arm64/boot/dts/freescale/imx8mp-kontron-osm-s.dtsi | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
arch/arm64/boot/dts/freescale/imx8mp-kontron-osm-s.dtsi +3 -4
@@ -311,7 +311,6 @@ reg_nvcc_sd: LDO5 { regulator-name = "NVCC_SD (LDO5)"; regulator-min-microvolt = <1800000>; regulator-max-microvolt = <3300000>; - sd-vsel-gpios = <&gpio1 4 GPIO_ACTIVE_HIGH>; }; }; };
@@ -815,7 +814,7 @@ MX8MP_IOMUXC_SD2_DATA0__USDHC2_DATA0 0x1d0 /* SDIO_A_D0 */ MX8MP_IOMUXC_SD2_DATA1__USDHC2_DATA1 0x1d0 /* SDIO_A_D1 */ MX8MP_IOMUXC_SD2_DATA2__USDHC2_DATA2 0x1d0 /* SDIO_A_D2 */ MX8MP_IOMUXC_SD2_DATA3__USDHC2_DATA3 0x1d0 /* SDIO_A_D3 */ - MX8MP_IOMUXC_GPIO1_IO04__USDHC2_VSELECT 0x400001d0 + MX8MP_IOMUXC_GPIO1_IO04__USDHC2_VSELECT 0x1d0 >; };
@@ -827,7 +826,7 @@ MX8MP_IOMUXC_SD2_DATA0__USDHC2_DATA0 0x1d4 /* SDIO_A_D0 */ MX8MP_IOMUXC_SD2_DATA1__USDHC2_DATA1 0x1d4 /* SDIO_A_D1 */ MX8MP_IOMUXC_SD2_DATA2__USDHC2_DATA2 0x1d4 /* SDIO_A_D2 */ MX8MP_IOMUXC_SD2_DATA3__USDHC2_DATA3 0x1d4 /* SDIO_A_D3 */ - MX8MP_IOMUXC_GPIO1_IO04__USDHC2_VSELECT 0x400001d0 + MX8MP_IOMUXC_GPIO1_IO04__USDHC2_VSELECT 0x1d0 >; };
@@ -839,7 +838,7 @@ MX8MP_IOMUXC_SD2_DATA0__USDHC2_DATA0 0x1d6 /* SDIO_A_D0 */ MX8MP_IOMUXC_SD2_DATA1__USDHC2_DATA1 0x1d6 /* SDIO_A_D1 */ MX8MP_IOMUXC_SD2_DATA2__USDHC2_DATA2 0x1d6 /* SDIO_A_D2 */ MX8MP_IOMUXC_SD2_DATA3__USDHC2_DATA3 0x1d6 /* SDIO_A_D3 */ - MX8MP_IOMUXC_GPIO1_IO04__USDHC2_VSELECT 0x400001d0 + MX8MP_IOMUXC_GPIO1_IO04__USDHC2_VSELECT 0x1d0 >; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 157/2077 vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kuniyuki Iwashima <[email protected]>
[ Upstream commit 30a45c0bffdd62350261e2f2689fdba426a33578 ]
udp_tunnel_sock_release() could set sk->sk_user_data to NULL while vxlan_gro_prepare_receive() is running.
Let's check if rcu_dereference_sk_user_data() is NULL after skb_gro_remcsum_init().
--- drivers/net/vxlan/vxlan_core.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
drivers/net/vxlan/vxlan_core.c +6 -2
@@ -657,14 +657,18 @@ static struct vxlanhdr *vxlan_gro_prepare_receive(struct sock *sk,struct sk_buff *skb, struct gro_remcsum *grc) { - struct sk_buff *p; struct vxlanhdr *vh, *vh2;unsigned int hlen, off_vx; -struct vxlan_sock *vs =rcu_dereference_sk_user_data (sk); +struct vxlan_sock *vs; +struct sk_buff *p;__be32 flags;skb_gro_remcsum_init (grc); + vs =rcu_dereference_sk_user_data (sk); +if (!vs) +return NULL ; + off_vx =skb_gro_offset (skb); hlen = off_vx +sizeof (*vh); vh =skb_gro_header (skb, hlen, off_vx);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 158/2077 drm: renesas: rz-du: mipi_dsi: Fix return path on error
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chris Brandt <[email protected]>
[ Upstream commit 79e1afecfe1afbfd06f63bf7bbe854a88155b7bd ]
In case of error, we should unwind correctly.
Switching to using dmam_ instead of dma_ and moving the code earlier fixes the issue.
--- drivers/gpu/drm/renesas/rz-du/rzg2l_mipi_dsi.c | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-)
drivers/gpu/drm/renesas/rz-du/rzg2l_mipi_dsi.c +5 -7
@@ -1441,6 +1441,11 @@ static int rzg2l_mipi_dsi_probe(struct platform_device *pdev)return dev_err_probe (dsi->dev,PTR_ERR (dsi->prstc),"failed to get prst\n" ); + dsi->dcs_buf_virt =dmam_alloc_coherent (dsi->dev,RZG2L_DCS_BUF_SIZE , + &dsi->dcs_buf_phys,GFP_KERNEL ); +if (!dsi->dcs_buf_virt) +return -ENOMEM ; +platform_set_drvdata (pdev, dsi);pm_runtime_enable (dsi->dev);
@@ -1473,11 +1478,6 @@ static int rzg2l_mipi_dsi_probe(struct platform_device *pdev)if (ret <0 ) goto err_pm_disable; - dsi->dcs_buf_virt =dma_alloc_coherent (dsi->host.dev,RZG2L_DCS_BUF_SIZE , - &dsi->dcs_buf_phys,GFP_KERNEL ); -if (!dsi->dcs_buf_virt) -return -ENOMEM ; -return 0 ; err_phy:
@@ -1492,8 +1492,6 @@ static void rzg2l_mipi_dsi_remove(struct platform_device *pdev) {struct rzg2l_mipi_dsi *dsi =platform_get_drvdata (pdev); -dma_free_coherent (dsi->host.dev,RZG2L_DCS_BUF_SIZE , dsi->dcs_buf_virt, - dsi->dcs_buf_phys);mipi_dsi_host_unregister (&dsi->host);pm_runtime_disable (&pdev->dev); }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 159/2077 alarmtimer: Remove stale return description from alarm_handle_timer()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhan Xusheng <[email protected]>
[ Upstream commit ed3b3c4976686b63b28e44f9805a88abc20ff18a ]
alarm_handle_timer() was converted from returning enum alarmtimer_restart to void, but the kernel-doc "Return:" line was not removed. Remove the stale description.
--- kernel/time/alarmtimer.c | 2 -- 1 file changed, 2 deletions(-)
kernel/time/alarmtimer.c +0 -2
@@ -512,8 +512,6 @@ static enum alarmtimer_type clock2alarm(clockid_t clockid)* @now: time at the timer expiration * * Posix timer callback for expired alarm timers. -* -* Return: whether the timer is to be restarted */ static void alarm_handle_timer (struct alarm *alarm,ktime_t now) {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 160/2077 OPP: Fix race between OPP addition and lookup
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Di Shen <[email protected]>
[ Upstream commit f5e1cc9a284bff2510981643a5bca4bc4c21b81a ]
A race exists between dev_pm_opp_add_dynamic() and dev_pm_opp_find_freq_exact():
CPU0 (add) CPU1 (lookup)
------------------------------- ------------------------------
_opp_add()
mutex_lock()
list_add(&new_opp->node, head)
mutex_unlock() _opp_table_find_key()
mutex_lock()
dev_pm_opp_get(opp)
kref_get()
mutex_unlock()
kref_init(&new_opp->kref)
dev_pm_opp_put()
kref_put_mutex()The newly added OPP is inserted into the list before its kref is initialized. A concurrent lookup can find this OPP and increment its reference count while it is still uninitialized, leading to refcount corruption and a potential premature free.
Fix this by initializing ->kref and ->opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup observes a fully initialized object.
--- drivers/opp/core.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
drivers/opp/core.c +2 -3
@@ -2088,11 +2088,10 @@ int _opp_add(struct device *dev, struct dev_pm_opp *new_opp,return ret;list_add (&new_opp->node, head); + new_opp->opp_table = opp_table; +kref_init (&new_opp->kref); } - new_opp->opp_table = opp_table; -kref_init (&new_opp->kref); -opp_debug_create_one (new_opp, opp_table);if (!_opp_supported_by_regulators (new_opp, opp_table)) {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 161/2077 crypto: ccp - Reverse the cleanup order in psp_dev_destroy()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tycho Andersen (AMD) <[email protected]>
[ Upstream commit 4a76a164ba1617f60d1c8a2fd754466c9d9e48e9 ]
Before SNP x86 shutdown [1], all HV_FIXED pages were always leaked on module unload. Now pages can be reclaimed if they are freed before SNP shutdown.
The SFS driver does sfs_dev_destroy() -> snp_free_hv_fixed_pages(), marking the command buffer as free. But this happens after sev_dev_destroy() in psp_dev_destroy(), so the pages are always leaked.
Rearrange psp_dev_destroy() to destroy things in the reverse order from psp_init(), so that any dependencies can be unwound accordingly. This lets SFS free the page and the subsequent SNP shutdown release it.
This was identified with use of Chris Mason's review-prompts:
https://github.com/masoncl/review-prompts
[1]: https://lore.kernel.org/all/[email protected]/
--- drivers/crypto/ccp/psp-dev.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/crypto/ccp/psp-dev.c +4 -4
@@ -316,15 +316,15 @@ void psp_dev_destroy(struct sp_device *sp)if (!psp)return ; -sev_dev_destroy (psp); +dbc_dev_destroy (psp); -tee_dev_destroy (psp); +platform_access_dev_destroy (psp);sfs_dev_destroy (psp); -dbc_dev_destroy (psp); +tee_dev_destroy (psp); -platform_access_dev_destroy (psp); +sev_dev_destroy (psp);sp_free_psp_irq (sp, psp);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 162/2077 crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tycho Andersen (AMD) <[email protected]>
[ Upstream commit 1b864b6cb213bbd7b406e9b2e98c962077f300df ]
Sashiko notes:
Quoted 9 lines
regarding the bounds check in
snp_filter_reserved_mem_regions()called viawalk_iomem_res_desc(): does the check
if ((range_list->num_elements* 16 + 8) >PAGE_SIZE) allow an off-by-one heap buffer overflow?If
range_list->num_elementsis 255, 255 * 16 + 8 = 4088, which is <= 4096. Writingrange->base(8 bytes) fills 4088-4095, but writingrange->page_count(4 bytes) would write to 4096-4099, overflowing the kzalloc-allocatedPAGE_SIZEbuffer.
Fix this by accounting for the entry about to be written to, in addition to the entries that are already allocated.
--- drivers/crypto/ccp/sev-dev.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
drivers/crypto/ccp/sev-dev.c +4 -3
@@ -1328,10 +1328,11 @@ static int snp_filter_reserved_mem_regions(struct resource *rs, void *arg)size_t size;/* -* Ensure the list of HV_FIXED pages that will be passed to firmware -* do not exceed the page-sized argument buffer. +* Ensure the list of HV_FIXED pages passed to the firmware including +* the one about to be written to do not exceed the page-sized argument +* buffer. */ -if ((range_list->num_elements *sizeof (struct sev_data_range ) + +if (((range_list->num_elements +1 ) *sizeof (struct sev_data_range ) +sizeof (struct sev_data_range_list )) >PAGE_SIZE )return -E2BIG ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 163/2077 crypto: ccp - Check for page allocation failure correctly in TIO
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tycho Andersen (AMD) <[email protected]>
[ Upstream commit a8d5370eef00eca132a292b1901c9914c817e385 ]
Sashiko notes:
Quoted 7 lines
if
__snp_alloc_firmware_pages()returns NULL under memory pressure, is it safe to pass it directly topage_address()?On architectures without
HASHED_PAGE_VIRTUAL,page_address(NULL)might compute a deterministic but invalid, non-zero virtual address. The subsequent if (tio_status) check would then evaluate to true, andsev_tsm_init_locked()would dereference the invalid pointer.
Indeed, page_address(NULL) will return non-NULL garbage here. Fix this by checking the page allocation itself for NULL, not the resulting virtual address.
--- drivers/crypto/ccp/sev-dev.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
drivers/crypto/ccp/sev-dev.c +8 -4
@@ -1488,6 +1488,8 @@ static int __sev_snp_init_locked(int *error, unsigned int max_snp_asid) &snp_panic_notifier);if (data.tio_en) { +struct page *page; +/* * This executes with the sev_cmd_mutex held so down the stack * snp_reclaim_pages(locked=false) might be needed (which is extremely
@@ -1495,12 +1497,14 @@ static int __sev_snp_init_locked(int *error, unsigned int max_snp_asid)* Instead of exporting __snp_alloc_firmware_pages(), allocate a page * for this one call here. */ -void *tio_status =page_address (__snp_alloc_firmware_pages ( -GFP_KERNEL_ACCOUNT | __GFP_ZERO,0 , true)); + page =__snp_alloc_firmware_pages (GFP_KERNEL_ACCOUNT | __GFP_ZERO, +0 , true); +if (page) { +void *tio_status =page_address (page); -if (tio_status) {sev_tsm_init_locked (sev, tio_status); -__snp_free_firmware_pages (virt_to_page (tio_status),0 , true); + +__snp_free_firmware_pages (page,0 , true); } }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 164/2077 crypto: ccp - Initialize data during __sev_snp_init_locked()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tycho Andersen (AMD) <[email protected]>
[ Upstream commit fed613c1230277105bb512bce6e1fda8f316d178 ]
Sashiko notes:
Quoted 4 lines
is the stack variable data left uninitialized when taking the else branch? Since data.tio_en is later evaluated unconditionally, could stack garbage cause it to evaluate to true, leading to erroneous attempts to allocate pages and initialize SEV-TIO on unsupported hardware?
If the firmware is too old to support SEV_INIT_EX, data is left uninitialized but used in the debug logging about whether TIO is enabled or not.
--- drivers/crypto/ccp/sev-dev.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/crypto/ccp/sev-dev.c +1 -3
@@ -1356,7 +1356,7 @@ static int __sev_snp_init_locked(int *error, unsigned int max_snp_asid) { struct sev_data_range_list *snp_range_list __free(kfree) = NULL;struct psp_device *psp = psp_master; -struct sev_data_snp_init_ex data; +struct sev_data_snp_init_ex data = {};struct sev_device *sev;void *arg = &data;int cmd, rc =0 ;
@@ -1420,8 +1420,6 @@ static int __sev_snp_init_locked(int *error, unsigned int max_snp_asid)*/ snp_add_hv_fixed_pages (sev, snp_range_list); -memset (&data,0 ,sizeof (data)); -if (max_snp_asid) { data.ciphertext_hiding_en =1 ; data.max_snp_asid = max_snp_asid;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 165/2077 crypto: atmel-sha204a - fix blocking and non-blocking rng logic
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lothar Rubusch <[email protected]>
[ Upstream commit 319400fc5ee15db5793aa45f854968141326effc ]
The blocking and non-blocking paths were failing to provide valid entropy due to improper buffer management. Reading the buffer starting from byte 1, only fetch the 32 bytes of random data from the return message.
Tested on an Atmel SHA204A device.
Before (here for blocking), tests showed repeatedly reading reduced bytes.
$ head -c 32 /dev/hwrng | hexdump -C 00000000 02 28 85 b3 47 40 f2 ee 00 00 00 00 00 00 00 00 |.(..G@..........| 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000020
After, the result will be similar to the following:
$ head -c 32 /dev/hwrng | hexdump -C 00000000 5a fc 3f 13 14 68 fe 06 68 0a bd 04 83 6e 09 69 |Z.?..h..h....n.i| 00000010 75 ff cf 87 10 84 3b c9 c1 df ae eb 45 53 4c c3 |u.....;.....ESL.| 00000020
--- drivers/crypto/atmel-sha204a.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/crypto/atmel-sha204a.c +4 -4
@@ -54,8 +54,8 @@ static int atmel_sha204a_rng_read_nonblocking(struct hwrng *rng, void *data,if (rng->priv) { work_data = (struct atmel_i2c_work_data *)rng->priv; - max =min (sizeof (work_data->cmd.data), max); -memcpy (data, &work_data->cmd.data, max); + max =min (RANDOM_RSP_SIZE -CMD_OVERHEAD_SIZE , max); +memcpy (data, &work_data->cmd.data[RSP_DATA_IDX ], max); rng->priv =0 ; }else { work_data =kmalloc_obj (*work_data,GFP_ATOMIC );
@@ -93,8 +93,8 @@ static int atmel_sha204a_rng_read(struct hwrng *rng, void *data, size_t max,if (ret)return ret; - max =min (sizeof (cmd.data), max); -memcpy (data, cmd.data, max); + max =min (RANDOM_RSP_SIZE -CMD_OVERHEAD_SIZE , max); +memcpy (data, &cmd.data[RSP_DATA_IDX ], max);return max; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 166/2077 crypto: ecrdsa - fix unknown OID check in ecrdsa_param_curve
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thorsten Blum <[email protected]>
[ Upstream commit 2d7b2cfc59998baf5e8622a24dc28f69a5212e06 ]
The ->curve_oid check in ecrdsa_param_curve() rejects the valid enum value 0 (OID_id_dsa_with_sha1), but look_up_OID() returns OID__NR on lookup failure. Compare ->curve_oid with OID__NR instead to ensure that only unknown OIDs return -EINVAL.
--- crypto/ecrdsa.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
crypto/ecrdsa.c +1 -1
@@ -145,7 +145,7 @@ int ecrdsa_param_curve(void *context, size_t hdrlen, unsigned char tag,struct ecrdsa_ctx *ctx = context; ctx->curve_oid =look_up_OID (value, vlen); -if (!ctx->curve_oid) +if (ctx->curve_oid ==OID__NR )return -EINVAL ; ctx->curve =get_curve_by_oid (ctx->curve_oid);return 0 ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 167/2077 crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Weiming Shi <[email protected]>
[ Upstream commit f7dd32c5179d7755de18e21d5674b08f9e5cb180 ]
pefile_digest_pe_contents() computes the trailing-data hash length as pelen - (hashed_bytes + certs_size). A crafted PE can make the addition exceed pelen, causing the unsigned subtraction to underflow to ~4 GiB. This is passed to crypto_shash_update() which reads out of bounds and panics on unmapped vmalloc guard pages.
BUG: unable to handle page fault for address: ffffc900038d8000 Oops: Oops: 0000 [#1] SMP KASAN NOPTI RIP: 0010:sha256_blocks_generic (lib/crypto/sha256.c:152) Call Trace: <TASK> __sha256_update (lib/crypto/sha256.c:208) crypto_sha256_update (crypto/sha256.c:142) verify_pefile_signature (crypto/asymmetric_keys/verify_pefile.c:436) kexec_kernel_verify_pe_sig (kernel/kexec_file.c:151) __do_sys_kexec_file_load (kernel/kexec_file.c:406) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) </TASK> Kernel panic - not syncing: Fatal exception
Validate that the addition does not overflow and the result does not exceed pelen before the subtraction. Return -ELIBBAD on failure.
--- crypto/asymmetric_keys/verify_pefile.c | 2 ++ 1 file changed, 2 insertions(+)
crypto/asymmetric_keys/verify_pefile.c +2 -0
@@ -305,6 +305,8 @@ static int pefile_digest_pe_contents(const void *pebuf, unsigned int pelen,if (pelen > hashed_bytes) { tmp = hashed_bytes + ctx->certs_size; +if (tmp <= hashed_bytes || pelen < tmp) +return -ELIBBAD ; ret =crypto_shash_update (desc, pebuf + hashed_bytes, pelen - tmp);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 168/2077 ARM: multi_v7_defconfig: Correct QCOM_RPMH and QCOM_RPMHPD
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Krzysztof Kozlowski <[email protected]>
[ Upstream commit 02802b40c31d2f2cfc94716189cfaf610930c589 ]
QCOM_RPMH and QCOM_RPMHPD can be build only as modules when QCOM_COMMAND_DB is module itself.
--- arch/arm/configs/multi_v7_defconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/configs/multi_v7_defconfig +2 -2
@@ -1155,7 +1155,7 @@ CONFIG_QCOM_COMMAND_DB=m CONFIG_QCOM_GSBI=y CONFIG_QCOM_OCMEM=m CONFIG_QCOM_RMTFS_MEM=m -CONFIG_QCOM_RPMH=y +CONFIG_QCOM_RPMH=m CONFIG_QCOM_SMEM=y CONFIG_QCOM_SMD_RPM=y CONFIG_QCOM_SMP2P=y
@@ -1170,7 +1170,7 @@ CONFIG_KEYSTONE_NAVIGATOR_DMA=y CONFIG_TI_PRUSS=m CONFIG_RASPBERRYPI_POWER=y CONFIG_QCOM_CPR=y -CONFIG_QCOM_RPMHPD=y +CONFIG_QCOM_RPMHPD=m CONFIG_QCOM_RPMPD=y CONFIG_ROCKCHIP_PM_DOMAINS=y CONFIG_TI_SCI_PM_DOMAINS=y
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 169/2077 accel/amdxdna: Fix clflush buffer size
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lizhi Hou <[email protected]>
[ Upstream commit ada61841caede131cc626f6cd28a60904296f248 ]
The firmware is told the buffer is req.buf_size bytes. It may read/write the entire region. If the CPU only flushes a subset, the remaining cache lines could contain stale data, causing the device to see garbage.
--- drivers/accel/amdxdna/aie2_message.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/accel/amdxdna/aie2_message.c +3 -3
@@ -390,7 +390,7 @@ int aie2_query_status(struct amdxdna_dev_hdl *ndev, char __user *buf, req.num_cols =hweight32 (aie_bitmap); req.aie_bitmap = aie_bitmap; -drm_clflush_virt_range (buff_addr, size);/* device can access */ +drm_clflush_virt_range (buff_addr, req.dump_buff_size);/* device can access */ ret =aie_send_mgmt_msg_wait (&ndev->aie, &msg);if (ret) {XDNA_ERR (xdna,"Error during NPU query, status %d" , ret);
@@ -442,7 +442,7 @@ int aie2_query_telemetry(struct amdxdna_dev_hdl *ndev, req.buf_size = buf_sz; req.type = header->type; -drm_clflush_virt_range (addr, size);/* device can access */ +drm_clflush_virt_range (addr, req.buf_size);/* device can access */ ret =aie_send_mgmt_msg_wait (&ndev->aie, &msg);if (ret) {XDNA_ERR (xdna,"Query telemetry failed, status %d" , ret);
@@ -1186,7 +1186,7 @@ int aie2_query_app_health(struct amdxdna_dev_hdl *ndev, u32 context_id, req.context_id = context_id; req.buf_size = buf_size; -drm_clflush_virt_range (buf,sizeof (*report)); +drm_clflush_virt_range (buf, req.buf_size); ret =aie_send_mgmt_msg_wait (&ndev->aie, &msg);if (ret) {XDNA_ERR (xdna,"Get app health failed, ret %d status 0x%x" , ret, resp.status);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 170/2077 dlm: fix add msg handle in send_queue ordered
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Aring <[email protected]>
[ Upstream commit d2248cb70c070f8f04762872772e155b59016f17 ]
In a benchmark scenario triggering a lot of requests that triggers a lot of DLM messages on the network it can be that the mh->seq is not ordered according the oldest seq number. This ordering is required by dlm_receive_ack as "before(mh->seq, seq)" will stop to check for older sequence numbers that are ordered in the tail of "node->send_queue".
The side effects of not having it correct ordered regarding "before(mh->seq, seq)" are refcounting issues and use-after free.
I only was able to reproduce this issue in a experimental DLM branch and a user space DLM benchmark that uses io_uring. After changing this I don't experienced any refcounting with the sending buffer issues anymore.
--- fs/dlm/midcomms.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/dlm/midcomms.c +2 -2
@@ -968,10 +968,10 @@ static void midcomms_new_msg_cb(void *data)atomic_inc (&mh->node->send_queue_cnt);spin_lock_bh (&mh->node->send_queue_lock); +/* need to be locked with list_add_tail_rcu() because list is ordered */ + mh->seq =atomic_fetch_inc (&mh->node->seq_send);list_add_tail_rcu (&mh->list, &mh->node->send_queue);spin_unlock_bh (&mh->node->send_queue_lock); - - mh->seq =atomic_fetch_inc (&mh->node->seq_send); } static struct dlm_msg *dlm_midcomms_get_msg_3_2(struct dlm_mhandle *mh, int nodeid,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 171/2077 nilfs2: fix backing_dev_info reference leak
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Shuangpeng Bai <[email protected]>
[ Upstream commit 665f192a2a11384cb7dc1be5f87d16438522a4ed ]
setup_bdev_super() already initializes sb->s_bdev and takes a reference on the block device backing_dev_info when assigning sb->s_bdi.
nilfs_fill_super() takes another reference to the same backing_dev_info and stores it in sb->s_bdi again. The extra reference is not paired with a matching bdi_put(), since generic_shutdown_super() releases sb->s_bdi only once.
Drop the redundant bdi_get() in nilfs_fill_super(). The single reference taken by setup_bdev_super() is enough and is released during superblock shutdown.
--- fs/nilfs2/super.c | 2 -- 1 file changed, 2 deletions(-)
fs/nilfs2/super.c +0 -2
@@ -1070,8 +1070,6 @@ nilfs_fill_super(struct super_block *sb, struct fs_context *fc) sb->s_time_gran =1 ; sb->s_max_links =NILFS_LINK_MAX ; - sb->s_bdi =bdi_get (sb->s_bdev->bd_disk->bdi); - err =load_nilfs (nilfs, sb);if (err) goto failed_nilfs;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 172/2077 ntb: Store original DMA address for future release
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Leon Romanovsky <[email protected]>
[ Upstream commit da6d997ac556479c112554ab5d95cbd04683eb11 ]
The DMA API requires that dma_free_attrs receive the exact dma_handle originally returned by the allocation function. Do not modify it.
--- drivers/ntb/ntb_transport.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/ntb/ntb_transport.c +3 -1
@@ -223,6 +223,7 @@ struct ntb_transport_mw {void *alloc_addr;void *virt_addr;dma_addr_t dma_addr; +dma_addr_t original_dma_addr; };struct ntb_transport_client_dev {
@@ -766,7 +767,7 @@ static void ntb_free_mw(struct ntb_transport_ctx *nt, int num_mw)ntb_mw_clear_trans (nt->ndev,PIDX , num_mw);dma_free_coherent (dma_dev, mw->alloc_size, - mw->alloc_addr, mw->dma_addr); + mw->alloc_addr, mw->original_dma_addr); mw->xlat_size =0 ; mw->buff_size =0 ; mw->alloc_size =0 ;
@@ -802,6 +803,7 @@ static int ntb_alloc_mw_buffer(struct ntb_transport_mw *mw,return -ENOMEM ; } virt_addr = alloc_addr; + mw->original_dma_addr = dma_addr;/* * we must ensure that the memory address allocated is BAR size
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 173/2077 ntb: Use consistent DMA attributes when freeing DMA mappings
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Leon Romanovsky <[email protected]>
[ Upstream commit 9d625aa2ebd445868955719e0abcf695b43f9318 ]
The counterpart of dma_alloc_attrs() is dma_free_attrs(), which must receive the same DMA attributes used during allocation. The code previously used dma_free_coherent(), which does not accept or apply any DMA attributes.
--- drivers/ntb/ntb_transport.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/ntb/ntb_transport.c +4 -4
@@ -766,8 +766,8 @@ static void ntb_free_mw(struct ntb_transport_ctx *nt, int num_mw)return ;ntb_mw_clear_trans (nt->ndev,PIDX , num_mw); -dma_free_coherent (dma_dev, mw->alloc_size, - mw->alloc_addr, mw->original_dma_addr); +dma_free_attrs (dma_dev, mw->alloc_size, mw->alloc_addr, + mw->original_dma_addr,DMA_ATTR_FORCE_CONTIGUOUS ); mw->xlat_size =0 ; mw->buff_size =0 ; mw->alloc_size =0 ;
@@ -828,8 +828,8 @@ static int ntb_alloc_mw_buffer(struct ntb_transport_mw *mw,return 0 ; err: -dma_free_coherent (ntb_dev, mw->alloc_size, alloc_addr, dma_addr); - +dma_free_attrs (ntb_dev, mw->alloc_size, alloc_addr, dma_addr, +DMA_ATTR_FORCE_CONTIGUOUS );return rc; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 174/2077 media: qcom: camss: vfe: fix PIX subdev naming on VFE lite
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wenmeng Liu <[email protected]>
[ Upstream commit c97e797a64cdfe4acecff831b4285418d2815893 ]
VFE lite hardware does not provide a functional PIX path, but after the per sub-device type resource changes the PIX subdev name is still assigned unconditionally.
Only assign the PIX subdev name on non-lite VFE variants to avoid exposing a misleading device name.
--- drivers/media/platform/qcom/camss/camss-vfe.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/platform/qcom/camss/camss-vfe.c +1 -1
@@ -2053,7 +2053,7 @@ int msm_vfe_register_entities(struct vfe_device *vfe,v4l2_subdev_init (sd, &vfe_v4l2_ops); sd->internal_ops = &vfe_v4l2_internal_ops; sd->flags |=V4L2_SUBDEV_FL_HAS_DEVNODE ; -if (i ==VFE_LINE_PIX ) +if (i ==VFE_LINE_PIX && vfe->res->is_lite == false)snprintf (sd->name,ARRAY_SIZE (sd->name),"%s%d_%s" ,MSM_VFE_NAME , vfe->id,"pix" );else
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 175/2077 dts: riscv: spacemit: correct 32k clock frequency
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yixun Lan <[email protected]>
[ Upstream commit 3c350f6284d8ea5e7a9648241b2e9604f2262d42 ]
The 32k oscillator's clock frequency is actually 32768Hz, so correct it.
--- arch/riscv/boot/dts/spacemit/k1.dtsi | 2 +- arch/riscv/boot/dts/spacemit/k3.dtsi | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
arch/riscv/boot/dts/spacemit/k1.dtsi +1 -1
@@ -333,7 +333,7 @@ vctcxo_3m: clock-3m { osc_32k: clock-32k { compatible = "fixed-clock"; - clock-frequency = <32000>; + clock-frequency = <32768>; clock-output-names = "osc_32k"; #clock-cells = <0>; };
arch/riscv/boot/dts/spacemit/k3.dtsi +1 -1
@@ -424,7 +424,7 @@ vctcxo_3m: clock-3m { osc_32k: clock-32k { compatible = "fixed-clock"; - clock-frequency = <32000>; + clock-frequency = <32768>; clock-output-names = "osc_32k"; #clock-cells = <0>; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 176/2077 arm64: dts: qcom: sdm660: set cdsp compute-cbs regs properly
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nickolay Goppen <[email protected]>
[ Upstream commit 708ab9d3bc5b74eeee767c678366624d3c02a4ec ]
Changing FastRPC compute-cbs' reg values to matching iommu streams solves SMMU translation errors when trying to use FastRPC on CDSP so change FastRPC compute-cbs' reg values that way
--- arch/arm64/boot/dts/qcom/sdm660.dtsi | 36 ++++++++++++++-------------- 1 file changed, 18 insertions(+), 18 deletions(-)
arch/arm64/boot/dts/qcom/sdm660.dtsi +18 -18
@@ -350,57 +350,57 @@ fastrpc { #address-cells = <1>; #size-cells = <0>; - compute-cb@5 { + compute-cb@3 { compatible = "qcom,fastrpc-compute-cb"; - reg = <5>; + reg = <3>; iommus = <&cdsp_smmu 3>; }; - compute-cb@6 { + compute-cb@4 { compatible = "qcom,fastrpc-compute-cb"; - reg = <6>; + reg = <4>; iommus = <&cdsp_smmu 4>; }; - compute-cb@7 { + compute-cb@5 { compatible = "qcom,fastrpc-compute-cb"; - reg = <7>; + reg = <5>; iommus = <&cdsp_smmu 5>; }; - compute-cb@8 { + compute-cb@6 { compatible = "qcom,fastrpc-compute-cb"; - reg = <8>; + reg = <6>; iommus = <&cdsp_smmu 6>; }; - compute-cb@9 { + compute-cb@7 { compatible = "qcom,fastrpc-compute-cb"; - reg = <9>; + reg = <7>; iommus = <&cdsp_smmu 7>; }; - compute-cb@10 { + compute-cb@8 { compatible = "qcom,fastrpc-compute-cb"; - reg = <10>; + reg = <8>; iommus = <&cdsp_smmu 8>; }; - compute-cb@11 { + compute-cb@9 { compatible = "qcom,fastrpc-compute-cb"; - reg = <11>; + reg = <9>; iommus = <&cdsp_smmu 9>; }; - compute-cb@12 { + compute-cb@10 { compatible = "qcom,fastrpc-compute-cb"; - reg = <12>; + reg = <10>; iommus = <&cdsp_smmu 10>; }; - compute-cb@13 { + compute-cb@11 { compatible = "qcom,fastrpc-compute-cb"; - reg = <13>; + reg = <11>; iommus = <&cdsp_smmu 11>; }; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 177/2077 arm64: dts: qcom: sdm630: set adsp compute-cbs regs properly
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nickolay Goppen <[email protected]>
[ Upstream commit e8e1fb5c703fc6962103ffdc60830df99351c139 ]
Changing FastRPC compute-cbs' reg values to matching iommu streams solves SMMU translation errors when trying to use FastRPC on ADSP so change FastRPC compute-cbs' reg values that way
--- arch/arm64/boot/dts/qcom/sdm630.dtsi | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
arch/arm64/boot/dts/qcom/sdm630.dtsi +8 -8
@@ -2459,27 +2459,27 @@ fastrpc { #address-cells = <1>; #size-cells = <0>; - compute-cb@1 { + compute-cb@3 { compatible = "qcom,fastrpc-compute-cb"; - reg = <1>; + reg = <3>; iommus = <&lpass_smmu 3>; }; - compute-cb@2 { + compute-cb@7 { compatible = "qcom,fastrpc-compute-cb"; - reg = <2>; + reg = <7>; iommus = <&lpass_smmu 7>; }; - compute-cb@3 { + compute-cb@8 { compatible = "qcom,fastrpc-compute-cb"; - reg = <3>; + reg = <8>; iommus = <&lpass_smmu 8>; }; - compute-cb@4 { + compute-cb@9 { compatible = "qcom,fastrpc-compute-cb"; - reg = <4>; + reg = <9>; iommus = <&lpass_smmu 9>; }; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 178/2077 arm64: dts: qcom: lemans: Move PCIe devices into soc node
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Shawn Guo <[email protected]>
[ Upstream commit 8222873cd4698627c08bffb2e40ba6f5a008fe32 ]
These PCIe devices with MMIO address should be inside soc node rather than outside.
--- arch/arm64/boot/dts/qcom/lemans.dtsi | 692 +++++++++++++-------------- 1 file changed, 346 insertions(+), 346 deletions(-)
arch/arm64/boot/dts/qcom/lemans.dtsi +346 -346
@@ -2694,6 +2694,352 @@ mmss_noc: interconnect@17a0000 { qcom,bcm-voters = <&apps_bcm_voter>; }; + pcie0: pcie@1c00000 { + compatible = "qcom,pcie-sa8775p"; + reg = <0x0 0x01c00000 0x0 0x3000>, + <0x0 0x40000000 0x0 0xf20>, + <0x0 0x40000f20 0x0 0xa8>, + <0x0 0x40001000 0x0 0x4000>, + <0x0 0x40100000 0x0 0x100000>, + <0x0 0x01c03000 0x0 0x1000>; + reg-names = "parf", "dbi", "elbi", "atu", "config", "mhi"; + device_type = "pci"; + + #address-cells = <3>; + #size-cells = <2>; + ranges = <0x01000000 0x0 0x00000000 0x0 0x40200000 0x0 0x100000>, + <0x02000000 0x0 0x40300000 0x0 0x40300000 0x0 0x1fd00000>; + bus-range = <0x00 0xff>; + + dma-coherent; + + linux,pci-domain = <0>; + num-lanes = <2>; + + interrupts = <GIC_SPI 307 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 308 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 309 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 312 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 313 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 314 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 374 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 375 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 306 IRQ_TYPE_LEVEL_HIGH>; + interrupt-names = "msi0", + "msi1", + "msi2", + "msi3", + "msi4", + "msi5", + "msi6", + "msi7", + "global"; + #interrupt-cells = <1>; + interrupt-map-mask = <0 0 0 0x7>; + interrupt-map = <0 0 0 1 &intc GIC_SPI 434 IRQ_TYPE_LEVEL_HIGH>, + <0 0 0 2 &intc GIC_SPI 435 IRQ_TYPE_LEVEL_HIGH>, + <0 0 0 3 &intc GIC_SPI 438 IRQ_TYPE_LEVEL_HIGH>, + <0 0 0 4 &intc GIC_SPI 439 IRQ_TYPE_LEVEL_HIGH>; + + clocks = <&gcc GCC_PCIE_0_AUX_CLK>, + <&gcc GCC_PCIE_0_CFG_AHB_CLK>, + <&gcc GCC_PCIE_0_MSTR_AXI_CLK>, + <&gcc GCC_PCIE_0_SLV_AXI_CLK>, + <&gcc GCC_PCIE_0_SLV_Q2A_AXI_CLK>; + + clock-names = "aux", + "cfg", + "bus_master", + "bus_slave", + "slave_q2a"; + + assigned-clocks = <&gcc GCC_PCIE_0_AUX_CLK>; + assigned-clock-rates = <19200000>; + + interconnects = <&pcie_anoc MASTER_PCIE_0 0 &mc_virt SLAVE_EBI1 0>, + <&gem_noc MASTER_APPSS_PROC 0 &config_noc SLAVE_PCIE_0 0>; + interconnect-names = "pcie-mem", "cpu-pcie"; + + iommu-map = <0x0 &pcie_smmu 0x0000 0x1>, + <0x100 &pcie_smmu 0x0001 0x1>; + + resets = <&gcc GCC_PCIE_0_BCR>, + <&gcc GCC_PCIE_0_LINK_DOWN_BCR>; + reset-names = "pci", + "link_down"; + + power-domains = <&gcc PCIE_0_GDSC>; + + phys = <&pcie0_phy>; + phy-names = "pciephy"; + + eq-presets-8gts = /bits/ 16 <0x5555 0x5555>; + eq-presets-16gts = /bits/ 8 <0x55 0x55>; + + status = "disabled"; + + pcieport0: pcie@0 { + device_type = "pci"; + reg = <0x0 0x0 0x0 0x0 0x0>; + bus-range = <0x01 0xff>; + + #address-cells = <3>; + #size-cells = <2>; + ranges; + }; + }; + + pcie0_ep: pcie-ep@1c00000 { + compatible = "qcom,sa8775p-pcie-ep"; + reg = <0x0 0x01c00000 0x0 0x3000>, + <0x0 0x40000000 0x0 0xf20>, + <0x0 0x40000f20 0x0 0xa8>, + <0x0 0x40001000 0x0 0x4000>, + <0x0 0x40200000 0x0 0x1fe00000>, + <0x0 0x01c03000 0x0 0x1000>, + <0x0 0x40005000 0x0 0x2000>; + reg-names = "parf", "dbi", "elbi", "atu", "addr_space", + "mmio", "dma"; + + clocks = <&gcc GCC_PCIE_0_AUX_CLK>, + <&gcc GCC_PCIE_0_CFG_AHB_CLK>, + <&gcc GCC_PCIE_0_MSTR_AXI_CLK>, + <&gcc GCC_PCIE_0_SLV_AXI_CLK>, + <&gcc GCC_PCIE_0_SLV_Q2A_AXI_CLK>; + + clock-names = "aux", + "cfg", + "bus_master", + "bus_slave", + "slave_q2a"; + + interrupts = <GIC_SPI 306 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 630 IRQ_TYPE_LEVEL_HIGH>; + + interrupt-names = "global", "doorbell", "dma"; + + interconnects = <&pcie_anoc MASTER_PCIE_0 0 &mc_virt SLAVE_EBI1 0>, + <&gem_noc MASTER_APPSS_PROC 0 &config_noc SLAVE_PCIE_0 0>; + interconnect-names = "pcie-mem", "cpu-pcie"; + + dma-coherent; + iommus = <&pcie_smmu 0x0000 0x7f>; + resets = <&gcc GCC_PCIE_0_BCR>; + reset-names = "core"; + power-domains = <&gcc PCIE_0_GDSC>; + phys = <&pcie0_phy>; + phy-names = "pciephy"; + num-lanes = <2>; + linux,pci-domain = <0>; + + status = "disabled"; + }; + + pcie0_phy: phy@1c04000 { + compatible = "qcom,sa8775p-qmp-gen4x2-pcie-phy"; + reg = <0x0 0x1c04000 0x0 0x2000>; + + clocks = <&gcc GCC_PCIE_0_PHY_AUX_CLK>, + <&gcc GCC_PCIE_0_CFG_AHB_CLK>, + <&gcc GCC_PCIE_CLKREF_EN>, + <&gcc GCC_PCIE_0_PHY_RCHNG_CLK>, + <&gcc GCC_PCIE_0_PIPE_CLK>, + <&gcc GCC_PCIE_0_PIPEDIV2_CLK>; + clock-names = "aux", + "cfg_ahb", + "ref", + "rchng", + "pipe", + "pipediv2"; + + assigned-clocks = <&gcc GCC_PCIE_0_PHY_RCHNG_CLK>; + assigned-clock-rates = <100000000>; + + resets = <&gcc GCC_PCIE_0_PHY_BCR>; + reset-names = "phy"; + + #clock-cells = <0>; + clock-output-names = "pcie_0_pipe_clk"; + + #phy-cells = <0>; + + status = "disabled"; + }; + + pcie1: pcie@1c10000 { + compatible = "qcom,pcie-sa8775p"; + reg = <0x0 0x01c10000 0x0 0x3000>, + <0x0 0x60000000 0x0 0xf20>, + <0x0 0x60000f20 0x0 0xa8>, + <0x0 0x60001000 0x0 0x4000>, + <0x0 0x60100000 0x0 0x100000>, + <0x0 0x01c13000 0x0 0x1000>; + reg-names = "parf", "dbi", "elbi", "atu", "config", "mhi"; + device_type = "pci"; + + #address-cells = <3>; + #size-cells = <2>; + ranges = <0x01000000 0x0 0x00000000 0x0 0x60200000 0x0 0x100000>, + <0x02000000 0x0 0x60300000 0x0 0x60300000 0x0 0x1fd00000>; + bus-range = <0x00 0xff>; + + dma-coherent; + + linux,pci-domain = <1>; + num-lanes = <4>; + + interrupts = <GIC_SPI 519 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 140 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 141 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 142 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 143 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 144 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 145 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 518 IRQ_TYPE_LEVEL_HIGH>; + interrupt-names = "msi0", + "msi1", + "msi2", + "msi3", + "msi4", + "msi5", + "msi6", + "msi7", + "global"; + #interrupt-cells = <1>; + interrupt-map-mask = <0 0 0 0x7>; + interrupt-map = <0 0 0 1 &intc GIC_SPI 148 IRQ_TYPE_LEVEL_HIGH>, + <0 0 0 2 &intc GIC_SPI 149 IRQ_TYPE_LEVEL_HIGH>, + <0 0 0 3 &intc GIC_SPI 150 IRQ_TYPE_LEVEL_HIGH>, + <0 0 0 4 &intc GIC_SPI 151 IRQ_TYPE_LEVEL_HIGH>; + + clocks = <&gcc GCC_PCIE_1_AUX_CLK>, + <&gcc GCC_PCIE_1_CFG_AHB_CLK>, + <&gcc GCC_PCIE_1_MSTR_AXI_CLK>, + <&gcc GCC_PCIE_1_SLV_AXI_CLK>, + <&gcc GCC_PCIE_1_SLV_Q2A_AXI_CLK>; + + clock-names = "aux", + "cfg", + "bus_master", + "bus_slave", + "slave_q2a"; + + assigned-clocks = <&gcc GCC_PCIE_1_AUX_CLK>; + assigned-clock-rates = <19200000>; + + interconnects = <&pcie_anoc MASTER_PCIE_1 0 &mc_virt SLAVE_EBI1 0>, + <&gem_noc MASTER_APPSS_PROC 0 &config_noc SLAVE_PCIE_1 0>; + interconnect-names = "pcie-mem", "cpu-pcie"; + + iommu-map = <0x0 &pcie_smmu 0x0080 0x1>, + <0x100 &pcie_smmu 0x0081 0x1>; + + resets = <&gcc GCC_PCIE_1_BCR>, + <&gcc GCC_PCIE_1_LINK_DOWN_BCR>; + reset-names = "pci", + "link_down"; + + power-domains = <&gcc PCIE_1_GDSC>; + + phys = <&pcie1_phy>; + phy-names = "pciephy"; + + eq-presets-8gts = /bits/ 16 <0x5555 0x5555 0x5555 0x5555>; + eq-presets-16gts = /bits/ 8 <0x55 0x55 0x55 0x55>; + + status = "disabled"; + + pcie@0 { + device_type = "pci"; + reg = <0x0 0x0 0x0 0x0 0x0>; + bus-range = <0x01 0xff>; + + #address-cells = <3>; + #size-cells = <2>; + ranges; + }; + }; + + pcie1_ep: pcie-ep@1c10000 { + compatible = "qcom,sa8775p-pcie-ep"; + reg = <0x0 0x01c10000 0x0 0x3000>, + <0x0 0x60000000 0x0 0xf20>, + <0x0 0x60000f20 0x0 0xa8>, + <0x0 0x60001000 0x0 0x4000>, + <0x0 0x60200000 0x0 0x1fe00000>, + <0x0 0x01c13000 0x0 0x1000>, + <0x0 0x60005000 0x0 0x2000>; + reg-names = "parf", "dbi", "elbi", "atu", "addr_space", + "mmio", "dma"; + + clocks = <&gcc GCC_PCIE_1_AUX_CLK>, + <&gcc GCC_PCIE_1_CFG_AHB_CLK>, + <&gcc GCC_PCIE_1_MSTR_AXI_CLK>, + <&gcc GCC_PCIE_1_SLV_AXI_CLK>, + <&gcc GCC_PCIE_1_SLV_Q2A_AXI_CLK>; + + clock-names = "aux", + "cfg", + "bus_master", + "bus_slave", + "slave_q2a"; + + interrupts = <GIC_SPI 518 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 152 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 474 IRQ_TYPE_LEVEL_HIGH>; + + interrupt-names = "global", "doorbell", "dma"; + + interconnects = <&pcie_anoc MASTER_PCIE_1 0 &mc_virt SLAVE_EBI1 0>, + <&gem_noc MASTER_APPSS_PROC 0 &config_noc SLAVE_PCIE_1 0>; + interconnect-names = "pcie-mem", "cpu-pcie"; + + dma-coherent; + iommus = <&pcie_smmu 0x80 0x7f>; + resets = <&gcc GCC_PCIE_1_BCR>; + reset-names = "core"; + power-domains = <&gcc PCIE_1_GDSC>; + phys = <&pcie1_phy>; + phy-names = "pciephy"; + num-lanes = <4>; + linux,pci-domain = <1>; + + status = "disabled"; + }; + + pcie1_phy: phy@1c14000 { + compatible = "qcom,sa8775p-qmp-gen4x4-pcie-phy"; + reg = <0x0 0x1c14000 0x0 0x4000>; + + clocks = <&gcc GCC_PCIE_1_PHY_AUX_CLK>, + <&gcc GCC_PCIE_1_CFG_AHB_CLK>, + <&gcc GCC_PCIE_CLKREF_EN>, + <&gcc GCC_PCIE_1_PHY_RCHNG_CLK>, + <&gcc GCC_PCIE_1_PIPE_CLK>, + <&gcc GCC_PCIE_1_PIPEDIV2_CLK>; + clock-names = "aux", + "cfg_ahb", + "ref", + "rchng", + "pipe", + "pipediv2"; + + assigned-clocks = <&gcc GCC_PCIE_1_PHY_RCHNG_CLK>; + assigned-clock-rates = <100000000>; + + resets = <&gcc GCC_PCIE_1_PHY_BCR>; + reset-names = "phy"; + + #clock-cells = <0>; + clock-output-names = "pcie_1_pipe_clk"; + + #phy-cells = <0>; + + status = "disabled"; + }; + ufs_mem_hc: ufshc@1d84000 { compatible = "qcom,sa8775p-ufshc", "qcom,ufshc", "jedec,ufs-2.0"; reg = <0x0 0x01d84000 0x0 0x3000>;
@@ -8601,350 +8947,4 @@ turing_llm_tpdm_out: endpoint { }; }; }; - - pcie0: pcie@1c00000 { - compatible = "qcom,pcie-sa8775p"; - reg = <0x0 0x01c00000 0x0 0x3000>, - <0x0 0x40000000 0x0 0xf20>, - <0x0 0x40000f20 0x0 0xa8>, - <0x0 0x40001000 0x0 0x4000>, - <0x0 0x40100000 0x0 0x100000>, - <0x0 0x01c03000 0x0 0x1000>; - reg-names = "parf", "dbi", "elbi", "atu", "config", "mhi"; - device_type = "pci"; - - #address-cells = <3>; - #size-cells = <2>; - ranges = <0x01000000 0x0 0x00000000 0x0 0x40200000 0x0 0x100000>, - <0x02000000 0x0 0x40300000 0x0 0x40300000 0x0 0x1fd00000>; - bus-range = <0x00 0xff>; - - dma-coherent; - - linux,pci-domain = <0>; - num-lanes = <2>; - - interrupts = <GIC_SPI 307 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 308 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 309 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 312 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 313 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 314 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 374 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 375 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 306 IRQ_TYPE_LEVEL_HIGH>; - interrupt-names = "msi0", - "msi1", - "msi2", - "msi3", - "msi4", - "msi5", - "msi6", - "msi7", - "global"; - #interrupt-cells = <1>; - interrupt-map-mask = <0 0 0 0x7>; - interrupt-map = <0 0 0 1 &intc GIC_SPI 434 IRQ_TYPE_LEVEL_HIGH>, - <0 0 0 2 &intc GIC_SPI 435 IRQ_TYPE_LEVEL_HIGH>, - <0 0 0 3 &intc GIC_SPI 438 IRQ_TYPE_LEVEL_HIGH>, - <0 0 0 4 &intc GIC_SPI 439 IRQ_TYPE_LEVEL_HIGH>; - - clocks = <&gcc GCC_PCIE_0_AUX_CLK>, - <&gcc GCC_PCIE_0_CFG_AHB_CLK>, - <&gcc GCC_PCIE_0_MSTR_AXI_CLK>, - <&gcc GCC_PCIE_0_SLV_AXI_CLK>, - <&gcc GCC_PCIE_0_SLV_Q2A_AXI_CLK>; - - clock-names = "aux", - "cfg", - "bus_master", - "bus_slave", - "slave_q2a"; - - assigned-clocks = <&gcc GCC_PCIE_0_AUX_CLK>; - assigned-clock-rates = <19200000>; - - interconnects = <&pcie_anoc MASTER_PCIE_0 0 &mc_virt SLAVE_EBI1 0>, - <&gem_noc MASTER_APPSS_PROC 0 &config_noc SLAVE_PCIE_0 0>; - interconnect-names = "pcie-mem", "cpu-pcie"; - - iommu-map = <0x0 &pcie_smmu 0x0000 0x1>, - <0x100 &pcie_smmu 0x0001 0x1>; - - resets = <&gcc GCC_PCIE_0_BCR>, - <&gcc GCC_PCIE_0_LINK_DOWN_BCR>; - reset-names = "pci", - "link_down"; - - power-domains = <&gcc PCIE_0_GDSC>; - - phys = <&pcie0_phy>; - phy-names = "pciephy"; - - eq-presets-8gts = /bits/ 16 <0x5555 0x5555>; - eq-presets-16gts = /bits/ 8 <0x55 0x55>; - - status = "disabled"; - - pcieport0: pcie@0 { - device_type = "pci"; - reg = <0x0 0x0 0x0 0x0 0x0>; - bus-range = <0x01 0xff>; - - #address-cells = <3>; - #size-cells = <2>; - ranges; - }; - }; - - pcie0_ep: pcie-ep@1c00000 { - compatible = "qcom,sa8775p-pcie-ep"; - reg = <0x0 0x01c00000 0x0 0x3000>, - <0x0 0x40000000 0x0 0xf20>, - <0x0 0x40000f20 0x0 0xa8>, - <0x0 0x40001000 0x0 0x4000>, - <0x0 0x40200000 0x0 0x1fe00000>, - <0x0 0x01c03000 0x0 0x1000>, - <0x0 0x40005000 0x0 0x2000>; - reg-names = "parf", "dbi", "elbi", "atu", "addr_space", - "mmio", "dma"; - - clocks = <&gcc GCC_PCIE_0_AUX_CLK>, - <&gcc GCC_PCIE_0_CFG_AHB_CLK>, - <&gcc GCC_PCIE_0_MSTR_AXI_CLK>, - <&gcc GCC_PCIE_0_SLV_AXI_CLK>, - <&gcc GCC_PCIE_0_SLV_Q2A_AXI_CLK>; - - clock-names = "aux", - "cfg", - "bus_master", - "bus_slave", - "slave_q2a"; - - interrupts = <GIC_SPI 306 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 630 IRQ_TYPE_LEVEL_HIGH>; - - interrupt-names = "global", "doorbell", "dma"; - - interconnects = <&pcie_anoc MASTER_PCIE_0 0 &mc_virt SLAVE_EBI1 0>, - <&gem_noc MASTER_APPSS_PROC 0 &config_noc SLAVE_PCIE_0 0>; - interconnect-names = "pcie-mem", "cpu-pcie"; - - dma-coherent; - iommus = <&pcie_smmu 0x0000 0x7f>; - resets = <&gcc GCC_PCIE_0_BCR>; - reset-names = "core"; - power-domains = <&gcc PCIE_0_GDSC>; - phys = <&pcie0_phy>; - phy-names = "pciephy"; - num-lanes = <2>; - linux,pci-domain = <0>; - - status = "disabled"; - }; - - pcie0_phy: phy@1c04000 { - compatible = "qcom,sa8775p-qmp-gen4x2-pcie-phy"; - reg = <0x0 0x1c04000 0x0 0x2000>; - - clocks = <&gcc GCC_PCIE_0_PHY_AUX_CLK>, - <&gcc GCC_PCIE_0_CFG_AHB_CLK>, - <&gcc GCC_PCIE_CLKREF_EN>, - <&gcc GCC_PCIE_0_PHY_RCHNG_CLK>, - <&gcc GCC_PCIE_0_PIPE_CLK>, - <&gcc GCC_PCIE_0_PIPEDIV2_CLK>; - clock-names = "aux", - "cfg_ahb", - "ref", - "rchng", - "pipe", - "pipediv2"; - - assigned-clocks = <&gcc GCC_PCIE_0_PHY_RCHNG_CLK>; - assigned-clock-rates = <100000000>; - - resets = <&gcc GCC_PCIE_0_PHY_BCR>; - reset-names = "phy"; - - #clock-cells = <0>; - clock-output-names = "pcie_0_pipe_clk"; - - #phy-cells = <0>; - - status = "disabled"; - }; - - pcie1: pcie@1c10000 { - compatible = "qcom,pcie-sa8775p"; - reg = <0x0 0x01c10000 0x0 0x3000>, - <0x0 0x60000000 0x0 0xf20>, - <0x0 0x60000f20 0x0 0xa8>, - <0x0 0x60001000 0x0 0x4000>, - <0x0 0x60100000 0x0 0x100000>, - <0x0 0x01c13000 0x0 0x1000>; - reg-names = "parf", "dbi", "elbi", "atu", "config", "mhi"; - device_type = "pci"; - - #address-cells = <3>; - #size-cells = <2>; - ranges = <0x01000000 0x0 0x00000000 0x0 0x60200000 0x0 0x100000>, - <0x02000000 0x0 0x60300000 0x0 0x60300000 0x0 0x1fd00000>; - bus-range = <0x00 0xff>; - - dma-coherent; - - linux,pci-domain = <1>; - num-lanes = <4>; - - interrupts = <GIC_SPI 519 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 140 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 141 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 142 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 143 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 144 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 145 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 518 IRQ_TYPE_LEVEL_HIGH>; - interrupt-names = "msi0", - "msi1", - "msi2", - "msi3", - "msi4", - "msi5", - "msi6", - "msi7", - "global"; - #interrupt-cells = <1>; - interrupt-map-mask = <0 0 0 0x7>; - interrupt-map = <0 0 0 1 &intc GIC_SPI 148 IRQ_TYPE_LEVEL_HIGH>, - <0 0 0 2 &intc GIC_SPI 149 IRQ_TYPE_LEVEL_HIGH>, - <0 0 0 3 &intc GIC_SPI 150 IRQ_TYPE_LEVEL_HIGH>, - <0 0 0 4 &intc GIC_SPI 151 IRQ_TYPE_LEVEL_HIGH>; - - clocks = <&gcc GCC_PCIE_1_AUX_CLK>, - <&gcc GCC_PCIE_1_CFG_AHB_CLK>, - <&gcc GCC_PCIE_1_MSTR_AXI_CLK>, - <&gcc GCC_PCIE_1_SLV_AXI_CLK>, - <&gcc GCC_PCIE_1_SLV_Q2A_AXI_CLK>; - - clock-names = "aux", - "cfg", - "bus_master", - "bus_slave", - "slave_q2a"; - - assigned-clocks = <&gcc GCC_PCIE_1_AUX_CLK>; - assigned-clock-rates = <19200000>; - - interconnects = <&pcie_anoc MASTER_PCIE_1 0 &mc_virt SLAVE_EBI1 0>, - <&gem_noc MASTER_APPSS_PROC 0 &config_noc SLAVE_PCIE_1 0>; - interconnect-names = "pcie-mem", "cpu-pcie"; - - iommu-map = <0x0 &pcie_smmu 0x0080 0x1>, - <0x100 &pcie_smmu 0x0081 0x1>; - - resets = <&gcc GCC_PCIE_1_BCR>, - <&gcc GCC_PCIE_1_LINK_DOWN_BCR>; - reset-names = "pci", - "link_down"; - - power-domains = <&gcc PCIE_1_GDSC>; - - phys = <&pcie1_phy>; - phy-names = "pciephy"; - - eq-presets-8gts = /bits/ 16 <0x5555 0x5555 0x5555 0x5555>; - eq-presets-16gts = /bits/ 8 <0x55 0x55 0x55 0x55>; - - status = "disabled"; - - pcie@0 { - device_type = "pci"; - reg = <0x0 0x0 0x0 0x0 0x0>; - bus-range = <0x01 0xff>; - - #address-cells = <3>; - #size-cells = <2>; - ranges; - }; - }; - - pcie1_ep: pcie-ep@1c10000 { - compatible = "qcom,sa8775p-pcie-ep"; - reg = <0x0 0x01c10000 0x0 0x3000>, - <0x0 0x60000000 0x0 0xf20>, - <0x0 0x60000f20 0x0 0xa8>, - <0x0 0x60001000 0x0 0x4000>, - <0x0 0x60200000 0x0 0x1fe00000>, - <0x0 0x01c13000 0x0 0x1000>, - <0x0 0x60005000 0x0 0x2000>; - reg-names = "parf", "dbi", "elbi", "atu", "addr_space", - "mmio", "dma"; - - clocks = <&gcc GCC_PCIE_1_AUX_CLK>, - <&gcc GCC_PCIE_1_CFG_AHB_CLK>, - <&gcc GCC_PCIE_1_MSTR_AXI_CLK>, - <&gcc GCC_PCIE_1_SLV_AXI_CLK>, - <&gcc GCC_PCIE_1_SLV_Q2A_AXI_CLK>; - - clock-names = "aux", - "cfg", - "bus_master", - "bus_slave", - "slave_q2a"; - - interrupts = <GIC_SPI 518 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 152 IRQ_TYPE_LEVEL_HIGH>, - <GIC_SPI 474 IRQ_TYPE_LEVEL_HIGH>; - - interrupt-names = "global", "doorbell", "dma"; - - interconnects = <&pcie_anoc MASTER_PCIE_1 0 &mc_virt SLAVE_EBI1 0>, - <&gem_noc MASTER_APPSS_PROC 0 &config_noc SLAVE_PCIE_1 0>; - interconnect-names = "pcie-mem", "cpu-pcie"; - - dma-coherent; - iommus = <&pcie_smmu 0x80 0x7f>; - resets = <&gcc GCC_PCIE_1_BCR>; - reset-names = "core"; - power-domains = <&gcc PCIE_1_GDSC>; - phys = <&pcie1_phy>; - phy-names = "pciephy"; - num-lanes = <4>; - linux,pci-domain = <1>; - - status = "disabled"; - }; - - pcie1_phy: phy@1c14000 { - compatible = "qcom,sa8775p-qmp-gen4x4-pcie-phy"; - reg = <0x0 0x1c14000 0x0 0x4000>; - - clocks = <&gcc GCC_PCIE_1_PHY_AUX_CLK>, - <&gcc GCC_PCIE_1_CFG_AHB_CLK>, - <&gcc GCC_PCIE_CLKREF_EN>, - <&gcc GCC_PCIE_1_PHY_RCHNG_CLK>, - <&gcc GCC_PCIE_1_PIPE_CLK>, - <&gcc GCC_PCIE_1_PIPEDIV2_CLK>; - clock-names = "aux", - "cfg_ahb", - "ref", - "rchng", - "pipe", - "pipediv2"; - - assigned-clocks = <&gcc GCC_PCIE_1_PHY_RCHNG_CLK>; - assigned-clock-rates = <100000000>; - - resets = <&gcc GCC_PCIE_1_PHY_BCR>; - reset-names = "phy"; - - #clock-cells = <0>; - clock-output-names = "pcie_1_pipe_clk"; - - #phy-cells = <0>; - - status = "disabled"; - }; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 179/2077 media: iris: scale MMCX power domain on SM8250
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dmitry Baryshkov <[email protected]>
[ Upstream commit 4170e2f25ce40b69f3827fcdabf395380095e136 ]
On SM8250 most of the video clocks are powered by the MMCX domain, while the PLL is powered on by the MX domain. Extend the driver to support scaling both power domains, while keeping compatibility with the existing DTs, which define only the MX domain.
--- drivers/media/platform/qcom/iris/iris_platform_gen1.c | 2 +- drivers/media/platform/qcom/iris/iris_probe.c | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-)
drivers/media/platform/qcom/iris/iris_platform_gen1.c +1 -1
@@ -281,7 +281,7 @@ static const struct bw_info sm8250_bw_table_dec[] = {static const char *const sm8250_pmdomain_table[] = {"venus" ,"vcodec0" }; -static const char *const sm8250_opp_pd_table[] = {"mx" }; +static const char *const sm8250_opp_pd_table[] = {"mx" ,"mmcx" };static const struct platform_clk_data sm8250_clk_table[] = { {IRIS_AXI_CLK ,"iface" },
drivers/media/platform/qcom/iris/iris_probe.c +7 -0
@@ -64,6 +64,13 @@ static int iris_init_power_domains(struct iris_core *core)return ret; ret =devm_pm_domain_attach_list (core->dev, &iris_opp_pd_data, &core->opp_pmdomain_tbl); +/* backwards compatibility for incomplete ABI SM8250 */ +if (ret == -ENODEV && +of_device_is_compatible (core->dev->of_node,"qcom,sm8250-venus" )) { + iris_opp_pd_data.num_pd_names--; + ret =devm_pm_domain_attach_list (core->dev, &iris_opp_pd_data, + &core->opp_pmdomain_tbl); + }if (ret <0 )return ret;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 180/2077 media: venus: scale MMCX power domain on SM8250
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dmitry Baryshkov <[email protected]>
[ Upstream commit f45fd3dbb5f6d60a8b31d5cc4affaf1ef40163b3 ]
On SM8250 most of the video clocks are powered by the MMCX domain, while the PLL is powered on by the MX domain. Extend the driver to support scaling both power domains, while keeping compatibility with the existing DTs, which define only the MX domain.
--- drivers/media/platform/qcom/venus/core.c | 7 ++++++- drivers/media/platform/qcom/venus/core.h | 1 + drivers/media/platform/qcom/venus/pm_helpers.c | 8 +++++++- 3 files changed, 14 insertions(+), 2 deletions(-)
drivers/media/platform/qcom/venus/core.c +6 -1
@@ -882,6 +882,7 @@ static const struct venus_resources sdm845_res_v2 = { .vcodec_pmdomains = (const char *[]) { "venus", "vcodec0", "vcodec1" }, .vcodec_pmdomains_num = 3, .opp_pmdomain = (const char *[]) { "cx" }, + .opp_pmdomain_num = 1, .vcodec_num = 2, .max_load = 3110400, /* 4096x2160@90 */ .hfi_version = HFI_VERSION_4XX,
@@ -933,6 +934,7 @@ static const struct venus_resources sc7180_res = { .vcodec_pmdomains = (const char *[]) { "venus", "vcodec0" }, .vcodec_pmdomains_num = 2, .opp_pmdomain = (const char *[]) { "cx" }, + .opp_pmdomain_num = 1, .vcodec_num = 1, .hfi_version = HFI_VERSION_4XX, .vpu_version = VPU_VERSION_AR50,
@@ -991,7 +993,8 @@ static const struct venus_resources sm8250_res = { .vcodec_clks_num = 1, .vcodec_pmdomains = (const char *[]) { "venus", "vcodec0" }, .vcodec_pmdomains_num = 2, - .opp_pmdomain = (const char *[]) { "mx" }, + .opp_pmdomain = (const char *[]) { "mx", "mmcx" }, + .opp_pmdomain_num = 2, .vcodec_num = 1, .max_load = 7833600, .hfi_version = HFI_VERSION_6XX,
@@ -1053,6 +1056,7 @@ static const struct venus_resources sc7280_res = { .vcodec_pmdomains = (const char *[]) { "venus", "vcodec0" }, .vcodec_pmdomains_num = 2, .opp_pmdomain = (const char *[]) { "cx" }, + .opp_pmdomain_num = 1, .vcodec_num = 1, .hfi_version = HFI_VERSION_6XX, .vpu_version = VPU_VERSION_IRIS2_1,
@@ -1100,6 +1104,7 @@ static const struct venus_resources qcm2290_res = { .vcodec_pmdomains = (const char *[]) { "venus", "vcodec0" }, .vcodec_pmdomains_num = 2, .opp_pmdomain = (const char *[]) { "cx" }, + .opp_pmdomain_num = 1, .vcodec_num = 1, .hfi_version = HFI_VERSION_4XX, .vpu_version = VPU_VERSION_AR50_LITE,
drivers/media/platform/qcom/venus/core.h +1 -0
@@ -83,6 +83,7 @@ struct venus_resources {const char **vcodec_pmdomains;unsigned int vcodec_pmdomains_num;const char **opp_pmdomain; +unsigned int opp_pmdomain_num;unsigned int vcodec_num;const char *const resets[VIDC_RESETS_NUM_MAX ];unsigned int resets_num;
drivers/media/platform/qcom/venus/pm_helpers.c +7 -1
@@ -887,7 +887,7 @@ static int vcodec_domains_get(struct venus_core *core) };struct dev_pm_domain_attach_data opp_pd_data = { .pd_names = res->opp_pmdomain, - .num_pd_names =1 , + .num_pd_names = res->opp_pmdomain_num, .pd_flags =PD_FLAG_DEV_LINK_ON |PD_FLAG_REQUIRED_OPP , };
@@ -904,6 +904,12 @@ static int vcodec_domains_get(struct venus_core *core)/* Attach the power domain for setting performance state */ ret =devm_pm_domain_attach_list (dev, &opp_pd_data, &core->opp_pmdomain); +/* backwards compatibility for incomplete ABI SM8250 */ +if (ret == -ENODEV && +of_device_is_compatible (dev->of_node,"qcom,sm8250-venus" )) { + opp_pd_data.num_pd_names--; + ret =devm_pm_domain_attach_list (dev, &opp_pd_data, &core->opp_pmdomain); + }if (ret <0 )return ret;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 181/2077 iommu/amd: Fix a stale comment about which legacy mode is user visible
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Christopherson <[email protected]>
[ Upstream commit 4bf53c2d0c08bbdaa32f2114281f1ddab61902bf ]
Update a stale comment about which of the legacy modes is visible to the user, i.e. can be forced via amd_iommu_intr=legacy.
--- drivers/iommu/amd/amd_iommu_types.h | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-)
drivers/iommu/amd/amd_iommu_types.h +6 -5
@@ -948,12 +948,13 @@ static inline int get_hpet_devid(int id) }enum amd_iommu_intr_mode_type { -AMD_IOMMU_GUEST_IR_LEGACY , - -/* This mode is not visible to users. It is used when -* we cannot fully enable vAPIC and fallback to only support -* legacy interrupt remapping via 128-bit IRTE. +/* +* The legacy format mode is not visible to users to prevent the user +* from crashing x2APIC systems, which for all intents and purposes +* require 128-bit IRTEs. The legacy format will be forced as needed +* when hardware doesn't support 128-bit IRTEs. */ +AMD_IOMMU_GUEST_IR_LEGACY ,AMD_IOMMU_GUEST_IR_LEGACY_GA ,AMD_IOMMU_GUEST_IR_VAPIC , };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 182/2077 soc: mediatek: mtk-mmsys: Restore MT8167 routing masks lost during merge
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Luca Leonardo Scorcia <[email protected]>
[ Upstream commit 7d462de9f65b002b439b1b168bf3b5579b0de48b ]
The original patch that was sent to the mailing lists included the values for the route masks, but they got lost during merge: add back the full register masks where missing.
--- drivers/soc/mediatek/mt8167-mmsys.h | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-)
drivers/soc/mediatek/mt8167-mmsys.h +8 -3
@@ -10,24 +10,29 @@#define MT8167_DISP_REG_CONFIG_DISP_RDMA0_SOUT_SEL_IN 0x06c#define MT8167_DITHER_MOUT_EN_RDMA0 0x1 +#define MT8167_DITHER_MOUT_EN_MASK 0x7 +#define MT8167_RDMA0_SOUT_DSI0 0x2 +#define MT8167_RDMA0_SOUT_MASK 0x3 +#define MT8167_DSI0_SEL_IN_RDMA0 0x1 +#define MT8167_DSI0_SEL_IN_MASK 0x3static const struct mtk_mmsys_routes mt8167_mmsys_routing_table[] = {MMSYS_ROUTE (OVL0 ,COLOR0 ,MT8167_DISP_REG_CONFIG_DISP_OVL0_MOUT_EN ,OVL0_MOUT_EN_COLOR0 ,OVL0_MOUT_EN_COLOR0 ),MMSYS_ROUTE (DITHER0 ,RDMA0 , -MT8167_DISP_REG_CONFIG_DISP_DITHER_MOUT_EN ,MT8167_DITHER_MOUT_EN_RDMA0 , +MT8167_DISP_REG_CONFIG_DISP_DITHER_MOUT_EN ,MT8167_DITHER_MOUT_EN_MASK ,MT8167_DITHER_MOUT_EN_RDMA0 ),MMSYS_ROUTE (OVL0 ,COLOR0 ,MT8167_DISP_REG_CONFIG_DISP_COLOR0_SEL_IN ,COLOR0_SEL_IN_OVL0 ,COLOR0_SEL_IN_OVL0 ),MMSYS_ROUTE (RDMA0 ,DSI0 , -MT8167_DISP_REG_CONFIG_DISP_DSI0_SEL_IN ,MT8167_DSI0_SEL_IN_RDMA0 , +MT8167_DISP_REG_CONFIG_DISP_DSI0_SEL_IN ,MT8167_DSI0_SEL_IN_MASK ,MT8167_DSI0_SEL_IN_RDMA0 ),MMSYS_ROUTE (RDMA0 ,DSI0 , -MT8167_DISP_REG_CONFIG_DISP_RDMA0_SOUT_SEL_IN ,MT8167_RDMA0_SOUT_DSI0 , +MT8167_DISP_REG_CONFIG_DISP_RDMA0_SOUT_SEL_IN ,MT8167_RDMA0_SOUT_MASK ,MT8167_RDMA0_SOUT_DSI0 ), };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 183/2077 bpf: fix crash in bpf_[set|remove]_dentry_xattr for negative dentries
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Matt Bobrowski <[email protected]>
[ Upstream commit 07410646f6ff1d23222f105ccab778957d401bbe ]
bpf_set_dentry_xattr and bpf_remove_dentry_xattr BPF kfuncs attempt to lock the inode of the supplied dentry without checking if it is NULL. If a negative dentry is passed (e.g. from security_inode_create), d_inode(dentry) returns NULL, and inode_lock(inode) will cause a NULL pointer dereference.
Trivially fix this by adding a NULL check for inode before attempting to lock it, returning -EINVAL if it is NULL.
Additionally, drop WARN_ON(!inode) in bpf_xattr_read_permission() and bpf_xattr_write_permission(). These warnings could be triggered by passing a negative dentry to bpf_get_dentry_xattr() or the _locked variants of the xattr kfuncs, potentially causing a Denial of Service on systems with panic_on_warn enabled. Instead, simply return -EINVAL.
--- fs/bpf_fs_kfuncs.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
fs/bpf_fs_kfuncs.c +8 -2
@@ -100,7 +100,7 @@ static bool match_security_bpf_prefix(const char *name__str)static int bpf_xattr_read_permission (const char *name,struct inode *inode) { -if (WARN_ON (!inode)) +if (!inode)return -EINVAL ;/* Allow reading xattr with user. and security.bpf. prefix */
@@ -170,7 +170,7 @@ __bpf_kfunc_end_defs();static int bpf_xattr_write_permission (const char *name,struct inode *inode) { -if (WARN_ON (!inode)) +if (!inode)return -EINVAL ;/* Only allow setting and removing security.bpf. xattrs */
@@ -289,6 +289,9 @@ __bpf_kfunc int bpf_set_dentry_xattr(struct dentry *dentry, const char *name__ststruct inode *inode =d_inode (dentry);int ret; +if (!inode) +return -EINVAL ; +inode_lock (inode); ret =bpf_set_dentry_xattr_locked (dentry, name__str, value_p, flags);inode_unlock (inode);
@@ -314,6 +317,9 @@ __bpf_kfunc int bpf_remove_dentry_xattr(struct dentry *dentry, const char *name_struct inode *inode =d_inode (dentry);int ret; +if (!inode) +return -EINVAL ; +inode_lock (inode); ret =bpf_remove_dentry_xattr_locked (dentry, name__str);inode_unlock (inode);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 184/2077 uaccess: fix ignored_trailing logic in copy_struct_to_user()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stefan Metzmacher <[email protected]>
[ Upstream commit 4911de3145a797389577abfdf9a5185d36cc18d7 ]
Currently all callers pass ignored_trailing=NULL, but I have code that will make use of.
Now it actually behaves like documented:
* If @usize < @ksize, then the kernel is trying to pass userspace a newer struct than it supports. Thus we only copy the interoperable portions (@usize) and ignore the rest (but @ignored_trailing is set to %true if any of the trailing (@ksize - @usize) bytes are non-zero).
--- include/linux/uaccess.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/uaccess.h +1 -1
@@ -510,7 +510,7 @@ copy_struct_to_user(void __user *dst, size_t usize, const void *src,return -EFAULT ; }if (ignored_trailing) - *ignored_trailing = ksize < usize && + *ignored_trailing = usize < ksize &&memchr_inv (src + size,0 , rest) !=NULL ;/* Copy the interoperable parts of the struct. */ if (copy_to_user (dst, src, size))
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 185/2077 sockptr: fix usize check in copy_struct_from_sockptr() for user pointers
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stefan Metzmacher <[email protected]>
[ Upstream commit db0493512931fe1e5a71612e6a358df1aa22d80c ]
copy_struct_from_user will never hit the check_zeroed_user() call and will never return -E2BIG if new userspace passed new bits in a larger structure than the current kernel structure.
As far as I can there are no critical/related uapi changes in
- include/net/bluetooth/bluetooth.h and net/bluetooth/sco.c after the use of copy_struct_from_sockptr in v6.13-rc3
- include/uapi/linux/tcp.h and net/ipv4/tcp_ao.c after the use of copy_struct_from_sockptr in v6.6-rc1
So that new callers will get the correct behavior from the start.
--- include/linux/sockptr.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/sockptr.h +1 -1
@@ -91,7 +91,7 @@ static inline int copy_struct_from_sockptr(void *dst, size_t ksize,size_t rest =max (ksize, usize) - size;if (!sockptr_is_kernel (src)) -return copy_struct_from_user (dst, ksize, src.user, size); +return copy_struct_from_user (dst, ksize, src.user, usize);if (usize < ksize) {memset (dst + size,0 , rest);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 186/2077 arm64: dts: mediatek: mt7988a-bpi-r4pro: rework pcie gpio-hog handling
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Frank Wunderlich <[email protected]>
[ Upstream commit e309fa232d12b969afac43a4b7d83dee025cfe63 ]
The active-high property in base-dt cannot be overwritten and must be set in separate overlay.
--- arch/arm64/boot/dts/mediatek/Makefile | 8 ++++++++ .../mt7988a-bananapi-bpi-r4-pro-cn13.dtso | 20 +++++++++++++++++++ .../mt7988a-bananapi-bpi-r4-pro-cn14.dtso | 20 +++++++++++++++++++ .../mediatek/mt7988a-bananapi-bpi-r4-pro.dtsi | 2 -- 4 files changed, 48 insertions(+), 2 deletions(-) create mode 100644 arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4-pro-cn13.dtso create mode 100644 arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4-pro-cn14.dtso
arch/arm64/boot/dts/mediatek/Makefile +8 -0
@@ -47,6 +47,8 @@ dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-2g5.dtb dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-emmc.dtbo dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-4e.dtb dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-8x.dtb +dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-cn13.dtbo +dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-cn14.dtbo dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-cn15.dtbo dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-cn18.dtbo dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-emmc.dtbo
@@ -70,18 +72,24 @@ mt7988a-bananapi-bpi-r4-2g5-sd-dtbs := \ dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-2g5-sd.dtb mt7988a-bananapi-bpi-r4-pro-8x-emmc-dtbs := \ mt7988a-bananapi-bpi-r4-pro-8x.dtb \ + mt7988a-bananapi-bpi-r4-pro-cn13.dtbo \ + mt7988a-bananapi-bpi-r4-pro-cn14.dtbo \ mt7988a-bananapi-bpi-r4-pro-emmc.dtbo dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-8x-emmc.dtb mt7988a-bananapi-bpi-r4-pro-8x-sd-dtbs := \ mt7988a-bananapi-bpi-r4-pro-8x.dtb \ + mt7988a-bananapi-bpi-r4-pro-cn13.dtbo \ + mt7988a-bananapi-bpi-r4-pro-cn14.dtbo \ mt7988a-bananapi-bpi-r4-pro-sd.dtbo dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-8x-sd.dtb mt7988a-bananapi-bpi-r4-pro-8x-sd-cn15-dtbs := \ mt7988a-bananapi-bpi-r4-pro-8x-sd.dtb \ + mt7988a-bananapi-bpi-r4-pro-cn14.dtbo \ mt7988a-bananapi-bpi-r4-pro-cn15.dtbo dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-8x-sd-cn15.dtb mt7988a-bananapi-bpi-r4-pro-8x-sd-cn18-dtbs := \ mt7988a-bananapi-bpi-r4-pro-8x-sd.dtb \ + mt7988a-bananapi-bpi-r4-pro-cn13.dtbo \ mt7988a-bananapi-bpi-r4-pro-cn18.dtbo dtb-$(CONFIG_ARCH_MEDIATEK) += mt7988a-bananapi-bpi-r4-pro-8x-sd-cn18.dtb dtb-$(CONFIG_ARCH_MEDIATEK) += mt8167-pumpkin.dtb
arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4-pro-cn13.dtso new file +20 -0
@@ -0,0 +1,20 @@ +// SPDX-License-Identifier: (GPL-2.0 OR MIT) +/* + * Copyright (C) 2025 MediaTek Inc. + * Author: Frank Wunderlich <[email protected]> + */ + +/* This enables key-m slot CN13 on pcie2(11280000 1L0) on BPI-R4-Pro */ + +/dts-v1/; +/plugin/; + +#include <dt-bindings/gpio/gpio.h> + +/ { + compatible = "bananapi,bpi-r4-pro", "mediatek,mt7988a"; +}; + +&{/soc/pinctrl@1001f000/pcie-2-hog} { + output-high; +};
arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4-pro-cn14.dtso new file +20 -0
@@ -0,0 +1,20 @@ +// SPDX-License-Identifier: (GPL-2.0 OR MIT) +/* + * Copyright (C) 2025 MediaTek Inc. + * Author: Frank Wunderlich <[email protected]> + */ + +/* This enables key-m slot CN14 on pcie3(11290000 1L1) on BPI-R4-Pro */ + +/dts-v1/; +/plugin/; + +#include <dt-bindings/gpio/gpio.h> + +/ { + compatible = "bananapi,bpi-r4-pro", "mediatek,mt7988a"; +}; + +&{/soc/pinctrl@1001f000/pcie-3-hog} { + output-high; +};
arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4-pro.dtsi +0 -2
@@ -437,14 +437,12 @@ mux { pcie-2-hog { gpio-hog; gpios = <79 GPIO_ACTIVE_HIGH>; - output-high; }; /* 1L1 0=key-b (CN18), 1=key-m (CN14) */ pcie-3-hog { gpio-hog; gpios = <63 GPIO_ACTIVE_HIGH>; - output-high; }; pwm0_pins: pwm0-pins {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 187/2077 arm64: dts: mediatek: mt8192-asurada: Move PCIe DMA bounce buffer to host
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chen-Yu Tsai <[email protected]>
[ Upstream commit 533275a4b5240a2bf2c592bd4536560388306d26 ]
The DMA bounce buffer is attached to the PCIe host controller, i.e. all PCIe DMA transfers should use it.
Move it from the PCIe (WiFi) device node down to the PCIe host controller node.
--- arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi +1 -1
@@ -525,6 +525,7 @@ flash@0 { &pcie { pinctrl-names = "default"; pinctrl-0 = <&pcie_pins>; + memory-region = <&wifi_restricted_dma_region>; pcie0: pcie@0,0 { device_type = "pci";
@@ -539,7 +540,6 @@ pcie0: pcie@0,0 { wifi: wifi@0,0 { reg = <0x10000 0 0 0 0x100000>, <0x10000 0 0x100000 0 0x100000>; - memory-region = <&wifi_restricted_dma_region>; }; }; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 188/2077 workqueue: forbid TEST_WORKQUEUE from being built-in
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Breno Leitao <[email protected]>
[ Upstream commit 1503043fd75e29ad49c7d506232e272f6951d07d ]
The benchmark drives the workqueue's affinity_scope through sysfs by filp_open()'ing /sys/bus/workqueue/devices/bench_wq/affinity_scope. When CONFIG_TEST_WORKQUEUE=y, the module_init runs during kernel init before userspace has mounted sysfs, so every open returns -ENOENT and the benchmark loop spins emitting:
test_workqueue: open /sys/bus/workqueue/devices/bench_wq/affinity_scope failed: -2
Mirror the TEST_BPF pattern and add "depends on m" so Kconfig will not let this be built into the kernel image, and document the reason in the help text.
--- lib/Kconfig.debug | 5 +++++ 1 file changed, 5 insertions(+)
lib/Kconfig.debug +5 -0
@@ -2649,12 +2649,17 @@ config TEST_VMALLOC config TEST_WORKQUEUE tristate "Test module for stress/performance analysis of workqueue" + depends on m default n help This builds the "test_workqueue" module for benchmarking workqueue throughput under contention. Useful for evaluating affinity scope changes (e.g., cache_shard vs cache). + The test drives sysfs to switch affinity scopes, so it must be + loaded after userspace has mounted sysfs; building it in (=y) + would run module_init before /sys is available. + If unsure, say N. config TEST_BPF
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 189/2077 drm/amdgpu: fix error return code in mes_v12_1_map_test_bo
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yang Wang <[email protected]>
[ Upstream commit 5da1e1dfd15727918aab2c1a79c019f179991e80 ]
The function mes_v12_1_map_test_bo incorrectly returned 0 unconditionallyon error path, which would hide the real error code and mislead upperlayers about the failure status. Fix it by returning the correct error code 'r' instead of 0.
--- drivers/gpu/drm/amd/amdgpu/mes_v12_1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/amd/amdgpu/mes_v12_1.c +1 -1
@@ -2016,7 +2016,7 @@ static int mes_v12_1_map_test_bo(struct amdgpu_device *adev, error:amdgpu_sync_free (&sync); -return 0 ; +return r; } static int mes_v12_1_test_ring(struct amdgpu_device *adev, int xcc_id,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 190/2077 arm64: dts: qcom: glymur-crd: Drop forced host mode for USB SS0 and SS1
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Abel Vesa <[email protected]>
[ Upstream commit d9dc254945756b44fa6f61b9cbd4adf0413c6a6f ]
The two USB Type-C ports on Glymur CRD are dual-role capable.
Do not force their controllers into host mode. Drop the explicit 'dr_mode = "host"' properties so they can use their default OTG mode instead.
--- arch/arm64/boot/dts/qcom/glymur-crd.dts | 4 ---- 1 file changed, 4 deletions(-)
arch/arm64/boot/dts/qcom/glymur-crd.dts +0 -4
@@ -322,8 +322,6 @@ reset-n-pins { }; &usb_0 { - dr_mode = "host"; - status = "okay"; };
@@ -353,8 +351,6 @@ &usb_0_qmpphy_out { }; &usb_1 { - dr_mode = "host"; - status = "okay"; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 191/2077 arm64: dts: qcom: glymur: Mark USB SS1 and SS2 as role-switch capable
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Abel Vesa <[email protected]>
[ Upstream commit 347fa2fa64e1cef0c7897522896c0c66e734c82b ]
Like USB SS0, the USB SS1 and SS2 controllers on Glymur also support USB role switching.
Describe this by adding the 'usb-role-switch' property to both controllers.
--- arch/arm64/boot/dts/qcom/glymur.dtsi | 4 ++++ 1 file changed, 4 insertions(+)
arch/arm64/boot/dts/qcom/glymur.dtsi +4 -0
@@ -3920,6 +3920,8 @@ usb_1: usb@a800000 { snps,dis_u2_susphy_quirk; snps,dis_enblslpm_quirk; + usb-role-switch; + status = "disabled"; ports {
@@ -3993,6 +3995,8 @@ usb_2: usb@a000000 { snps,dis_u2_susphy_quirk; snps,dis_enblslpm_quirk; + usb-role-switch; + status = "disabled"; ports {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 192/2077 rhashtable: give each instance its own lockdep class
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christian Brauner <[email protected]>
[ Upstream commit 060d4e94b8d400b62453890821bd7feecd4cde2c ]
syzbot reported a possible circular locking dependency between &ht->mutex and fs_reclaim:
CPU0 (kswapd0) CPU1 (kworker)
-------------- --------------
fs_reclaim ht->mutex
shmem_evict_inode rhashtable_rehash_alloc
simple_xattrs_free bucket_table_alloc(GFP_KERNEL)
rhashtable_free_and_destroy __kvmalloc_node
mutex_lock(&ht->mutex) might_alloc -> fs_reclaimThe two halves of the splat refer to two different events on &ht->mutex.
The kswapd0 path is unambiguous: shmem_evict_inode at mm/shmem.c:1429 calls simple_xattrs_free(), which calls rhashtable_free_and_destroy() on the per-inode simple_xattrs rhashtable being torn down with the inode.
The previously-recorded ht->mutex -> fs_reclaim edge comes from rht_deferred_worker -> rhashtable_rehash_alloc -> bucket_table_alloc(GFP_KERNEL) -> __kvmalloc_node -> might_alloc -> fs_reclaim. That stack stops at generic library code:
there is no subsystem-specific frame above rht_deferred_worker, so the splat does not identify which rhashtable's worker recorded the edge -- only that some rhashtable in the system did.
Whether or not that recording happened on the same simple_xattrs ht that is now being destroyed, the predicted deadlock cannot occur:rhashtable_free_and_destroy() does cancel_work_sync(&ht->run_work) before taking ht->mutex, so the deferred worker cannot be running on the instance being torn down. If the recording was on a different rhashtable instance, the two ht->mutex acquisitions are on distinct mutex objects and cannot deadlock either.
Lockdep flags a cycle regardless because mutex_init(&ht->mutex) lives on a single source line in rhashtable_init_noprof(), so every ht->mutex in the kernel shares one static lockdep class. Lockdep matches by class, not by instance, and collapses all of these into one node.
Lift the lockdep key out of rhashtable_init_noprof() and into the caller. The user-visible rhashtable_init_noprof() / rhltable_init_noprof() identifiers become macros that declare a per-call-site static lock_class_key.
--- include/linux/rhashtable-types.h | 22 ++++++++++++++++++---- lib/rhashtable.c | 17 ++++++++++------- 2 files changed, 28 insertions(+), 11 deletions(-)
include/linux/rhashtable-types.h +18 -4
@@ -136,12 +136,26 @@ struct rhashtable_iter { bool end_of_table; }; -int rhashtable_init_noprof (struct rhashtable *ht, -const struct rhashtable_params *params); +int __rhashtable_init_noprof (struct rhashtable *ht, +const struct rhashtable_params *params, +struct lock_class_key *key); +#define rhashtable_init_noprof (ht, params) \ +({ \ + static struct lock_class_key __key; \ + \ + __rhashtable_init_noprof(ht, params, &__key); \ +})#define rhashtable_init (...) alloc_hooks(rhashtable_init_noprof(__VA_ARGS__)) -int rhltable_init_noprof (struct rhltable *hlt, -const struct rhashtable_params *params); +int __rhltable_init_noprof (struct rhltable *hlt, +const struct rhashtable_params *params, +struct lock_class_key *key); +#define rhltable_init_noprof (hlt, params) \ +({ \ + static struct lock_class_key __key; \ + \ + __rhltable_init_noprof(hlt, params, &__key); \ +})#define rhltable_init (...) alloc_hooks(rhltable_init_noprof(__VA_ARGS__))#endif /* _LINUX_RHASHTABLE_TYPES_H */
lib/rhashtable.c +10 -7
@@ -1057,8 +1057,9 @@ static u32 rhashtable_jhash2(const void *key, u32 length, u32 seed)* .obj_hashfn = my_hash_fn, * }; */ -int rhashtable_init_noprof (struct rhashtable *ht, -const struct rhashtable_params *params) +int __rhashtable_init_noprof (struct rhashtable *ht, +const struct rhashtable_params *params, +struct lock_class_key *key) {struct bucket_table *tbl;size_t size;
@@ -1068,7 +1069,7 @@ int rhashtable_init_noprof(struct rhashtable *ht,return -EINVAL ;memset (ht,0 ,sizeof (*ht)); -mutex_init (&ht->mutex); +mutex_init_with_key (&ht->mutex, key);spin_lock_init (&ht->lock);memcpy (&ht->p, params,sizeof (*params));
@@ -1120,7 +1121,7 @@ int rhashtable_init_noprof(struct rhashtable *ht,return 0 ; } -EXPORT_SYMBOL_GPL (rhashtable_init_noprof); +EXPORT_SYMBOL_GPL (__rhashtable_init_noprof);/** * rhltable_init - initialize a new hash list table
@@ -1131,15 +1132,17 @@ EXPORT_SYMBOL_GPL(rhashtable_init_noprof);* * See documentation for rhashtable_init. */ -int rhltable_init_noprof (struct rhltable *hlt,const struct rhashtable_params *params) +int __rhltable_init_noprof (struct rhltable *hlt, +const struct rhashtable_params *params, +struct lock_class_key *key) {int err; - err =rhashtable_init_noprof (&hlt->ht, params); + err =__rhashtable_init_noprof (&hlt->ht, params, key); hlt->ht.rhlist = true;return err; } -EXPORT_SYMBOL_GPL (rhltable_init_noprof); +EXPORT_SYMBOL_GPL (__rhltable_init_noprof); static void rhashtable_free_one(struct rhashtable *ht, struct rhash_head *obj, void (*free_fn)(void *ptr, void *arg),
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 193/2077 rust: alloc: fix `Vec::extend_with` SAFETY comment
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hsiu Che Yu <[email protected]>
[ Upstream commit f497aae6ded43f91b1dbf29a35d7062823635640 ]
Fix an incorrect operator in the SAFETY comment, changing < to <=, since Vec::reserve guarantees capacity for exactly n additional elements, so the equal case should be included.
--- rust/kernel/alloc/kvec.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
rust/kernel/alloc/kvec.rs +1 -1
@@ -866,7 +866,7 @@ impl<T: Clone, A: Allocator> Vec<T, A> { spare[n -1 ].write (value);// SAFETY: -// - `self.len() + n < self.capacity()` due to the call to reserve above, +// - `self.len() + n <= self.capacity()` due to the call to reserve above, // - the loop and the line above initialized the next `n` elements. unsafe { self.inc_len (n) };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 194/2077 clk: scmi: Fix clock rate rounding
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Cristian Marussi <[email protected]>
[ Upstream commit d0c81a38d06d446d341532700b3a4a43d3b00eb1 ]
While the do_div() helper used for rounding expects its divisor argument to be a 32bits quantity, the currently provided divisor parameter is a 64bit value that, as a consequence, is silently truncated and a possible source of bugs.
Fix by using the proper div64_ul helper.
--- drivers/clk/clk-scmi.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/clk/clk-scmi.c +2 -2
@@ -10,9 +10,9 @@#include <linux/device.h> #include <linux/err.h> #include <linux/of.h> +#include <linux/math64.h> #include <linux/module.h> #include <linux/scmi_protocol.h> -#include <asm/div64.h> #define NOT_ATOMIC false#define ATOMIC true
@@ -83,7 +83,7 @@ static int scmi_clk_determine_rate(struct clk_hw *hw, ftmp = req->rate - fmin; ftmp += clk->info->range.step_size -1 ;/* to round up */ -do_div (ftmp, clk->info->range.step_size); + ftmp =div64_ul (ftmp, clk->info->range.step_size); req->rate = ftmp * clk->info->range.step_size + fmin;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 195/2077 arm64: dts: qcom: sm8750: Fix DSI1 phy reference clock rate
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Krzysztof Kozlowski <[email protected]>
[ Upstream commit f4d7c5875a215cd3989b59d13a9c30cec9f0a33b ]
The DSI PHY CXO clock input is the SoC CXO divided by two. DSI0 already uses correct one, but DSI1 got copy-paste from SM8650. Wrong clock parent will cause incorrect DSI1 PHY PLL frequencies to be used making the DSI panel non-working, although there is no upstream user of DSI1.
--- arch/arm64/boot/dts/qcom/sm8750.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/qcom/sm8750.dtsi +1 -1
@@ -3313,7 +3313,7 @@ mdss_dsi1_phy: phy@ae97000 { "dsi_pll"; clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>, - <&rpmhcc RPMH_CXO_CLK>; + <&bi_tcxo_div2>; clock-names = "iface", "ref";
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 196/2077 arm64: dts: qcom: kodiak: Fix ICE reg size
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kuldeep Singh <[email protected]>
[ Upstream commit fa9c7403af64d3e56a6c20dedc60e0a55b527509 ]
The ICE register region on Kodiak is currently defined as 0x8000 bytes. According to the hardware specification, the correct register size is 0x18000.
Update the ICE node reg property to match the hardware.
--- arch/arm64/boot/dts/qcom/kodiak.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/qcom/kodiak.dtsi +1 -1
@@ -2578,7 +2578,7 @@ ufs_mem_phy: phy@1d87000 { ice: crypto@1d88000 { compatible = "qcom,sc7280-inline-crypto-engine", "qcom,inline-crypto-engine"; - reg = <0 0x01d88000 0 0x8000>; + reg = <0 0x01d88000 0 0x18000>; clocks = <&gcc GCC_UFS_PHY_ICE_CORE_CLK>; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 197/2077 arm64: dts: qcom: sm8450: Fix ICE reg size
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kuldeep Singh <[email protected]>
[ Upstream commit 7fb3d0512dacc0d09217eb45057357f00298203d ]
The ICE register region size was originally described incorrectly when the ICE hardware was first introduced. The same value was later carried over unchanged when the ICE node was split out from the UFS node into its own DT entry.
Correct the register size to match the hardware specification.
--- arch/arm64/boot/dts/qcom/sm8450.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/qcom/sm8450.dtsi +1 -1
@@ -5373,7 +5373,7 @@ ufs_mem_phy: phy@1d87000 { ice: crypto@1d88000 { compatible = "qcom,sm8450-inline-crypto-engine", "qcom,inline-crypto-engine"; - reg = <0 0x01d88000 0 0x8000>; + reg = <0 0x01d88000 0 0x18000>; clocks = <&gcc GCC_UFS_PHY_ICE_CORE_CLK>; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 198/2077 platform/chrome: chromeos_privacy_screen: Check ACPI_COMPANION()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rafael J. Wysocki <[email protected]>
[ Upstream commit 8a4a217f617b1ac2f8c095f33efd67d947ddb2cf ]
Every platform driver can be forced to match a device that doesn't match its list of device IDs because of device_match_driver_override(), so platform drivers that rely on the existence of a device's ACPI companion object need to verify its presence.
Accordingly, add a requisite ACPI_COMPANION() check against NULL to the chromeos_privacy_screen driver.
--- drivers/platform/chrome/chromeos_privacy_screen.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/platform/chrome/chromeos_privacy_screen.c +3 -0
@@ -104,6 +104,9 @@ static const struct drm_privacy_screen_ops chromeos_privacy_screen_ops = {static int chromeos_privacy_screen_probe (struct platform_device *pdev) { +if (!ACPI_COMPANION (&pdev->dev)) +return -ENODEV ; +struct drm_privacy_screen *drm_privacy_screen = drm_privacy_screen_register(&pdev->dev, &chromeos_privacy_screen_ops,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 199/2077 platform/chrome: chromeos_tbmc: Check ACPI_COMPANION()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rafael J. Wysocki <[email protected]>
[ Upstream commit c15dbae7c856fb53cc6ffb86c6c64ebb816d07c8 ]
Every platform driver can be forced to match a device that doesn't match its list of device IDs because of device_match_driver_override(), so platform drivers that rely on the existence of a device's ACPI companion object need to verify its presence.
Accordingly, add a requisite ACPI_COMPANION() check against NULL to the chromeos_tbmc driver.
--- drivers/platform/chrome/chromeos_tbmc.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/platform/chrome/chromeos_tbmc.c +5 -1
@@ -69,9 +69,13 @@ static int chromeos_tbmc_probe(struct platform_device *pdev) {struct input_dev *idev;struct device *dev = &pdev->dev; -struct acpi_device *adev =ACPI_COMPANION (dev); +struct acpi_device *adev;int ret; + adev =ACPI_COMPANION (dev); +if (!adev) +return -ENODEV ; + idev =devm_input_allocate_device (dev);if (!idev)return -ENOMEM ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 200/2077 platform/chrome: wilco_ec: event: Check ACPI_COMPANION()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rafael J. Wysocki <[email protected]>
[ Upstream commit 51dcff9796fd486d7abf01081ca62e4072789e9d ]
Every platform driver can be forced to match a device that doesn't match its list of device IDs because of device_match_driver_override(), so platform drivers that rely on the existence of a device's ACPI companion object need to verify its presence.
Accordingly, add a requisite ACPI_COMPANION() check against NULL to the wilco_ec event driver.
--- drivers/platform/chrome/wilco_ec/event.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
drivers/platform/chrome/wilco_ec/event.c +6 -2
@@ -452,8 +452,13 @@ static void hangup_device(struct event_device_data *dev_data)static int event_device_probe (struct platform_device *pdev) {struct event_device_data *dev_data; +struct acpi_device *adev;int error, minor; + adev =ACPI_COMPANION (&pdev->dev); +if (!adev) +return -ENODEV ; + minor =ida_alloc_max (&event_ida,EVENT_MAX_DEV -1 ,GFP_KERNEL );if (minor <0 ) { error = minor;
@@ -494,8 +499,7 @@ static int event_device_probe(struct platform_device *pdev) goto free_dev_data;/* Install an ACPI notify handler. */ - error =acpi_dev_install_notify_handler (ACPI_COMPANION (&pdev->dev), -ACPI_DEVICE_NOTIFY , + error =acpi_dev_install_notify_handler (adev,ACPI_DEVICE_NOTIFY , event_device_notify, &pdev->dev);if (error) goto free_cdev;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 201/2077 drm/hisilicon/hibmc: add updating link cap in DP detect()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lin He <[email protected]>
[ Upstream commit 7d380ef98dd469747b6df43fb0243301b0caaacf ]
In the past, the link cap is updated in link training at encoder enable stage, but the hibmc_dp_mode_valid() is called before it, which will use DP link's rate and lanes. So add the hibmc_dp_update_caps() in hibmc_dp_update_caps() to avoid some potential risks.
--- drivers/gpu/drm/hisilicon/hibmc/dp/dp_comm.h | 1 + drivers/gpu/drm/hisilicon/hibmc/dp/dp_link.c | 2 +- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_dp.c | 2 ++ 3 files changed, 4 insertions(+), 1 deletion(-)
drivers/gpu/drm/hisilicon/hibmc/dp/dp_comm.h +1 -0
@@ -69,5 +69,6 @@ int hibmc_dp_link_training(struct hibmc_dp_dev *dp);int hibmc_dp_serdes_init (struct hibmc_dp_dev *dp);int hibmc_dp_serdes_rate_switch (u8 rate,struct hibmc_dp_dev *dp);int hibmc_dp_serdes_set_tx_cfg (struct hibmc_dp_dev *dp,u8 train_set[HIBMC_DP_LANE_NUM_MAX ]); +void hibmc_dp_update_caps (struct hibmc_dp_dev *dp);#endif
drivers/gpu/drm/hisilicon/hibmc/dp/dp_link.c +1 -1
@@ -325,7 +325,7 @@ static int hibmc_dp_link_downgrade_training_eq(struct hibmc_dp_dev *dp)return hibmc_dp_link_reduce_rate (dp); } -static void hibmc_dp_update_caps (struct hibmc_dp_dev *dp) +void hibmc_dp_update_caps (struct hibmc_dp_dev *dp) { dp->link.cap.link_rate = dp->dpcd[DP_MAX_LINK_RATE ];if (dp->link.cap.link_rate >DP_LINK_BW_8_1 || !dp->link.cap.link_rate)
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_dp.c +2 -0
@@ -41,6 +41,8 @@ static bool hibmc_dp_get_dpcd(struct hibmc_dp_dev *dp_dev)if (ret)return false; +hibmc_dp_update_caps (dp_dev); + dp_dev->is_branch =drm_dp_is_branch (dp_dev->dpcd); ret =drm_dp_read_desc (dp_dev->aux, &dp_dev->desc, dp_dev->is_branch);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 202/2077 drm/hisilicon/hibmc: fix no showing when no connectors connected
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lin He <[email protected]>
[ Upstream commit 4110e29a7c384f1ff21d6b187b6a1772f6e17b23 ]
Our chip support KVM over IP feature, so hibmc driver need to support displaying without any connectors plugged in. If no connectors are connected, the vdac connector status should be set to 'connected' to ensure proper KVM display functionality. Additionally, for previous-generation products that may lack hardware link support and thus cannot detect the monitor, the same approach should be applied to ensure VGA display functionality.
* Add phys_state in the struct of dp and vdac to check physical outputs.
* The 'epoch_counter' of the vdac connector is incremented when the physical status changes.
For get_modes: using BMC modes for connector if no display is attached to phys VGA cable, otherwise use EDID modes by drm_connector_helper_get_modes, because KVM doesn't provide EDID reads.
The polling mechanism for the KMS helper is enabled.
--- drivers/gpu/drm/hisilicon/hibmc/dp/dp_hw.h | 1 + .../gpu/drm/hisilicon/hibmc/hibmc_drm_dp.c | 33 ++++++++---- .../gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 3 ++ .../gpu/drm/hisilicon/hibmc/hibmc_drm_drv.h | 1 + .../gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c | 53 +++++++++++++------ 5 files changed, 64 insertions(+), 27 deletions(-)
drivers/gpu/drm/hisilicon/hibmc/dp/dp_hw.h +1 -0
@@ -55,6 +55,7 @@ struct hibmc_dp {struct drm_dp_aux aux;struct hibmc_dp_cbar_cfg cfg;u32 irq_status; +int phys_status; };int hibmc_dp_hw_init (struct hibmc_dp *dp);
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_dp.c +23 -10
@@ -61,27 +61,38 @@ static int hibmc_dp_detect(struct drm_connector *connector, {struct hibmc_dp *dp =to_hibmc_dp (connector);struct hibmc_dp_dev *dp_dev = dp->dp_dev; -int ret; +int ret = connector_status_disconnected;if (dp->irq_status) { -if (dp_dev->hpd_status !=HIBMC_HPD_IN ) -return connector_status_disconnected; +if (dp_dev->hpd_status !=HIBMC_HPD_IN ) { + ret = connector_status_disconnected; + goto exit; + } } -if (!hibmc_dp_get_dpcd (dp_dev)) -return connector_status_disconnected; +if (!hibmc_dp_get_dpcd (dp_dev)) { + ret = connector_status_disconnected; + goto exit; + } -if (!dp_dev->is_branch) -return connector_status_connected; +if (!dp_dev->is_branch) { + ret = connector_status_connected; + goto exit; + }if (drm_dp_read_sink_count_cap (connector, dp_dev->dpcd, &dp_dev->desc) && dp_dev->downstream_ports[0 ] &DP_DS_PORT_HPD ) { ret =drm_dp_read_sink_count (dp_dev->aux); -if (ret >0 ) -return connector_status_connected; +if (ret >0 ) { + ret = connector_status_connected; + goto exit; + } } -return connector_status_disconnected; +exit: + dp->phys_status = ret; + +return ret; } static int hibmc_dp_mode_valid(struct drm_connector *connector,
@@ -243,5 +254,7 @@ int hibmc_dp_init(struct hibmc_drm_private *priv) connector->polled =DRM_CONNECTOR_POLL_HPD ; + dp->phys_status = connector_status_disconnected; +return 0 ; }
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c +3 -0
@@ -24,6 +24,7 @@#include <drm/drm_managed.h> #include <drm/drm_module.h> #include <drm/drm_vblank.h> +#include <drm/drm_probe_helper.h> #include "hibmc_drm_drv.h" #include "hibmc_drm_regs.h"
@@ -355,6 +356,8 @@ static int hibmc_load(struct drm_device *dev)/* reset all the states of crtc/plane/encoder/connector */ drm_mode_config_reset (dev); +drmm_kms_helper_poll_init (dev); +return 0 ; err:
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.h +1 -0
@@ -31,6 +31,7 @@ struct hibmc_vdac {struct drm_connector connector;struct i2c_adapter adapter;struct i2c_algo_bit_data bit_data; +int phys_status; };struct hibmc_drm_private {
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c +36 -17
80 lines not on this page · raw message
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 203/2077 drm/hisilicon/hibmc: move display contrl config to hibmc_probe()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lin He <[email protected]>
[ Upstream commit de2a56c71f9b223922ea8fe0192d3c1fa2954608 ]
If there's no VGA output, this encoder modeset won't be called, which will cause displaying data from GPU being cut off. It's actually a common display config for DP and VGA, so move the vdac encoder modeset to driver load stage.
Removed invalid bit configurations from hibmc_display_ctrl
--- .../gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 11 ++++++++++ .../gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c | 22 ------------------- 2 files changed, 11 insertions(+), 22 deletions(-)
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c +11 -0
@@ -215,6 +215,15 @@ void hibmc_set_current_gate(struct hibmc_drm_private *priv, unsigned int gate)writel (gate, mmio + gate_reg); } +static void hibmc_display_ctrl (struct hibmc_drm_private *priv) +{ +u32 reg; + + reg =readl (priv->mmio +HIBMC_DISPLAY_CONTROL_HISILE ); + reg |=HIBMC_DISPLAY_CONTROL_PANELDATE (1 ); +writel (reg, priv->mmio +HIBMC_DISPLAY_CONTROL_HISILE ); +} +static void hibmc_hw_config (struct hibmc_drm_private *priv) {u32 reg;
@@ -246,6 +255,8 @@ static void hibmc_hw_config(struct hibmc_drm_private *priv) reg |=HIBMC_MSCCTL_LOCALMEM_RESET (1 );writel (reg, priv->mmio +HIBMC_MISC_CTRL ); + +hibmc_display_ctrl (priv); }static int hibmc_hw_map (struct hibmc_drm_private *priv)
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c +0 -22
@@ -88,26 +88,6 @@ static const struct drm_connector_funcs hibmc_connector_funcs = { .atomic_destroy_state = drm_atomic_helper_connector_destroy_state, }; -static void hibmc_encoder_mode_set (struct drm_encoder *encoder, -struct drm_display_mode *mode, -struct drm_display_mode *adj_mode) -{ -u32 reg; -struct drm_device *dev = encoder->dev; -struct hibmc_drm_private *priv =to_hibmc_drm_private (dev); - - reg =readl (priv->mmio +HIBMC_DISPLAY_CONTROL_HISILE ); - reg |=HIBMC_DISPLAY_CONTROL_FPVDDEN (1 ); - reg |=HIBMC_DISPLAY_CONTROL_PANELDATE (1 ); - reg |=HIBMC_DISPLAY_CONTROL_FPEN (1 ); - reg |=HIBMC_DISPLAY_CONTROL_VBIASEN (1 ); -writel (reg, priv->mmio +HIBMC_DISPLAY_CONTROL_HISILE ); -} - -static const struct drm_encoder_helper_funcs hibmc_encoder_helper_funcs = { - .mode_set = hibmc_encoder_mode_set, -}; -int hibmc_vdac_init (struct hibmc_drm_private *priv) {struct drm_device *dev = &priv->dev;
@@ -130,8 +110,6 @@ int hibmc_vdac_init(struct hibmc_drm_private *priv) goto err; } -drm_encoder_helper_add (encoder, &hibmc_encoder_helper_funcs); - ret = drm_connector_init_with_ddc(dev, connector, &hibmc_connector_funcs, DRM_MODE_CONNECTOR_VGA,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 204/2077 drm/hisilicon/hibmc: use clock to look up the PLL value
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lin He <[email protected]>
[ Upstream commit 99ef3a4f1c1813cabd50bb3e8522e85e00838bb2 ]
In the past, we use width and height to look up our PLL value. But actually the actual clock check is also necessnary. There are some resolutions that width and height same, but its clock different. Add the clock check when using pll_table to determine the PLL value.
--- .../gpu/drm/hisilicon/hibmc/hibmc_drm_de.c | 80 +++++++++++-------- 1 file changed, 45 insertions(+), 35 deletions(-)
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.c +45 -35
@@ -32,26 +32,43 @@ struct hibmc_display_panel_pll {struct hibmc_dislay_pll_config {u64 hdisplay;u64 vdisplay; +int clock;u32 pll1_config_value;u32 pll2_config_value; };static const struct hibmc_dislay_pll_config hibmc_pll_table[] = { - {640 ,480 ,CRT_PLL1_HS_25MHZ ,CRT_PLL2_HS_25MHZ }, - {800 ,600 ,CRT_PLL1_HS_40MHZ ,CRT_PLL2_HS_40MHZ }, - {1024 ,768 ,CRT_PLL1_HS_65MHZ ,CRT_PLL2_HS_65MHZ }, - {1152 ,864 ,CRT_PLL1_HS_80MHZ_1152 ,CRT_PLL2_HS_80MHZ }, - {1280 ,768 ,CRT_PLL1_HS_80MHZ ,CRT_PLL2_HS_80MHZ }, - {1280 ,720 ,CRT_PLL1_HS_74MHZ ,CRT_PLL2_HS_74MHZ }, - {1280 ,960 ,CRT_PLL1_HS_108MHZ ,CRT_PLL2_HS_108MHZ }, - {1280 ,1024 ,CRT_PLL1_HS_108MHZ ,CRT_PLL2_HS_108MHZ }, - {1440 ,900 ,CRT_PLL1_HS_106MHZ ,CRT_PLL2_HS_106MHZ }, - {1600 ,900 ,CRT_PLL1_HS_108MHZ ,CRT_PLL2_HS_108MHZ }, - {1600 ,1200 ,CRT_PLL1_HS_162MHZ ,CRT_PLL2_HS_162MHZ }, - {1920 ,1080 ,CRT_PLL1_HS_148MHZ ,CRT_PLL2_HS_148MHZ }, - {1920 ,1200 ,CRT_PLL1_HS_193MHZ ,CRT_PLL2_HS_193MHZ }, + {640 ,480 ,25000 ,CRT_PLL1_HS_25MHZ ,CRT_PLL2_HS_25MHZ }, + {800 ,600 ,40000 ,CRT_PLL1_HS_40MHZ ,CRT_PLL2_HS_40MHZ }, + {1024 ,768 ,65000 ,CRT_PLL1_HS_65MHZ ,CRT_PLL2_HS_65MHZ }, + {1152 ,864 ,78750 ,CRT_PLL1_HS_80MHZ_1152 ,CRT_PLL2_HS_80MHZ }, + {1280 ,768 ,80000 ,CRT_PLL1_HS_80MHZ ,CRT_PLL2_HS_80MHZ }, + {1280 ,720 ,74375 ,CRT_PLL1_HS_74MHZ ,CRT_PLL2_HS_74MHZ }, + {1280 ,960 ,108000 ,CRT_PLL1_HS_108MHZ ,CRT_PLL2_HS_108MHZ }, + {1280 ,1024 ,108000 ,CRT_PLL1_HS_108MHZ ,CRT_PLL2_HS_108MHZ }, + {1440 ,900 ,105952 ,CRT_PLL1_HS_106MHZ ,CRT_PLL2_HS_106MHZ }, + {1600 ,900 ,108000 ,CRT_PLL1_HS_108MHZ ,CRT_PLL2_HS_108MHZ }, + {1600 ,1200 ,162500 ,CRT_PLL1_HS_162MHZ ,CRT_PLL2_HS_162MHZ }, + {1920 ,1080 ,148750 ,CRT_PLL1_HS_148MHZ ,CRT_PLL2_HS_148MHZ }, + {1920 ,1200 ,193750 ,CRT_PLL1_HS_193MHZ ,CRT_PLL2_HS_193MHZ }, }; +static int hibmc_get_best_clock_idx (const struct drm_display_mode *mode) +{ +int i, diff; + +for (i =0 ; i <ARRAY_SIZE (hibmc_pll_table); i++) { +if (hibmc_pll_table[i].hdisplay == mode->hdisplay && + hibmc_pll_table[i].vdisplay == mode->vdisplay) { + diff =abs (mode->clock - hibmc_pll_table[i].clock); +if (diff < mode->clock /100 )/* tolerance 1/100 */ +return i; + } + } + +return -MODE_CLOCK_RANGE ; +} +static int hibmc_plane_atomic_check (struct drm_plane *plane,struct drm_atomic_state *state) {
@@ -214,19 +231,15 @@ static enum drm_mode_status hibmc_crtc_mode_valid(struct drm_crtc *crtc, const struct drm_display_mode *mode) { - size_t i = 0; int vrefresh = drm_mode_vrefresh(mode);if (vrefresh <59 || vrefresh >61 )return MODE_NOCLOCK ; -for (i =0 ; i <ARRAY_SIZE (hibmc_pll_table); i++) { -if (hibmc_pll_table[i].hdisplay == mode->hdisplay && - hibmc_pll_table[i].vdisplay == mode->vdisplay) -return MODE_OK ; - } +if (hibmc_get_best_clock_idx (mode) >=0 ) +return MODE_OK ; -return MODE_BAD ; +return MODE_CLOCK_RANGE ; }static u32 format_pll_reg (void )
@@ -281,23 +294,20 @@ static void set_vclock_hisilicon(struct drm_device *dev, u64 pll)writel (val, priv->mmio +CRT_PLL1_HS ); } -static void get_pll_config (u64 x,u64 y,u32 *pll1,u32 *pll2) +static void get_pll_config (struct drm_display_mode *mode,u32 *pll1,u32 *pll2) { -size_t i; -size_t count =ARRAY_SIZE (hibmc_pll_table); - -for (i =0 ; i < count; i++) { -if (hibmc_pll_table[i].hdisplay == x && - hibmc_pll_table[i].vdisplay == y) { - *pll1 = hibmc_pll_table[i].pll1_config_value; - *pll2 = hibmc_pll_table[i].pll2_config_value; -return ; - } +int idx; + + idx =hibmc_get_best_clock_idx (mode); +if (idx <0 ) { +/* if found none, we use default value */ + *pll1 =CRT_PLL1_HS_25MHZ ; + *pll2 =CRT_PLL2_HS_25MHZ ; +return ; } -/* if found none, we use default value */ - *pll1 =CRT_PLL1_HS_25MHZ ; - *pll2 =CRT_PLL2_HS_25MHZ ; + *pll1 = hibmc_pll_table[idx].pll1_config_value; + *pll2 = hibmc_pll_table[idx].pll2_config_value; }/*
@@ -319,7 +329,7 @@ static u32 display_ctrl_adjust(struct drm_device *dev, x = mode->hdisplay; y = mode->vdisplay; -get_pll_config (x, y, &pll1, &pll2); +get_pll_config (mode, &pll1, &pll2);writel (pll2, priv->mmio +CRT_PLL2_HS );set_vclock_hisilicon (dev, pll1);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 205/2077 evm: terminate and bound the evm_xattrs read buffer
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Pengpeng Hou <[email protected]>
[ Upstream commit 11143a19f5b8dc8f414deab87571134f9f447313 ]
evm_read_xattrs() allocates size + 1 bytes, fills them from the list of enabled xattrs, and then passes strlen(temp) to simple_read_from_buffer(). When no configured xattrs are enabled, the fill loop stores nothing and temp[0] remains uninitialized, so strlen() reads beyond initialized memory.
Explicitly terminate the buffer after allocation, use snprintf() for each formatted line, and pass the accumulated length, without risk of truncation, to simple_read_from_buffer().
--- security/integrity/evm/evm_secfs.c | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-)
security/integrity/evm/evm_secfs.c +11 -5
@@ -127,8 +127,8 @@ static ssize_t evm_read_xattrs(struct file *filp, char __user *buf, size_t count, loff_t *ppos) { char *temp; -int offset =0 ; -ssize_t rc, size =0 ; +size_t offset =0 , size =0 ; +ssize_t rc;struct xattr_list *xattr;if (*ppos !=0 )
@@ -151,16 +151,22 @@ static ssize_t evm_read_xattrs(struct file *filp, char __user *buf,return -ENOMEM ; } + temp[size] ='\0' ; + +/* +* No truncation possible: size is computed over the same enabled +* xattrs under xattr_list_mutex, so offset never exceeds size. +*/ list_for_each_entry (xattr, &evm_config_xattrnames, list) {if (!xattr->enabled)continue ; -sprintf (temp + offset,"%s\n" , xattr->name); - offset +=strlen (xattr->name) +1 ; + offset +=snprintf (temp + offset, size +1 - offset,"%s\n" , + xattr->name); }mutex_unlock (&xattr_list_mutex); - rc =simple_read_from_buffer (buf, count, ppos, temp,strlen (temp)); + rc =simple_read_from_buffer (buf, count, ppos, temp, offset);kfree (temp);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 206/2077 thermal: hwmon: Fix critical temperature attribute removal
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rafael J. Wysocki <[email protected]>
[ Upstream commit c2114dbda05354dbcf4dfbb30a2c623e8611c43a ]
Since the return value of thermal_zone_crit_temp_valid() depends on the behavior of the thermal zone .get_crit_temp() callback which may change over time in theory, thermal_remove_hwmon_sysfs() may attempt to remove a critical temperature attribute that has not been created, passing a pointer to an uninitialized attribute structure to device_remove_file().
To avoid that, set a flag in struct thermal_hwmon_temp after creating a critical temperature attribute and use the value of that flag to decide whether or not the attribute needs to be removed.
--- drivers/thermal/thermal_hwmon.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/thermal/thermal_hwmon.c +4 -1
@@ -40,6 +40,7 @@ struct thermal_hwmon_temp {struct thermal_zone_device *tz;struct thermal_hwmon_attr temp_input;/* hwmon sys attr */ struct thermal_hwmon_attr temp_crit;/* hwmon sys attr */ +bool temp_crit_present; };static LIST_HEAD (thermal_hwmon_list);
@@ -191,6 +192,8 @@ int thermal_add_hwmon_sysfs(struct thermal_zone_device *tz) &temp->temp_crit.attr);if (result) goto unregister_input; + + temp->temp_crit_present = true; }mutex_lock (&thermal_hwmon_list_lock);
@@ -235,7 +238,7 @@ void thermal_remove_hwmon_sysfs(struct thermal_zone_device *tz) }device_remove_file (hwmon->device, &temp->temp_input.attr); -if (thermal_zone_crit_temp_valid (tz)) +if (temp->temp_crit_present)device_remove_file (hwmon->device, &temp->temp_crit.attr);mutex_lock (&thermal_hwmon_list_lock);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 207/2077 thermal: hwmon: Register a hwmon device for each thermal zone
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rafael J. Wysocki <[email protected]>
[ Upstream commit d6323469bcfbda91f0aa89b7b39ad45fe822ca5d ]
The current code creates one hwmon device per thermal zone type and that device is registered under the first thermal zone of the given type.
That turns out to be problematic when the thermal zone holding the hwmon device is removed.
For example, say that there are two ACPI thermal zones on a system
/sys/devices/virtual/thermal/thermal_zone0//sys/devices/virtual/thermal/thermal_zone1/
The current code registers a hwmon class device for thermal_zone0 only:
/sys/devices/virtual/thermal/thermal_zone0/hwmon0/
because the type is "acpitz" for both of them, but it adds a sysfs attribute that belongs to thermal_zone1 under it:
/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp2_input
There is also
/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input
which belongs to thermal_zone0.
When thermal_zone0 is removed, say because the ACPI thermal driver is unbound from the underlying platform device, the removal code skips the removal of hwmon0 because of the temp2_input attribute belonging to thermal_zone1 which effectively prevents thermal_zone0 removal from making progress.
To address this problem, rework the thermal hwmon code to register one hwmon device for each thermal zone, but since user space utilities produce confusing output in some cases when there are multiple hwmon devices with the same name attribute value present under thermal zones of the same type, append the thermal zone ID preceded by an underline character to the name of the hwmon device registered for that thermal zone.
--- drivers/thermal/thermal_hwmon.c | 151 ++++++++++---------------------- 1 file changed, 47 insertions(+), 104 deletions(-)
drivers/thermal/thermal_hwmon.c +47 -104
@@ -19,30 +19,33 @@#include "thermal_hwmon.h" #include "thermal_core.h" -/* hwmon sys I/F */ -/* thermal zone devices with the same type share one hwmon device */ -struct thermal_hwmon_device { -char type[THERMAL_NAME_LENGTH ]; -struct device *device; -int count; -struct list_head tz_list; -struct list_head node; -}; +/* +* Needs to be large enough to hold a thermal zone type string followed by an +* underline character and a 32-bit integer in decimal representation. +*/ +#define THERMAL_HWMON_NAME_LENGTH (THERMAL_NAME_LENGTH + 11)struct thermal_hwmon_attr {struct device_attribute attr; -char name[16 ]; };/* one temperature input for each thermal zone */ struct thermal_hwmon_temp { -struct list_head hwmon_node;struct thermal_zone_device *tz;struct thermal_hwmon_attr temp_input;/* hwmon sys attr */ struct thermal_hwmon_attr temp_crit;/* hwmon sys attr */ bool temp_crit_present; }; +/* hwmon sys I/F */ +/* thermal zone devices with the same type share one hwmon device */ +struct thermal_hwmon_device { +char name[THERMAL_HWMON_NAME_LENGTH ]; +struct device *device; +struct list_head node; +struct thermal_hwmon_temp tz_temp; +}; +static LIST_HEAD (thermal_hwmon_list);static DEFINE_MUTEX (thermal_hwmon_list_lock);
@@ -88,45 +91,6 @@ temp_crit_show(struct device *dev, struct device_attribute *attr, char *buf)return sysfs_emit (buf,"%d\n" , temperature); } - -static struct thermal_hwmon_device * -thermal_hwmon_lookup_by_type (const struct thermal_zone_device *tz) -{ -struct thermal_hwmon_device *hwmon; -char type[THERMAL_NAME_LENGTH ]; - -mutex_lock (&thermal_hwmon_list_lock); -list_for_each_entry (hwmon, &thermal_hwmon_list, node) { -strscpy (type, tz->type); -strreplace (type,'-' ,'_' ); -if (!strcmp (hwmon->type, type)) { -mutex_unlock (&thermal_hwmon_list_lock); -return hwmon; - } - } -mutex_unlock (&thermal_hwmon_list_lock); - -return NULL ; -} - -/* Find the temperature input matching a given thermal zone */ -static struct thermal_hwmon_temp * -thermal_hwmon_lookup_temp (const struct thermal_hwmon_device *hwmon, -const struct thermal_zone_device *tz) -{ -struct thermal_hwmon_temp *temp; - -mutex_lock (&thermal_hwmon_list_lock); -list_for_each_entry (temp, &hwmon->tz_list, hwmon_node) -if (temp->tz == tz) { -mutex_unlock (&thermal_hwmon_list_lock); -return temp; - } -mutex_unlock (&thermal_hwmon_list_lock); - -return NULL ; -} -static bool thermal_zone_crit_temp_valid (struct thermal_zone_device *tz) {int temp;
@@ -137,54 +101,39 @@ int thermal_add_hwmon_sysfs(struct thermal_zone_device *tz) {struct thermal_hwmon_device *hwmon;struct thermal_hwmon_temp *temp; -int new_hwmon_device =1 ;int result; - hwmon =thermal_hwmon_lookup_by_type (tz); -if (hwmon) { - new_hwmon_device =0 ; - goto register_sys_interface; - } - hwmon =kzalloc_obj (*hwmon);if (!hwmon)return -ENOMEM ; -INIT_LIST_HEAD (&hwmon->tz_list); -strscpy (hwmon->type, tz->type,THERMAL_NAME_LENGTH ); -strreplace (hwmon->type,'-' ,'_' ); +/* +* Append the thermal zone ID preceded by an underline character to the +* type to disambiguate the sensors command output. +*/ +scnprintf (hwmon->name,THERMAL_HWMON_NAME_LENGTH ,"%s_%d" , tz->type, tz->id); +strreplace (hwmon->name,'-' ,'_' ); hwmon->device =hwmon_device_register_for_thermal (&tz->device, - hwmon->type, hwmon); + hwmon->name, hwmon);if (IS_ERR (hwmon->device)) { result =PTR_ERR (hwmon->device); goto free_mem; } - register_sys_interface: - temp =kzalloc_obj (*temp); -if (!temp) { - result = -ENOMEM ; - goto unregister_name; - } + temp = &hwmon->tz_temp; temp->tz = tz; - hwmon->count++; -snprintf (temp->temp_input.name,sizeof (temp->temp_input.name), -"temp%d_input" , hwmon->count); - temp->temp_input.attr.attr.name = temp->temp_input.name; + temp->temp_input.attr.attr.name ="temp1_input" ; temp->temp_input.attr.attr.mode =0444 ; temp->temp_input.attr.show = temp_input_show;sysfs_attr_init (&temp->temp_input.attr.attr); result =device_create_file (hwmon->device, &temp->temp_input.attr);if (result) - goto free_temp_mem; + goto unregister_name;if (thermal_zone_crit_temp_valid (tz)) { -snprintf (temp->temp_crit.name, -sizeof (temp->temp_crit.name), -"temp%d_crit" , hwmon->count); - temp->temp_crit.attr.attr.name = temp->temp_crit.name; + temp->temp_crit.attr.attr.name ="temp1_crit" ; temp->temp_crit.attr.attr.mode =0444 ; temp->temp_crit.attr.show = temp_crit_show;sysfs_attr_init (&temp->temp_crit.attr.attr);
@@ -196,21 +145,17 @@ int thermal_add_hwmon_sysfs(struct thermal_zone_device *tz) temp->temp_crit_present = true; } +/* The list is needed for hwmon lookup during removal. */ mutex_lock (&thermal_hwmon_list_lock); -if (new_hwmon_device) -list_add_tail (&hwmon->node, &thermal_hwmon_list); -list_add_tail (&temp->hwmon_node, &hwmon->tz_list); +list_add_tail (&hwmon->node, &thermal_hwmon_list);mutex_unlock (&thermal_hwmon_list_lock);return 0 ; unregister_input:device_remove_file (hwmon->device, &temp->temp_input.attr); - free_temp_mem: -kfree (temp); unregister_name: -if (new_hwmon_device) -hwmon_device_unregister (hwmon->device); +hwmon_device_unregister (hwmon->device); free_mem:kfree (hwmon);
@@ -218,39 +163,37 @@ int thermal_add_hwmon_sysfs(struct thermal_zone_device *tz) }EXPORT_SYMBOL_GPL (thermal_add_hwmon_sysfs); +static struct thermal_hwmon_device * +thermal_hwmon_lookup (const struct thermal_zone_device *tz) +{ +struct thermal_hwmon_device *hwmon; + +list_for_each_entry (hwmon, &thermal_hwmon_list, node) { +if (hwmon->tz_temp.tz == tz) +return hwmon; + } +return NULL ; +} +void thermal_remove_hwmon_sysfs (struct thermal_zone_device *tz) {struct thermal_hwmon_device *hwmon;struct thermal_hwmon_temp *temp; - hwmon =thermal_hwmon_lookup_by_type (tz); -if (unlikely (!hwmon)) { -/* Should never happen... */ -dev_dbg (&tz->device,"hwmon device lookup failed!\n" ); -return ; - } + scoped_guard(mutex, &thermal_hwmon_list_lock) { + hwmon =thermal_hwmon_lookup (tz); +if (!hwmon) +return ; - temp =thermal_hwmon_lookup_temp (hwmon, tz); -if (unlikely (!temp)) { -/* Should never happen... */ -dev_dbg (&tz->device,"temperature input lookup failed!\n" ); -return ; +list_del (&hwmon->node); } + temp = &hwmon->tz_temp; +device_remove_file (hwmon->device, &temp->temp_input.attr);if (temp->temp_crit_present)device_remove_file (hwmon->device, &temp->temp_crit.attr); -mutex_lock (&thermal_hwmon_list_lock); -list_del (&temp->hwmon_node); -kfree (temp); -if (!list_empty (&hwmon->tz_list)) { -mutex_unlock (&thermal_hwmon_list_lock); -return ; - } -list_del (&hwmon->node); -mutex_unlock (&thermal_hwmon_list_lock); -hwmon_device_unregister (hwmon->device);kfree (hwmon); }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 208/2077 clk: scpi: Unregister child clock providers on remove
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stepan Ionichev <[email protected]>
[ Upstream commit b79d9b5747d961516c35ef4d5e91efa579fd3e9a ]
SCPI clock providers are registered for each child node in scpi_clk_add(), but scpi_clocks_remove() unregisters the parent node on each iteration.
of_clk_del_provider() matches providers by the node used at registration time, so passing the parent node leaves the child providers registered. This leaks the provider allocations and the node references held by the clock provider core.
Pass the child node to of_clk_del_provider() so the remove path matches the probe path.
(sudeep.holla: Updated commit title and message a bit)
--- drivers/clk/clk-scpi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/clk/clk-scpi.c +1 -1
@@ -258,7 +258,7 @@ static void scpi_clocks_remove(struct platform_device *pdev) }for_each_available_child_of_node (np, child) -of_clk_del_provider (np); +of_clk_del_provider (child); }static int scpi_clocks_probe (struct platform_device *pdev)
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 209/2077 net/sched: sch_hfsc: annotate data-races in hfsc_dump_class_stats()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit e300c7d470ad2726d6abf7d11b31b5d9912d9cf0 ]
hfsc_dump_class_stats() runs without qdisc spinlock being held.
Add READ_ONCE()/WRITE_ONCE() annotations around:
- cl->level
- cl->cl_vtperiod
- cl->cl_total
- cl->cl_cumul
--- net/sched/sch_hfsc.c | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-)
net/sched/sch_hfsc.c +11 -11
@@ -715,7 +715,7 @@ init_vf(struct hfsc_class *cl, unsigned int len)rtsc_min (&cl->cl_virtual, &cl->cl_fsc, cl->cl_vt, cl->cl_total); cl->cl_vtadj =0 ; - cl->cl_vtperiod++;/* increment vt period */ +WRITE_ONCE (cl->cl_vtperiod, cl->cl_vtperiod +1 );/* increment vt period */ cl->cl_parentperiod = cl->cl_parent->cl_vtperiod;if (cl->cl_parent->cl_nactive ==0 ) cl->cl_parentperiod++;
@@ -757,7 +757,7 @@ update_vf(struct hfsc_class *cl, unsigned int len, u64 cur_time) go_passive =1 ;for (; cl->cl_parent !=NULL ; cl = cl->cl_parent) { - cl->cl_total += len; +WRITE_ONCE (cl->cl_total, cl->cl_total + len);if (!(cl->cl_flags &HFSC_FSC ) || cl->cl_nactive ==0 )continue ;
@@ -847,7 +847,7 @@ hfsc_adjust_levels(struct hfsc_class *cl)if (p->level >= level) level = p->level +1 ; } - cl->level = level; +WRITE_ONCE (cl->level, level); }while ((cl = cl->cl_parent) !=NULL ); }
@@ -1338,10 +1338,10 @@ hfsc_dump_class_stats(struct Qdisc *sch, unsigned long arg,__u32 qlen;qdisc_qstats_qlen_backlog (cl->qdisc, &qlen, &cl->qstats.backlog); - xstats.level = cl->level; - xstats.period = cl->cl_vtperiod; - xstats.work = cl->cl_total; - xstats.rtwork = cl->cl_cumul; + xstats.level =READ_ONCE (cl->level); + xstats.period =READ_ONCE (cl->cl_vtperiod); + xstats.work =READ_ONCE (cl->cl_total); + xstats.rtwork =READ_ONCE (cl->cl_cumul); if (gnet_stats_copy_basic(d, NULL, &cl->bstats, true) < 0 || gnet_stats_copy_rate_est(d, &cl->rate_est) < 0 ||
@@ -1452,15 +1452,15 @@ hfsc_change_qdisc(struct Qdisc *sch, struct nlattr *opt,static void hfsc_reset_class (struct hfsc_class *cl) { - cl->cl_total =0 ; - cl->cl_cumul =0 ; +WRITE_ONCE (cl->cl_total,0 ); +WRITE_ONCE (cl->cl_cumul,0 ); cl->cl_d =0 ; cl->cl_e =0 ; cl->cl_vt =0 ; cl->cl_vtadj =0 ; cl->cl_cvtmin =0 ; cl->cl_cvtoff =0 ; - cl->cl_vtperiod =0 ; +WRITE_ONCE (cl->cl_vtperiod,0 ); cl->cl_parentperiod =0 ; cl->cl_f =0 ; cl->cl_myf =0 ;
@@ -1626,7 +1626,7 @@ hfsc_dequeue(struct Qdisc *sch)bstats_update (&cl->bstats, skb);update_vf (cl,qdisc_pkt_len (skb), cur_time);if (realtime) - cl->cl_cumul +=qdisc_pkt_len (skb); +WRITE_ONCE (cl->cl_cumul, cl->cl_cumul +qdisc_pkt_len (skb));if (cl->cl_flags &HFSC_RSC ) {if (cl->qdisc->q.qlen !=0 ) {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 210/2077 scsi: hisi_sas: Add slave_destroy interface for v3 hw
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yihang Li <[email protected]>
[ Upstream commit 67b85a88265df19f049241d8c00571a5408f4eeb ]
WARNING is triggered when executing link reset of remote PHY and rmmod SAS driver simultaneously. Following is the WARNING log:
WARNING: CPU: 61 PID: 21818 at drivers/base/core.c:1347 __device_links_no_driver+0xb4/0xc0 Call trace: __device_links_no_driver+0xb4/0xc0 device_links_driver_cleanup+0xb0/0xfc __device_release_driver+0x198/0x23c device_release_driver+0x38/0x50 bus_remove_device+0x130/0x140 device_del+0x184/0x434 __scsi_remove_device+0x118/0x150 scsi_remove_target+0x1bc/0x240 sas_rphy_remove+0x90/0x94 sas_rphy_delete+0x24/0x3c sas_destruct_devices+0x64/0xa0 [libsas] sas_revalidate_domain+0xe4/0x150 [libsas] process_one_work+0x1e0/0x46c worker_thread+0x15c/0x464 kthread+0x160/0x170 ret_from_fork+0x10/0x20 ---[ end trace 71e059eb58f85d4a ]---
During SAS phy up, link->status is set to DL_STATE_AVAILABLE in device_links_driver_bound, then this setting influences __device_links_no_driver() before driver rmmod and caused WARNING.
Add the slave_destroy interface to make sure link is removed after flush workque.
--- drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-)
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c +11 -1
@@ -2977,7 +2977,7 @@ static int sdev_configure_v3_hw(struct scsi_device *sdev,return 0 ;if (!device_link_add (&sdev->sdev_gendev, dev, -DL_FLAG_PM_RUNTIME |DL_FLAG_RPM_ACTIVE )) { +DL_FLAG_STATELESS |DL_FLAG_PM_RUNTIME |DL_FLAG_RPM_ACTIVE )) {if (pm_runtime_enabled (dev)) {dev_info (dev,"add device link failed, disable runtime PM for the host\n" );pm_runtime_disable (dev);
@@ -2987,6 +2987,15 @@ static int sdev_configure_v3_hw(struct scsi_device *sdev,return 0 ; } +static void hisi_sas_sdev_destroy (struct scsi_device *sdev) +{ +struct Scsi_Host *shost =dev_to_shost (&sdev->sdev_gendev); +struct hisi_hba *hisi_hba =shost_priv (shost); +struct device *dev = hisi_hba->dev; + +device_link_remove (&sdev->sdev_gendev, dev); +} +static struct attribute *host_v3_hw_attrs[] = { &dev_attr_phy_event_threshold.attr, &dev_attr_intr_conv_v3_hw.attr,
@@ -3401,6 +3410,7 @@ static const struct scsi_host_template sht_v3_hw = { .sg_tablesize = HISI_SAS_SGE_PAGE_CNT, .sg_prot_tablesize = HISI_SAS_SGE_PAGE_CNT, .sdev_init = hisi_sas_sdev_init, + .sdev_destroy = hisi_sas_sdev_destroy, .shost_groups = host_v3_hw_groups, .sdev_groups = sdev_groups_v3_hw, .tag_alloc_policy_rr = true,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 211/2077 crypto: ccp - Treat zero-length cert chain as query for blob lengths
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Christopherson <[email protected]>
[ Upstream commit ef8c9dacda2871accd64e3eda951fef6b788b1ea ]
When handling a PDH export, treat a zero-length userspace cert chain buffer as a request to query the length of the relevant blobs. Failure to account for the zero-length buffer trips a BUG_ON() when running with CONFIG_DEBUG_VIRTUAL=y due to trying to get the physical address of the ZERO_SIZE_PTR (returned by kzalloc() on the bogus allocation).
kernel BUG at arch/x86/mm/physaddr.c:28 !
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 30 UID: 0 PID: 28580 Comm: syz.2.18 Kdump: loaded
Tainted: G W 6.18.16-smp-DEV #1 NONE
Tainted: [W]=WARN
Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025
RIP: 0010:__phys_addr+0x16a/0x180 arch/x86/mm/physaddr.c:28
RSP: 0018:ffffc9008329fc80 EFLAGS: 00010293
RAX: ffffffff8179110a RBX: 0000778000000010 RCX: ffff8884e6992600
RDX: 0000000000000000 RSI: 0000000080000010 RDI: 0000778000000010
RBP: ffffc9008329fdf0 R08: 0000000000000dc0 R09: 00000000ffffffff
R10: dffffc0000000000 R11: fffffbfff126d297 R12: dffffc0000000000
R13: 1ffff92010653fc8 R14: 0000000080000010 R15: dffffc0000000000
FS: 0000555556bec9c0(0000) GS:ffff88aa4ce1c000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd3159e7000 CR3: 00000004fbc44000 CR4: 0000000000350ef0
Call Trace:
<TASK>
[<ffffffff853d3869>] sev_ioctl_do_pdh_export+0x559/0x7a0 drivers/crypto/ccp/sev-dev.c:2308
[<ffffffff853d1fdd>] sev_ioctl+0x2cd/0x480 drivers/crypto/ccp/sev-dev.c:2556
[<ffffffff82549ebc>] vfs_ioctl fs/ioctl.c:52 [inline]
[<ffffffff82549ebc>] __do_sys_ioctl fs/ioctl.c:598 [inline]
[<ffffffff82549ebc>] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:584
[<ffffffff8630115f>] do_syscall_x64 arch/x86/entry/syscall_64.c:64 [inline]
[<ffffffff8630115f>] do_syscall_64+0x9f/0xf40 arch/x86/entry/syscall_64.c:98
[<ffffffff81000136>] entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7fd3158eac39
</TASK>Thankfully, the bug is benign outside of CONFIG_DEBUG_VIRTUAL=y as getting the physical address is just arithmetic, and the PSP errors out before trying to write to the garbage address (which it must, otherwise querying the blob lengths would clobber memory at pfn=0).
--- drivers/crypto/ccp/sev-dev.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/crypto/ccp/sev-dev.c +2 -1
@@ -2286,7 +2286,8 @@ static int sev_ioctl_do_pdh_export(struct sev_issue_cmd *argp, bool writable)/* Userspace wants to query the certificate length. */ if (!input.pdh_cert_address || !input.pdh_cert_len || - !input.cert_chain_address) + !input.cert_chain_address || + !input.cert_chain_len) goto cmd;/* Allocate a physically contiguous buffer to store the PDH blob. */
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 212/2077 crypto: af_alg - Cap AEAD AD length to 0x80000000
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Herbert Xu <[email protected]>
[ Upstream commit e4c06479d7059888adf2f22bc1ebcf053bf691a2 ]
In order to prevent arithmetic overflows when checking the TX buffer size, cap the associated data length to 0x80000000.
--- crypto/af_alg.c | 2 ++ 1 file changed, 2 insertions(+)
crypto/af_alg.c +2 -0
@@ -584,6 +584,8 @@ static int af_alg_cmsg_send(struct msghdr *msg, struct af_alg_control *con)if (cmsg->cmsg_len <CMSG_LEN (sizeof (u32)))return -EINVAL ; con->aead_assoclen = *(u32 *)CMSG_DATA (cmsg); +if (con->aead_assoclen >=0x80000000u ) +return -EINVAL ;break ;default :
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 213/2077 crypto: ccp/sev-dev-tsm - bail out early when pdev->bus is NULL
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stepan Ionichev <[email protected]>
[ Upstream commit 930d9d36ea618a775985446a125aedeb401db522 ]
dsm_create() initially checks pdev->bus when computing segment_id:
u8 segment_id = pdev->bus ? pci_domain_nr(pdev->bus) : 0;
But the next two lines unconditionally dereference pdev->bus via pcie_find_root_port() and especially pci_dev_id(pdev), which expands to PCI_DEVID(dev->bus->number, dev->devfn). If pdev->bus is in fact NULL, segment_id is initialised to 0 but the very next statement crashes the kernel.
smatch flags this:
drivers/crypto/ccp/sev-dev-tsm.c:253 dsm_create() error: we
previously assumed 'pdev->bus' could be null (see line 251)
Make the NULL handling consistent: if pdev->bus is NULL the device has no PCI context to work with and SEV TIO setup cannot proceed, so return -ENODEV before any of the bus-dependent lookups. The remaining initialisation now runs only on the path where pdev->bus is known to be valid.
No change for callers where pdev->bus is non-NULL, which is the only case where dsm_create() did meaningful work before this change.
--- drivers/crypto/ccp/sev-dev-tsm.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
drivers/crypto/ccp/sev-dev-tsm.c +10 -3
@@ -248,12 +248,19 @@ static void dsm_remove(struct pci_tsm *tsm)static int dsm_create (struct tio_dsm *dsm) {struct pci_dev *pdev = dsm->tsm.base_tsm.pdev; -u8 segment_id = pdev->bus ?pci_domain_nr (pdev->bus) :0 ; -struct pci_dev *rootport =pcie_find_root_port (pdev); -u16 device_id =pci_dev_id (pdev); +struct pci_dev *rootport; +u8 segment_id; +u16 device_id;u16 root_port_id;u32 lnkcap =0 ; +if (!pdev->bus) +return -ENODEV ; + + segment_id =pci_domain_nr (pdev->bus); + rootport =pcie_find_root_port (pdev); + device_id =pci_dev_id (pdev); +if (pci_read_config_dword (rootport,pci_pcie_cap (rootport) +PCI_EXP_LNKCAP , &lnkcap))return -ENODEV ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 214/2077 crypto: safexcel - Fix potential memory leak in safexcel_pci_probe()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Abdun Nihaal <[email protected]>
[ Upstream commit c36faca103a685590281412e47df74b550f71886 ]
The memory allocated for priv in safexcel_pci_probe() is not freed in the error paths, as well as in the PCI remove function. Fix this by using device managed allocation.
--- drivers/crypto/inside-secure/safexcel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/crypto/inside-secure/safexcel.c +1 -1
@@ -1893,7 +1893,7 @@ static int safexcel_pci_probe(struct pci_dev *pdev, ent->vendor, ent->device, ent->subvendor, ent->subdevice, ent->driver_data); - priv =kzalloc_obj (*priv); + priv =devm_kzalloc (dev,sizeof (*priv),GFP_KERNEL );if (!priv)return -ENOMEM ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 215/2077 spi: hisi-kunpeng: Use dev_err_probe() for host registration failure
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Qiang Ma <[email protected]>
[ Upstream commit 59b991990a04b1d1ce95373983b7c8b65bdf7acc ]
When the SPI core registers the Kunpeng controller it may need to acquire chip-select GPIO descriptors. If the GPIO provider has not probed yet, spi_register_controller() returns -EPROBE_DEFER.
On a Kunpeng system this currently prints an alarming error even though the next deferred-probe retry succeeds:
hisi-kunpeng-spi HISI03E1:00: failed to register spi host, ret=-517 hisi-kunpeng-spi HISI03E1:00: hw version:0x30 max-freq:12500 kHz
Use dev_err_probe() so that -EPROBE_DEFER is reported through the deferred probe mechanism instead of as a hard error, while preserving normal error reporting for real registration failures.
--- drivers/spi/spi-hisi-kunpeng.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
drivers/spi/spi-hisi-kunpeng.c +2 -4
@@ -520,10 +520,8 @@ static int hisi_spi_probe(struct platform_device *pdev) } ret =spi_register_controller (host); -if (ret) { -dev_err (dev,"failed to register spi host, ret=%d\n" , ret); -return ret; - } +if (ret) +return dev_err_probe (dev, ret,"failed to register spi host\n" );if (hisi_spi_debugfs_init (hs))dev_info (dev,"failed to create debugfs dir\n" );
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 216/2077 net/sched: add qdisc_qlen_inc() and qdisc_qlen_dec()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit 863cd78652018576c60f1b73477a15bdb0ea7551 ]
Helpers to increment or decrement sch->q.qlen, with appropriate WRITE_ONCE() to prevent store tearing.
Add other WRITE_ONCE() when sch->q.qlen is changed.
Stable-dep-of: 5658bddaca41 ("net/sched: sch_dualpi2: annotate data-races in dualpi2_dump_stats()")
--- include/net/sch_generic.h | 32 +++++++++++++++++++++----------- net/sched/sch_api.c | 2 +- net/sched/sch_cake.c | 8 ++++---- net/sched/sch_cbs.c | 4 ++-- net/sched/sch_choke.c | 8 ++++---- net/sched/sch_drr.c | 4 ++-- net/sched/sch_dualpi2.c | 6 +++--- net/sched/sch_etf.c | 8 ++++---- net/sched/sch_ets.c | 4 ++-- net/sched/sch_fq.c | 6 +++--- net/sched/sch_fq_codel.c | 7 ++++--- net/sched/sch_fq_pie.c | 4 ++-- net/sched/sch_generic.c | 10 +++++----- net/sched/sch_hfsc.c | 4 ++-- net/sched/sch_hhf.c | 7 ++++--- net/sched/sch_htb.c | 4 ++-- net/sched/sch_mq.c | 5 +++-- net/sched/sch_mqprio.c | 18 ++++++++++-------- net/sched/sch_multiq.c | 4 ++-- net/sched/sch_netem.c | 10 +++++----- net/sched/sch_prio.c | 4 ++-- net/sched/sch_qfq.c | 6 +++--- net/sched/sch_red.c | 4 ++-- net/sched/sch_sfb.c | 4 ++-- net/sched/sch_sfq.c | 9 +++++---- net/sched/sch_skbprio.c | 4 ++-- net/sched/sch_taprio.c | 4 ++-- net/sched/sch_tbf.c | 6 +++--- net/sched/sch_teql.c | 2 +- 29 files changed, 107 insertions(+), 91 deletions(-)
include/net/sch_generic.h +21 -11
@@ -542,6 +542,16 @@ static inline int qdisc_qlen(const struct Qdisc *q)return q->q.qlen; } +static inline void qdisc_qlen_inc (struct Qdisc *q) +{ +WRITE_ONCE (q->q.qlen, q->q.qlen +1 ); +} + +static inline void qdisc_qlen_dec (struct Qdisc *q) +{ +WRITE_ONCE (q->q.qlen, q->q.qlen -1 ); +} +static inline int qdisc_qlen_sum (const struct Qdisc *q) {__u32 qlen = q->qstats.qlen;
@@ -549,9 +559,9 @@ static inline int qdisc_qlen_sum(const struct Qdisc *q)if (qdisc_is_percpu_stats (q)) {for_each_possible_cpu (i) - qlen +=per_cpu_ptr (q->cpu_qstats, i)->qlen; + qlen +=READ_ONCE (per_cpu_ptr (q->cpu_qstats, i)->qlen); }else { - qlen += q->q.qlen; + qlen +=READ_ONCE (q->q.qlen); }return qlen;
@@ -1063,7 +1073,7 @@ static inline void __qdisc_enqueue_tail(struct sk_buff *skb, qh->tail = skb; qh->head = skb; } - qh->qlen++; +WRITE_ONCE (qh->qlen, qh->qlen +1 ); }static inline int qdisc_enqueue_tail (struct sk_buff *skb,struct Qdisc *sch)
@@ -1081,7 +1091,7 @@ static inline void __qdisc_enqueue_head(struct sk_buff *skb,if (!qh->head) qh->tail = skb; qh->head = skb; - qh->qlen++; +WRITE_ONCE (qh->qlen, qh->qlen +1 ); }static inline struct sk_buff *__qdisc_dequeue_head (struct qdisc_skb_head *qh)
@@ -1090,7 +1100,7 @@ static inline struct sk_buff *__qdisc_dequeue_head(struct qdisc_skb_head *qh)if (likely (skb !=NULL )) { qh->head = skb->next; - qh->qlen--; +WRITE_ONCE (qh->qlen, qh->qlen -1 );if (qh->head ==NULL ) qh->tail =NULL ; skb->next =NULL ;
@@ -1105,7 +1115,7 @@ static inline struct sk_buff *qdisc_dequeue_internal(struct Qdisc *sch, bool dir skb =__skb_dequeue (&sch->gso_skb);if (skb) { - sch->q.qlen--; +qdisc_qlen_dec (sch);qdisc_qstats_backlog_dec (sch, skb);return skb; }
@@ -1261,7 +1271,7 @@ static inline struct sk_buff *qdisc_peek_dequeued(struct Qdisc *sch)__skb_queue_head (&sch->gso_skb, skb);/* it's still part of the queue */ qdisc_qstats_backlog_inc (sch, skb); - sch->q.qlen++; +qdisc_qlen_inc (sch); } }
@@ -1278,7 +1288,7 @@ static inline void qdisc_update_stats_at_dequeue(struct Qdisc *sch, }else {qdisc_qstats_backlog_dec (sch, skb);qdisc_bstats_update (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch); } }
@@ -1290,7 +1300,7 @@ static inline void qdisc_update_stats_at_enqueue(struct Qdisc *sch,this_cpu_add (sch->cpu_qstats->backlog, pkt_len); }else { sch->qstats.backlog += pkt_len; - sch->q.qlen++; +qdisc_qlen_inc (sch); } }
@@ -1306,7 +1316,7 @@ static inline struct sk_buff *qdisc_dequeue_peeked(struct Qdisc *sch)qdisc_qstats_cpu_qlen_dec (sch); }else {qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch); } }else { skb = sch->dequeue (sch);
@@ -1327,7 +1337,7 @@ static inline void __qdisc_reset_queue(struct qdisc_skb_head *qh) qh->head =NULL ; qh->tail =NULL ; - qh->qlen =0 ; +WRITE_ONCE (qh->qlen,0 ); } }
net/sched/sch_api.c +1 -1
@@ -805,7 +805,7 @@ void qdisc_tree_reduce_backlog(struct Qdisc *sch, int n, int len) cl = cops->find (sch, parentid); cops->qlen_notify (sch, cl); } - sch->q.qlen -= n; +WRITE_ONCE (sch->q.qlen, sch->q.qlen - n); sch->qstats.backlog -= len;__qdisc_qstats_drop (sch, drops); }
net/sched/sch_cake.c +4 -4
@@ -1612,7 +1612,7 @@ static unsigned int cake_drop(struct Qdisc *sch, struct sk_buff **to_free)cake_advance_shaper (q, b, skb, now, true);qdisc_drop_reason (skb, sch, to_free,QDISC_DROP_OVERLIMIT ); - sch->q.qlen--; +qdisc_qlen_dec (sch);cake_heapify (q,0 );
@@ -1822,7 +1822,7 @@ static s32 cake_enqueue(struct sk_buff *skb, struct Qdisc *sch, segs);flow_queue_add (flow, segs); - sch->q.qlen++; +qdisc_qlen_inc (sch); numsegs++; slen += segs->len; q->buffer_used += segs->truesize;
@@ -1861,7 +1861,7 @@ static s32 cake_enqueue(struct sk_buff *skb, struct Qdisc *sch,qdisc_tree_reduce_backlog (sch,1 , ack_pkt_len);consume_skb (ack); }else { - sch->q.qlen++; +qdisc_qlen_inc (sch); q->buffer_used += skb->truesize; }
@@ -1987,7 +1987,7 @@ static struct sk_buff *cake_dequeue_one(struct Qdisc *sch)WRITE_ONCE (b->tin_backlog, b->tin_backlog - len); sch->qstats.backlog -= len; q->buffer_used -= skb->truesize; - sch->q.qlen--; +qdisc_qlen_dec (sch);if (q->overflow_timeout)cake_heapify (q, b->overflow_idx[q->cur_flow]);
net/sched/sch_cbs.c +2 -2
@@ -97,7 +97,7 @@ static int cbs_child_enqueue(struct sk_buff *skb, struct Qdisc *sch,return err; sch->qstats.backlog += len; - sch->q.qlen++; +qdisc_qlen_inc (sch);return NET_XMIT_SUCCESS ; }
@@ -168,7 +168,7 @@ static struct sk_buff *cbs_child_dequeue(struct Qdisc *sch, struct Qdisc *child)qdisc_qstats_backlog_dec (sch, skb);qdisc_bstats_update (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);return skb; }
net/sched/sch_choke.c +4 -4
@@ -123,7 +123,7 @@ static void choke_drop_by_idx(struct Qdisc *sch, unsigned int idx,if (idx == q->tail)choke_zap_tail_holes (q); - --sch->q.qlen; +qdisc_qlen_dec (sch);qdisc_qstats_backlog_dec (sch, skb);qdisc_tree_reduce_backlog (sch,1 ,qdisc_pkt_len (skb));qdisc_drop (skb, sch, to_free);
@@ -271,7 +271,7 @@ static int choke_enqueue(struct sk_buff *skb, struct Qdisc *sch,if (sch->q.qlen < q->limit) { q->tab[q->tail] = skb; q->tail = (q->tail +1 ) & q->tab_mask; - ++sch->q.qlen; +qdisc_qlen_inc (sch);qdisc_qstats_backlog_inc (sch, skb);return NET_XMIT_SUCCESS ; }
@@ -298,7 +298,7 @@ static struct sk_buff *choke_dequeue(struct Qdisc *sch) skb = q->tab[q->head]; q->tab[q->head] =NULL ;choke_zap_head_holes (q); - --sch->q.qlen; +qdisc_qlen_dec (sch);qdisc_qstats_backlog_dec (sch, skb);qdisc_bstats_update (sch, skb);
@@ -396,7 +396,7 @@ static int choke_change(struct Qdisc *sch, struct nlattr *opt, } dropped +=qdisc_pkt_len (skb);qdisc_qstats_backlog_dec (sch, skb); - --sch->q.qlen; +qdisc_qlen_dec (sch);rtnl_qdisc_drop (skb, sch); }qdisc_tree_reduce_backlog (sch, oqlen - sch->q.qlen, dropped);
net/sched/sch_drr.c +2 -2
@@ -366,7 +366,7 @@ static int drr_enqueue(struct sk_buff *skb, struct Qdisc *sch, } sch->qstats.backlog += len; - sch->q.qlen++; +qdisc_qlen_inc (sch);return err; }
@@ -399,7 +399,7 @@ static struct sk_buff *drr_dequeue(struct Qdisc *sch)bstats_update (&cl->bstats, skb);qdisc_bstats_update (sch, skb);qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);return skb; }
net/sched/sch_dualpi2.c +3 -3
@@ -415,7 +415,7 @@ static int dualpi2_enqueue_skb(struct sk_buff *skb, struct Qdisc *sch,dualpi2_skb_cb (skb)->apply_step =skb_apply_step (skb, q);/* Keep the overall qdisc stats consistent */ - ++sch->q.qlen; +qdisc_qlen_inc (sch);qdisc_qstats_backlog_inc (sch, skb); ++q->packets_in_l;if (!q->l_head_ts)
@@ -529,7 +529,7 @@ static struct sk_buff *dequeue_packet(struct Qdisc *sch,qdisc_qstats_backlog_dec (q->l_queue, skb);/* Keep the global queue size consistent */ - --sch->q.qlen; +qdisc_qlen_dec (sch); q->memory_used -= skb->truesize; }else if (c_len) { skb =__qdisc_dequeue_head (&sch->q);
@@ -887,7 +887,7 @@ static int dualpi2_change(struct Qdisc *sch, struct nlattr *opt,* l_queue on enqueue; qdisc_dequeue_internal() * handled l_queue, so we further account for sch. */ - --sch->q.qlen; +qdisc_qlen_dec (sch);qdisc_qstats_backlog_dec (sch, skb); q->memory_used -= skb->truesize;rtnl_qdisc_drop (skb, q->l_queue);
net/sched/sch_etf.c +4 -4
@@ -189,7 +189,7 @@ static int etf_enqueue_timesortedlist(struct sk_buff *nskb, struct Qdisc *sch,rb_insert_color_cached (&nskb->rbnode, &q->head, leftmost);qdisc_qstats_backlog_inc (sch, nskb); - sch->q.qlen++; +qdisc_qlen_inc (sch);/* Now we may need to re-arm the qdisc watchdog for the next packet. */ reset_watchdog (sch);
@@ -222,7 +222,7 @@ static void timesortedlist_drop(struct Qdisc *sch, struct sk_buff *skb,qdisc_qstats_backlog_dec (sch, skb);qdisc_drop (skb, sch, &to_free);qdisc_qstats_overlimit (sch); - sch->q.qlen--; +qdisc_qlen_dec (sch); }kfree_skb_list (to_free);
@@ -247,7 +247,7 @@ static void timesortedlist_remove(struct Qdisc *sch, struct sk_buff *skb) q->last = skb->tstamp; - sch->q.qlen--; +qdisc_qlen_dec (sch); }static struct sk_buff *etf_dequeue_timesortedlist (struct Qdisc *sch)
@@ -426,7 +426,7 @@ static void timesortedlist_clear(struct Qdisc *sch)rb_erase_cached (&skb->rbnode, &q->head);rtnl_kfree_skbs (skb, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch); } }
net/sched/sch_ets.c +2 -2
@@ -449,7 +449,7 @@ static int ets_qdisc_enqueue(struct sk_buff *skb, struct Qdisc *sch, } sch->qstats.backlog += len; - sch->q.qlen++; +qdisc_qlen_inc (sch);return err; }
@@ -458,7 +458,7 @@ ets_qdisc_dequeue_skb(struct Qdisc *sch, struct sk_buff *skb) {qdisc_bstats_update (sch, skb);qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);return skb; }
net/sched/sch_fq.c +3 -3
@@ -497,7 +497,7 @@ static void fq_dequeue_skb(struct Qdisc *sch, struct fq_flow *flow,fq_erase_head (sch, flow, skb);skb_mark_not_on_list (skb);qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);qdisc_bstats_update (sch, skb); }
@@ -597,7 +597,7 @@ static int fq_enqueue(struct sk_buff *skb, struct Qdisc *sch,flow_queue_add (f, skb);qdisc_qstats_backlog_inc (sch, skb); - sch->q.qlen++; +qdisc_qlen_inc (sch);return NET_XMIT_SUCCESS ; }
@@ -801,7 +801,7 @@ static void fq_reset(struct Qdisc *sch)struct fq_flow *f;unsigned int idx; - sch->q.qlen =0 ; +WRITE_ONCE (sch->q.qlen,0 ); sch->qstats.backlog =0 ;fq_flow_purge (&q->internal);
net/sched/sch_fq_codel.c +4 -3
@@ -178,7 +178,7 @@ static unsigned int fq_codel_drop(struct Qdisc *sch, unsigned int max_packets, q->memory_usage -= mem; sch->qstats.drops += i; sch->qstats.backlog -= len; - sch->q.qlen -= i; +WRITE_ONCE (sch->q.qlen, sch->q.qlen - i);return idx; }
@@ -215,7 +215,8 @@ static int fq_codel_enqueue(struct sk_buff *skb, struct Qdisc *sch,get_codel_cb (skb)->mem_usage = skb->truesize; q->memory_usage +=get_codel_cb (skb)->mem_usage; memory_limited = q->memory_usage > q->memory_limit; -if (++sch->q.qlen <= sch->limit && !memory_limited) +qdisc_qlen_inc (sch); +if (sch->q.qlen <= sch->limit && !memory_limited)return NET_XMIT_SUCCESS ; prev_backlog = sch->qstats.backlog;
@@ -266,7 +267,7 @@ static struct sk_buff *dequeue_func(struct codel_vars *vars, void *ctx)WRITE_ONCE (q->backlogs[flow - q->flows], q->backlogs[flow - q->flows] -qdisc_pkt_len (skb)); q->memory_usage -=get_codel_cb (skb)->mem_usage; - sch->q.qlen--; +qdisc_qlen_dec (sch); sch->qstats.backlog -=qdisc_pkt_len (skb); }return skb;
net/sched/sch_fq_pie.c +2 -2
@@ -185,7 +185,7 @@ static int fq_pie_qdisc_enqueue(struct sk_buff *skb, struct Qdisc *sch, q->stats.packets_in++; q->memory_usage += skb->truesize; sch->qstats.backlog += pkt_len; - sch->q.qlen++; +qdisc_qlen_inc (sch);flow_queue_add (sel_flow, skb);if (list_empty (&sel_flow->flowchain)) {list_add_tail (&sel_flow->flowchain, &q->new_flows);
@@ -263,7 +263,7 @@ static struct sk_buff *fq_pie_qdisc_dequeue(struct Qdisc *sch) skb =dequeue_head (flow); pkt_len =qdisc_pkt_len (skb); sch->qstats.backlog -= pkt_len; - sch->q.qlen--; +qdisc_qlen_dec (sch);qdisc_bstats_update (sch, skb); }
net/sched/sch_generic.c +5 -5
@@ -118,7 +118,7 @@ static inline struct sk_buff *__skb_dequeue_bad_txq(struct Qdisc *q)qdisc_qstats_cpu_qlen_dec (q); }else {qdisc_qstats_backlog_dec (q, skb); - q->q.qlen--; +qdisc_qlen_dec (q); } }else { skb =SKB_XOFF_MAGIC ;
@@ -159,7 +159,7 @@ static inline void qdisc_enqueue_skb_bad_txq(struct Qdisc *q,qdisc_qstats_cpu_qlen_inc (q); }else {qdisc_qstats_backlog_inc (q, skb); - q->q.qlen++; +qdisc_qlen_inc (q); }if (lock)
@@ -188,7 +188,7 @@ static inline void dev_requeue_skb(struct sk_buff *skb, struct Qdisc *q) }else { q->qstats.requeues++;qdisc_qstats_backlog_inc (q, skb); - q->q.qlen++; +qdisc_qlen_inc (q); } skb = next;
@@ -294,7 +294,7 @@ static struct sk_buff *dequeue_skb(struct Qdisc *q, bool *validate,qdisc_qstats_cpu_qlen_dec (q); }else {qdisc_qstats_backlog_dec (q, skb); - q->q.qlen--; +qdisc_qlen_dec (q); } }else { skb =NULL ;
@@ -1059,7 +1059,7 @@ void qdisc_reset(struct Qdisc *qdisc)__skb_queue_purge (&qdisc->gso_skb);__skb_queue_purge (&qdisc->skb_bad_txq); - qdisc->q.qlen =0 ; +WRITE_ONCE (qdisc->q.qlen,0 ); qdisc->qstats.backlog =0 ; }EXPORT_SYMBOL (qdisc_reset);
net/sched/sch_hfsc.c +2 -2
@@ -1561,7 +1561,7 @@ hfsc_enqueue(struct sk_buff *skb, struct Qdisc *sch, struct sk_buff **to_free) } sch->qstats.backlog += len; - sch->q.qlen++; +qdisc_qlen_inc (sch);if (first && !cl_in_el_or_vttree (cl)) {if (cl->cl_flags &HFSC_RSC )
@@ -1650,7 +1650,7 @@ hfsc_dequeue(struct Qdisc *sch)qdisc_bstats_update (sch, skb);qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);return skb; }
net/sched/sch_hhf.c +4 -3
@@ -360,7 +360,7 @@ static unsigned int hhf_drop(struct Qdisc *sch, struct sk_buff **to_free)if (bucket->head) {struct sk_buff *skb =dequeue_head (bucket); - sch->q.qlen--; +qdisc_qlen_dec (sch);qdisc_qstats_backlog_dec (sch, skb);qdisc_drop (skb, sch, to_free); }
@@ -400,7 +400,8 @@ static int hhf_enqueue(struct sk_buff *skb, struct Qdisc *sch, } bucket->deficit = weight * q->quantum; } -if (++sch->q.qlen <= sch->limit) +qdisc_qlen_inc (sch); +if (sch->q.qlen <= sch->limit)return NET_XMIT_SUCCESS ; prev_backlog = sch->qstats.backlog;
@@ -443,7 +444,7 @@ static struct sk_buff *hhf_dequeue(struct Qdisc *sch)if (bucket->head) { skb =dequeue_head (bucket); - sch->q.qlen--; +qdisc_qlen_dec (sch);qdisc_qstats_backlog_dec (sch, skb); }
net/sched/sch_htb.c +2 -2
@@ -651,7 +651,7 @@ static int htb_enqueue(struct sk_buff *skb, struct Qdisc *sch, } sch->qstats.backlog += len; - sch->q.qlen++; +qdisc_qlen_inc (sch);return NET_XMIT_SUCCESS ; }
@@ -951,7 +951,7 @@ static struct sk_buff *htb_dequeue(struct Qdisc *sch) ok:qdisc_bstats_update (sch, skb);qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);return skb; }
net/sched/sch_mq.c +3 -2
@@ -143,10 +143,10 @@ EXPORT_SYMBOL_NS_GPL(mq_attach, "NET_SCHED_INTERNAL");void mq_dump_common (struct Qdisc *sch,struct sk_buff *skb) {struct net_device *dev =qdisc_dev (sch); +unsigned int qlen =0 ;struct Qdisc *qdisc;unsigned int ntx; - sch->q.qlen =0 ;gnet_stats_basic_sync_init (&sch->bstats);memset (&sch->qstats,0 ,sizeof (sch->qstats));
@@ -163,10 +163,11 @@ void mq_dump_common(struct Qdisc *sch, struct sk_buff *skb) &qdisc->bstats, false);gnet_stats_add_queue (&sch->qstats, qdisc->cpu_qstats, &qdisc->qstats); - sch->q.qlen +=qdisc_qlen (qdisc); + qlen +=qdisc_qlen (qdisc);spin_unlock_bh (qdisc_lock (qdisc)); } +WRITE_ONCE (sch->q.qlen, qlen); }EXPORT_SYMBOL_NS_GPL (mq_dump_common,"NET_SCHED_INTERNAL" );
net/sched/sch_mqprio.c +10 -8
@@ -555,10 +555,11 @@ static int mqprio_dump(struct Qdisc *sch, struct sk_buff *skb)struct mqprio_sched *priv =qdisc_priv (sch);struct nlattr *nla = (struct nlattr *)skb_tail_pointer (skb);struct tc_mqprio_qopt opt = {0 }; +unsigned int qlen =0 ;struct Qdisc *qdisc;unsigned int ntx; - sch->q.qlen =0 ; + qlen =0 ;gnet_stats_basic_sync_init (&sch->bstats);memset (&sch->qstats,0 ,sizeof (sch->qstats));
@@ -575,10 +576,11 @@ static int mqprio_dump(struct Qdisc *sch, struct sk_buff *skb) &qdisc->bstats, false);gnet_stats_add_queue (&sch->qstats, qdisc->cpu_qstats, &qdisc->qstats); - sch->q.qlen +=qdisc_qlen (qdisc); + qlen +=qdisc_qlen (qdisc);spin_unlock_bh (qdisc_lock (qdisc)); } +WRITE_ONCE (sch->q.qlen, qlen);mqprio_qopt_reconstruct (dev, &opt); opt.hw = priv->hw_offload;
@@ -663,12 +665,12 @@ static int mqprio_dump_class_stats(struct Qdisc *sch, unsigned long cl, __acquires(d->lock) {if (cl >=TC_H_MIN_PRIORITY ) { -int i; -__u32 qlen; -struct gnet_stats_queue qstats = {0 }; -struct gnet_stats_basic_sync bstats;struct net_device *dev =qdisc_dev (sch);struct netdev_tc_txq tc = dev->tc_to_txq[cl &TC_BITMASK ]; +struct gnet_stats_queue qstats = {0 }; +struct gnet_stats_basic_sync bstats; +u32 qlen =0 ; +int i;gnet_stats_basic_sync_init (&bstats);/* Drop lock here it will be reclaimed before touching
@@ -689,11 +691,11 @@ static int mqprio_dump_class_stats(struct Qdisc *sch, unsigned long cl, &qdisc->bstats, false);gnet_stats_add_queue (&qstats, qdisc->cpu_qstats, &qdisc->qstats); - sch->q.qlen +=qdisc_qlen (qdisc); + qlen +=qdisc_qlen (qdisc);spin_unlock_bh (qdisc_lock (qdisc)); } - qlen =qdisc_qlen (sch) + qstats.qlen; + qlen = qlen + qstats.qlen;/* Reclaim root sleeping lock before completing stats */ if (d->lock)
net/sched/sch_multiq.c +2 -2
@@ -76,7 +76,7 @@ multiq_enqueue(struct sk_buff *skb, struct Qdisc *sch, ret =qdisc_enqueue (skb, qdisc, to_free);if (ret ==NET_XMIT_SUCCESS ) { - sch->q.qlen++; +qdisc_qlen_inc (sch);return NET_XMIT_SUCCESS ; }if (net_xmit_drop_count (ret))
@@ -106,7 +106,7 @@ static struct sk_buff *multiq_dequeue(struct Qdisc *sch) skb = qdisc->dequeue (qdisc);if (skb) {qdisc_bstats_update (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);return skb; } }
net/sched/sch_netem.c +5 -5
@@ -416,7 +416,7 @@ static void tfifo_enqueue(struct sk_buff *nskb, struct Qdisc *sch)rb_insert_color (&nskb->rbnode, &q->t_root); } q->t_len++; - sch->q.qlen++; +qdisc_qlen_inc (sch); }/* netem can't properly corrupt a megapacket (like we get from GSO), so instead
@@ -750,19 +750,19 @@ static struct sk_buff *netem_dequeue(struct Qdisc *sch)if (net_xmit_drop_count (err))qdisc_qstats_drop (sch); sch->qstats.backlog -= pkt_len; - sch->q.qlen--; +qdisc_qlen_dec (sch);qdisc_tree_reduce_backlog (sch,1 , pkt_len); } goto tfifo_dequeue; } - sch->q.qlen--; +qdisc_qlen_dec (sch); goto deliver; }if (q->qdisc) { skb = q->qdisc->ops->dequeue (q->qdisc);if (skb) { - sch->q.qlen--; +qdisc_qlen_dec (sch); goto deliver; } }
@@ -775,7 +775,7 @@ static struct sk_buff *netem_dequeue(struct Qdisc *sch)if (q->qdisc) { skb = q->qdisc->ops->dequeue (q->qdisc);if (skb) { - sch->q.qlen--; +qdisc_qlen_dec (sch); goto deliver; } }
net/sched/sch_prio.c +2 -2
@@ -86,7 +86,7 @@ prio_enqueue(struct sk_buff *skb, struct Qdisc *sch, struct sk_buff **to_free) ret =qdisc_enqueue (skb, qdisc, to_free);if (ret ==NET_XMIT_SUCCESS ) { sch->qstats.backlog += len; - sch->q.qlen++; +qdisc_qlen_inc (sch);return NET_XMIT_SUCCESS ; }if (net_xmit_drop_count (ret))
@@ -119,7 +119,7 @@ static struct sk_buff *prio_dequeue(struct Qdisc *sch)if (skb) {qdisc_bstats_update (sch, skb);qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);return skb; } }
net/sched/sch_qfq.c +3 -3
@@ -1152,12 +1152,12 @@ static struct sk_buff *qfq_dequeue(struct Qdisc *sch)if (!skb)return NULL ; - sch->q.qlen--; +qdisc_qlen_dec (sch); skb =agg_dequeue (in_serv_agg, cl, len);if (!skb) { - sch->q.qlen++; +qdisc_qlen_inc (sch);return NULL ; }
@@ -1265,7 +1265,7 @@ static int qfq_enqueue(struct sk_buff *skb, struct Qdisc *sch,_bstats_update (&cl->bstats, len, gso_segs); sch->qstats.backlog += len; - ++sch->q.qlen; +qdisc_qlen_inc (sch); agg = cl->agg;/* if the class is active, then done here */
net/sched/sch_red.c +2 -2
@@ -139,7 +139,7 @@ static int red_enqueue(struct sk_buff *skb, struct Qdisc *sch, ret =qdisc_enqueue (skb, child, to_free);if (likely (ret ==NET_XMIT_SUCCESS )) { sch->qstats.backlog += len; - sch->q.qlen++; +qdisc_qlen_inc (sch); }else if (net_xmit_drop_count (ret)) {WRITE_ONCE (q->stats.pdrop, q->stats.pdrop +1 );
@@ -166,7 +166,7 @@ static struct sk_buff *red_dequeue(struct Qdisc *sch)if (skb) {qdisc_bstats_update (sch, skb);qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch); }else {if (!red_is_idling (&q->vars))red_start_of_idle_period (&q->vars);
net/sched/sch_sfb.c +2 -2
@@ -416,7 +416,7 @@ static int sfb_enqueue(struct sk_buff *skb, struct Qdisc *sch, ret =qdisc_enqueue (skb, child, to_free);if (likely (ret ==NET_XMIT_SUCCESS )) { sch->qstats.backlog += len; - sch->q.qlen++; +qdisc_qlen_inc (sch);increment_qlen (&cb, q); }else if (net_xmit_drop_count (ret)) { WRITE_ONCE(q->stats.childdrop,
@@ -446,7 +446,7 @@ static struct sk_buff *sfb_dequeue(struct Qdisc *sch)if (skb) {qdisc_bstats_update (sch, skb);qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);decrement_qlen (skb, q); }
net/sched/sch_sfq.c +5 -4
@@ -302,7 +302,7 @@ static unsigned int sfq_drop(struct Qdisc *sch, struct sk_buff **to_free) len =qdisc_pkt_len (skb);WRITE_ONCE (slot->backlog, slot->backlog - len);sfq_dec (q, x); - sch->q.qlen--; +qdisc_qlen_dec (sch);qdisc_qstats_backlog_dec (sch, skb);qdisc_drop_reason (skb, sch, to_free,QDISC_DROP_OVERLIMIT );return len;
@@ -456,7 +456,8 @@ sfq_enqueue(struct sk_buff *skb, struct Qdisc *sch, struct sk_buff **to_free)/* We could use a bigger initial quantum for new flows */ WRITE_ONCE (slot->allot, q->quantum); } -if (++sch->q.qlen <= q->limit) +qdisc_qlen_inc (sch); +if (sch->q.qlen <= q->limit)return NET_XMIT_SUCCESS ; qlen = slot->qlen;
@@ -497,7 +498,7 @@ sfq_dequeue(struct Qdisc *sch) skb =slot_dequeue_head (slot);sfq_dec (q, a);qdisc_bstats_update (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);qdisc_qstats_backlog_dec (sch, skb);WRITE_ONCE (slot->backlog, slot->backlog -qdisc_pkt_len (skb));/* Is the slot empty? */
@@ -596,7 +597,7 @@ static void sfq_rehash(struct Qdisc *sch)WRITE_ONCE (slot->allot, q->quantum); } } - sch->q.qlen -= dropped; +WRITE_ONCE (sch->q.qlen, sch->q.qlen - dropped);qdisc_tree_reduce_backlog (sch, dropped, drop_len); }
net/sched/sch_skbprio.c +2 -2
@@ -93,7 +93,7 @@ static int skbprio_enqueue(struct sk_buff *skb, struct Qdisc *sch,if (prio < q->lowest_prio) q->lowest_prio = prio; - sch->q.qlen++; +qdisc_qlen_inc (sch);return NET_XMIT_SUCCESS ; }
@@ -145,7 +145,7 @@ static struct sk_buff *skbprio_dequeue(struct Qdisc *sch)if (unlikely (!skb))return NULL ; - sch->q.qlen--; +qdisc_qlen_dec (sch);qdisc_qstats_backlog_dec (sch, skb);qdisc_bstats_update (sch, skb);
net/sched/sch_taprio.c +2 -2
@@ -574,7 +574,7 @@ static int taprio_enqueue_one(struct sk_buff *skb, struct Qdisc *sch, }qdisc_qstats_backlog_inc (sch, skb); - sch->q.qlen++; +qdisc_qlen_inc (sch);return qdisc_enqueue (skb, child, to_free); }
@@ -755,7 +755,7 @@ static struct sk_buff *taprio_dequeue_from_txq(struct Qdisc *sch, int txq,qdisc_bstats_update (sch, skb);qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);return skb; }
net/sched/sch_tbf.c +3 -3
@@ -231,7 +231,7 @@ static int tbf_segment(struct sk_buff *skb, struct Qdisc *sch, len += seg_len; } } - sch->q.qlen += nb; +WRITE_ONCE (sch->q.qlen, sch->q.qlen + nb); sch->qstats.backlog += len;if (nb >0 ) {qdisc_tree_reduce_backlog (sch,1 - nb, prev_len - len);
@@ -264,7 +264,7 @@ static int tbf_enqueue(struct sk_buff *skb, struct Qdisc *sch, } sch->qstats.backlog += len; - sch->q.qlen++; +qdisc_qlen_inc (sch);return NET_XMIT_SUCCESS ; }
@@ -309,7 +309,7 @@ static struct sk_buff *tbf_dequeue(struct Qdisc *sch) q->tokens = toks; q->ptokens = ptoks;qdisc_qstats_backlog_dec (sch, skb); - sch->q.qlen--; +qdisc_qlen_dec (sch);qdisc_bstats_update (sch, skb);return skb; }
net/sched/sch_teql.c +1 -1
@@ -107,7 +107,7 @@ teql_dequeue(struct Qdisc *sch) }else {qdisc_bstats_update (sch, skb); } - sch->q.qlen = dat->q.qlen + q->q.qlen; +WRITE_ONCE (sch->q.qlen, dat->q.qlen +READ_ONCE (q->q.qlen));return skb; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 217/2077 net/sched: sch_dualpi2: annotate data-races in dualpi2_dump_stats()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit 5658bddaca41417331d2ac4b24a9b159a839ab87 ]
dualpi2_dump_stats() runs without qdisc lock held.
Add missing READ_ONCE()/WRITE_ONCE() annotations.
--- net/sched/sch_dualpi2.c | 68 ++++++++++++++++++++--------------------- 1 file changed, 34 insertions(+), 34 deletions(-)
net/sched/sch_dualpi2.c +34 -34
@@ -190,7 +190,7 @@ static bool skb_apply_step(struct sk_buff *skb, struct dualpi2_sched_data *q)static bool dualpi2_mark (struct dualpi2_sched_data *q,struct sk_buff *skb) {if (INET_ECN_set_ce (skb)) { - q->ecn_mark++; +WRITE_ONCE (q->ecn_mark, q->ecn_mark +1 );return true; }return false;
@@ -198,7 +198,7 @@ static bool dualpi2_mark(struct dualpi2_sched_data *q, struct sk_buff *skb)static void dualpi2_reset_c_protection (struct dualpi2_sched_data *q) { - q->c_protection_credit = q->c_protection_init; +WRITE_ONCE (q->c_protection_credit, q->c_protection_init); }/* This computes the initial credit value and WRR weight for the L queue (wl)
@@ -403,12 +403,12 @@ static int dualpi2_enqueue_skb(struct sk_buff *skb, struct Qdisc *sch, cb =dualpi2_skb_cb (skb); cb->ts =ktime_get_ns (); - q->memory_used += skb->truesize; +WRITE_ONCE (q->memory_used, q->memory_used + skb->truesize);if (q->memory_used > q->max_memory_used) - q->max_memory_used = q->memory_used; +WRITE_ONCE (q->max_memory_used, q->memory_used);if (qdisc_qlen (sch) > q->maxq) - q->maxq =qdisc_qlen (sch); +WRITE_ONCE (q->maxq,qdisc_qlen (sch));if (skb_in_l_queue (skb)) {/* Apply step thresh if skb is L4S && L-queue len >= min_qlen */
@@ -417,14 +417,14 @@ static int dualpi2_enqueue_skb(struct sk_buff *skb, struct Qdisc *sch,/* Keep the overall qdisc stats consistent */ qdisc_qlen_inc (sch);qdisc_qstats_backlog_inc (sch, skb); - ++q->packets_in_l; +WRITE_ONCE (q->packets_in_l, q->packets_in_l +1 );if (!q->l_head_ts) - q->l_head_ts = cb->ts; +WRITE_ONCE (q->l_head_ts, cb->ts);return qdisc_enqueue_tail (skb, q->l_queue); } - ++q->packets_in_c; +WRITE_ONCE (q->packets_in_c, q->packets_in_c +1 );if (!q->c_head_ts) - q->c_head_ts = cb->ts; +WRITE_ONCE (q->c_head_ts, cb->ts);return qdisc_enqueue_tail (skb, sch); }
@@ -530,17 +530,16 @@ static struct sk_buff *dequeue_packet(struct Qdisc *sch,/* Keep the global queue size consistent */ qdisc_qlen_dec (sch); - q->memory_used -= skb->truesize; }else if (c_len) { skb =__qdisc_dequeue_head (&sch->q);WRITE_ONCE (q->c_head_ts,head_enqueue_time (sch));if (qdisc_qlen (q->l_queue)) *credit_change = ~((s32 )q->c_protection_wl) +1 ; - q->memory_used -= skb->truesize; }else {dualpi2_reset_c_protection (q);return NULL ; } +WRITE_ONCE (q->memory_used, q->memory_used - skb->truesize); *credit_change *=qdisc_pkt_len (skb);qdisc_qstats_backlog_dec (sch, skb);return skb;
@@ -563,7 +562,7 @@ static int do_step_aqm(struct dualpi2_sched_data *q, struct sk_buff *skb, }if (dualpi2_mark (q, skb)) - ++q->step_marks; +WRITE_ONCE (q->step_marks, q->step_marks +1 ); }qdisc_bstats_update (q->l_queue, skb);return 0 ;
@@ -599,7 +598,8 @@ static struct sk_buff *dualpi2_qdisc_dequeue(struct Qdisc *sch)continue ; } - q->c_protection_credit += credit_change; +WRITE_ONCE (q->c_protection_credit, + q->c_protection_credit + credit_change);qdisc_bstats_update (sch, skb);break ; }
@@ -875,7 +875,7 @@ static int dualpi2_change(struct Qdisc *sch, struct nlattr *opt,WARN_ON_ONCE (1 );break ; } - q->memory_used -= skb->truesize; +WRITE_ONCE (q->memory_used, q->memory_used - skb->truesize);rtnl_qdisc_drop (skb, sch); }else if (qdisc_qlen (q->l_queue)) { skb =qdisc_dequeue_internal (q->l_queue, true);
@@ -889,7 +889,7 @@ static int dualpi2_change(struct Qdisc *sch, struct nlattr *opt,*/ qdisc_qlen_dec (sch);qdisc_qstats_backlog_dec (sch, skb); - q->memory_used -= skb->truesize; +WRITE_ONCE (q->memory_used, q->memory_used - skb->truesize);rtnl_qdisc_drop (skb, q->l_queue);qdisc_qstats_drop (sch); }else {
@@ -1045,15 +1045,15 @@ static int dualpi2_dump_stats(struct Qdisc *sch, struct gnet_dump *d)struct dualpi2_sched_data *q =qdisc_priv (sch);struct tc_dualpi2_xstats st = { .prob =READ_ONCE (q->pi2_prob), - .packets_in_c = q->packets_in_c, - .packets_in_l = q->packets_in_l, - .maxq = q->maxq, - .ecn_mark = q->ecn_mark, - .credit = q->c_protection_credit, - .step_marks = q->step_marks, - .memory_used = q->memory_used, - .max_memory_used = q->max_memory_used, - .memory_limit = q->memory_limit, + .packets_in_c =READ_ONCE (q->packets_in_c), + .packets_in_l =READ_ONCE (q->packets_in_l), + .maxq =READ_ONCE (q->maxq), + .ecn_mark =READ_ONCE (q->ecn_mark), + .credit =READ_ONCE (q->c_protection_credit), + .step_marks =READ_ONCE (q->step_marks), + .memory_used =READ_ONCE (q->memory_used), + .max_memory_used =READ_ONCE (q->max_memory_used), + .memory_limit =READ_ONCE (q->memory_limit), };u64 qc, ql;
@@ -1073,16 +1073,16 @@ static void dualpi2_reset(struct Qdisc *sch)qdisc_reset_queue (sch);qdisc_reset_queue (q->l_queue); - q->c_head_ts =0 ; - q->l_head_ts =0 ; - q->pi2_prob =0 ; - q->packets_in_c =0 ; - q->packets_in_l =0 ; - q->maxq =0 ; - q->ecn_mark =0 ; - q->step_marks =0 ; - q->memory_used =0 ; - q->max_memory_used =0 ; +WRITE_ONCE (q->c_head_ts,0 ); +WRITE_ONCE (q->l_head_ts,0 ); +WRITE_ONCE (q->pi2_prob,0 ); +WRITE_ONCE (q->packets_in_c,0 ); +WRITE_ONCE (q->packets_in_l,0 ); +WRITE_ONCE (q->maxq,0 ); +WRITE_ONCE (q->ecn_mark,0 ); +WRITE_ONCE (q->step_marks,0 ); +WRITE_ONCE (q->memory_used,0 ); +WRITE_ONCE (q->max_memory_used,0 );dualpi2_reset_c_protection (q); }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 218/2077 net/sched: sch_htb: do not change sch->flags in htb_dump()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit 9b949fa69129e4b694ed11ee3be6d6edd4a9b8f4 ]
htb_dump() runs without holding qdisc spinlock.
It is illegal to touch sch->flags with non locked RMW, as concurrent readers might see intermediate wrong values.
Set TCQ_F_OFFLOADED in control path (htb_init()) instead.
--- net/sched/sch_htb.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-)
net/sched/sch_htb.c +1 -5
@@ -1147,6 +1147,7 @@ static int htb_init(struct Qdisc *sch, struct nlattr *opt,* parts (especially calling ndo_setup_tc) on errors. */ q->offload = true; + sch->flags |=TCQ_F_OFFLOADED ;return 0 ; }
@@ -1207,11 +1208,6 @@ static int htb_dump(struct Qdisc *sch, struct sk_buff *skb)struct nlattr *nest;struct tc_htb_glob gopt; -if (q->offload) - sch->flags |=TCQ_F_OFFLOADED ; -else - sch->flags &= ~TCQ_F_OFFLOADED ; - sch->qstats.overlimits = q->overlimits;/* Its safe to not acquire qdisc lock. As we hold RTNL, * no change can happen on the qdisc parameters.
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 219/2077 net/sched: sch_htb: annotate data-races (I)
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit e54c33503bf7cebb1c1790251ce90f1252678081 ]
htb_dump() runs without holding qdisc spinlock.
Add missing READ_ONCE()/WRITE_ONCE() annotations around q->overlimits and q->direct_pkts.
--- net/sched/sch_htb.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
net/sched/sch_htb.c +4 -4
@@ -568,7 +568,7 @@ htb_change_class_mode(struct htb_sched *q, struct htb_class *cl, s64 *diff)if (new_mode ==HTB_CANT_SEND ) { cl->overlimits++; - q->overlimits++; +WRITE_ONCE (q->overlimits, q->overlimits +1 ); }if (cl->prio_activity) {/* not necessary: speed optimization */
@@ -628,7 +628,7 @@ static int htb_enqueue(struct sk_buff *skb, struct Qdisc *sch,/* enqueue to helper queue */ if (q->direct_queue.qlen < q->direct_qlen) {__qdisc_enqueue_tail (skb, &q->direct_queue); - q->direct_pkts++; +WRITE_ONCE (q->direct_pkts, q->direct_pkts +1 ); }else {return qdisc_drop (skb, sch, to_free); }
@@ -1208,12 +1208,12 @@ static int htb_dump(struct Qdisc *sch, struct sk_buff *skb)struct nlattr *nest;struct tc_htb_glob gopt; - sch->qstats.overlimits = q->overlimits; + sch->qstats.overlimits =READ_ONCE (q->overlimits);/* Its safe to not acquire qdisc lock. As we hold RTNL, * no change can happen on the qdisc parameters. */ - gopt.direct_pkts = q->direct_pkts; + gopt.direct_pkts =READ_ONCE (q->direct_pkts); gopt.version =HTB_VER ; gopt.rate2quantum = q->rate2quantum; gopt.defcls = q->defcls;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 220/2077 ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Linmao Li <[email protected]>
[ Upstream commit 627ac78f2741e2ebd2225e2e953b6964a8a9182f ]
addrconf_dad_failure() transitions ifp->state from DAD to POSTDAD via addrconf_dad_end(), which drops ifp->lock on return. The lock is re-acquired after net_info_ratelimited(). A concurrent ipv6_del_addr() can take the lock in that window, set ifp->state to DEAD and run list_del_rcu(&ifp->if_list).
addrconf_dad_failure() then overwrites DEAD with ERRDAD at errdad:
and schedules a new dad_work. The work calls ipv6_del_addr() again, hitting the already-poisoned list entry:
general protection fault: 0000 [#1] SMP NOPTI CPU: 4 PID: 217 Comm: kworker/4:1 Workqueue: ipv6_addrconf addrconf_dad_work RIP: 0010:ipv6_del_addr+0xe9/0x280 RAX: dead000000000122 Call Trace: addrconf_dad_stop+0x113/0x140 addrconf_dad_work+0x28c/0x430 process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ret_from_fork+0x35/0x40
Fold the addrconf_dad_end() logic into addrconf_dad_failure() under a single ifp->lock critical section. The STABLE_PRIVACY branch temporarily drops ifp->lock around address regeneration, so atlock_errdad: verify the state is still POSTDAD before transitioning to ERRDAD; bail out otherwise to avoid overwriting a state set by another path while the lock was released.
--- net/ipv6/addrconf.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
net/ipv6/addrconf.c +10 -3
@@ -2168,16 +2168,18 @@ void addrconf_dad_failure(struct sk_buff *skb, struct inet6_ifaddr *ifp)struct net *net =dev_net (idev->dev);int max_addresses; -if (addrconf_dad_end (ifp)) { +spin_lock_bh (&ifp->lock); + +if (ifp->state !=INET6_IFADDR_STATE_DAD ) { +spin_unlock_bh (&ifp->lock);in6_ifa_put (ifp);return ; } + ifp->state =INET6_IFADDR_STATE_POSTDAD ;net_info_ratelimited ("%s: IPv6 duplicate address %pI6c used by %pM detected!\n" , ifp->idev->dev->name, &ifp->addr,eth_hdr (skb)->h_source); -spin_lock_bh (&ifp->lock); -if (ifp->flags &IFA_F_STABLE_PRIVACY ) {struct in6_addr new_addr;struct inet6_ifaddr *ifp2;
@@ -2225,6 +2227,11 @@ void addrconf_dad_failure(struct sk_buff *skb, struct inet6_ifaddr *ifp)in6_ifa_put (ifp2); lock_errdad:spin_lock_bh (&ifp->lock); +if (ifp->state !=INET6_IFADDR_STATE_POSTDAD ) { +spin_unlock_bh (&ifp->lock); +in6_ifa_put (ifp); +return ; + } } errdad:
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 221/2077 IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Prathamesh Deshpande <[email protected]>
[ Upstream commit e79389115b9d27287ff6230a9750675106ed7668 ]
mlx5_ib_alloc_transport_domain() allocates a transport domain and then may fail in mlx5_ib_enable_lb(). In that case, the allocated TD is leaked.
Fix this by deallocating the TD when mlx5_ib_enable_lb() returns an error. Also return 0 explicitly in the no-loopback-capability success branch, and move dev->lb.mutex initialization to mlx5_ib_stage_init_init().
--- drivers/infiniband/hw/mlx5/main.c | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-)
drivers/infiniband/hw/mlx5/main.c +8 -7
@@ -2069,9 +2069,13 @@ static int mlx5_ib_alloc_transport_domain(struct mlx5_ib_dev *dev, u32 *tdn,if ((MLX5_CAP_GEN (dev->mdev, port_type) !=MLX5_CAP_PORT_TYPE_ETH ) || (!MLX5_CAP_GEN (dev->mdev, disable_local_lb_uc) && !MLX5_CAP_GEN (dev->mdev, disable_local_lb_mc))) -return err; +return 0 ; + + err =mlx5_ib_enable_lb (dev, true, false); +if (err) +mlx5_cmd_dealloc_transport_domain (dev->mdev, *tdn, uid); -return mlx5_ib_enable_lb (dev, true, false); +return err; } static void mlx5_ib_dealloc_transport_domain(struct mlx5_ib_dev *dev, u32 tdn,
@@ -4488,6 +4492,8 @@ static int mlx5_ib_stage_init_init(struct mlx5_ib_dev *dev) dev->port[i].roce.last_port_state =IB_PORT_DOWN ; } +mutex_init (&dev->lb.mutex); + err =mlx5r_cmd_query_special_mkeys (dev);if (err)return err;
@@ -4788,11 +4794,6 @@ static int mlx5_ib_stage_caps_init(struct mlx5_ib_dev *dev)if (err)return err; -if ((MLX5_CAP_GEN (dev->mdev, port_type) ==MLX5_CAP_PORT_TYPE_ETH ) && - (MLX5_CAP_GEN (dev->mdev, disable_local_lb_uc) || -MLX5_CAP_GEN (dev->mdev, disable_local_lb_mc))) -mutex_init (&dev->lb.mutex); -if (MLX5_CAP_GEN_64 (dev->mdev, general_obj_types) &MLX5_GENERAL_OBJ_TYPES_CAP_VIRTIO_NET_Q ) { err =mlx5_ib_init_var_region (dev);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 222/2077 RDMA/hns: Fix arithmetic overflow in calc_hem_config()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Chesnokov <[email protected]>
[ Upstream commit a38e4410af9ad8b7ad2217254da06cd4dc21f0ed ]
If bt_num is 3 or 2, then the expressions like l0_idx * chunk_ba_num + l1_idx are computed in 32-bit arithmetic before being assigned to a u64 index field, which can lead to overflow.
Cast the first operand to u64 to ensure the arithmetic is performed in 64-bit.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
--- drivers/infiniband/hw/hns/hns_roce_hem.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/infiniband/hw/hns/hns_roce_hem.c +4 -4
@@ -314,14 +314,14 @@ static int calc_hem_config(struct hns_roce_dev *hr_dev, bt_num =hns_roce_get_bt_num (table->type, mhop->hop_num);switch (bt_num) {case 3 : - index->l1 = l0_idx * chunk_ba_num + l1_idx; + index->l1 = (u64 )l0_idx * chunk_ba_num + l1_idx; index->l0 = l0_idx; - index->buf = l0_idx * chunk_ba_num * chunk_ba_num + - l1_idx * chunk_ba_num + l2_idx; + index->buf = (u64 )l0_idx * chunk_ba_num * chunk_ba_num + + (u64 )l1_idx * chunk_ba_num + l2_idx;break ;case 2 : index->l0 = l0_idx; - index->buf = l0_idx * chunk_ba_num + l1_idx; + index->buf = (u64 )l0_idx * chunk_ba_num + l1_idx;break ;case 1 : index->buf = l0_idx;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 223/2077 RDMA/mlx5: Fix UMR XLT cleanup on ODP populate failure
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Prathamesh Deshpande <[email protected]>
[ Upstream commit 1eae35b37923cb71b0cb5136d00671440d488b9f ]
mlx5r_umr_update_xlt() allocates and DMA maps an XLT buffer with mlx5r_umr_create_xlt(). The buffer is released by the common cleanup path through mlx5r_umr_unmap_free_xlt().
After mlx5_odp_populate_xlt() became fallible, its error path returned directly and skipped that cleanup. This leaks the XLT DMA mapping and buffer. If the emergency XLT page was used, it also leaves xlt_emergency_page_mutex locked.
Break out of the loop so execution falls through the existing cleanup path.
--- drivers/infiniband/hw/mlx5/umr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/infiniband/hw/mlx5/umr.c +1 -1
@@ -915,7 +915,7 @@ int mlx5r_umr_update_xlt(struct mlx5_ib_mr *mr, u64 idx, int npages,*/ err =mlx5_odp_populate_xlt (xlt, idx, npages, mr, flags);if (err) -return err; +break ;dma_sync_single_for_device (ddev, sg.addr, sg.length,DMA_TO_DEVICE ); sg.length =ALIGN (size_to_map,MLX5_UMR_FLEX_ALIGNMENT );
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 224/2077 RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Prathamesh Deshpande <[email protected]>
[ Upstream commit 43f8f7946814c8e5f464518246fdbc69b6e32326 ]
MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT() links event_sub into sub_list before initializing the fields used by the shared error path.
If eventfd_ctx_fdget() then fails, the unwind path dereferences event_sub->ev_file in uverbs_uobject_put() and calls subscribe_event_xa_dealloc() with an unset xa_key_level1.
subscribe_event_xa_alloc() creates the XA entry exactly once for a given key_level1, on the first occurrence of that key. The unwind path must therefore call subscribe_event_xa_dealloc() exactly once for it as well.
Enforce that by adding devx_key_in_sub_list() and calling subscribe_event_xa_dealloc() only when the last matching pending entry is being cleaned up.
--- drivers/infiniband/hw/mlx5/devx.c | 30 +++++++++++++++++++++++------- 1 file changed, 23 insertions(+), 7 deletions(-)
drivers/infiniband/hw/mlx5/devx.c +23 -7
@@ -1913,6 +1913,17 @@ static int UVERBS_HANDLER(MLX5_IB_METHOD_DEVX_OBJ_ASYNC_QUERY)(return err; } +static bool devx_key_in_sub_list (struct list_head *list,u32 key_level1) +{ +struct devx_event_subscription *s; + +list_for_each_entry (s, list, event_list) +if (s->xa_key_level1 == key_level1) +return true; + +return false; +} + static void subscribe_event_xa_dealloc(struct mlx5_devx_event_table *devx_event_table, u32 key_level1,
@@ -2160,10 +2171,17 @@ static int UVERBS_HANDLER(MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT)( event_sub =kzalloc_obj (*event_sub);if (!event_sub) { +if (!devx_key_in_sub_list (&sub_list, key_level1)) +subscribe_event_xa_dealloc (devx_event_table, + key_level1, + obj, + obj_id); err = -ENOMEM ; goto err; } + event_sub->ev_file = ev_file; + event_sub->xa_key_level1 = key_level1;list_add_tail (&event_sub->event_list, &sub_list);uverbs_uobject_get (&ev_file->uobj);if (use_eventfd) {
@@ -2178,9 +2196,6 @@ static int UVERBS_HANDLER(MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT)( } event_sub->cookie = cookie; - event_sub->ev_file = ev_file; -/* May be needed upon cleanup the devx object/subscription */ - event_sub->xa_key_level1 = key_level1; event_sub->xa_key_level2 = obj_id;INIT_LIST_HEAD (&event_sub->obj_list); }
@@ -2225,10 +2240,11 @@ static int UVERBS_HANDLER(MLX5_IB_METHOD_DEVX_SUBSCRIBE_EVENT)(list_for_each_entry_safe (event_sub, tmp_sub, &sub_list, event_list) {list_del (&event_sub->event_list); -subscribe_event_xa_dealloc (devx_event_table, - event_sub->xa_key_level1, - obj, - obj_id); +if (!devx_key_in_sub_list (&sub_list, event_sub->xa_key_level1)) +subscribe_event_xa_dealloc (devx_event_table, + event_sub->xa_key_level1, + obj, + obj_id);if (event_sub->eventfd)eventfd_ctx_put (event_sub->eventfd);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 225/2077 RDMA/srpt: fix integer overflow in immediate data length check
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sara Venkatesh <[email protected]>
[ Upstream commit eb4ecdf631fe00e8020bf461503cb9b7017ed796 ]
imm_buf->len is a user-controlled uint32_t received from the network. Adding it to imm_data_offset without overflow checking allows a malicious initiator to send len=0xFFFFFFFF, causing req_size to wrap around to a small value, bypassing the bounds check, and subsequently passing a ~4GB length to sg_init_one().
Use check_add_overflow() to detect wrapping before the comparison.
--- drivers/infiniband/ulp/srpt/ib_srpt.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/infiniband/ulp/srpt/ib_srpt.c +3 -2
@@ -1129,9 +1129,10 @@ static int srpt_get_desc_tbl(struct srpt_recv_ioctx *recv_ioctx,struct srp_imm_buf *imm_buf =srpt_get_desc_buf (srp_cmd);void *data = (void *)srp_cmd + imm_data_offset;uint32_t len =be32_to_cpu (imm_buf->len); -uint32_t req_size = imm_data_offset + len; +uint32_t req_size; -if (req_size > srp_max_req_size) { +if (check_add_overflow ((uint32_t )imm_data_offset, len, &req_size) || + req_size > srp_max_req_size) {pr_err ("Immediate data (length %d + %d) exceeds request size %d\n" , imm_data_offset, len, srp_max_req_size);return -EINVAL ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 226/2077 RDMA/hns: Initialize seqfile before creating file
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Junxian Huang <[email protected]>
[ Upstream commit b4070770506ff516e21b4923afdaf7eb5da0e150 ]
The debugfs file was created before seq->read and seq->data were set, leaving a small window where userspace could access an uninitialized seqfile.
Move debugfs_create_file() after the assignments to avoid this issue. Also, inline the original init_debugfs_seqfile() since it is not a really necessary helper.
--- drivers/infiniband/hw/hns/hns_roce_debugfs.c | 19 +++++-------------- 1 file changed, 5 insertions(+), 14 deletions(-)
drivers/infiniband/hw/hns/hns_roce_debugfs.c +5 -14
@@ -26,17 +26,6 @@ static const struct file_operations hns_debugfs_seqfile_fops = { .llseek = seq_lseek }; -static void init_debugfs_seqfile (struct hns_debugfs_seqfile *seq, -const char *name,struct dentry *parent, -int (*read_fn)(struct seq_file *,void *), -void *data) -{ -debugfs_create_file (name,0400 , parent, seq, &hns_debugfs_seqfile_fops); - - seq->read = read_fn; - seq->data = data; -} -static const char *const sw_stat_info[] = { [HNS_ROCE_DFX_AEQE_CNT ] ="aeqe" , [HNS_ROCE_DFX_CEQE_CNT ] ="ceqe" ,
@@ -76,10 +65,12 @@ static void create_sw_stat_debugfs(struct hns_roce_dev *hr_dev, {struct hns_sw_stat_debugfs *dbgfs = &hr_dev->dbgfs.sw_stat_root; - dbgfs->root =debugfs_create_dir ("sw_stat" , parent); + dbgfs->sw_stat.read = sw_stat_debugfs_show; + dbgfs->sw_stat.data = hr_dev; -init_debugfs_seqfile (&dbgfs->sw_stat,"sw_stat" , dbgfs->root, - sw_stat_debugfs_show, hr_dev); + dbgfs->root =debugfs_create_dir ("sw_stat" , parent); +debugfs_create_file ("sw_stat" ,0400 , dbgfs->root, &dbgfs->sw_stat, + &hns_debugfs_seqfile_fops); }/* debugfs for device */
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 227/2077 tools/rtla: Fix --dump-tasks usage in timerlat
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Costa Shulyupin <[email protected]>
[ Upstream commit 704fe8f3d97bba842f5f357e317116f1b88169e8 ]
Fix --dump-task to --dump-tasks in timerlat_hist usage string and getopt_long table for consistency with timerlat_top.
Add missing --dump-tasks to timerlat_top usage synopsis.
--- tools/tracing/rtla/src/timerlat_hist.c | 4 ++-- tools/tracing/rtla/src/timerlat_top.c | 3 ++- 2 files changed, 4 insertions(+), 3 deletions(-)
tools/tracing/rtla/src/timerlat_hist.c +2 -2
@@ -694,7 +694,7 @@ static void timerlat_hist_usage(void)"[-d s] [-D] [-n] [-a us] [-p us] [-i us] [-T us] [-s us] \\" ," [-t [file]] [-e sys[:event]] [--filter <filter>] [--trigger <trigger>] [-c cpu-list] [-H cpu-list]\\" ," [-P priority] [-E N] [-b N] [--no-irq] [--no-thread] [--no-header] [--no-summary] \\" , -" [--no-index] [--with-zeros] [--dma-latency us] [-C [cgroup_name]] [--no-aa] [--dump-task] [-u|-k]" , +" [--no-index] [--with-zeros] [--dma-latency us] [-C [cgroup_name]] [--no-aa] [--dump-tasks] [-u|-k]" ," [--warm-up s] [--deepest-idle-state n]" , NULL, };
@@ -809,7 +809,7 @@ static struct common_params {"filter", required_argument, 0, '7'}, {"dma-latency", required_argument, 0, '8'}, {"no-aa", no_argument, 0, '9'}, - {"dump-task", no_argument, 0, '\1'}, + {"dump-tasks", no_argument, 0, '\1'}, {"warm-up", required_argument, 0, '\2'}, {"trace-buffer-size", required_argument, 0, '\3'}, {"deepest-idle-state", required_argument, 0, '\4'},
tools/tracing/rtla/src/timerlat_top.c +2 -1
@@ -467,7 +467,8 @@ static void timerlat_top_usage(void)static const char *const msg_start[] = {"[-q] [-a us] [-d s] [-D] [-n] [-p us] [-i us] [-T us] [-s us] \\" ," [[-t [file]] [-e sys[:event]] [--filter <filter>] [--trigger <trigger>] [-c cpu-list] [-H cpu-list]\\" , -" [-P priority] [--dma-latency us] [--aa-only us] [-C [cgroup_name]] [-u|-k] [--warm-up s] [--deepest-idle-state n]" , +" [-P priority] [--dma-latency us] [--aa-only us] [-C [cgroup_name]] [--dump-tasks] [-u|-k] [--warm-up s]\\" , +" [--deepest-idle-state n]" ,NULL , };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 228/2077 rtla: Stop the record trace on interrupt
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Crystal Wood <[email protected]>
[ Upstream commit f03a59f949176ce4312cb466245d1243aaf40389 ]
Before, when rtla got a signal, it stopped the main trace but not the record trace. With "--on-end trace", this can lead to save_trace_to_file() failing to keep up, especially on a debug kernel. Plus, it adds post-stoppage noise to the trace file.
--- tools/tracing/rtla/src/common.c | 19 +++++++++++-------- tools/tracing/rtla/src/common.h | 1 - tools/tracing/rtla/src/timerlat.c | 2 +- 3 files changed, 12 insertions(+), 10 deletions(-)
tools/tracing/rtla/src/common.c +11 -8
@@ -10,7 +10,7 @@#include "common.h" -struct trace_instance *trace_inst; +struct osnoise_tool *trace_tool;volatile int stop_tracing;int nr_cpus;
@@ -21,12 +21,16 @@ static void stop_trace(int sig)* Stop requested twice in a row; abort event processing and * exit immediately */ -tracefs_iterate_stop (trace_inst->inst); +if (trace_tool) +tracefs_iterate_stop (trace_tool->trace.inst);return ; } stop_tracing =1 ; -if (trace_inst) -trace_instance_stop (trace_inst); +if (trace_tool) { +trace_instance_stop (&trace_tool->trace); +if (trace_tool->record) +trace_instance_stop (&trace_tool->record->trace); + } }/*
@@ -255,11 +259,10 @@ int run_tool(struct tool_ops *ops, int argc, char *argv[]) tool->params = params;/* -* Save trace instance into global variable so that SIGINT can stop -* the timerlat tracer. +* Expose the tool to signal handlers so they can stop the trace. * Otherwise, rtla could loop indefinitely when overloaded. */ - trace_inst = &tool->trace; + trace_tool = tool; retval = ops->apply_config (tool);if (retval) {
@@ -267,7 +270,7 @@ int run_tool(struct tool_ops *ops, int argc, char *argv[]) goto out_free; } - retval =enable_tracer_by_name (trace_inst->inst, ops->tracer); + retval =enable_tracer_by_name (tool->trace.inst, ops->tracer);if (retval) {err_msg ("Failed to enable %s tracer\n" , ops->tracer); goto out_free;
tools/tracing/rtla/src/common.h +0 -1
@@ -54,7 +54,6 @@ struct osnoise_context {int opt_workload; }; -extern struct trace_instance *trace_inst;extern volatile int stop_tracing;struct hist_params {
tools/tracing/rtla/src/timerlat.c +1 -1
@@ -202,7 +202,7 @@ void timerlat_analyze(struct osnoise_tool *tool, bool stopped)* If the trace did not stop with --aa-only, at least print * the max known latency. */ - max_lat =tracefs_instance_file_read (trace_inst->inst,"tracing_max_latency" ,NULL ); + max_lat =tracefs_instance_file_read (tool->trace.inst,"tracing_max_latency" ,NULL );if (max_lat) {printf (" Max latency was %s\n" , max_lat);free (max_lat);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 229/2077 drm/syncobj: Fix memory leak in drm_syncobj_find_fence()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Liviu Dudau <[email protected]>
[ Upstream commit e5b93bd6fdb92aa5e4689715d7e8487d9ce66a38 ]
Commit 18226ba52159 ("drm/syncobj: reject invalid flags in drm_syncobj_find_fence") forgot to take into account the fact that drm_syncobj_find() takes a reference to syncobj and returns early without dropping the reference, leading to memory leaks.
Reported by: Sam Spencer <[email protected]>
--- drivers/gpu/drm/drm_syncobj.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
drivers/gpu/drm/drm_syncobj.c +6 -4
@@ -442,13 +442,15 @@ int drm_syncobj_find_fence(struct drm_file *file_private,u64 timeout =nsecs_to_jiffies64 (DRM_SYNCOBJ_WAIT_FOR_SUBMIT_TIMEOUT );int ret; -if (flags & ~DRM_SYNCOBJ_WAIT_FLAGS_WAIT_FOR_SUBMIT ) -return -EINVAL ; -if (!syncobj)return -ENOENT ; -/* Waiting for userspace with locks help is illegal cause that can +if (flags & ~DRM_SYNCOBJ_WAIT_FLAGS_WAIT_FOR_SUBMIT ) { + ret = -EINVAL ; + goto out; + } + +/* Waiting for userspace with locks held is illegal cause that can * trivial deadlock with page faults for example. Make lockdep complain * about it early on. */
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 230/2077 dm: limit target bio polling to one shot
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Fengnan Chang <[email protected]>
[ Upstream commit 5aa0f9231cbacade065cedd8e9b5ebd067231171 ]
dm_poll_bio() is the ->poll_bio() callback for a stacked dm device. The caller only knows about the dm queue, so it may decide to do a spinning poll if it thinks a single queue is being polled. Passing those flags unchanged to the mapped clone lets blk_mq_poll() spin on a target queue from inside dm_poll_bio().
With io_uring IOPOLL on a dm-stripe target this can keep a task in
dm_poll_bio() -> bio_poll() -> blk_mq_poll()
long enough to trigger an RCU CPU stall, before io_uring gets back to io_iopoll_check() and its need_resched() check.
Keep dm's ->poll_bio() bounded by forcing one-shot polling for target bios. The caller can invoke dm_poll_bio() again if it wants to keep polling, and it also gets a chance to reap completions or reschedule between passes.
--- drivers/md/dm.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
drivers/md/dm.c +11 -2
@@ -2098,8 +2098,17 @@ static bool dm_poll_dm_io(struct dm_io *io, struct io_comp_batch *iob,WARN_ON_ONCE (!dm_tio_is_normal (&io->tio));/* don't poll if the mapped io is done */ -if (atomic_read (&io->io_count) >1 ) -bio_poll (&io->tio.clone, iob, flags); +if (atomic_read (&io->io_count) >1 ) { +/* +* DM hides the target queues from the upper poller, which may +* decide it is safe to spin on a single stacked queue. Do not +* pass that spinning policy down to a target queue: one slow +* clone could keep the task inside dm_poll_bio() for a long +* time. Poll target bios once and let the caller decide +* whether to keep polling, reap completions or reschedule. +*/ +bio_poll (&io->tio.clone, iob, flags |BLK_POLL_ONESHOT ); + }/* bio_poll holds the last reference */ return atomic_read (&io->io_count) ==1 ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 231/2077 selftests/bpf: Override EXTRA_LDFLAGS for static builds
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Paul Chaignon <[email protected]>
[ Upstream commit 879daba303f7d7c3057f4d218921621e751f1912 ]
When running vmtest.sh with static linking, the bpftool_map_access selftests fail. These selftests are calling the bpftool binary in tools/sbin/ directly, which results in the following error:
error while loading shared libraries: libLLVM.so.21.1:
cannot open shared object file: No such file or directory
To fix this, we need to also build bpftool statically. That can be done by setting EXTRA_LDFLAGS=-static.
--- tools/testing/selftests/bpf/README.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/bpf/README.rst +1 -1
@@ -77,7 +77,7 @@ In case of linker errors when running selftests, try using static linking: .. code-block:: console - $ LDLIBS=-static PKG_CONFIG='pkg-config --static' vmtest.sh + $ LDLIBS=-static EXTRA_LDFLAGS=-static PKG_CONFIG='pkg-config --static' vmtest.sh .. note:: Some distros may not support static linking.
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 232/2077 selftests/bpf: Reject unsupported -k option in vmtest.sh
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Roman Kvasnytskyi <[email protected]>
[ Upstream commit 6df582112aa9ac9d190169abdb0e42e496659ec9 ]
vmtest.sh does not document a -k option and does not handle it in the getopts case statement. However, the getopts optstring includes k, which causes the script to accept -k silently instead of reporting it as an invalid option.
Remove k from the optstring so unsupported options are rejected through the existing invalid-option path.
--- tools/testing/selftests/bpf/vmtest.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/bpf/vmtest.sh +1 -1
@@ -382,7 +382,7 @@ main() local exit_command="poweroff -f" local debug_shell="no" - while getopts ':hskl:id:j:' opt; do + while getopts ':hsl:id:j:' opt; do case ${opt} in l) LOCAL_ROOTFS_IMAGE="$OPTARG"
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 233/2077 selftests/bpf: Fix test for refinement of single-value tnum
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Paul Chaignon <[email protected]>
[ Upstream commit 523d2f42b406f5be2989f436b03eacebf3679835 ]
This patch fixes the "bounds refinement with single-value tnum on umin" verifier selftest. This selftest was introduced in commit e6ad477d1bf8 ("selftests/bpf: Test refinement of single-value tnum") to cover the logic from __update_reg64_bounds(), introduced in commit efc11a667878 ("bpf: Improve bounds when tnum has a single possible value"). However, the test still passes if that last commit is reverted.
The test is supposed to cover the case when the tnum and u64 range (or cnum64 now) overlap in a single value. __update_reg64_bounds() detects that case and refines the bounds to a known constant. However, the constants for the test were poorly chosen and the bounds get refined to a known constant even without __update_reg64_bounds(). The code is as follows:
0: call bpf_get_prandom_u32#7 ; R0=scalar() 1: r0 |= 224 ; R0=scalar(umin=umin32=224,var_off=(0xe0; 0xffffffffffffff1f)) 2: r0 &= 240 ; R0=scalar(smin=umin=smin32=umin32=224,smax=umax=smax32=umax32=240,var_off=(0xe0; 0x10)) 3: if r0 == 0xf0 goto pc+2 ; R0=224
After instruction 3, we have u64=[0xe0; 0xef] and tnum=(0xe0; 0x10). __reg_bound_offset() is able to deduce a new tnum from the u64, tnum=(0xe0; 0x0f), which combined with the existing tnum gives us a
constant: 0xe0 or 224.
We can easily fix this by choosing different starting bounds. If we make it u64=[0xe1; 0xf0], then __reg_bound_offset() doesn't have any impact.
--- .../testing/selftests/bpf/progs/verifier_bounds.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
tools/testing/selftests/bpf/progs/verifier_bounds.c +7 -7
@@ -1890,25 +1890,25 @@ __naked void bounds_refinement_tnum_umax(void *ctx)/* This test covers the bounds deduction when the u64 range and the tnum * overlap only at umin. After instruction 3, the ranges look as follows: * -* 0 umin=0xe00 umax=0xeff U64_MAX +* 0 umin=0xe1 umax=0xf0 U64_MAX * | [xxxxxxxxxxxxxx] | * |----------------------------|------------------------------| * | x x | tnum values * -* The verifier can therefore deduce that the R0=0xe0=224. +* The verifier can therefore deduce that the R0=0xe1=225. */ SEC("socket") __description("bounds refinement with single-value tnum on umin") -__msg("3: (15) if r0 == 0xf0 {{.*}} R0=224") +__msg("3: (15) if r0 == 0xf1 {{.*}} R0=225") __success __log_level(2) __naked void bounds_refinement_tnum_umin(void *ctx) { asmvolatile (" \ call %[bpf_get_prandom_u32]; \ -r0 |= 0xe0; \ -r0 &= 0xf0; \ -if r0 == 0xf0 goto +2; \ -if r0 == 0xe0 goto +1; \ +r0 |= 0xe1; \ +r0 &= 0xf1; \ +if r0 == 0xf1 goto +2; \ +if r0 == 0xe1 goto +1; \ r10 = 0; \ exit; \ " :
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 234/2077 iommu/arm-smmu-qcom: Fix fastrpc compatible string in ACTLR client match table
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Bibek Kumar Patro <[email protected]>
[ Upstream commit a6e1618a65d453d4e739e5898c662ccb1e3de6c0 ]
The qcom_smmu_actlr_client_of_match table contained "qcom,fastrpc" as the compatible string for applying ACTLR prefetch settings to FastRPC devices. However, "qcom,fastrpc" is the compatible string for the parent rpmsg channel node, which is not an IOMMU client — it carries no "iommus" property in the device tree and is never attached to an SMMU context bank.
The actual IOMMU clients are the compute context bank (CB) child nodes, which use the compatible string "qcom,fastrpc-compute-cb". These nodes carry the "iommus" property and are probed by fastrpc_cb_driver via fastrpc_cb_probe(), which sets up the DMA mask and IOMMU mappings for each FastRPC session. The device tree structure is:
fastrpc {
compatible = "qcom,fastrpc"; /* rpmsg channel, no iommus */
...
compute-cb@3 {
compatible = "qcom,fastrpc-compute-cb";
iommus = <&apps_smmu 0x1823 0x0>; /* actual IOMMU client */
};
};Since qcom_smmu_set_actlr_dev() calls of_match_device() against the device being attached to the SMMU context bank, the "qcom,fastrpc" entry was never matching any device. As a result, the ACTLR prefetch settings (PREFETCH_DEEP | CPRE | CMTLB) were silently never applied for FastRPC compute context banks.
Fix this by replacing "qcom,fastrpc" with "qcom,fastrpc-compute-cb" in the match table so that the ACTLR settings are correctly applied to the compute CB devices that are the true IOMMU clients.
--- drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c +1 -1
@@ -39,7 +39,7 @@ static const struct of_device_id qcom_smmu_actlr_client_of_match[] = { .data = (const void *) (PREFETCH_DEEP | CPRE | CMTLB) }, { .compatible = "qcom,adreno-smmu", .data = (const void *) (PREFETCH_DEEP | CPRE | CMTLB) }, - { .compatible = "qcom,fastrpc", + { .compatible = "qcom,fastrpc-compute-cb", .data = (const void *) (PREFETCH_DEEP | CPRE | CMTLB) }, { .compatible = "qcom,qcm2290-mdss", .data = (const void *) (PREFETCH_SHALLOW | CPRE | CMTLB) },
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 235/2077 sched/fair: Update util_est after updating util_avg during dequeue
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Vincent Guittot <[email protected]>
[ Upstream commit 6d2051403d6c93832d3058a1b275c6aef2c97f44 ]
util_est_update() must be called after updating util_avg during the dequeue of a task and only when the task is not delayed dequeue.
Move util_est_update() in update_load_avg().
--- kernel/sched/fair.c | 188 ++++++++++++++++++++++---------------------- 1 file changed, 92 insertions(+), 96 deletions(-)
kernel/sched/fair.c +92 -96
@@ -4959,13 +4959,86 @@ static void detach_entity_load_avg(struct cfs_rq *cfs_rq, struct sched_entity *strace_pelt_cfs_tp (cfs_rq); } +#define UTIL_EST_MARGIN (SCHED_CAPACITY_SCALE / 100) + +static inline void util_est_update (struct sched_entity *se) +{ +unsigned int ewma, dequeued, last_ewma_diff; + +if (!sched_feat (UTIL_EST )) +return ; + +/* Get current estimate of utilization */ + ewma =READ_ONCE (se->avg.util_est); + +/* +* If the PELT values haven't changed since enqueue time, +* skip the util_est update. +*/ +if (ewma &UTIL_AVG_UNCHANGED ) +return ; + +/* Get utilization at dequeue */ + dequeued =READ_ONCE (se->avg.util_avg); + +/* +* Reset EWMA on utilization increases, the moving average is used only +* to smooth utilization decreases. +*/ +if (ewma <= dequeued) { + ewma = dequeued; + goto done; + } + +/* +* Skip update of task's estimated utilization when its members are +* already ~1% close to its last activation value. +*/ + last_ewma_diff = ewma - dequeued; +if (last_ewma_diff <UTIL_EST_MARGIN ) + goto done; + +/* +* To avoid underestimate of task utilization, skip updates of EWMA if +* we cannot grant that thread got all CPU time it wanted. +*/ +if ((dequeued +UTIL_EST_MARGIN ) <READ_ONCE (se->avg.runnable_avg)) + goto done; + +/* +* Update Task's estimated utilization +* +* When *p completes an activation we can consolidate another sample +* of the task size. This is done by using this value to update the +* Exponential Weighted Moving Average (EWMA): +* +* ewma(t) = w * task_util(p) + (1-w) * ewma(t-1) +* = w * task_util(p) + ewma(t-1) - w * ewma(t-1) +* = w * (task_util(p) - ewma(t-1)) + ewma(t-1) +* = w * ( -last_ewma_diff ) + ewma(t-1) +* = w * (-last_ewma_diff + ewma(t-1) / w) +* +* Where 'w' is the weight of new samples, which is configured to be +* 0.25, thus making w=1/4 ( >>= UTIL_EST_WEIGHT_SHIFT) +*/ + ewma <<=UTIL_EST_WEIGHT_SHIFT ; + ewma -= last_ewma_diff; + ewma >>=UTIL_EST_WEIGHT_SHIFT ; +done: + ewma |=UTIL_AVG_UNCHANGED ; +WRITE_ONCE (se->avg.util_est, ewma); + +trace_sched_util_est_se_tp (se); +} +/* * Optional action to be done while updating the load average */ -#define UPDATE_TG 0x1 -#define SKIP_AGE_LOAD 0x2 -#define DO_ATTACH 0x4 -#define DO_DETACH 0x8 +#define UPDATE_TG 0x01 +#define SKIP_AGE_LOAD 0x02 +#define DO_ATTACH 0x04 +#define DO_DETACH 0x08 +#define UPDATE_UTIL_EST 0x10/* Update task and its cfs_rq load average */ static inline void update_load_avg (struct cfs_rq *cfs_rq,struct sched_entity *se,int flags)
@@ -5008,6 +5081,9 @@ static inline void update_load_avg(struct cfs_rq *cfs_rq, struct sched_entity *sif (flags &UPDATE_TG )update_tg_load_avg (cfs_rq); } + +if (flags &UPDATE_UTIL_EST ) +util_est_update (se); }/*
@@ -5066,11 +5142,6 @@ static inline unsigned long task_util(struct task_struct *p)return READ_ONCE (p->se.avg.util_avg); } -static inline unsigned long task_runnable (struct task_struct *p) -{ -return READ_ONCE (p->se.avg.runnable_avg); -} -static inline unsigned long _task_util_est (struct task_struct *p) {return READ_ONCE (p->se.avg.util_est) & ~UTIL_AVG_UNCHANGED ;
@@ -5113,88 +5184,6 @@ static inline void util_est_dequeue(struct cfs_rq *cfs_rq,trace_sched_util_est_cfs_tp (cfs_rq); } -#define UTIL_EST_MARGIN (SCHED_CAPACITY_SCALE / 100) - -static inline void util_est_update (struct cfs_rq *cfs_rq, -struct task_struct *p, -bool task_sleep) -{ -unsigned int ewma, dequeued, last_ewma_diff; - -if (!sched_feat (UTIL_EST )) -return ; - -/* -* Skip update of task's estimated utilization when the task has not -* yet completed an activation, e.g. being migrated. -*/ -if (!task_sleep) -return ; - -/* Get current estimate of utilization */ - ewma =READ_ONCE (p->se.avg.util_est); - -/* -* If the PELT values haven't changed since enqueue time, -* skip the util_est update. -*/ -if (ewma &UTIL_AVG_UNCHANGED ) -return ; - -/* Get utilization at dequeue */ - dequeued =task_util (p); - -/* -* Reset EWMA on utilization increases, the moving average is used only -* to smooth utilization decreases. -*/ -if (ewma <= dequeued) { - ewma = dequeued; - goto done; - } - -/* -* Skip update of task's estimated utilization when its members are -* already ~1% close to its last activation value. -*/ - last_ewma_diff = ewma - dequeued; -if (last_ewma_diff <UTIL_EST_MARGIN ) - goto done; - -/* -* To avoid underestimate of task utilization, skip updates of EWMA if -* we cannot grant that thread got all CPU time it wanted. -*/ -if ((dequeued +UTIL_EST_MARGIN ) <task_runnable (p)) - goto done; - - -/* -* Update Task's estimated utilization -* -* When *p completes an activation we can consolidate another sample -* of the task size. This is done by using this value to update the -* Exponential Weighted Moving Average (EWMA): -* -* ewma(t) = w * task_util(p) + (1-w) * ewma(t-1) -* = w * task_util(p) + ewma(t-1) - w * ewma(t-1) -* = w * (task_util(p) - ewma(t-1)) + ewma(t-1) -* = w * ( -last_ewma_diff ) + ewma(t-1) -* = w * (-last_ewma_diff + ewma(t-1) / w) -* -* Where 'w' is the weight of new samples, which is configured to be -* 0.25, thus making w=1/4 ( >>= UTIL_EST_WEIGHT_SHIFT) -*/ - ewma <<=UTIL_EST_WEIGHT_SHIFT ; - ewma -= last_ewma_diff; - ewma >>=UTIL_EST_WEIGHT_SHIFT ; -done: - ewma |=UTIL_AVG_UNCHANGED ; -WRITE_ONCE (p->se.avg.util_est, ewma); - -trace_sched_util_est_se_tp (&p->se); -} -static inline unsigned long get_actual_cpu_capacity (int cpu) {unsigned long capacity =arch_scale_cpu_capacity (cpu);
@@ -5647,7 +5636,7 @@ static bool dequeue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags) { bool sleep = flags & DEQUEUE_SLEEP; -int action =UPDATE_TG ; +int action =0 ;update_curr (cfs_rq);clear_buddies (cfs_rq, se);
@@ -5667,15 +5656,23 @@ dequeue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags)if (sched_feat (DELAY_DEQUEUE ) && delay && !entity_eligible (cfs_rq, se)) { -update_load_avg (cfs_rq, se,0 ); +if (entity_is_task (se)) + action |=UPDATE_UTIL_EST ; +update_load_avg (cfs_rq, se, action);update_entity_lag (cfs_rq, se);set_delayed (se);return false; } } -if (entity_is_task (se) &&task_on_rq_migrating (task_of (se))) - action |=DO_DETACH ; + action =UPDATE_TG ; +if (entity_is_task (se)) { +if (task_on_rq_migrating (task_of (se))) + action |=DO_DETACH ; + +if (sleep && !(flags &DEQUEUE_DELAYED )) + action |=UPDATE_UTIL_EST ; + }/* * When dequeuing a sched_entity, we must:
@@ -7438,7 +7435,6 @@ static bool dequeue_task_fair(struct rq *rq, struct task_struct *p, int flags)if (!p->se.sched_delayed)util_est_dequeue (&rq->cfs, p); -util_est_update (&rq->cfs, p, flags &DEQUEUE_SLEEP );if (dequeue_entities (rq, &p->se, flags) <0 )return false;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 236/2077 selftests/mm: Fix resv_sz when parsing arm64 signal frame
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kevin Brodsky <[email protected]>
[ Upstream commit c364aa56d6738c8759e88941d7a45a1d6b4c52d0 ]
get_header() wants the size of the reserved area in struct sigcontext, but instead we pass it the size of the entire struct. This could in theory result in an out-of-bounds read (if the signal frame is malformed).
Fix this using one of the existing macros from tools/testing/selftests/arm64/signal/testcases/testcases.h.
This issue was reported by Sashiko on a patch that copied this portion of the code.
--- tools/testing/selftests/mm/pkey-arm64.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
tools/testing/selftests/mm/pkey-arm64.h +2 -1
@@ -130,9 +130,10 @@ static inline u64 get_pkey_bits(u64 reg, int pkey)static inline void aarch64_write_signal_pkey (ucontext_t *uctxt,u64 pkey) {struct _aarch64_ctx *ctx =GET_UC_RESV_HEAD (uctxt); +size_t resv_size =GET_UCP_RESV_SIZE (uctxt);struct poe_context *poe_ctx = (struct poe_context *)get_header (ctx,POE_MAGIC , -sizeof (uctxt->uc_mcontext),NULL ); + resv_size,NULL );if (poe_ctx) poe_ctx->por_el0 = pkey; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 237/2077 firmware: arm_ffa: Honor partition info descriptor size
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jamie Nguyen <[email protected]>
[ Upstream commit 01b9cae706161a39452a2cce0f281d4369344c51 ]
FFA_PARTITION_INFO_GET_REGS reports the size of each partition information descriptor in x2[63:48]. However, __ffa_partition_info_get_regs() walks the returned register payload with a hardcoded 24-byte stride (regs += 3), even though the size is already read into buf_sz.
That works for the FF-A v1.1/v1.2 24-byte descriptor layout, where each descriptor consumes three registers. Newer FF-A revisions can extend the descriptor while keeping the existing fields at the front. For example, a 48-byte descriptor consumes six registers, so advancing by only three registers desynchronises the parser and can make it read subsequent entries from the middle of a descriptor.
Use the advertised descriptor size to derive the register stride. Validate that the size is register-aligned, large enough for the fields parsed by the driver, and that the requested number of descriptors fits in the returned x3..x17 register window. The driver still copies only the fields it understands, but now skips over any trailing descriptor fields correctly.
(sudeep.holla: Minor rewordng of the commit message and subject)
--- drivers/firmware/arm_ffa/driver.c | 27 ++++++++++++++++----------- 1 file changed, 16 insertions(+), 11 deletions(-)
drivers/firmware/arm_ffa/driver.c +16 -11
@@ -324,11 +324,9 @@ __ffa_partition_info_get(u32 uuid0, u32 uuid1, u32 uuid2, u32 uuid3,#define PART_INFO_EXEC_CXT_MASK GENMASK(31, 16)#define PART_INFO_PROPS_MASK GENMASK(63, 32)#define FFA_PART_INFO_GET_REGS_FIRST_REG 3 -#define FFA_PART_INFO_GET_REGS_REGS_PER_DESC 3 -#define FFA_PART_INFO_GET_REGS_MAX_DESC \ - (((sizeof(ffa_value_t) / sizeof_field(ffa_value_t, a0)) - \ - FFA_PART_INFO_GET_REGS_FIRST_REG) / \ - FFA_PART_INFO_GET_REGS_REGS_PER_DESC) +#define FFA_PART_INFO_GET_REGS_MIN_REGS_PER_DESC 3 +#define FFA_PART_INFO_GET_REGS_NUM_REGS \ + (sizeof(ffa_value_t) / sizeof_field(ffa_value_t, a0))#define PART_INFO_ID (x) ((u16)(FIELD_GET(PART_INFO_ID_MASK, (x))))#define PART_INFO_EXEC_CXT (x) ((u16)(FIELD_GET(PART_INFO_EXEC_CXT_MASK, (x))))#define PART_INFO_PROPERTIES (x) ((u32)(FIELD_GET(PART_INFO_PROPS_MASK, (x))))
@@ -342,7 +340,7 @@ __ffa_partition_info_get_regs(u32 uuid0, u32 uuid1, u32 uuid2, u32 uuid3, do { __le64 *regs; - int idx, nr_desc, buf_idx; + int idx, nr_desc, buf_idx, regs_per_desc, max_desc; invoke_ffa_fn((ffa_value_t){ .a0 = FFA_PARTITION_INFO_GET_REGS,
@@ -365,8 +363,18 @@ __ffa_partition_info_get_regs(u32 uuid0, u32 uuid1, u32 uuid2, u32 uuid3,if (cur_idx < start_idx || cur_idx >= count)return -EINVAL ; + buf_sz =PARTITION_INFO_SZ (partition_info.a2); +if (buf_sz %sizeof (*regs)) +return -EINVAL ; + + regs_per_desc = buf_sz /sizeof (*regs); +if (regs_per_desc <FFA_PART_INFO_GET_REGS_MIN_REGS_PER_DESC ) +return -EINVAL ; + nr_desc = cur_idx - start_idx +1 ; -if (nr_desc >FFA_PART_INFO_GET_REGS_MAX_DESC ) + max_desc = (FFA_PART_INFO_GET_REGS_NUM_REGS - +FFA_PART_INFO_GET_REGS_FIRST_REG ) / regs_per_desc; +if (nr_desc > max_desc)return -EINVAL ; buf_idx = buf - buffer;
@@ -374,9 +382,6 @@ __ffa_partition_info_get_regs(u32 uuid0, u32 uuid1, u32 uuid2, u32 uuid3,return -EINVAL ; tag =UUID_INFO_TAG (partition_info.a2); - buf_sz =PARTITION_INFO_SZ (partition_info.a2); -if (buf_sz >sizeof (*buffer)) - buf_sz =sizeof (*buffer); regs = (void *)&partition_info.a3;for (idx =0 ; idx < nr_desc; idx++, buf++) {
@@ -395,7 +400,7 @@ __ffa_partition_info_get_regs(u32 uuid0, u32 uuid1, u32 uuid2, u32 uuid3, buf->exec_ctxt =PART_INFO_EXEC_CXT (val); buf->properties =PART_INFO_PROPERTIES (val);uuid_copy (&buf->uuid, &uuid_regs.uuid); - regs +=3 ; + regs += regs_per_desc; } start_idx = cur_idx +1 ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 238/2077 arm64: dts: freescale: imx95-verdin-ivy: fix RS485 RTS polarity
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Francesco Dolcini <[email protected]>
[ Upstream commit 9f004f2afded2870838c0ae4906c2fa9307286bb ]
Fix the RS485 functionality, the RS485 RTS signal is active high on Ivy.
--- arch/arm64/boot/dts/freescale/imx95-verdin-ivy.dtsi | 1 - 1 file changed, 1 deletion(-)
arch/arm64/boot/dts/freescale/imx95-verdin-ivy.dtsi +0 -1
@@ -452,7 +452,6 @@ &lpuart7 { /* Verdin UART_2, through RS485 transceiver */ &lpuart8 { - rs485-rts-active-low; rs485-rx-during-tx; linux,rs485-enabled-at-boot-time;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 239/2077 arm64: dts: imx8dxl-evk: Remove unnecessary PCIe EP properties
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sherry Sun <[email protected]>
[ Upstream commit 538525f34158deb21b782164bde23ec07a353e4a ]
For PCIe endpoint mode, only M.2 power supply needs to be ensured. On imx8dxl-evk, the M.2 power is always on and cannot be controlled, while reg_pcieb only controls the M.2 W_DISABLE1# signal. Remove the unnecessary vpcie-supply property from pcie0_ep node.
Also remove reset-gpio as PCIe endpoint mode doesn't require reset control.
--- arch/arm64/boot/dts/freescale/imx8dxl-evk.dts | 2 -- 1 file changed, 2 deletions(-)
arch/arm64/boot/dts/freescale/imx8dxl-evk.dts +0 -2
@@ -686,8 +686,6 @@ &pcie0_ep { phy-names = "pcie-phy"; pinctrl-0 = <&pinctrl_pcieb>; pinctrl-names = "default"; - reset-gpio = <&lsio_gpio4 0 GPIO_ACTIVE_LOW>; - vpcie-supply = <®_pcieb>; status = "disabled"; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 240/2077 arm64: dts: imx8qxp-mek: Remove unnecessary PCIe EP vpcie-supply
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sherry Sun <[email protected]>
[ Upstream commit b5ba136d535f1060322af31c0cf74d85ea19892d ]
For PCIe endpoint mode, only M.2 power supply needs to be ensured. On imx8qxp-mek, the M.2 power is always on and cannot be controlled, while reg_pcieb only controls the M.2 W_DISABLE1# signal. Remove the unnecessary vpcie-supply property from pcie0_ep node.
--- arch/arm64/boot/dts/freescale/imx8qxp-mek.dts | 1 - 1 file changed, 1 deletion(-)
arch/arm64/boot/dts/freescale/imx8qxp-mek.dts +0 -1
@@ -742,7 +742,6 @@ &pcie0_ep { phy-names = "pcie-phy"; pinctrl-0 = <&pinctrl_pcieb>; pinctrl-names = "default"; - vpcie-supply = <®_pcieb>; status = "disabled"; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 241/2077 arm64: dts: imx95-19x19-evk: Fix PCIe EP vpcie-supply
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sherry Sun <[email protected]>
[ Upstream commit 596d0f9f4fefffbf783ab26cfa90cf50f5dd6bb0 ]
The vpcie-supply property should reference the regulator that controls the actual M.2 power supply, not the W_DISABLE1# signal.
On imx95-19x19-evk:
- reg_pcie0 controls M.2 W_DISABLE1# signal
- reg_m2_pwr controls the actual M.2 power supply
Fix the vpcie-supply to use reg_m2_pwr for proper power control in PCIe endpoint mode.
--- arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts +1 -1
@@ -550,7 +550,7 @@ &pcie0 { &pcie0_ep { pinctrl-0 = <&pinctrl_pcie0>; pinctrl-names = "default"; - vpcie-supply = <®_pcie0>; + vpcie-supply = <®_m2_pwr>; status = "disabled"; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 242/2077 hfs: fix incorrect inode ID assignment in hfs_new_inode()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Viacheslav Dubeyko <[email protected]>
[ Upstream commit 6592287869bffee91f59363e51de5f971ec2bd9d ]
The xfstests' test-case generic/003 reveals the HFS volume corruption:
sudo ./check generic/003
FSTYP -- hfs
PLATFORM -- Linux/x86_64 hfsplus-testing-0001 7.0.0-rc1+ #18 SMP PREEMPT_DYNAMIC Fri Mar 13 17:54:19 PDT 2026 MKFS_OPTIONS -- /dev/loop51MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch
generic/003 51s ... _check_generic_filesystem: filesystem on /dev/loop51 is inconsistent
sudo fsck.hfs -d /dev/loop51
** /dev/loop51
Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K. Executing fsck_hfs (version 540.1-Linux).
** Checking HFS volume.
The volume name is untitled
** Checking extents overflow file.
** Checking catalog file.
** Checking catalog hierarchy.
** Checking volume bitmap.
** Checking volume information.
invalid MDB drNxtCNID
Master Directory Block needs minor repair
(1, 0)
Verify Status: VIStat = 0x8000, ABTStat = 0x0000 EBTStat = 0x0000 CBTStat = 0x0000 CatStat = 0x00000000
** Repairing volume.
** Rechecking volume.
** Checking HFS volume.
The volume name is untitled
** Checking extents overflow file.
** Checking catalog file.
** Checking catalog hierarchy.
** Checking volume bitmap.
** Checking volume information.
** The volume untitled was repaired successfully.
The reason of corruption is incorrect value of drNxtCNID (next CNID) in the MDB or superblock. The generic/003 test-case creates several new inodes:
kernel: run fstests generic/003
hfs: hfs_mdb_get():179 next_id 16
hfs: hfs_mdb_get():179 next_id 16
hfs: hfs_new_inode():208 next_id 17
hfs: hfs_new_inode():208 next_id 18
hfs: hfs_mdb_commit():307 next_id 18
hfs: hfs_mdb_get():179 next_id 18
hfs: hfs_new_inode():208 next_id 19
hfs: hfs_new_inode():208 next_id 20
hfs_mdb_commit():307 next_id 20
hfs: hfs_mdb_get():179 next_id 20
hfs: hfs_new_inode():208 next_id 21
hfs: hfs_mdb_commit():307 next_id 21
hfs: hfs_mdb_get():179 next_id 21
The final assigned CNID was 21 but fsck correct it on 22. It is possible to see that the reason of the issue is incrementing the next_id value at first and assigning already incremented value to the inode->i_ino:
struct inode *hfs_new_inode(...)
{
<skipped>
next_id = atomic64_inc_return(&HFS_SB(sb)->next_id);
<skipped>
inode->i_ino = (u32)next_id;<skipped>
}
This patch fixes the issue by assigning the decremented value to inode->i_ino.
--- fs/hfs/inode.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/hfs/inode.c +1 -1
@@ -204,7 +204,7 @@ struct inode *hfs_new_inode(struct inode *dir, const struct qstr *name, umode_tpr_err ("cannot create new inode: next CNID exceeds limit\n" ); goto out_discard; } - inode->i_ino = (u32 )next_id; + inode->i_ino = (u32 )next_id -1 ; inode->i_mode = mode; inode->i_uid =current_fsuid (); inode->i_gid =current_fsgid ();
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 243/2077 media: atomisp: Fix memory leak in atomisp_fixed_pattern_table()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zilin Guan <[email protected]>
[ Upstream commit 4e8156bd9517fa18c3613ea39c222c7035f0221e ]
atomisp_v4l2_framebuffer_to_css_frame() allocates memory for temporary variable raw_black_frame, which must be released via ia_css_frame_free() before the function returns. However, if sh_css_set_black_frame() fails, the function returns immediately without performing this cleanup, leading to a memory leak.
Fix this by assigning the return value of sh_css_set_black_frame() to ret. This ensures that the error code is propagated while allowing the execution to fall through to the ia_css_frame_free() cleanup call.
The bug was originally detected on v6.13-rc1 using an experimental static analysis tool we are developing, and we have verified that the issue persists in the latest mainline kernel. The tool is based on the LLVM framework and is specifically designed to detect memory management issues. It is currently under active development and not yet publicly available.
We performed build testing on x86_64 with allyesconfig. Since triggering this error path in atomisp requires specific Intel Atom ISP hardware and firmware, we were unable to perform runtime testing and instead verified the fix according to the code logic.
--- drivers/staging/media/atomisp/pci/atomisp_cmd.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
drivers/staging/media/atomisp/pci/atomisp_cmd.c +2 -4
@@ -3364,10 +3364,8 @@ int atomisp_fixed_pattern_table(struct atomisp_sub_device *asd,if (ret)return ret; -if (sh_css_set_black_frame (asd->stream_env[ATOMISP_INPUT_STREAM_GENERAL ].stream, - raw_black_frame) !=0 ) -return -ENOMEM ; - + ret =sh_css_set_black_frame (asd->stream_env[ATOMISP_INPUT_STREAM_GENERAL ].stream, + raw_black_frame);ia_css_frame_free (raw_black_frame);return ret; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 244/2077 media: atomisp: gc2235: fix UAF and memory leak
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yuho Choi <[email protected]>
[ Upstream commit 628f763aee0047ff44974388d6f70f75a763026b ]
gc2235_probe() handles its error paths incorrectly.
If media_entity_pads_init() fails, gc2235_remove() is called, which tears down the subdev and frees dev, but then still falls through to atomisp_register_i2c_module(). This results in use-after-free.
If atomisp_register_i2c_module() fails, the media entity and control handler are left initialized and dev is leaked.
gc2235_remove() unconditionally calls media_entity_cleanup() and v4l2_ctrl_handler_free(), but these are not initialized at every error path in gc2235_probe().
Replace gc2235_remove() calls in the probe error paths with explicit unwind labels that free only the resources initialized at each point of failure, in reverse order of initialization.
--- .../media/atomisp/i2c/atomisp-gc2235.c | 29 ++++++++++++------- 1 file changed, 18 insertions(+), 11 deletions(-)
drivers/staging/media/atomisp/i2c/atomisp-gc2235.c +18 -11
@@ -809,7 +809,7 @@ static int gc2235_probe(struct i2c_client *client) ret =gc2235_s_config (&dev->sd, client->irq, gcpdev);if (ret) - goto out_free; + goto err_unregister_subdev; dev->sd.flags |=V4L2_SUBDEV_FL_HAS_DEVNODE ; dev->pad.flags =MEDIA_PAD_FL_SOURCE ;
@@ -818,18 +818,16 @@ static int gc2235_probe(struct i2c_client *client) ret =v4l2_ctrl_handler_init (&dev->ctrl_handler,ARRAY_SIZE (gc2235_controls)); -if (ret) { -gc2235_remove (client); -return ret; - } +if (ret) + goto err_csi_cfg;for (i =0 ; i <ARRAY_SIZE (gc2235_controls); i++)v4l2_ctrl_new_custom (&dev->ctrl_handler, &gc2235_controls[i],NULL );if (dev->ctrl_handler.error) { -gc2235_remove (client); -return dev->ctrl_handler.error; + ret = dev->ctrl_handler.error; + goto err_ctrl_handler; }/* Use same lock for controls as for everything else. */
@@ -838,14 +836,23 @@ static int gc2235_probe(struct i2c_client *client) ret =media_entity_pads_init (&dev->sd.entity,1 , &dev->pad);if (ret) -gc2235_remove (client); + goto err_ctrl_handler; + + ret =atomisp_register_i2c_module (&dev->sd, gcpdev); +if (ret) + goto err_media_cleanup; -return atomisp_register_i2c_module (&dev->sd, gcpdev); +return 0 ; -out_free: +err_media_cleanup: +media_entity_cleanup (&dev->sd.entity); +err_ctrl_handler: +v4l2_ctrl_handler_free (&dev->ctrl_handler); +err_csi_cfg: + dev->platform_data->csi_cfg (&dev->sd,0 ); +err_unregister_subdev:v4l2_device_unregister_subdev (&dev->sd);kfree (dev); -return ret; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 245/2077 staging: media: atomisp: fix loop shadowing in ia_css_stream_destroy()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jose A. Perez de Azpillaga <[email protected]>
[ Upstream commit 9087395a383212ab1beaefcbe3b57ed131c7823d ]
The nested loop inside the IS_ISP2401 block incorrectly uses the same variable 'i' as the outer loop. This shadows the outer loop variable and causes premature termination or skipped array elements.
Change the inner loop to use a new variable 'j' to prevent this.
--- drivers/staging/media/atomisp/pci/sh_css.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/staging/media/atomisp/pci/sh_css.c +4 -4
@@ -8192,7 +8192,7 @@ ia_css_stream_create(const struct ia_css_stream_config *stream_config,int ia_css_stream_destroy (struct ia_css_stream *stream) { -int i; +int i, j;int err =0 ;IA_CSS_ENTER_PRIVATE ("stream = %p" , stream);
@@ -8223,10 +8223,10 @@ ia_css_stream_destroy(struct ia_css_stream *stream) sp_pipeline_input_terminal = &sh_css_sp_group.pipe_io[sp_thread_id].input; -for (i =0 ; i <IA_CSS_STREAM_MAX_ISYS_STREAM_PER_CH ; i++) { +for (j =0 ; j <IA_CSS_STREAM_MAX_ISYS_STREAM_PER_CH ; j++) {ia_css_isys_stream_h isys_stream = - &sp_pipeline_input_terminal->context.virtual_input_system_stream[i]; -if (stream->config.isys_config[i].valid && isys_stream->valid) + &sp_pipeline_input_terminal->context.virtual_input_system_stream[j]; +if (stream->config.isys_config[j].valid && isys_stream->valid)ia_css_isys_stream_destroy (isys_stream); } }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 246/2077 riscv: dts: spacemit: set console baud rate on Milk-V Jupiter
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Aurelien Jarno <[email protected]>
[ Upstream commit 4f97acb4f744f516bbe976da8282c0fe213216ff ]
Because the default console's baud rate is not set, defconfig kernels do not have any serial output on this platform. Set the baud rate to 115200, matching what is used by U-Boot etc on this platform.
See-also: 24c12ca43b12c ("dts: spacemit: set console baud rate on bpif3")
--- arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts +1 -1
@@ -20,7 +20,7 @@ aliases { }; chosen { - stdout-path = "serial0"; + stdout-path = "serial0:115200n8"; }; leds {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 247/2077 riscv: dts: spacemit: fix uboot partition offset on Milk-V Jupiter
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Aurelien Jarno <[email protected]>
[ Upstream commit 6edd9a0d32e1ef81133b8cb5b3bb3157a44da4d1 ]
Correct the uboot partition node name to match its actual offset.
--- arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/riscv/boot/dts/spacemit/k1-milkv-jupiter.dts +1 -1
@@ -367,7 +367,7 @@ env@60000 { opensbi@70000 { reg = <0x70000 0x30000>; }; - uboot@a00000 { + uboot@a0000 { reg = <0xa0000 0x760000>; }; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 248/2077 firmware: smccc: Fix Arm SMCCC SOC_ID name call
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andre Przywara <[email protected]>
[ Upstream commit 70492cfce2a4d41e87bf46989028a90f4bc6b38f ]
Commit 5f9c23abc477 ("firmware: smccc: Support optional Arm SMCCC SOC_ID name") introduced the SOC_ID name string call, which reports a human readable string describing the SoC, as returned by firmware.
The SMCCC spec v1.6 describes this feature as AArch64 only, since we rely on 8 characters to be transmitted per register. Consequently the SMCCC call must use the AArch64 calling convention, which requires bit 30 of the FID to be set. The spec is a bit confusing here, since it mentions that in the parameter description ("2: SoC name (optionally implemented for SMC64 calls, ..."), but still prints the FID explicitly as 0x80000002.
But as this FID is using the SMC32 calling convention (correct for the other two calls), it will not match what any SMCCC conformant firmware is expecting, so any call would return NOT_SUPPORTED.
Add a 64-bit version of the ARCH_SOC_ID FID macro, and use that for the SoC name version of the call to fix the issue.
--- drivers/firmware/smccc/soc_id.c | 2 +- include/linux/arm-smccc.h | 5 +++++ 2 files changed, 6 insertions(+), 1 deletion(-)
drivers/firmware/smccc/soc_id.c +1 -1
@@ -60,7 +60,7 @@ static char __init *smccc_soc_name_init(void)* to the ARM_SMCCC_ARCH_SOC_ID function. Fetch it if * available. */ - args.a0 =ARM_SMCCC_ARCH_SOC_ID ; + args.a0 =ARM_SMCCC_ARCH_SOC_ID64 ; args.a1 =2 ;/* SOC_ID name */ arm_smccc_1_2_invoke (&args, &res);
include/linux/arm-smccc.h +5 -0
@@ -90,6 +90,11 @@ ARM_SMCCC_SMC_32, \ 0, 2) +#define ARM_SMCCC_ARCH_SOC_ID64 \ + ARM_SMCCC_CALL_VAL(ARM_SMCCC_FAST_CALL, \ + ARM_SMCCC_SMC_64, \ + 0, 2) +#define ARM_SMCCC_ARCH_WORKAROUND_1 \ ARM_SMCCC_CALL_VAL(ARM_SMCCC_FAST_CALL, \ ARM_SMCCC_SMC_32, \
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 249/2077 firmware: arm_scmi: Read sensor config as 32-bit value
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sudeep Holla <[email protected]>
[ Upstream commit f6fe7c3c007df18afd289ff2d98c692fae9ab085 ]
The SENSOR_CONFIG_GET response contains a 32-bit sensor_config field, and the xfer is initialized with a 4-byte RX buffer. Reading it with get_unaligned_le64() can consume bytes past the returned payload.
Use get_unaligned_le32() to match the protocol layout and the allocated response size.
--- drivers/firmware/arm_scmi/sensors.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/firmware/arm_scmi/sensors.c +1 -1
@@ -793,7 +793,7 @@ static int scmi_sensor_config_get(const struct scmi_protocol_handle *ph,if (!ret) {struct scmi_sensor_info *s = si->sensors + sensor_id; - *sensor_config =get_unaligned_le64 (t->rx.buf); + *sensor_config =get_unaligned_le32 (t->rx.buf); s->sensor_config = *sensor_config; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 250/2077 media: synopsys: Fix IPI using hardcoded datatype
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Guoniu Zhou <[email protected]>
[ Upstream commit 8ba166ff7c921da610376156d7c0a5fc985fa983 ]
The imx93_csi2rx_dphy_ipi_enable() function configures the IPI datatype using csi2->formats->csi_dt, which is initialized during probe but never updated in set_fmt(). This causes the IPI to always use the probe-time default datatype, ignoring the actual media bus format negotiated at runtime. When userspace requests a different format, the IPI hardware is configured with the wrong datatype, resulting in incorrect image output.
Fix by updating csi2->formats in the set_fmt callback to reflect the currently negotiated format, ensuring the IPI configuration matches the runtime datatype.
--- drivers/media/platform/synopsys/dw-mipi-csi2rx.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-)
drivers/media/platform/synopsys/dw-mipi-csi2rx.c +13 -2
@@ -311,7 +311,7 @@ dw_mipi_csi2rx_find_format(struct dw_mipi_csi2rx_device *csi2, u32 mbus_code)WARN_ON (csi2->formats_num ==0 );for (unsigned int i =0 ; i < csi2->formats_num; i++) { -const struct dw_mipi_csi2rx_format *format = &csi2->formats[i]; +const struct dw_mipi_csi2rx_format *format = &formats[i];if (format->code == mbus_code)return format;
@@ -433,7 +433,7 @@ dw_mipi_csi2rx_enum_mbus_code(struct v4l2_subdev *sd,if (code->index >= csi2->formats_num)return -EINVAL ; - code->code = csi2->formats[code->index].code; + code->code = formats[code->index].code;return 0 ;default :return -EINVAL ;
@@ -470,6 +470,17 @@ static int dw_mipi_csi2rx_set_fmt(struct v4l2_subdev *sd, *src = *sink; +/* Store the CSIS format descriptor for active formats. */ +if (format->which ==V4L2_SUBDEV_FORMAT_ACTIVE ) { + csi2->formats = fmt ? : +dw_mipi_csi2rx_find_format (csi2, default_format.code); + +if (!csi2->formats) { +dev_err (csi2->dev,"Failed to find valid format\n" ); +return -EINVAL ; + } + } +return 0 ; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 251/2077 sysfs: clamp show() return value in sysfs_kf_read()
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Greg Kroah-Hartman <[email protected]>
[ Upstream commit 454257f6d124a92342dcbb7710c03dd6ef96c731 ]
sysfs_kf_seq_show() defends against buggy show() callbacks that return larger than PAGE_SIZE by clamping the value and printing a warning. sysfs_kf_read(), the prealloc variant, has no such defense.
The only current in-tree user of __ATTR_PREALLOC is drivers/md/md.c, whose show() callbacks are well-behaved, so this is hardening against future drivers doing foolish things and out-of-tree code doing even more foolish things.
--- fs/sysfs/file.c | 4 ++++ 1 file changed, 4 insertions(+)
fs/sysfs/file.c +4 -0
@@ -120,6 +120,10 @@ static ssize_t sysfs_kf_read(struct kernfs_open_file *of, char *buf, len = ops->show (kobj, of->kn->priv, buf);if (len <0 )return len; +if (len >= (ssize_t )PAGE_SIZE ) { +printk ("fill_read_buffer: %pS returned bad count\n" , ops->show); + len =PAGE_SIZE -1 ; + }if (pos) {if (len <= pos)return 0 ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 252/2077 bitops: use common function parameter names
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Randy Dunlap <[email protected]>
[ Upstream commit 8a51b2e874f47a6094353b59ecae421f0968fe3a ]
Fix the function prototypes to use the common parameter name 'addr' instead of 'p' (common to arch-specific implementations of these functions).
This avoids the kernel-doc warnings:
Warning: include/asm-generic/bitops/lock.h:19 function parameter 'p'
not described in 'arch_test_and_set_bit_lock'
Warning: include/asm-generic/bitops/lock.h:41 function parameter 'p'
not described in 'arch_clear_bit_unlock'
Warning: include/asm-generic/bitops/lock.h:59 function parameter 'p'
not described in 'arch___clear_bit_unlock'
--- include/asm-generic/bitops/lock.h | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-)
include/asm-generic/bitops/lock.h +11 -11
@@ -16,16 +16,16 @@* It can be used to implement bit locks. */ static __always_inline int -arch_test_and_set_bit_lock (unsigned int nr,volatile unsigned long *p) +arch_test_and_set_bit_lock (unsigned int nr,volatile unsigned long *addr) {long old;unsigned long mask =BIT_MASK (nr); - p +=BIT_WORD (nr); -if (READ_ONCE (*p) & mask) + addr +=BIT_WORD (nr); +if (READ_ONCE (*addr) & mask)return 1 ; - old =raw_atomic_long_fetch_or_acquire (mask, (atomic_long_t *)p); + old =raw_atomic_long_fetch_or_acquire (mask, (atomic_long_t *)addr);return !!(old & mask); }
@@ -38,10 +38,10 @@ arch_test_and_set_bit_lock(unsigned int nr, volatile unsigned long *p)* This operation is atomic and provides release barrier semantics. */ static __always_inline void -arch_clear_bit_unlock (unsigned int nr,volatile unsigned long *p) +arch_clear_bit_unlock (unsigned int nr,volatile unsigned long *addr) { - p +=BIT_WORD (nr); -raw_atomic_long_fetch_andnot_release (BIT_MASK (nr), (atomic_long_t *)p); + addr +=BIT_WORD (nr); +raw_atomic_long_fetch_andnot_release (BIT_MASK (nr), (atomic_long_t *)addr); }/**
@@ -56,14 +56,14 @@ arch_clear_bit_unlock(unsigned int nr, volatile unsigned long *p)* See for example x86's implementation. */ static inline void -arch___clear_bit_unlock (unsigned int nr,volatile unsigned long *p) +arch___clear_bit_unlock (unsigned int nr,volatile unsigned long *addr) {unsigned long old; - p +=BIT_WORD (nr); - old =READ_ONCE (*p); + addr +=BIT_WORD (nr); + old =READ_ONCE (*addr); old &= ~BIT_MASK (nr); -raw_atomic_long_set_release ((atomic_long_t *)p, old); +raw_atomic_long_set_release ((atomic_long_t *)addr, old); }#ifndef arch_xor_unlock_is_negative_byte
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 253/2077 regulator: dt-bindings: mt6359: Drop regulator-name pattern restrictions
In reply to Greg Kroah-Hartman7.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chen-Yu Tsai <[email protected]>
[ Upstream commit cdc517688ffa2c30a64a20b558a9ecbf046c70f1 ]
The name of the regulator should match what the board design specifies for the power rail. There should be no limitations on what the name can be, and they definitely don't always follow the PMIC's own names.
Drop the restrictions on regulator-name.
--- .../bindings/regulator/mt6359-regulator.yaml | 43 ------------------- 1 file changed, 43 deletions(-)
Documentation/devicetree/bindings/regulator/mt6359-regulator.yaml +0 -43
@@ -18,84 +18,41 @@ patternProperties: "^buck_v(s1|gpu11|modem|pu|core|s2|pa|proc2|proc1|core_sshub)$": type: object $ref: regulator.yaml# - - properties: - regulator-name: - pattern: "^v(s1|gpu11|modem|pu|core|s2|pa|proc2|proc1|core_sshub)$" - unevaluatedProperties: false "^ldo_v(ibr|rf12|usb|camio|efuse|xo22)$": type: object $ref: regulator.yaml# - - properties: - regulator-name: - pattern: "^v(ibr|rf12|usb|camio|efuse|xo22)$" - unevaluatedProperties: false "^ldo_v(rfck|emc|a12|a09|ufs|bbck)$": type: object $ref: regulator.yaml# - - properties: - regulator-name: - pattern: "^v(rfck|emc|a12|a09|ufs|bbck)$" - unevaluatedProperties: false "^ldo_vcn(18|13|33_1_bt|13_1_wifi|33_2_bt|33_2_wifi)$": type: object $ref: regulator.yaml# - - properties: - regulator-name: - pattern: "^vcn(18|13|33_1_bt|13_1_wifi|33_2_bt|33_2_wifi)$" - unevaluatedProperties: false "^ldo_vsram_(proc2|others|md|proc1|others_sshub)$": type: object $ref: regulator.yaml# - - properties: - regulator-name: - pattern: "^vsram_(proc2|others|md|proc1|others_sshub)$" - unevaluatedProperties: false "^ldo_v(fe|bif|io)28$": type: object $ref: regulator.yaml# - - properties: - regulator-name: - pattern: "^v(fe|bif|io)28$" - unevaluatedProperties: false "^ldo_v(aud|io|aux|rf|m)18$": type: object $ref: regulator.yaml# - - properties: - regulator-name: - pattern: "^v(aud|io|aux|rf|m)18$" - unevaluatedProperties: false "^ldo_vsim[12]$": type: object $ref: regulator.yaml# - - properties: - regulator-name: - pattern: "^vsim[12]$" - - required: - - regulator-name - unevaluatedProperties: false additionalProperties: false
Signature · 1 line
2.53.0