Is it possible (pun intended) to compromise on
`CONFIG_SQUASHFS_DECOMP_MULTI` (which uses num_online_cpus) instead of
`CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU` (which uses `num_possible_cpus`)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
The log message[1] says that this issues is under investigation:
> For the moment turn it off while it can be investigated.
Did we find the root cause? Seems like Debian is successfully uses it nowadays:
```
tar -xOzf linux_5.10.19-1.debian.tar.xz ./debian/config/config | fgrep
CONFIG_SQUASHFS_D
Sadly, we've already workedaround that problem with a custom-built
module. Let me see if my colleagues can test the kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1708604
Title:
** Description changed:
- 4.10 kernel is commonly used for test BBR Congestion Control
- deployments.
+ 4.10 kernel is commonly used to test BBR Congestion Control deployments.
- Recent 4.13 release had a bunch of fixes for the initial BBR release, namely:
+ Recent net-next pull in 4.13-rc1 had
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1708604
Title:
Backport recent bbr bugfixes to 4.10 kernel
Status in li
Public bug reported:
4.10 kernel is commonly used for test BBR Congestion Control
deployments.
Recent 4.13 release had a bunch of fixes for the initial BBR release, namely:
4aea287e90dd61a48268ff2994b56f9799441b62 tcp_bbr: cut pacing rate only if
filled pipe
f19fd62dafaf1ed6cf615dba655b82fa9df59
6 matches
Mail list logo
