April 2018 - Linux-stable-mirror

Re: [PATCH RESEND v4 2/9] PCI: Take bridge window alignment into account when distributing resources

by Sasha Levin

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

6 years, 9 months

1
0
0 0

Re: [PATCH RESEND 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

6 years, 9 months

1
0
0 0

Re: [PATCH RESEND 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

6 years, 9 months

1
0
0 0

Re: [PATCH v4 2/9] PCI: Take bridge window alignment into account when distributing resources

by Sasha Levin

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

6 years, 9 months

1
0
0 0

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

6 years, 9 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

6 years, 9 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

6 years, 9 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

6 years, 9 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

6 years, 9 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

6 years, 9 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror April 2018