- Linux-stable-mirror - lists.linaro.org

Re: [PATCH v4 4/9] ACPI / hotplug / PCI: Do not scan all bridges when native PCIe hotplug is used

by Sasha Levin

Hi, [This is an automated email] This commit has been processed because it contains a -stable tag. The stable tag indicates that it's relevant for the following trees: all The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92, v4.4.126. v4.16: Build OK! v4.15.15: Build OK! v4.14.32: Failed to apply! Possible dependencies: 5a99e09ca3a1 ("ACPI / hotplug / PCI: Do not scan all bridges when native PCIe hotplug is used") v4.9.92: Failed to apply! Possible dependencies: 437eb7bf7b28 ("ACPI / hotplug / PCI: Make device_is_managed_by_native_pciehp() public") 5a99e09ca3a1 ("ACPI / hotplug / PCI: Do not scan all bridges when native PCIe hotplug is used") v4.4.126: Failed to apply! Possible dependencies: 437eb7bf7b28 ("ACPI / hotplug / PCI: Make device_is_managed_by_native_pciehp() public") 5a99e09ca3a1 ("ACPI / hotplug / PCI: Do not scan all bridges when native PCIe hotplug is used") Please let us know if you'd like to have this patch included in a stable tree. -- Thanks, Sasha

7 years, 2 months

1
0
0 0

Re: [PATCH v4 1/9] PCI: Take all bridges into account when calculating bus numbers for extension

by Sasha Levin

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 1c02ea810065 PCI: Distribute available buses to hotplug-capable bridges. The bot has also determined it's probably a bug fixing patch. (score: 93.5345) The bot has tested the following trees: v4.16, v4.15.15. v4.16: Build OK! v4.15.15: Build OK! -- Thanks, Sasha

7 years, 2 months

1
0
0 0

Re: [PATCH v4 3/9] PCI: pciehp: Clear Presence Detect and Data Link Layer Status Changed on resume

by Sasha Levin

Hi, [This is an automated email] This commit has been processed because it contains a -stable tag. The stable tag indicates that it's relevant for the following trees: all The bot has also determined it's probably a bug fixing patch. (score: 43.1022) The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92, v4.4.126. v4.16: Build OK! v4.15.15: Build OK! v4.14.32: Build OK! v4.9.92: Build OK! v4.4.126: Build OK! Please let us know if you'd like to have this patch included in a stable tree. -- Thanks, Sasha

7 years, 2 months

1
0
0 0

[PATCH 1/1] taging: fbtft: fix memory leak

by Xidong Wang

