** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905336
Title:
sha1_ce and sha2_ce modules no longer load on arm64
To
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905475
Title:
Fails to build on powerpc
To manage notifications
t; Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905475
Title:
Fails to buil
Public bug reported:
[Impact]
powerpc flavor powerpc64-emb fails to build with kernel 4.4.0-196.
[Test case]
Build the kernel with all powerpc flavors.
[Potential regression]
The kernel might still not boot. Userspace data might be corrupted when kernel
writes to it. Kernel might not read
** Also affects: linux-riscv (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux-riscv (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: linux-riscv (Ubuntu Groovy)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** C
** Summary changed:
- linux 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu
+ linux-riscv 5.8.0-9-generic (all 5.8 kernels) fail to boot in qemu
** Description changed:
- 5.8.0-9.11 and other v5.8 kernels all fail to boot in qemu with opensbi
- and qemu.
+ [Impact]
+ linux-riscv won't
changes.
[Regression Potential]
We could break changelogs, or the kernel preparation altogether.
** Affects: linux (Ubuntu)
Importance: Low
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Xenial)
Importance: Low
I think 512M for a 2GB system is a little too much to reserve. Can you
double check the details of that LUKS partition? Was it created during
an installation with a 2GB system? Or did you reduce the VM size after
installation?
Can you send the output of cryptsetup luksDump /dev/XXX?
Thanks.
http://lists.linux.it/pipermail/ltp/2020-October/019254.html
Sent a fix to LTP, waiting to hear from it.
The good thing is that I reproduced this by using clocksource=jiffies
when booting. And the test change fixed it.
Now I wonder what is the clocksource like at this AWS instance.
Cascardo.
Ah, I see now what is happening. The userspace code is dealing with
microseconds, while the syscalls all deal with nanoseconds.
So, when using absolute time, we read the clock (in nanoseconds), add
that to our microseconds value after converting (that is, rounding the
value), then set the timer,
The reading back of the timer seems relatively recent.
commit b34e243e85dde089dbb84dd6d63dc0fe95b4d504
Author: Viresh Kumar
Date: Wed Jul 8 16:01:04 2020 +0530
syscalls/timer_settime01: Make sure the timer fires
This patch improves the testcase by doing multiple things:
So, it looks like the latest version from the same ppa:cascardo/kdump2
should be working much better now, handling that specific situation from
a new install containing crashkernel=196M. I tested both upgrade paths
from older kdump-tools or new installs, and they are working fine
starting with
So, after some investigation, it looks like the zipl-installer d-i
component is responsible for creating /etc/zipl.conf with the default
crashkernel parameter with value 196M.
With that into consideration, one wonders how kdump-tools would
previously set its default value of "384M-:128M" in
There should be no difference between using di or the new installer,
unless there is something the installer is doing that is causing this.
If you remove the crashkernel line from zipl.conf and run dpkg-
reconfigure kdump-tools, it should add the new configuration value.
Otherwise, it will keep
Where does that 196 value come from? Was it present on zipl.conf after a
pristine install? I wouldn't expect that on a pristine Ubuntu 20.04.1
install, so we would need to investigate where that value comes from. I
know s390-tools itself used to add that crashkernel value there, but
that only
mp_irqdomain_activate from arch/x86/kernel/apic/io_apic.c will use the
chip_data that is set by the commit referred by Stefan ("XEN uses
irqdesc::irq_data_common::handler_data to store a per interrupt XEN data
pointer which contains XEN specific information.").
>From
If the user has not changed the value to something else, the size should
be increased after upgrade. If the user has changed, we keep the user's
value.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
nee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
UCT mentions commits 9060cb719e61b685ec0102574e10337fa5f445ea (specific
to AF_ALG) and ff7b11aa481f682e0e9711abfeb7d03f5cd612bf (all sockets).
The other commit we should care about is
6d8c50dcb029872b298eea68cc6209c866fd3e14 ("socket: close race condition
between sock_close() and
It seems that you *can* chown a socket, so this call just works fine. No
races with close needed. So, it seems to be a bogus assumption on the
part of the test.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So, the test is running with the newer definition as it is picked up
from linux-libc-dev. But the kernel (linux-oem-5.6, in this case)
doesn't know about it. So it fails.
However, any binaries out there would be using the old definition, which
the linux-oem-5.6 should accept just fine. I guess we
I pushed a version for focal on my ppa. It is based on the latest
version found on groovy, so there should be other changes besides the
one for setting a better default of crashkernel on /etc/zipl.conf.
It's at ppa:cascardo/kdump2. Note that if the user has changed the value
from the previous
** Description changed:
+ [Impact]
+ kmemcaches will fail to be created after they have just been removed but not
completely ripped out. This will cause some drivers (like lvm snapshots) to
properly work and cause kernel traces to go on the logs.
+
+ [Test case]
+ See comment #9.
+
+
After reverting commit 79ffe7107b13042c69c4a06394175362121b06b5
(upstream commit d38a2b7a9c939e6d7329ab92b96559ccebf7b135) ("mm:
memcg/slab: fix memory leak at non-root kmem_cache destroy"), things
seem to go back to normal.
The probable reason this one causes a problem is because it has:
@@
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/ppc64el/g/glibc/20200911_170104_5f83a@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/ppc64el/g/glibc/20200911_170104_5f83a@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
** Description changed:
- We need to run BPF filters to analyse and monitor network traffic. The
- BPF filters are created by skydive (http://skydive.network). Currently
- skydive fails to install BPF filters on s390x (using Ubuntu 18.04
- currently, soon moving to Ubuntu 20.04).
+ [Impact]
+
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888332
Title:
[Potential Regression] dscr_inherit_exec_test from powerpc in
** Description changed:
+ [Impact]
+ Code that touches DSCR user MSR does not set dscr_inherit, which breaks DSCR
restore doing context switches and inheritance when forking. DSCR is used to
control cache hinting. This is caused by lack of kernel interrupt when the DSCR
user MSR is written,
Apparently, cherry-picking 0828137e8f16721842468e33df0460044a0c588b
("powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()") fixes the issue.
Which explains why 5.8 does not show the problem.
Building a kernel with that patch applied so I can test it.
Cascardo.
--
You received this bug
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888332
Title:
[Potential Regression] dscr_inherit_exec_test from powerpc in
Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (
*** This bug is a duplicate of bug 1888332 ***
https://bugs.launchpad.net/bugs/1888332
Same thing as LP: #1888332. When writing to the privileged DSCR MSR
before running the remainder of the test, things will just work. This is
hinting again to dscr_inherit being unset when using the user
*** This bug is a duplicate of bug 1888332 ***
https://bugs.launchpad.net/bugs/1888332
Same issue as LP: #1888332. If we use DSCR privileged MSR when writing
in the tracee, it will set dscr_inherit, which will properly restore the
DSCR that is written by the tracer.
Cascardo.
** This bug
This test failure is caused by the kernel not setting dscr_inherit when
the user dscr MSR is written to. Which is caused by FSCR not raising a
facility unavailable interrupt. Which is ironic as one of the other
patches that is backported is 993e3d96fd08c3ebf7566e43be9b8cd622063e6d
("powerpc/64s:
** Changed in: linux (Ubuntu Eoan)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
YPE", flags: RDONLY|CLOEXEC) = 3
0.565 ( 0.003 ms): cat/2256 openat(dfd: CWD, filename: "/etc/passwd")
= 3
[Potential regression]
We might ship incompatible code with the running kernel. It might break
building such examples.
Or we might break the old contens
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu
Hi.
So if I understand correctly, this will be 18.04 userspace on top of a
20.04 kernel, that is, 5.4. I noticed 5.4 also lacks probe_read_user. I
will keep working on a backport of this to 5.4 kernel, then. Let me know
if there is anything else missing here.
Thanks.
Cascardo.
--
You received
https://aws.amazon.com/security/security-bulletins/AWS-2019-004/
According to Amazon advisory, fixes have been applied and "no customer
action is required at the Infrastructure level". Reading from other
sources [1], I can only conclude that Amazon has not provided the knobs
needed to do the
Now building on ppa:cascardo/ppa.
** Patch added: "Fix for groovy"
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1891565/+attachment/5401581/+files/oss4_4.2-build2010-5ubuntu7.debdiff
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
You received this bug
So, dot-symbols on powerpc are not a thing on userspace since a while
(from gcc 3.4 times). And, then, I realized this header comes directly
from alsa, and for a different reason, this same section has already
been dropped there. So applying the same changes makes sense here.
--
You received
Hi.
So, we clarified that some of the problems were not caused by the kernel
at all. The only thing missing is support to probe_read_kernel and
probe_read_user on 4.15 kernels. Is that needed for the offering?
If I didn't get it right, I am sorry. So, in order for us to meet your
expectations,
** Also affects: binutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891565
Title:
oss4 does not build on ppc64el on groovy
To manage
l, name, version) \
__asm__ (".symver " #real "," #name "@" #version)
** Affects: oss4 (Ubuntu)
Importance: Medium
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Changed in: oss4 (Ubuntu)
Assignee: (unassigned) =&
** Patch added: "Fix for groovy"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1884640/+attachment/5400792/+files/evdi_1.7.0+dfsg-1ubuntu1.debdiff
** Changed in: evdi (Ubuntu)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in:
** Description changed:
+ [Impact]
+ evdi-dkms won't build with later kernels than 5.5. In some cases (upstream
version 1.7.0), it won't build specifically on ppc64el. The fix includes a
missing header that is indirectly included on other arches.
+
+ [Test case]
+ Install the package with a
So, of course the patch is useless, as s390x uses zipl. I will work on
upgrade paths during this week, so we can allow upgrades to have the new
setting when the old setting is kept as is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Attached is a fix for s390x that is also built at my
ppa:cascardo/kdump2.
** Patch added: "Fix for groovy"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877533/+attachment/5398755/+files/makedumpfile_1.6.7-3ubuntu2.debdiff
--
You received this bug notification because you are a
I am going to work out on a change to the default crashkernel value on
s390x to match what we do for ppc64el. That will improve the situation
on default installations.
** Changed in: makedumpfile (Ubuntu Groovy)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Chan
Yep, and the commit that first fixes up these probe_read vs
probe_read_kernel/probe_read_user problems is:
6ae08ae3dea2cfa03dd3665a3c8475c2d429ef47 "bpf: Add probe_read_{user,
kernel} and probe_read_{user, kernel}_str helpers"
So, these helpers are not available until 5.5. We may consider this a
After some investigation, I found out that failures caused by "invalid
relo for insn[4].code 0x85" are due to a small typo in some headers.
That has caused LLVM to emit relocations (thinking those missing macro
calls were external function calls) that are not supported by the
loader. This is all
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Invalid
** Description changed:
- When net_prio and net_cls cgroups are used, cgroup refcount is bogus, as
- it's not incremented anymore, but decremented when sockets are closed.
+ [Impact]
+ When net_prio and net_cls cgroups
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linu
Reproducer is here.
https://launchpad.net/~cascardo/+archive/ubuntu/ppa/+sourcepub/11445138
/+listing-archive-extra
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886860
Title:
cgroup refcount is
Kleber has identified the backport of commit 692d7b5d1f91 ("tls: Fix
recvmsg() to be able to peek across multiple records") as the
responsible for this regression.
It turns out this commit has 4 fixups upstream, 3 of which can be easily
cherry picked, while the fourth one seems related to TLS 1.3
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
You received th
https://launchpad.net/~cascardo/+archive/ubuntu/ppa/+sourcepub/11419106
/+listing-archive-extra
So, this package on my ppa is built for bionic, but should work on other
series too.
It has a service that will call a wrapper that will start the reproducer
and reboot. The reason for the reboot is
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: Invalid
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Test kernels at https://people.canonical.com/~cascardo/lp1886668/.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886668
Title:
linux 4.15.0-109-generic network DoS regression vs -108
To manage
** Description changed:
[Impact]
On systems using cgroups and sockets extensively, like docker, kubernetes,
lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic.
[Fix]
Revert the patch that disables sk_alloc cgroup refcounting when tasks are
added to net_prio
Bugs are LP#1886860 and LP#1886859.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886668
Title:
linux 4.15.0-109-generic network DoS regression vs -108
To manage notifications about this bug go
** Description changed:
+ [Impact]
+ On systems using cgroups and sockets extensively, like docker, kubernetes,
lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic.
+
+ [Fix]
+ Revert the patch that disables sk_alloc cgroup refcounting when tasks are
added to net_prio
Public bug reported:
When net_prio is used without setting ifpriomap and BFP cgroup is used,
memory may be leaked. This was fixed by upstream commit
090e28b229af92dc5b40786ca673999d59e73056, but it had to be reverted to
fix LP #1886668.
When a real fix for this cgroup BFP crash lands, this patch
.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: Confirmed
** Affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
cts: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lim
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876982
Title:
tunnels over IPv6 are unencrypted when using IPsec
To
So, B-GCP-5.4 as well as F-GCP 5.4.0-1011 have RT_GROUP_SCHED on, and
that has been turned off by later versions, like F-GCP 5.4.0-1012 and
B-GCP-5.4 5.4.0-1016.
@cypressyew, can you confirm that it doesn't happen on such kernels?
Thanks.
Cascardo.
--
You received this bug notification because
@xnox, the unlock must happen for the root filesystem during dump,
independently from where it's going to dump to, though default
configuration is into local /var/crash/.
And even if the memory parameter is picked up depending on the system
size and crashkernel does that too, crashkernel takes
So, everything done was correct, aside from generating the initrd image.
The one at /boot/ is used for booting. For crashing, it's used the one
from /var/lib/kdump/. You should remove it and reload kdump:
rm /var/lib/kdump/initrd.img-`uname -r`
kdump-config reload
** Changed in: makedumpfile
de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Groovy)
Importance: Medium
Assignee: Thadeu Lima de Souza
So after some investigation on systemd failures on ppc64el triggered by
the kernel on eoan, I noticed some coredumps on processes when running
under qemu inside the ADT environment.
As one of these processes is sleep, I am pretty confident this is caused
by the lack of emulation or rather the
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885757
Title:
seccomp_bpf fails on powerpc
To manage notifications
.
[Regression potential]
We may break the test on different architectures. That doesn't break users,
though, as the changes are only on tests. It has been tested at least on
ppc64el and amd64.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Thadeu Lima de Souza Cascardo (cascardo
https://lore.kernel.org/linux-
kselftest/20200630164739.1268222-1-casca...@canonical.com/T/#u
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885757
Title:
seccomp_bpf fails on powerpc
To manage
*** This bug is a duplicate of bug 1872047 ***
https://bugs.launchpad.net/bugs/1872047
** This bug is no longer a duplicate of bug 1864073
seccomp_bpf fails Eoan 5.3 in ubuntu_kernel_selftests
** This bug has been marked a duplicate of bug 1872047
kselftest: seccomp kill_after_ptrace()
*** This bug is a duplicate of bug 1872047 ***
https://bugs.launchpad.net/bugs/1872047
** This bug has been marked a duplicate of bug 1872047
kselftest: seccomp kill_after_ptrace() timeout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Patch added: "fix for bionic"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/+attachment/5388335/+files/glibc_2.27-3ubuntu1.1.debdiff
** Description changed:
+ [Impact]
+ When tested against newer versions of linux, glibc tests will fail as it
makes some assumptions about
** Description changed:
-
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
- /autopkgtest-cosmic-canonical-kernel-team-
- bootstrap/cosmic/arm64/g/glibc/20180510_173125_32961@/log.gz
+ [Impact]
+ When tested against newer versions of linux, glibc tests
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => In
tu/+source/glibc/+bug/1853193/+attachment/5385113/+files/test-disable-copy_file_range-cross_device_failure.patch
** Changed in: glibc (Ubuntu Bionic)
Status: New => In Progress
** Changed in: glibc (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
urce/glibc/+bug/1770480/+attachment/5385112/+files/test-make-preadwritev2-invalid-flag-unsupported.patch
** Changed in: glibc (Ubuntu Bionic)
Status: New => In Progress
** Changed in: glibc (Ubuntu Bionic)
Assignee: Adam Conrad (adconrad) => Thadeu Lima de Souza Cascardo
(ca
When using a large directory with large names, I noticed a 50% increase
in the time it took to readdir the entire directory. With small names,
the increase did not seem noticeable enough. Tested on a VM with bionic,
no SMAP involved. Compared before memchr and after memchr. Need to
compare before
https://git.kernel.org/torvalds/c/065fcfd49763ec71ae345bb5c5a74f961031e70e
Applied to Torvalds' tree.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826848
Title:
ip_defrag.sh in net from
The test failure is intermittent, I have sent a suggested fix upstream,
will send it as SAUCE to the mailing list soon.
https://lore.kernel.org/linux-
kselftest/20200602183837.1540345-1-casca...@canonical.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I noticed that failure too, tested it manually on trusty amd64 with both
64-bit and 32-bit binary, and with 3.2 kernel, and it worked fine. I'll
try the whole suite on a precise VM and see if I can reproduce it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is a very old version, present in precise-updates, not the ESM
repo. I don't see us producing lowlatency kernels or meta packages on
ESM. Was that a different source package that produced those lowlatency
packages?
It looks to me this is not a regression, or even a problem at all. It
should
Confirmed this is a different source package on precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882012
Title:
Dependency issue for 3.2 linux-lowlatency meta package
To manage notifications
That speed comes from
drivers/net/ethernet/cisco/enic/enic_ethtool.c:enic_get_ksettings.
static int enic_get_ksettings(struct net_device *netdev,
struct ethtool_link_ksettings *ecmd)
{
struct enic *enic = netdev_priv(netdev);
struct
** Description changed:
- Test failed becuase:
-./ip_defrag: sendto overlap: 1400: Operation not permitted
+ [Impact]
+ Failure to run ip_defrag deterministically.
+
+ [Fix]
+ Use smaller packets and ignore EPERM.
+
+ [Test case]
+ Run the test multiple times without observing failures.
+
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz
[...]
03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop
objects [FAIL]
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Fix Released => In Progress
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
--
** Description changed:
- As it tries to calibrate how many samples will take more than 5 seconds
- to execute, it may end up picking up a number of samples that take 10
- (but up to 12) seconds. As the calibration will take double that time,
- it takes around 20 seconds. Then, it executes the
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Also affects: linux
For what matters, the alternative would probably to pick
fe60b0ce8e7335269722ec080173a9411a9d58a5. More exactly, all the
following commits:
41af3cf587f476f9a879b08219324c8b456e6a4c tracing/uprobe: Add multi-probe per
uprobe event support
60d53e2c3b75e79c83970fe73db79123d9462c7c tracing/probe:
..1 selftests: ftrace: ftracetest [FAIL]
** Changed in: linux (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
Bionic)
Importance: Low
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: kernel-sru-workflow
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
201 - 300 of 2328 matches
Mail list logo
