Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: .
The bot has tested the following trees: v5.2.4, v5.1.21, v4.19.62, v4.14.134, v4.9.186, v4.4.186.
v5.2.4: Build OK!
v5.1.21: Build OK!
v4.19.62: Build OK!
v4.14.134: Failed to apply! Possible dependencies:
25a13e382de2 ("bluetooth: hci_qca: Replace GFP_ATOMIC with GFP_KERNEL")
v4.9.186: Failed to apply! Possible dependencies:
25a13e382de2 ("bluetooth: hci_qca: Replace GFP_ATOMIC with GFP_KERNEL")
v4.4.186: Failed to apply! Possible dependencies:
162f812f23ba ("Bluetooth: hci_uart: Add Marvell support")
25a13e382de2 ("bluetooth: hci_qca: Replace GFP_ATOMIC with GFP_KERNEL")
395174bb07c1 ("Bluetooth: hci_uart: Add Intel/AG6xx support")
9e69130c4efc ("Bluetooth: hci_uart: Add Nokia Protocol identifier")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
These patches include few backported fixes for the 4.4 stable
tree.
I would appreciate if you could kindly consider including them in the
next release.
Ajay
---
[PATCH 1/8]:
Backporting of upstream commit f958d7b528b1:
mm: make page ref count overflow check tighter and more explicit
[PATCH 2/8]:
Backporting of upstream commit 88b1a17dfc3e:
mm: add 'try_get_page()' helper function
[PATCH 3/8]:
Backporting of upstream commit 7aef4172c795:
mm: handle PTE-mapped tail pages in gerneric fast gup implementaiton
[PATCH 4/8]:
Backporting of upstream commit a3e328556d41:
mm, gup: remove broken VM_BUG_ON_PAGE compound check for hugepages
[PATCH 5/8]:
Backporting of upstream commit d63206ee32b6:
mm, gup: ensure real head page is ref-counted when using hugepages
[PATCH 6/8]:
Backporting of upstream commit 8fde12ca79af:
mm: prevent get_user_pages() from overflowing page refcount
[PATCH 7/8]:
Backporting of upstream commit 7bf2d1df8082:
pipe: add pipe_buf_get() helper
[PATCH 8/8]:
Backporting of upstream commit 15fab63e1e57:
fs: prevent page refcount overflow in pipe_buf_get
Hi,
Sunil Muthuswamy <sunilmut(a)microsoft.com> made some important fixes for
hv_sock recently. I and Sunil think it would be great to backport the
fixes to the longterm stable kernels.
Since hv_sock was firstly introduced in v4.14, we only care about
v4.14, v4.19 and v5.2.
For linux-5.2.y (currently it's v5.2.4), only one patch is missing.
The mainline commit ID is:
d5afa82c977e ("vsock: correct removal of socket from the list")
It can be cleanly cherry-picked from the mainline.
For linux-4.19.y (currently it's v4.19.62), 3 patches are missing.
The mainline commit IDs are:
cb359b604167 ("hvsock: fix epollout hang from race condition")
a9eeb998c28d ("hv_sock: Add support for delayed close")
d5afa82c977e ("vsock: correct removal of socket from the list")
They can be cleanly cherry-picked from the mainline, in the listed order here.
Note: it looks the first commit (cb359b604167) has been queued.
For linux-4.14.y (currently it's v4.14.134), 4 patches are missing.
The mainline commit IDs are:
cb359b604167 ("hvsock: fix epollout hang from race condition")
3b4477d2dcf2 ("VSOCK: use TCP state constants for sk_state")
a9eeb998c28d ("hv_sock: Add support for delayed close")
d5afa82c977e ("vsock: correct removal of socket from the list")
The third patch (a9eeb998c28d) needs small manual adjustments, and please
use the attached backported patch for it; the other 3 patches can be cleanly
cherry-picked from the mainline, in the listed order here.
Note: it looks the first commit (cb359b604167) has been queued.
Please let me know, if any clarification is needed.
Thanks!
-- Dexuan
On Thu, 1 Aug 2019 at 07:31, Sasha Levin <sashal(a)kernel.org> wrote:
>
> 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: v5.2.4, v5.1.21, v4.19.62, v4.14.134, v4.9.186, v4.4.186.
>
> v5.2.4: Build OK!
> v5.1.21: Build OK!
> v4.19.62: Failed to apply! Possible dependencies:
> 41a75cdde735 ("coresight: Convert driver messages to dev_dbg")
> 68a147752d04 ("coresight: etmx: Claim devices before use")
> e006d89abedd ("coresight: etm4x: Add support for handling errors")
> e2a1551a881f ("coresight: etm3: Add support for handling errors")
>
> v4.14.134: Failed to apply! Possible dependencies:
> 41a75cdde735 ("coresight: Convert driver messages to dev_dbg")
> 68a147752d04 ("coresight: etmx: Claim devices before use")
> e006d89abedd ("coresight: etm4x: Add support for handling errors")
> e2a1551a881f ("coresight: etm3: Add support for handling errors")
>
> v4.9.186: Failed to apply! Possible dependencies:
> 297ab90f15f6 ("coresight: tmc: Cleanup operation mode handling")
> 2cd541402829 ("coresight: tmc: minor fix for output log")
> 41a75cdde735 ("coresight: Convert driver messages to dev_dbg")
> 68a147752d04 ("coresight: etmx: Claim devices before use")
> c38e505e2701 ("coresight: tmc: Get rid of mode parameter for helper routines")
> e006d89abedd ("coresight: etm4x: Add support for handling errors")
> e2a1551a881f ("coresight: etm3: Add support for handling errors")
>
> v4.4.186: Failed to apply! Possible dependencies:
> 1925a470ce69 ("coresight: etm3x: splitting struct etm_drvdata")
> 2127154d115d ("coresight: etm3x: implementing user/kernel mode tracing")
> 22fd532eaa0c ("coresight: etm3x: adding operation mode for etm_enable()")
> 27b10da8fff2 ("coresight: etb10: moving to local atomic operations")
> 41a75cdde735 ("coresight: Convert driver messages to dev_dbg")
> 52210c8745e4 ("coresight: implementing 'cpu_id()' API")
> 68a147752d04 ("coresight: etmx: Claim devices before use")
> 882d5e112491 ("coresight: etm3x: implementing perf_enable/disable() API")
> b3e94405941e ("coresight: associating path with session rather than tracer")
> c04148e708c0 ("coresight: etm3x: moving sysFS entries to dedicated file")
> c1f8e57c9e66 ("coresight: etm3x: moving etm_readl/writel to header file")
> e2a1551a881f ("coresight: etm3: Add support for handling errors")
> e827d4550aa3 ("coresight: etb10: adding operation mode for sink->enable()")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
I have another one like that - will send a separate set that applies correctly.
Thanks for the consideration,
Mathieu
>
> --
> Thanks,
> Sasha
On 01/08/2019 14:31, Sasha Levin wrote:
> 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: v5.2.4, v5.1.21, v4.19.62, v4.14.134, v4.9.186, v4.4.186.
>
> v5.2.4: Build OK!
> v5.1.21: Build OK!
> v4.19.62: Build OK!
> v4.14.134: Failed to apply! Possible dependencies:
> 031e3601869c ("lib: Add generic PIO mapping method")
>
> v4.9.186: Failed to apply! Possible dependencies:
> 031e3601869c ("lib: Add generic PIO mapping method")
>
> v4.4.186: Failed to apply! Possible dependencies:
> 031e3601869c ("lib: Add generic PIO mapping method")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
>
Please only consider for v4.19.x, v5.1.x, and v5.2.x stable trees, same
for all patches in the patchset.
Thanks,
John
> --
> Thanks,
> Sasha
>
> .
>