From: Xidong Wang <2711406067(a)qq.com> In function fbtft_framebuffer_alloc(), the memory allocated by framebuffer_alloc() is not released on the error path that txbuflen > 0 and txbuf, which holds the return value of devm_kzalloc(), is NULL. This will result in a memory leak bug. Signed-off-by: Xidong Wang <2711406067(a)qq.com> --- drivers/staging/fbtft/fbtft-core.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/staging/fbtft/fbtft-core.c b/drivers/staging/fbtft/fbtft-core.c index 0e36b66..e92771e 100644 --- a/drivers/staging/fbtft/fbtft-core.c +++ b/drivers/staging/fbtft/fbtft-core.c @@ -836,7 +836,7 @@ struct fb_info *fbtft_framebuffer_alloc(struct fbtft_display *display, if (txbuflen > 0) { txbuf = devm_kzalloc(par->info->device, txbuflen, GFP_KERNEL); if (!txbuf) - goto alloc_fail; + goto err_info; par->txbuf.buf = txbuf; par->txbuf.len = txbuflen; } @@ -872,6 +872,9 @@ struct fb_info *fbtft_framebuffer_alloc(struct fbtft_display *display, return info; +err_info: + framebuffer_release(info); + alloc_fail: vfree(vmem); -- 2.7.4

7 years, 2 months

3
2
0 0

[PATCH 1/1] taging: fbtft: fix memory leak

by Xidong Wang

From: Xidong Wang <2711406067(a)qq.com> In function fbtft_framebuffer_alloc(), the memory allocated by framebuffer_alloc() is not released on the error path that txbuflen > 0 and txbuf, which holds the return value of devm_kzalloc(), is NULL. This will result in a memory leak bug. Signed-off-by: Xidong Wang <2711406067(a)qq.com> --- drivers/staging/fbtft/fbtft-core.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/staging/fbtft/fbtft-core.c b/drivers/staging/fbtft/fbtft-core.c index 0e36b66..169e9dc 100644 --- a/drivers/staging/fbtft/fbtft-core.c +++ b/drivers/staging/fbtft/fbtft-core.c @@ -819,7 +819,7 @@ struct fb_info *fbtft_framebuffer_alloc(struct fbtft_display *display, if (par->gamma.curves && gamma) { if (fbtft_gamma_parse_str(par, par->gamma.curves, gamma, strlen(gamma))) - goto alloc_fail; + goto err_info; } /* Transmit buffer */ @@ -872,6 +872,9 @@ struct fb_info *fbtft_framebuffer_alloc(struct fbtft_display *display, return info; +err_info: + framebuffer_release(info); + alloc_fail: vfree(vmem); -- 2.7.4

7 years, 2 months

4
3
0 0

Re: [PATCH net v6 4/4] ipv6: udp: set dst cache for a connected sk if current not valid

by Sasha Levin

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 33c162a980fe ipv6: datagram: Update dst cache of a connected datagram sk during pmtu update. The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92. v4.16: Failed to apply! Possible dependencies: 96818159c3c0 ("ipv6: allow to cache dst for a connected sk in ip6_sk_dst_lookup_flow()") v4.15.15: Failed to apply! Possible dependencies: 96818159c3c0 ("ipv6: allow to cache dst for a connected sk in ip6_sk_dst_lookup_flow()") v4.14.32: Failed to apply! Possible dependencies: 96818159c3c0 ("ipv6: allow to cache dst for a connected sk in ip6_sk_dst_lookup_flow()") v4.9.92: Failed to apply! Possible dependencies: 96818159c3c0 ("ipv6: allow to cache dst for a connected sk in ip6_sk_dst_lookup_flow()") -- Thanks, Sasha

7 years, 2 months

1
0
0 0

Re: Re: general protection fault in __mem_cgroup_free

by Sasha Levin

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 00f3ca2c2d66 mm: memcontrol: per-lruvec stats infrastructure. The bot has also determined it's probably a bug fixing patch. (score: 37.8569) The bot has tested the following trees: v4.16, v4.15.15, v4.14.32. v4.16: Build OK! v4.15.15: Failed to apply! Possible dependencies: a983b5ebee57 ("mm: memcontrol: fix excessive complexity in memory.stat reporting") v4.14.32: Failed to apply! Possible dependencies: a983b5ebee57 ("mm: memcontrol: fix excessive complexity in memory.stat reporting") -- Thanks, Sasha

7 years, 2 months

1
0
0 0

[PATCH] drm/sti: Depend on OF rather than selecting it

by Oliver O'Halloran

Commit cc6b741c6f63 ("drm: sti: remove useless fields from vtg structure") reworked some code inside of this driver and made it select CONFIG_OF. This results in the entire OF layer being enabled when building an allmodconfig on ia64. OF on ia64 is completely unsupported so this isn't a great state of affairs. The 0day robot noticed a link-time failure on ia64 caused by using of_node_to_nid() in an otherwise unrelated driver. The generic fallback for of_node_to_nid() only exists when: defined(CONFIG_OF) && defined(CONFIG_NUMA) == false Since CONFIG_NUMA is usually selected for IA64 we get the link failure. Fix this by making the driver depend on OF rather than selecting it, odds are that was the original intent. Link: https://lists.01.org/pipermail/kbuild-all/2018-March/045172.html Fixes: cc6b741c6f63 ("drm: sti: remove useless fields from vtg structure") Cc: Benjamin Gaignard <benjamin.gaignard(a)linaro.org> Cc: Vincent Abriou <vincent.abriou(a)st.com> Cc: David Airlie <airlied(a)linux.ie> Cc: dri-devel(a)lists.freedesktop.org Cc: linux-ia64(a)vger.kernel.org Cc: stable(a)vger.kernel.org Signed-off-by: Oliver O'Halloran <oohall(a)gmail.com> --- Cc`ed to stable since the ia64 guys might want it backported. I'm not bothered if it just goes into mainline. --- drivers/gpu/drm/sti/Kconfig | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpu/drm/sti/Kconfig b/drivers/gpu/drm/sti/Kconfig index cca4b3c9aeb5..1963cc1b1cc5 100644 --- a/drivers/gpu/drm/sti/Kconfig +++ b/drivers/gpu/drm/sti/Kconfig @@ -1,6 +1,6 @@ config DRM_STI tristate "DRM Support for STMicroelectronics SoC stiH4xx Series" - depends on DRM && (ARCH_STI || ARCH_MULTIPLATFORM) + depends on OF && DRM && (ARCH_STI || ARCH_MULTIPLATFORM) select RESET_CONTROLLER select DRM_KMS_HELPER select DRM_GEM_CMA_HELPER @@ -8,6 +8,5 @@ config DRM_STI select DRM_PANEL select FW_LOADER select SND_SOC_HDMI_CODEC if SND_SOC - select OF help Choose this option to enable DRM on STM stiH4xx chipset -- 2.9.5

7 years, 2 months

4
3
0 0

[PATCH 0/6] nfit, address-range-scrub: rework and fixes

by Dan Williams

Given the fact that ARS can take 10s to 100s of seconds it is not feasible to wait for ARS completion before publishing persistent memory namespaces. Instead convert the ARS implementation to perform a short ARS for critical errors, ones that caused a previous system reset, before registering namespaces. Finally, arrange for all long ARS operations to run in the background and populate the badblock lists at run time. While developing this rework a handful of cleanups and fixes also fell out. --- Dan Williams (6): nfit: fix region registration vs block-data-window ranges nfit, address-range-scrub: fix scrub in-progress reporting libnvdimm: add an api to cast a 'struct nd_region' to its 'struct device' nfit, address-range-scrub: introduce nfit_spa->ars_state nfit, address-range-scrub: rework and simplify ARS state machine nfit, address-range-scrub: add module option to skip initial ars drivers/acpi/nfit/core.c | 443 ++++++++++++++++++------------------------ drivers/acpi/nfit/nfit.h | 13 + drivers/nvdimm/nd.h | 1 drivers/nvdimm/region_devs.c | 8 + include/linux/libnvdimm.h | 1 5 files changed, 213 insertions(+), 253 deletions(-)

7 years, 2 months

3
6
0 0

Re: [PATCH net] net: dsa: b53: Fix sparse warnings in b53_mmap.c

by Sasha Levin

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 967dd82ffc52 net: dsa: b53: Add support for Broadcom RoboSwitch. The bot has also determined it's probably a bug fixing patch. (score: 8.8847) The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92. v4.16: Build OK! v4.15.15: Build OK! v4.14.32: Build OK! v4.9.92: Build OK! -- Thanks, Sasha

7 years, 2 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror