[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])
I've made some good progress here. I found that older version like 4.19 work, so I ran git bisect. I'm still doing the final check, but it looks like the series that causes the issue is the one containing these: d53d2f78cead bpf: Use vmalloc special flag 1a7b7d922081 modules: Use vmalloc special flag 868b104d7379 mm/vmalloc: Add flag for freeing of special permsissions In particular: commit 868b104d7379e28013e9d48bdd2db25e0bdcf751 (HEAD) Author: Rick Edgecombe Date: Thu Apr 25 17:11:36 2019 -0700 mm/vmalloc: Add flag for freeing of special permsissions Add a new flag VM_FLUSH_RESET_PERMS, for enabling vfree operations to immediately clear executable TLB entries before freeing pages, and handle resetting permissions on the directmap. This flag is useful for any kind of memory with elevated permissions, or where there can be related permissions changes on the directmap. Today this is RO+X and RO memory. Although this enables directly vfreeing non-writeable memory now, non-writable memory cannot be freed in an interrupt because the allocation itself is used as a node on deferred free list. So when RO memory needs to be freed in an interrupt the code doing the vfree needs to have its own work queue, as was the case before the deferred vfree list was added to vmalloc. For architectures with set_direct_map_ implementations this whole operation can be done with one TLB flush when centralized like this. For others with directmap permissions, currently only arm64, a backup method using set_memory functions is used to reset the directmap. When arm64 adds set_direct_map_ functions, this backup can be removed. When the TLB is flushed to both remove TLB entries for the vmalloc range mapping and the direct map permissions, the lazy purge operation could be done to try to save a TLB flush later. However today vm_unmap_aliases could flush a TLB range that does not include the directmap. So a helper is added with extra parameters that can allow both the vmalloc address and the direct mapping to be flushed during this operation. The behavior of the normal vm_unmap_aliases function is unchanged. and commit d53d2f78ceadba081fc7785570798c3c8d50a718 Author: Rick Edgecombe Date: Thu Apr 25 17:11:38 2019 -0700 bpf: Use vmalloc special flag Use new flag VM_FLUSH_RESET_PERMS for handling freeing of special permissioned memory in vmalloc and remove places where memory was set RW before freeing which is no longer needed. Don't track if the memory is RO anymore because it is now tracked in vmalloc. This is _extremely_ in "subtly break under the hash MMU" areas. Hopefully this is enough to get some Power MMU experts to weigh in. I will keep working on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])
I can repro on upstream, all the way back to 5.4.0. It might have existed before that - I haven't tested any earlier yet. Was the test methodology changed just before this was found? I'm just wondering why it suddenly appeared ~a year after Focal was released. I thought it might have been a patch picked up for a SRU, but it's looking like the problem predates Focal by some way... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])
I can repro this with the latest Focal kernel on: description: PowerNV product: 8247-22L (IBM Power System S822L) Trying to see if I can repro it upstream. FWIW my opening hypothesis is that something in a percpu data structure isn't getting updated over hotplug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
I cannot yet explain this, but after bisecting the config, I can repro this with pseries_le_defconfig + CONFIG_RCU_SCALE_TEST=m That's weird to me, and I'll continue to investigate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871451] Re: powerpc segfault on exponential of negative in python
Hi, I tested this on a real ppc64le machine: root@1325f5985861:/# python3 -c "import math; print(math.exp(-1))" 0.36787944117144233 root@1325f5985861:/# uname -a Linux 1325f5985861 5.4.0-21-generic #25+lp1866909v202004031128-Ubuntu SMP Fri Apr 3 18:38:30 UTC 202 ppc64le ppc64le ppc64le GNU/Linux It looks like it's a qemu bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871451 Title: powerpc segfault on exponential of negative in python To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1871451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter
The 5.3.0 HWE kernel also works, which means we now have a good workaround while we debug things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863044 Title: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter
Hi Mauricio, 5.4.0-14 works for me, dmesg attached. I'll see if an HWE kernel supplied in the bionic repositories also works, maybe we can use that in the mean time so we don't fall any further behind on kernel updates while we debug this. Regards, Daniel ** Attachment added: "dmesg-5.4.0-14-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5329404/+files/dmesg-5.4.0-14-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863044 Title: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter
Ah, I was just about to tell you that I have just tried master-next at a59858e18bc8996f8c96d307a33e504b079dc541 ! I think that is the same sha that ended up being tagged as -89, so I think it provides us with the same information. Sadly -89 also doesn't seem to work; dmesg attached. I don't know anything about the qla2xxx driver, so I was planning to confirm that the problem was introduced by the set of qla2xxx changes that went into -73 and then bisect them. But, if you have any insight or specific knowledge that would suggest a better path, I'm very happy to give that a go. Regards, Daniel ** Attachment added: "dmesg-89" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5329273/+files/dmesg-89 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863044 Title: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter
Hi Mauricio, Thanks for the prompt answer! After a lot of messing around to get a remote console, I can finally test. It looks like -88 doesn't work. I'm attaching a dmesg from -88 and -72. I will build and test master-next next. Regards, Daniel ** Attachment added: "dmesg from -88" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5329132/+files/dmesg-88 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863044 Title: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter
** Attachment added: "dmesg from -72" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5329133/+files/dmesg-72 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863044 Title: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5327820/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863044 Title: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863044] [NEW] qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter
Public bug reported: We have an IBM BladeCentre Hx5 with a number of blades running Ubuntu 18.04.3. Storage is attached over Fiber Channel. They all boot fine with 4.15.0-72 - the qla2xxx detects all the LUNs. On 4.15.0-74 and 4.15.0-76, the qla2xxx driver loads but the LUNs are not detected. This breaks the boot. rescan-scsi-bus.sh is also unable to find the LUNs. Reverting to the 4.15.0-72 kernel works. lspci reports: 06:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA Flags: bus master, fast devsel, latency 0, IRQ 24, NUMA node 0 I/O ports at 2c00 [size=256] Memory at 903fc000 (64-bit, non-prefetchable) [size=16K] Expansion ROM at 9030 [disabled] [size=256K] Capabilities: [44] Power Management version 3 Capabilities: [4c] Express Endpoint, MSI 00 Capabilities: [88] MSI: Enable- Count=1/32 Maskable- 64bit+ Capabilities: [98] Vital Product Data Capabilities: [a0] MSI-X: Enable+ Count=2 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [138] Power Budgeting Kernel driver in use: qla2xxx Kernel modules: qla2xxx Let me know if you need any more details. I attach a version.log and lspci-vnvn.log from a working -72 boot. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1863044/+attachment/5327819/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863044 Title: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853142] Re: CVE-2019-18660: patches for Ubuntu
My colleague has verified all 4 versions. In all cases, on supported hardware, the test now operates as expected: the secret does not leak unless the mitigation is manually turned off. I notice the SRU verification is happening a bit sooner than I expected - when do you expect these kernels to be released? ** Tags removed: verification-needed-bionic verification-needed-disco verification-needed-eoan verification-needed-xenial ** Tags added: verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853142 Title: CVE-2019-18660: patches for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853142] Re: CVE-2019-18660: patches for Ubuntu
The embargo has expired so I'm making this public now. ** Description changed: Hi, Recently you would have been notified about CVE-2019-18660 via email to the linux-distros private mailing list. In short, it is a bug in the Spectre v2 class affecting powerpc. We have developed some backports for supported Ubuntu kernels, and tested them in our lab. I will attach the patches shortly. Most of them should end up being identical to the versions in linux-stable, but the ones for Bionic are slightly different due to it using a 4.15 kernel. Please get in touch with me or Michael Ellerman (powerpc maintainer) if you have any questions or if we can be of any assistance. - If I understand the SRU cycles correctly, we've missed the current one - due for release on 2 December, so the earliest these patches could land - in is the kernel nominally slated to be released ~23 December. Are you - planning to still release a kernel then, or are your cycles going to - change over the end of year period? - - (If it helps, we've got some automation set up so we're able to do the - regression testing of -proposed kernels with these patches quickly.) Kind regards, Daniel ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853142 Title: CVE-2019-18660: patches for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)
Hi Michael R, I tried to apply your patches to test them and support the effort to get them included in the Bionic kernel, but I'm having some trouble applying them: ubuntu@dja-bionic:~/bionic$ git am ../patches/01-powerpc-64s-add-support-for-ori-barrier_nospec.patch Patch format detection failed. ubuntu@dja-bionic:~/bionic$ git am ../patches/01-powerpc-64s-add-support-for-ori-barrier_nospec.patch --patch-format mbox Applying: commit 2eea7f067f495e33b8b116b35b5988ab2b8aec55 fatal: empty ident name (for <>) not allowed How are you generating them? They don't look like they've been generated with git format-patch...? Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822870 Title: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
OK, so with the magic of debug symbols and gdb on Cosmic:
(gdb) run
...
ens8: Gained IPv6LL
Assertion 'link->state == LINK_STATE_SETTING_ADDRESSES' failed at
../src/network/networkd-link.c:803, function link_enter_set_routes(). Aborting.
...
(gdb) up
#3 0x5566b194 in link_enter_set_routes (link=0x5571d050) at
../src/network/networkd-link.c:803
803 ../src/network/networkd-link.c: No such file or directory.
(gdb) p link->state
$3 = LINK_STATE_PENDING
Looking at the code, it seems we are hitting link_enter_set_routes()
before link_enter_set_addresses() which is where the state is set. We're
hitting link_enter_set_routes() because link_check_ready() now calls it
straight off the bat.
I think the backport just needs to add a check to not flow through to
setting the routes until after we've gone through the process of setting
the addresses; we can do that with the attached patch. (It applies to
the cosmic version, I haven't tested it against Bionic.)
Having said that Dan you've obviously had a closer look at the code and more
recently, what patches did you think were needed? It looks like perhaps you
could solve this by backporting c42ff3a1a7bf ("networkd: Track address
configuration")
and 289e6774d0da ("networkd: Use only a generic CONFIGURING state") - is that
what you had in mind?
** Patch added:
"0001-Do-not-call-link_enter_set_routes-until-LINK_STATE_S.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+attachment/5243670/+files/0001-Do-not-call-link_enter_set_routes-until-LINK_STATE_S.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818340
Title:
systemd-networkd core dumps in bionic-proposed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
Never mind, I can reproduce on Cosmic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818340 Title: systemd-networkd core dumps in bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
Oof, sorry! It's not clear to me from the bug report and subsequent comments - is it just Bionic that's affected, or is it also Cosmic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818340 Title: systemd-networkd core dumps in bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793901] Re: kernel oops in bcache module
** Description changed:
+ SRU Justification
+ =
+
+ [Impact]
+
+ Some users see panics like the following when performing fstrim on a
+ bcached volume:
+
+ [ 529.803060] BUG: unable to handle kernel NULL pointer dereference at
0008
+ [ 530.183928] #PF error: [normal kernel read fault]
+ [ 530.412392] PGD 801f42163067 P4D 801f42163067 PUD 1f42168067 PMD 0
+ [ 530.750887] Oops: [#1] SMP PTI
+ [ 530.920869] CPU: 10 PID: 4167 Comm: fstrim Kdump: loaded Not tainted
5.0.0-rc1+ #3
+ [ 531.290204] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9,
BIOS P89 12/27/2015
+ [ 531.693137] RIP: 0010:blk_queue_split+0x148/0x620
+ [ 531.922205] Code: 60 38 89 55 a0 45 31 db 45 31 f6 45 31 c9 31 ff 89 4d 98
85 db 0f 84 7f 04 00 00 44 8b 6d 98 4c 89 ee 48 c1 e6 04 49 03 70 78 <8b> 46 08
44 8b 56 0c 48
+ 8b 16 44 29 e0 39 d8 48 89 55 a8 0f 47 c3
+ [ 532.838634] RSP: 0018:b9b708df39b0 EFLAGS: 00010246
+ [ 533.093571] RAX: RBX: 00046000 RCX:
+ [ 533.441865] RDX: 0200 RSI: RDI:
+ [ 533.789922] RBP: b9b708df3a48 R08: 940d3b3fdd20 R09:
+ [ 534.137512] R10: b9b708df3958 R11: R12:
+ [ 534.485329] R13: R14: R15:
940d39212020
+ [ 534.833319] FS: 7efec26e3840() GS:940d1f48()
knlGS:
+ [ 535.224098] CS: 0010 DS: ES: CR0: 80050033
+ [ 535.504318] CR2: 0008 CR3: 001f4e256004 CR4:
001606e0
+ [ 535.851759] Call Trace:
+ [ 535.970308] ? mempool_alloc_slab+0x15/0x20
+ [ 536.174152] ? bch_data_insert+0x42/0xd0 [bcache]
+ [ 536.403399] blk_mq_make_request+0x97/0x4f0
+ [ 536.607036] generic_make_request+0x1e2/0x410
+ [ 536.819164] submit_bio+0x73/0x150
+ [ 536.980168] ? submit_bio+0x73/0x150
+ [ 537.149731] ? bio_associate_blkg_from_css+0x3b/0x60
+ [ 537.391595] ? _cond_resched+0x1a/0x50
+ [ 537.573774] submit_bio_wait+0x59/0x90
+ [ 537.756105] blkdev_issue_discard+0x80/0xd0
+ [ 537.959590] ext4_trim_fs+0x4a9/0x9e0
+ [ 538.137636] ? ext4_trim_fs+0x4a9/0x9e0
+ [ 538.324087] ext4_ioctl+0xea4/0x1530
+ [ 538.497712] ? _copy_to_user+0x2a/0x40
+ [ 538.679632] do_vfs_ioctl+0xa6/0x600
+ [ 538.853127] ? __do_sys_newfstat+0x44/0x70
+ [ 539.051951] ksys_ioctl+0x6d/0x80
+ [ 539.212785] __x64_sys_ioctl+0x1a/0x20
+ [ 539.394918] do_syscall_64+0x5a/0x110
+ [ 539.568674] entry_SYSCALL_64_after_hwframe+0x44/0xa9
+
+ [Fix]
+
+ Under certain conditions, the test for whether an operation should be
+ written back to the underlying device was incorrect. Specifically, in
+ should_writeback(), we were hitting a case where an optimisation for
+ partial stripe conditions was returning true and so should_writeback()
+ was returning true early. This caused the code to go down an incorrect
+ path and create bios that contained NULL pointers.
+
+ To fix this issue, make sure that should_writeback() on a discard op
+ never returns true.
+
+
+ [Test Case]
+
+ We have observed it on some systems where both:
+ 1) LVM/devmapper is involved (bcache backing device is LVM volume) and
+ 2) writeback cache is involved (bcache cache_mode is writeback)
+
+ Not every machine exhibits the bug. On one machine that does exhibit the
+ bug, we can reliably reproduce it with:
+
+ # echo writeback > /sys/block/bcache0/bcache/cache_mode
+ # mount /dev/bcache0 /test
+ # for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd if=/dev/zero
of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test
+
+
+ [Regression Potential]
+
+ This could affect any device where bcache is used.
+
+ In mitigation, however: the patch is simple, is limited to considering
+ discard operations. The patch has been accepted upstream [1] and the
+ maintainer will be including it in SuSE kernels [2]. A Gentoo user
+ validated the upstream patch independently [3].
+
+
+ [1] https://www.spinics.net/lists/linux-bcache/msg06997.html
+ [2] https://www.spinics.net/lists/linux-bcache/msg06998.html
+ [3] https://bugzilla.kernel.org/show_bug.cgi?id=196103#c3
+
+
+ [Original Description]
+
This was on an 18.04.1 install running the 4.15-34 generic kernel image,
running from a normal ext4 root device.
I had just a short while before created a new bcache device that was mounted
but to which no data had been written yet. Then without any apparent particular
reason, an apport error popped up to inform of a bcache kernel oops. Crash log
was uploaded but no idea how to link it, so I attach it as well.
Mostly I would like to know how concerned I should be as after a previous,
successful test I wanted to move the whole install to bcache. Ideally, if this
is a bug or similar, it would be nice if it could get fixed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-34-generic
[Bug 1750392] Re: nplan cannot enable IPv6 privacy extensions
** Changed in: nplan (Ubuntu) Assignee: Daniel Axtens (daxtens) => (unassigned) ** Changed in: nplan (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750392 Title: nplan cannot enable IPv6 privacy extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1750392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802421] Re: Xenial: data corruption when using i40e with iommu
The user has verified that the -proposed kernel resolves their issue. Regards, Daniel ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802421 Title: Xenial: data corruption when using i40e with iommu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812760] Re: networkd: [Route] PreferredSource not working in *.network files
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812760 Title: networkd: [Route] PreferredSource not working in *.network files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812760] [NEW] networkd: [Route] PreferredSource not working in *.network files
Public bug reported: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the configuration of obscure network setups. The backport requires pulling in two further commits that also change behaviour: currently systemd deletes all addresses and routes that were attached to an interface. With this change, it will only delete those that are not specified in the configuration files. I do not know how this could cause issues - it moves from a surprising behaviour to a less surprising behaviour, but it's worth pointing out. ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Daniel Axtens (daxtens) Status: In Progress ** Changed in: systemd (Ubuntu) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Daniel Axtens (daxtens) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812760 Title: networkd: [Route] PreferredSource not working in *.network files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805245] Re: powerpc/powernv/pci: Work around races in PCI bridge enabling
The OpenPower partner reports that their system is fixed with this kernel. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805245 Title: powerpc/powernv/pci: Work around races in PCI bridge enabling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812667] [NEW] Can't verify some ssl certificates (e.g. imap.gmail.com)
Public bug reported: Hi, I just upgraded to cosmic and have hit the issue described in debian bug #9065955 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906955 - mbsync won't connect to e.g. gmail because of SSL errors. I downloaded 1.3.0-2 from Debian and it works. Would it be possible to backport the fix to Cosmic please? Bionic is unaffected. Regards, Daniel ** Affects: isync (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/1812667 Title: Can't verify some ssl certificates (e.g. imap.gmail.com) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isync/+bug/1812667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793901] Re: kernel oops in bcache module
Hi, I have a patch which I believe fixes your issue: https://www.spinics.net/lists/linux-bcache/msg06997.html It looks like it will go in to the 5.1 kernel, and I will propose it for backporting to earlier Ubuntu kernels. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793901 Title: kernel oops in bcache module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810372] Re: Infinite busy-loop trying to cull when cache space is short
Hi, Thanks Eric. I specifically tested the version from Trusty: 0.10.5-1ubuntu0.14.04.1. I tested it by enabling cachefilesd and using dd to get the disk to about 95% full. With 0.10.5-1, starting cachefilesd with a full disk caused the process to spin at 100% cpu usage. With the version from proposed, CPU usage was down to normal negligible levels. The other user did a similar test with the Xenial version 0.10.5-1ubuntu0.16.04.1 and had similar results: the version in -proposed does not max out a CPU core when the disk is full. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810372 Title: Infinite busy-loop trying to cull when cache space is short To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/1810372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810372] Re: Infinite busy-loop trying to cull when cache space is short
User has verified the Xenial version. I have verified the Trusty version. Regards, Daniel ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810372 Title: Infinite busy-loop trying to cull when cache space is short To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/1810372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810372] Re: Infinite busy-loop trying to cull when cache space is short
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810372 Title: Infinite busy-loop trying to cull when cache space is short To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/1810372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793901] Re: kernel oops in bcache module
I think I have discovered the cause: https://lore.kernel.org/linux- block/87h8e9ii2l@linkitivity.dja.id.au/ ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793901 Title: kernel oops in bcache module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810372] Re: Infinite busy-loop trying to cull when cache space is short
The full .diff.tar.gz is attached. ** Attachment added: "cachefilesd_0.10.5-1ubuntu1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/1810372/+attachment/5227284/+files/cachefilesd_0.10.5-1ubuntu1.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810372 Title: Infinite busy-loop trying to cull when cache space is short To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/1810372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810372] Re: Infinite busy-loop trying to cull when cache space is short
It turns out the package uses the cdbs system rather than quilt, so providing a debdiff is a bit tricky. Here's the patch that I applied, the result is at https://launchpad.net/~daxtens/+archive/ubuntu/builder/+build/16226405 and it works on my test system, and I am asking the original reporter to verify it as well. ** Patch added: "0001-cachefilesd-can-spin-when-disk-space-is-short.patch" https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/1810372/+attachment/5226523/+files/0001-cachefilesd-can-spin-when-disk-space-is-short.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810372 Title: Infinite busy-loop trying to cull when cache space is short To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/1810372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810372] [NEW] Infinite busy-loop trying to cull when cache space is short
Public bug reported:
[Impact]
A user reports that cachefilesd will spin at 100% of a cpu when started
on a filesystem where the free space is less than the bcull threshold
and culling the cache is insufficient to free up space.
Investigation shows that this is because cachefilesd detects that
culling is required, tries to cull, and does not realise that culling
cannot free up enough space, so just keeps retrying.
[Testing/Reproducing]
I created a VM with a spare disk, mounted it to /raid (or whatever).
I changed the /etc/default/cachefilesd to start at boot, filled the /raid
filesystem to over the bcull threshold, and started cachefilesd. When running
top, the cachefilesd process is at the top using approx 100% of 1 CPU. It
appears to be trying to free up space in the cache (that is not even used)
because the filesystem is over the threshold for culling.
[Fix]
This is fixed upstream in 0.10.6:
* Wed Feb 3 2016 David Howells 0.10.6-1
...
- Suspend culling when cache space is short and cache objects are pinned.
The particular patch is ce353f5b6b5b ("cachefilesd can spin when disk
space is short.")
[Regression Potential]
The patch is small and easily understood and backports with minimal effort.
** Affects: cachefilesd (Ubuntu)
Importance: Undecided
Assignee: Daniel Axtens (daxtens)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810372
Title:
Infinite busy-loop trying to cull when cache space is short
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/1810372/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794909] Re: Memory corruption in RAR decoder
Here's a test case for the NULL pointer dereference in ACL handling. ** Attachment added: "aclcrasher.txt" https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1794909/+attachment/5221005/+files/aclcrasher.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794909 Title: Memory corruption in RAR decoder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1794909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794909] Re: Memory corruption in RAR decoder
This is the warc infinite loop test case. Unlike the other files, it's *not* encoded, and I use ./bsdtar -Oxf warcloop.warc to see the looping behaviour. ** Attachment added: "warcloop.warc" https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1794909/+attachment/5221006/+files/warcloop.warc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794909 Title: Memory corruption in RAR decoder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1794909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794909] Re: Memory corruption in RAR decoder
(as with the other test cases, it's in plain text, convert it back with xxd -r aclcrasher.txt aclcrasher) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794909 Title: Memory corruption in RAR decoder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1794909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794909] Re: Memory corruption in RAR decoder
Hi Seth, I've pushed them to https://github.com/libarchive/libarchive/pull/1105 Thanks for walking me through the Ubuntu process. Regards, Daniel ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794909 Title: Memory corruption in RAR decoder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1794909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801305] Re: Restore request-based mode to xen-blkfront for AWS kernels
I've checked that the proposed Xenial AWS kernel works - it boots successfully and uses the deadline scheduler by default on a t2.micro instance. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801305 Title: Restore request-based mode to xen-blkfront for AWS kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805245] [NEW] powerpc/powernv/pci: Work around races in PCI bridge enabling
Public bug reported: SRU Justification = [Impact] An IBM OpenPower partner reports their system with a bunch of NVMe drives fails the NVMe init due to some drives taking PCIe EEH errors. [Fix] Pick patch db2173198b9513f7add8009f225afa1f1c79bcc6 upstream. [Testing] IBM reports that this patch fixes the user's issue. [Regression Potential] The patch is already in Cosmic (db33bbe77b9594133fecf0dc290322437170627f) and in some stable trees (1eb08e7b192d2c412175f607cf51449c916abd57 in 4.14.y). It only affects PowerPC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: SRU Justification = [Impact] An IBM OpenPower partner reports their system with a bunch of NVMe drives fails the NVMe init due to some drives taking PCIe EEH errors. [Fix] Pick patch db2173198b9513f7add8009f225afa1f1c79bcc6 upstream. [Testing] IBM reports that this patch fixes the user's issue. [Regression Potential] - The patch is already in some stable trees (1eb08e7b192d2c412175f607cf51449c916abd57 in 4.14.y). + The patch is already in Cosmic (db33bbe77b9594133fecf0dc290322437170627f) and in some stable trees (1eb08e7b192d2c412175f607cf51449c916abd57 in 4.14.y). It only affects PowerPC. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805245 Title: powerpc/powernv/pci: Work around races in PCI bridge enabling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802421] Re: Xenial: data corruption when using i40e with iommu
** Description changed:
A user reports that using an i40e with intel_iommu=on with the Xenial GA
kernel causes data corruption. Using the Xenial HWE kernel or an out-of-
tree driver more recent than the version shipped with Xenial solves the
issue.
[Impact]
Corrupted data is returned from the network card intermittently. This is
often noticeable when using apt, as the checksums are verified. If often leads
to failure of apt operations. When there are no checksums done, this could lead
to silent data corruption.
[Fix]
- This was fixed somewhere post-4.4. Testing identified b32bfa17246d ("i40e:
Drop packet split receive routine") which is part of a broader refactor. My
theory is that iommu exposes an issue in the packet split receive routine and
so removing it is sufficient to prevent the problem from occurring.
+ This was fixed somewhere post-4.4. Testing identified b32bfa17246d ("i40e:
Drop packet split receive routine") which is part of a broader refactor.
Picking this patch alone is sufficient to fix the issue. My theory is that
iommu exposes an issue in the packet split receive routine and so removing it
is sufficient to prevent the problem from occurring.
[Test]
A user tested a Xenial 4.4 kernel with this patch applied and it fixed their
issue - no data corruption was observed. (The test repeatedly deletes the apt
cache and then does apt update.)
[Regression Potential]
It's a messy change inside i40e, so the risk is that i40e will be broken in
some subtle way we haven't noticed, or have performance issues. None of these
have been observed so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802421
Title:
Xenial: data corruption when using i40e with iommu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802421/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802421] [NEW] Xenial: data corruption when using i40e with iommu
Public bug reported:
A user reports that using an i40e with intel_iommu=on with the Xenial GA
kernel causes data corruption. Using the Xenial HWE kernel or an out-of-
tree driver more recent than the version shipped with Xenial solves the
issue.
[Impact]
Corrupted data is returned from the network card intermittently. This is often
noticeable when using apt, as the checksums are verified. If often leads to
failure of apt operations. When there are no checksums done, this could lead to
silent data corruption.
[Fix]
This was fixed somewhere post-4.4. Testing identified b32bfa17246d ("i40e: Drop
packet split receive routine") which is part of a broader refactor. Picking
this patch alone is sufficient to fix the issue. My theory is that iommu
exposes an issue in the packet split receive routine and so removing it is
sufficient to prevent the problem from occurring.
[Test]
A user tested a Xenial 4.4 kernel with this patch applied and it fixed their
issue - no data corruption was observed. (The test repeatedly deletes the apt
cache and then does apt update.)
[Regression Potential]
It's a messy change inside i40e, so the risk is that i40e will be broken in
some subtle way we haven't noticed, or have performance issues. None of these
have been observed so far.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802421
Title:
Xenial: data corruption when using i40e with iommu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802421/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801305] Re: Restore request-based mode to xen-blkfront for AWS kernels
** Description changed: In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. + For B/C this patchset is bigger as it includes the suspend/resume + patches already in X, and a new fixup. These are desirable as the + request mode patch assumes their presence. + [Regression Potential] - Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. + Could potentially break xen based disks on AWS. + + For B/C, the patches also add some code to the xen core around suspend + and resume, this code is much smaller and also mirrors code already in + Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). ** Description changed: In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. + For X this needs a small patch from upstream for error handling. + For B/C this patchset is bigger as it includes the suspend/resume patches already in X, and a new fixup. These are desirable as the request mode patch assumes their presence. [Regression Potential] - Could potentially break xen based disks on AWS. + Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801305 Title: Restore request-based mode to xen-blkfront for AWS kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801305] [NEW] Restore request-based mode to xen-blkfront for AWS kernels
Public bug reported: In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. For X this needs a small patch from upstream for error handling. For B/C this patchset is bigger as it includes the suspend/resume patches already in X, and a new fixup. These are desirable as the request mode patch assumes their presence. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by - default. + default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. ** Description changed: In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] - Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. + Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801305 Title: Restore request-based mode to xen-blkfront for AWS kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798706] Re: Incomplete linking with boost_regex
Hi, For Xenial: daniel_axtens_canonical_com@dja-202158:~$ sudo apt install google-compute-engine-oslogin=20180905+dfsg1-0ubuntu1~16.04.1 ... Get:1 http://au.archive.ubuntu.com/ubuntu xenial-proposed/universe amd64 google-compute-engine-oslogin amd64 20180905+dfsg1-0ubuntu1~16.04.1 [76.7 kB] ... Unpacking google-compute-engine-oslogin (20180905+dfsg1-0ubuntu1~16.04.1) over (20180510+dfsg1-0ubuntu3~16.04.1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Setting up google-compute-engine-oslogin (20180905+dfsg1-0ubuntu1~16.04.1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... daniel_axtens_canonical_com@dja-202158:~$ logout Connection to 35.189.60.142 closed. $ gcloud compute --project "ubuntu-os-support" ssh --zone "australia-southeast1-b" "dja-202158" WARNING: Using OS Login user [daniel_axtens_canonical_com] instead of default user [dja] Welcome to Ubuntu 16.04.5 LTS (GNU/Linux 4.15.0-1021-gcp x86_64) ---> Xenial verification succeeds. For Trusty: dja@dja-trusty:~$ sudo apt install google-compute-engine-oslogin/trusty-proposed Reading package lists... Done Building dependency tree Reading state information... Done Selected version '20180905+dfsg1-0ubuntu1~14.04.1' (Ubuntu:14.04/trusty-proposed [amd64]) for 'google-compute-engine-oslogin' ... $ gcloud compute instances add-metadata --project "ubuntu-os-support" --zone "australia-southeast1-b" "dja-trusty" --metadata enable-oslogin=TRUE Updated [https://www.googleapis.com/compute/v1/projects/ubuntu-os-support/zones/australia-southeast1-b/instances/dja-trusty]. $ gcloud compute --project "ubuntu-os-support" ssh --zone "australia-southeast1-b" "dja-trusty" WARNING: Using OS Login user [daniel_axtens_canonical_com] instead of default user [dja] Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-137-generic x86_64) ---> Trusty verification succeeds. Regards, Daniel ** Tags removed: verification-needed-trusty verification-needed-xenial ** Tags added: verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798706 Title: Incomplete linking with boost_regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1798706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663280] Re: Serious performance degradation of math functions
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663280 Title: Serious performance degradation of math functions To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1663280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798706] Re: Incomplete linking with boost_regex
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798706 Title: Incomplete linking with boost_regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798706] [NEW] Incomplete linking with boost_regex
: linux (Ubuntu) Importance: Critical Assignee: Daniel Axtens (daxtens) Status: In Progress ** Patch added: "set-LDFLAGS-for-PAM.patch" https://bugs.launchpad.net/bugs/1798706/+attachment/5202754/+files/set-LDFLAGS-for-PAM.patch ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1798706 Title: Incomplete linking with boost_regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798705] [NEW] Incomplete linking with boost_regex
: linux (Ubuntu) Importance: Critical Assignee: Daniel Axtens (daxtens) Status: Confirmed ** Patch added: "set-LDFLAGS-for-PAM.patch" https://bugs.launchpad.net/bugs/1798705/+attachment/5202753/+files/set-LDFLAGS-for-PAM.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798705 Title: Incomplete linking with boost_regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663280] Re: Serious performance degradation of math functions
** Description changed:
+ SRU Justification
+ =
+
+ [Impact]
+
+ * Severe performance hit on many maths-heavy workloads. For example, a
+ user reports linpack performance of 13 Gflops on Trusty and Bionic and
+ 3.9 Gflops on Xenial.
+
+ * Because the impact is so large (>3x) and Xenial is supported until
+ 2021, the fix should be backported.
+
+ * The fix avoids an AVX-SSE transition penalty. It stops
+ _dl_runtime_resolve() from using AVX-256 instructions which touch the
+ upper halves of various registers. This change means that the processor
+ does not need to save and restore them.
+
+ [Test Case]
+
+ Firstly, you need a suitable Intel machine. Users report that Sandy
+ Bridge, Ivy Bridge, Haswell, and Broadwell CPUs are affected, and I
+ have been able to reproduce it on a Skylake CPU using a suitable Azure
+ VM.
+
+ Create the following C file, exp.c:
+
+ #include
+ #include
+
+ int main () {
+ double a, b;
+ for (a = b = 0.0; b < 2.0; b += 0.0005) a += exp(b);
+ printf("%f\n", a);
+ return 0;
+ }
+
+ $ gcc -O3 -march=x86-64 -o exp exp.c -lm
+
+ With the current version of glibc:
+
+ $ time ./exp
+ ...
+ real0m1.349s
+ user0m1.349s
+
+
+ $ time LD_BIND_NOW=1 ./exp
+ ...
+ real0m0.625s
+ user0m0.621s
+
+ Observe that LD_BIND_NOW makes a big difference as it avoids the call to
+ _dl_runtime_resolve.
+
+ With the proposed update:
+
+ $ time ./exp
+ ...
+ real0m0.625s
+ user0m0.621s
+
+
+ $ time LD_BIND_NOW=1 ./exp
+ ...
+
+ real0m0.631s
+ user0m0.631s
+
+ Observe that the normal case is faster, and LD_BIND_NOW makes a
+ negligible difference.
+
+ [Regression Potential]
+
+ glibc is the nightmare case for regressions as could affect pretty much
+ anything, and this patch touches a key part (dynamic libraries).
+
+ We can be fairly confident in the fix generally - it's in the glibc in
+ Bionic, Debian and some RPM-based distros. The backport is based on
+ the patches in the release/2.23/master branch in the upstream glibc
+ repository, and the backport was straightforward.
+
+ Obviously that doesn't remove all risk. There is also a fair bit of
+ Ubuntu-specific patching in glibc so other distros are of limited
+ value for ruling out bugs. So I have done the following testing, and
+ I'm happy to do more as required. All testing has been done:
+ - on an Azure VM (affected by the change), with proposed package
+ - on a local VM (not affected by the change), with proposed package
+
+ * Boot with the upgraded libc6.
+
+ * Watch a youtube video in Firefox over VNC.
+
+ * Build some C code (debuild of zlib).
+
+ * Test Java by installing and running Eclipse.
+
+ Autopkgtest also passes.
+
+ [Original Description]
+
Bug [0] has been introduced in Glibc 2.23 [1] and fixed in Glibc 2.25
[2]. All Ubuntu versions starting from 16.04 are affected because they
use either Glibc 2.23 or 2.24. Bug introduces serious (2x-4x)
performance degradation of math functions (pow, exp/exp2/exp10,
log/log2/log10, sin/cos/sincos/tan, asin/acos/atan/atan2,
sinh/cosh/tanh, asinh/acosh/atanh) provided by libm. Bug can be
reproduced on any AVX-capable x86-64 machine.
@strikov: According to a quite reliable source [5] all AMD CPUs and
latest Intel CPUs (Skylake and Knights Landing) don't suffer from
AVX/SSE transition penalty. It means that the scope of this bug becomes
smaller and includes only the following generations of Intel's CPUs:
Sandy Bridge, Ivy Bridge, Haswell, and Broadwell. Scope still remains
quite large though.
@strikov: Ubuntu 16.10/17.04 which use Glibc 2.24 may recieve the fix
from upstream 2.24 branch (as Marcel pointed out, fix has been
backported to 2.24 branch where Fedora took it successfully) if such
synchronization will take place. Ubuntu 16.04 (the main target of this
bug) uses Glibc 2.23 which hasn't been patched upstream and will suffer
from performance degradation until we fix it manually.
This bug is all about AVX-SSE transition penalty [3]. 256-bit YMM
registers used by AVX-256 instructions extend 128-bit registers used by
SSE (XMM0 is a low half of YMM0 and so on). Every time CPU executes SSE
instruction after AVX-256 instruction it has to store upper half of the
YMM register to the internal buffer and then restore it when execution
returns back to AVX instructions. Store/restore is required because old-
fashioned SSE knows nothing about the upper halves of its registers and
may damage them. This store/restore operation is time consuming (several
tens of clock cycles for each operation). To deal with this issue, Intel
introduced AVX-128 instructions which operate on the same 128-bit XMM
register as SSE but take into account upper halves of YMM registers.
Hence, no store/restore required. Practically speaking, AVX-128
instructions is a new smart form of SSE instructions which can be used
together with full-size AVX-256 instructions
[Bug 1797314] Re: fscache: bad refcounting in fscache_op_complete leads to OOPS
** Description changed: SRU Justification - [Impact] A kernel BUG is sometimes observed when using fscache: [4740718.880898] FS-Cache: [4740718.880920] FS-Cache: Assertion failed [4740718.880934] FS-Cache: 0 > 0 is false [4740718.881001] [ cut here ] [4740718.881017] kernel BUG at /usr/src/linux-4.4.0/fs/fscache/operation.c:449! [4740718.881040] invalid opcode: [#1] SMP - + [4740718.892659] Call Trace: [4740718.893506] [] cachefiles_read_copier+0x3a9/0x410 [cachefiles] [4740718.894374] [] fscache_op_work_func+0x22/0x50 [fscache] [4740718.895180] [] process_one_work+0x150/0x3f0 [4740718.895966] [] worker_thread+0x11a/0x470 [4740718.896753] [] ? __schedule+0x359/0x980 [4740718.897783] [] ? rescuer_thread+0x310/0x310 [4740718.898581] [] kthread+0xd6/0xf0 [4740718.899469] [] ? kthread_park+0x60/0x60 [4740718.900477] [] ret_from_fork+0x3f/0x70 [4740718.901514] [] ? kthread_park+0x60/0x60 [Problem] - In include/fscache-cache.h, fscache_retrieval_complete reads, in part: + In include/linux/fscache-cache.h, fscache_retrieval_complete reads, in + part: atomic_sub(n_pages, >n_pages); if (atomic_read(>n_pages) <= 0) fscache_op_complete(>op, true); The code is using atomic_sub followed by an atomic_read. This causes two threads doing a decrement of pages to race with each other seeing the op->refcount <= 0 at same time, and end up calling fscache_op_complete in both the threads leading to the OOPS. [Fix] The fix is trivial to use atomic_sub_return instead of two calls. [Testcase] - The user has tested the patch successfully on their fscache/cachefiles setup. + I believe the user has tested the patch successfully on their fscache/cachefiles setup. [Regression Potential] Limited to fscache. Small, comprehensible change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797314 Title: fscache: bad refcounting in fscache_op_complete leads to OOPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1771704] Re: support for ipv4 link-local addressing
Hi Steve, No worries, that sounds fair enough. I will file the bugs as separate issues in the next few days then. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771704 Title: support for ipv4 link-local addressing To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1771704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797314] [NEW] fscache: bad refcounting in fscache_op_complete leads to OOPS
Public bug reported: SRU Justification - [Impact] A kernel BUG is sometimes observed when using fscache: [4740718.880898] FS-Cache: [4740718.880920] FS-Cache: Assertion failed [4740718.880934] FS-Cache: 0 > 0 is false [4740718.881001] [ cut here ] [4740718.881017] kernel BUG at /usr/src/linux-4.4.0/fs/fscache/operation.c:449! [4740718.881040] invalid opcode: [#1] SMP [4740718.892659] Call Trace: [4740718.893506] [] cachefiles_read_copier+0x3a9/0x410 [cachefiles] [4740718.894374] [] fscache_op_work_func+0x22/0x50 [fscache] [4740718.895180] [] process_one_work+0x150/0x3f0 [4740718.895966] [] worker_thread+0x11a/0x470 [4740718.896753] [] ? __schedule+0x359/0x980 [4740718.897783] [] ? rescuer_thread+0x310/0x310 [4740718.898581] [] kthread+0xd6/0xf0 [4740718.899469] [] ? kthread_park+0x60/0x60 [4740718.900477] [] ret_from_fork+0x3f/0x70 [4740718.901514] [] ? kthread_park+0x60/0x60 [Problem] In include/fscache-cache.h, fscache_retrieval_complete reads, in part: atomic_sub(n_pages, >n_pages); if (atomic_read(>n_pages) <= 0) fscache_op_complete(>op, true); The code is using atomic_sub followed by an atomic_read. This causes two threads doing a decrement of pages to race with each other seeing the op->refcount <= 0 at same time, and end up calling fscache_op_complete in both the threads leading to the OOPS. [Fix] The fix is trivial to use atomic_sub_return instead of two calls. [Testcase] The user has tested the patch successfully on their fscache/cachefiles setup. [Regression Potential] Limited to fscache. Small, comprehensible change. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: SRU Justification - [Impact] A kernel BUG is sometimes observed when using fscache: + [4740718.880898] FS-Cache: + [4740718.880920] FS-Cache: Assertion failed + [4740718.880934] FS-Cache: 0 > 0 is false + [4740718.881001] [ cut here ] + [4740718.881017] kernel BUG at /usr/src/linux-4.4.0/fs/fscache/operation.c:449! + [4740718.881040] invalid opcode: [#1] SMP + + [4740718.892659] Call Trace: + [4740718.893506] [] cachefiles_read_copier+0x3a9/0x410 [cachefiles] + [4740718.894374] [] fscache_op_work_func+0x22/0x50 [fscache] + [4740718.895180] [] process_one_work+0x150/0x3f0 + [4740718.895966] [] worker_thread+0x11a/0x470 + [4740718.896753] [] ? __schedule+0x359/0x980 + [4740718.897783] [] ? rescuer_thread+0x310/0x310 + [4740718.898581] [] kthread+0xd6/0xf0 + [4740718.899469] [] ? kthread_park+0x60/0x60 + [4740718.900477] [] ret_from_fork+0x3f/0x70 + [4740718.901514] [] ? kthread_park+0x60/0x60 - Jun 25 11:32:08 kernel: [4740718.880898] FS-Cache: - Jun 25 11:32:08 kernel: [4740718.880920] FS-Cache: Assertion failed - Jun 25 11:32:08 kernel: [4740718.880934] FS-Cache: 0 > 0 is false - Jun 25 11:32:08 kernel: [4740718.881001] [ cut here ] - Jun 25 11:32:08 kernel: [4740718.881017] kernel BUG at /usr/src/linux-4.4.0/fs/fscache/operation.c:449! - Jun 25 11:32:08 kernel: [4740718.881040] invalid opcode: [#1] SMP - ... - Jun 25 11:32:08 kernel: [4740718.892659] Call Trace: - Jun 25 11:32:08 kernel: [4740718.893506] [] cachefiles_read_copier+0x3a9/0x410 [cachefiles] - Jun 25 11:32:08 kernel: [4740718.894374] [] fscache_op_work_func+0x22/0x50 [fscache] - Jun 25 11:32:08 kernel: [4740718.895180] [] process_one_work+0x150/0x3f0 - Jun 25 11:32:08 kernel: [4740718.895966] [] worker_thread+0x11a/0x470 - Jun 25 11:32:08 kernel: [4740718.896753] [] ? __schedule+0x359/0x980 - Jun 25 11:32:08 kernel: [4740718.897783] [] ? rescuer_thread+0x310/0x310 - Jun 25 11:32:08 kernel: [4740718.898581] [] kthread+0xd6/0xf0 - Jun 25 11:32:08 kernel: [4740718.899469] [] ? kthread_park+0x60/0x60 - Jun 25 11:32:08 kernel: [4740718.900477] [] ret_from_fork+0x3f/0x70 - Jun 25 11:32:08 kernel: [4740718.901514] [] ? kthread_park+0x60/0x60 - [Problem] In include/fscache-cache.h, fscache_retrieval_complete reads, in part: - atomic_sub(n_pages, >n_pages); - if (atomic_read(>n_pages) <= 0) - fscache_op_complete(>op, true); - - The code is using atomic_sub followed by an atomic_read. This causes two threads doing a decrement of pages to race with each other seeing the op->refcount <= 0 at same time, - and end up calling fscache_op_complete in both the threads leading to the OOPS. - + atomic_sub(n_pages, >n_pages); + if (atomic_read(>n_pages) <= 0) + fscache_op_complete(>op, true); + + The code is using atomic_sub followed by an atomic_read.
[Bug 1771704] Re: support for ipv4 link-local addressing
Hi, I added this to my netplan-config-tester and it's turned up a couple of issues with NetworkManager. 1) If a static IPv4 address is specified and link-local: [ipv4] is specified, there is no link-local address added. The documentation doesn't make this clear; it only refers to DHCP conflicting with link- local. network: ethernets: ens7: addresses: [16.16.250.1/22] link-local: [ipv4] renderer: NetworkManager version: 2 ubuntu@netplan2:~$ sudo ip a flush dev ens7 ubuntu@netplan2:~$ sudo ip l set dev ens7 down ubuntu@netplan2:~$ sudo netplan apply ubuntu@netplan2:~$ sleep 15 # give LL addresses time to be set up ubuntu@netplan2:~$ ip a show dev ens7 9: ens7: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:b4:02:6e brd ff:ff:ff:ff:ff:ff inet 16.16.250.1/22 brd 16.16.251.255 scope global noprefixroute ens7 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:feb4:26e/64 scope link valid_lft forever preferred_lft forever This is doubly wrong: there's not IPv4 LL address and there is an IPv6 LL address. Which leads me to bug 2... 2) With NM, link-local: [ipv4] and link-local: [] don't disable a IPv6 LL address. If you modify the config file above to have link-local: [] and repeat the test, you still get an IPv6 link-local address. I don't know if you want to gate the backport on this working/being documented correctly or if you'd prefer this to go through for now while we get it fixed upstream. Let me know. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771704 Title: support for ipv4 link-local addressing To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1771704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
Hi, This works on reboot but not so well after the system boots. Say I have the following file: network: version: 2 ethernets: ens7: dhcp4: true match: macaddress: 52:54:00:b4:02:6e set-name: myif1 optional: true If I reboot, everything is fine: ubuntu@netplan2:~$ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:d2:9b:b5 brd ff:ff:ff:ff:ff:ff 3: myif1: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:b4:02:6e brd ff:ff:ff:ff:ff:ff But if I now change set-name to myif0, I can't get it to change the name 'live'. If I apply with the interface 'up', nothing happens, which is fine: ubuntu@netplan2:~$ sudo netplan apply ubuntu@netplan2:~$ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:d2:9b:b5 brd ff:ff:ff:ff:ff:ff 3: myif1: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:b4:02:6e brd ff:ff:ff:ff:ff:ff But if I bring it down and run netplan apply, the interface is renamed to ens7, not myif0, and it stays down. ubuntu@netplan2:~$ sudo ip l set dev myif1 down ubuntu@netplan2:~$ sudo netplan apply ubuntu@netplan2:~$ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:d2:9b:b5 brd ff:ff:ff:ff:ff:ff 3: ens7: mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:b4:02:6e brd ff:ff:ff:ff:ff:ff If I downgrade to 0.36.3, the interface is correctly renamed and brought up: 9: myif0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:b4:02:6e brd ff:ff:ff:ff:ff:ff So not an unqualified success here. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663280] Re: Serious performance degradation of math functions
** Changed in: glibc (Ubuntu Xenial) Status: New => Confirmed ** Changed in: glibc (Ubuntu Xenial) Assignee: (unassigned) => Daniel Axtens (daxtens) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663280 Title: Serious performance degradation of math functions To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1663280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742658] Re: linux-generic-hwe-16.04 OOPS in nouveau after security update
Hi, I haven't found the time to do this yet, sorry. Is it still an issue on the current Xenial kernel? Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742658 Title: linux-generic-hwe-16.04 OOPS in nouveau after security update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756701] Re: 'gratuitious-arp' may be a spelling error
Hi Matt, I don't think this is documentation-only: it was rendered incorrectly out to networkd - see my comment #4. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756701 Title: 'gratuitious-arp' may be a spelling error To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1756701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767849] Re: from key in routes generates incorrect networkd configuration
This has been fixed in Cosmic. I have attempted to nominate it for Xenial and Bionic for backporting. ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Fix Committed ** Changed in: netplan Status: Fix Committed => 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/1767849 Title: from key in routes generates incorrect networkd configuration To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1767849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793430] [NEW] Page leaking in cachefiles_read_backing_file while vmscan is active
Public bug reported: SRU Justification - [Description] In a heavily loaded system where the system pagecache is nearing memory limits and fscache is enabled, pages can be leaked by fscache while trying read pages from cachefiles backend. This can happen because two applications can be reading same page from a single mount, two threads can be trying to read the backing page at same time. This results in one of the thread finding that a page for the backing file or netfs file is already in the radix tree. During the error handling cachefiles does not cleanup the reference on backing page, leading to page leak. [Fix] The fix is straightforward, to decrement the reference when error is encounterd. [Testing] A user has tested the fix using following method for 12+ hrs. 1) mkdir -p /mnt/nfs ; mount -o vers=3,fsc :/export /mnt/nfs 2) create 1 files of 2.8MB in a NFS mount. 3) start a thread to simulate heavy VM presssure (while true ; do echo 3 > /proc/sys/vm/drop_caches ; sleep 1 ; done)& 4) start multiple parallel reader for data set at same time find /mnt/nfs -type f | xargs -P 80 cat > /dev/null & find /mnt/nfs -type f | xargs -P 80 cat > /dev/null & find /mnt/nfs -type f | xargs -P 80 cat > /dev/null & .. .. find /mnt/nfs -type f | xargs -P 80 cat > /dev/null & find /mnt/nfs -type f | xargs -P 80 cat > /dev/null & 5) finally check using cat /proc/fs/fscache/stats | grep -i pages ; free -h , cat /proc/meminfo and page-types -r -b lru to ensure all pages are freed. [Regression Potential] Limited to cachefiles. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Daniel Axtens (daxtens) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793430 Title: Page leaking in cachefiles_read_backing_file while vmscan is active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783246] Re: Cephfs + fscache: unable to handle kernel NULL pointer dereference at 0000000000000000 IP: jbd2__journal_start+0x22/0x1f0
** Changed in: linux (Ubuntu) Assignee: Daniel Axtens (daxtens) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783246 Title: Cephfs + fscache: unable to handle kernel NULL pointer dereference at IP: jbd2__journal_start+0x22/0x1f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785544] [NEW] package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1
Public bug reported: Hi, I installed trousers on my Dell XPS 13, and the following error occurred: Aug 06 12:03:45 linkitivity trousers[11173]: * Starting Trusted Computing daemon tcsd Aug 06 12:03:45 linkitivity trousers[11173]: /etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator Aug 06 12:03:45 linkitivity trousers[11173]: * TPM device owner for /dev/tpmrm0 is not 'tss', this can cause problems. Aug 06 12:03:45 linkitivity tcsd[11196]: TCSD TDDL[11196]: TrouSerS ioctl: (25) Inappropriate ioctl for device Aug 06 12:03:45 linkitivity tcsd[11196]: TCSD TDDL[11196]: TrouSerS Falling back to Read/Write device support. Aug 06 12:03:45 linkitivity tcsd[11196]: TCSD TCS[11196]: TrouSerS ERROR: TCS GetCapability failed with result = 0x1e Aug 06 12:03:45 linkitivity trousers[11173]:...fail! Aug 06 12:03:45 linkitivity systemd[1]: trousers.service: Control process exited, code=exited status=30 Aug 06 12:03:45 linkitivity systemd[1]: trousers.service: Failed with result 'exit-code'. Aug 06 12:03:45 linkitivity systemd[1]: Failed to start LSB: starts tcsd. The first problem in /etc/init.d/trousers is: if [ ! -e /dev/tpm* ] then log_warning_msg "device driver not loaded, skipping." exit 0 fi I have two devices that match /dev/tpm*: /dev/tpm0 and /dev/tpmrm0, and [ -e only works with one input. This doesn't cause the warning to fire, so it's purely a cosmetic warning. The second warning seems to related to the ownership of /dev/tpmrm0: # ls -l /dev/tpm* crw--- 1 tss tss 10, 224 Aug 6 12:03 /dev/tpm0 crw--- 1 root root 253, 65536 Jul 27 19:50 /dev/tpmrm0 So it looks like /dev/tpm0 is set correctly but not /dev/tpmrm0. Looking at the source, it seems that debian/trousers.udev contains only the following: KERNEL=="tpm[0-9]*", MODE="0600", OWNER="tss", GROUP="tss" I think per some reading online it needs to read something like this: KERNEL=="tpmrm[0-9]*|tpm[0-9]*", MODE="0660", OWNER="tss", GROUP="tss" Editing /lib/udev/rules.d/45-trousers.rules to include this line and running `udevadm trigger` makes the warning go away. Finally, the whole thing fails with "ERROR: TCS GetCapability failed with result = 0x1e". This is apparently due to the presence of a TPM2 chip rather than the 1.2 chip that trousers understands. I think trousers should print a loud warning in this case (and preferably a much more informative one!) but that it should not fail to configure the package. This is Ubuntu 18.04, with: trousers: Installed: 0.3.14+fixed1-1build1 Candidate: 0.3.14+fixed1-1build1 Version table: *** 0.3.14+fixed1-1build1 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 18.04 Package: trousers 0.3.14+fixed1-1build1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libtspi1:amd64: Install libtpm-unseal1:amd64: Install trousers:amd64: Install tpm-tools:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Aug 6 12:03:45 2018 ErrorMessage: installed trousers package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-04-05 (487 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: trousers Title: package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-30 (97 days ago) ** Affects: trousers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785544 Title: package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1785544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774336] Re: FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false
** Description changed: == SRU Justification == [Impact] Oops during heavy NFS + FSCache use: - [81738.886634] FS-Cache: + [81738.886634] FS-Cache: [81738.888281] FS-Cache: Assertion failed [81738.889461] FS-Cache: 6 == 5 is false [81738.890625] [ cut here ] [81738.891706] kernel BUG at /build/linux-hVVhWi/linux-4.4.0/fs/fscache/operation.c:494! 6 == 5 represents an operation being DEAD when it was not expected to be. [Cause] - There is a race in fscache and cachefiles. + There is a race in fscache and cachefiles. One thread is in cachefiles_read_waiter: - 1) object->work_lock is taken. - 2) the operation is added to the to_do list. - 3) the work lock is dropped. - 4) fscache_enqueue_retrieval is called, which takes a reference. + Â 1) object->work_lock is taken. + Â 2) the operation is added to the to_do list. + Â 3) the work lock is dropped. + Â 4) fscache_enqueue_retrieval is called, which takes a reference. Another thread is in cachefiles_read_copier: - 1) object->work_lock is taken - 2) an item is popped off the to_do list. - 3) object->work_lock is dropped. - 4) some processing is done on the item, and fscache_put_retrieval() is called, dropping a reference. + Â 1) object->work_lock is taken + Â 2) an item is popped off the to_do list. + Â 3) object->work_lock is dropped. + Â 4) some processing is done on the item, and fscache_put_retrieval() is called, dropping a reference. Now if the this process in cachefiles_read_copier takes place *between* steps 3 and 4 in cachefiles_read_waiter, a reference will be dropped before it is taken, which leads to the objects reference count hitting zero, which leads to lifecycle events for the object happening too soon, leading to the assertion failure later on. (This is simplified and clarified from the original upstream analysis for this patch at https://www.redhat.com/archives/linux- cachefs/2018-February/msg1.html and from a similar patch with a different approach to fixing the bug at https://www.redhat.com/archives /linux-cachefs/2017-June/msg2.html) [Fix] - Move fscache_enqueue_retrieval under the lock in cachefiles_read_waiter. This means that the object cannot be popped off the to_do list until it is in a fully consistent state with the reference taken. + + + (Old sauce patch being reverted) Move fscache_enqueue_retrieval under the lock in cachefiles_read_waiter. This means that the object cannot be popped off the to_do list until it is in a fully consistent state with the reference taken. + + (New upstream patch) Explicitly take a reference to the object while it + is being enqueued. Adjust another part of the code to deal with the + greater range of object states this exposes. [Testcase] A user has run ~100 hours of NFS stress tests and not seen this bug recur. [Regression Potential] - - Limited to fscache/cachefiles. - - The change makes things more conservative (doing more under lock) so that's reassuring. - - There may be performance impacts but none have been observed so far. + Â - Limited to fscache/cachefiles. + Â - The change makes things more conservative (taking more references) so that's reassuring. + Â - There may be performance impacts but none have been observed so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774336 Title: FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784864] Re: Various fscache/cachefiles bugs
Oops, my mistake, there are already LP bugs covering these issues. Regards, Daniel ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784864 Title: Various fscache/cachefiles bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784864] [NEW] Various fscache/cachefiles bugs
Public bug reported:
SRU Justification
-
A few bugs while using fscache/cachefiles on a NFS share have been
reported by a user. All are intermittent/race conditions.
[Impact]
Various BUGs/OOPSes:
- BUG on "Unexpected object collision"
- CacheFiles: Error: Overlong wait for old active object to go away /
CacheFiles: Error: Object already active /
kernel BUG at fs/cachefiles/namei.c:163!
- Unmounting an NFS share sometimes leads to an oops
[Fix]
Grab the following patches from Dave Howell's tree linux-fs tree in the
fscache-fixes branch
(https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-fixes)
- they're various small fixes within fscache/cachefiles.
4856fccd559f cachefiles: Wait rather than BUG'ing on "Unexpected object
collision"
28d64cf8990c cachefiles: Fix missing clear of the CACHEFILES_OBJECT_ACTIVE flag
aedc4ca703bc fscache: Fix reference overput in fscache_attach_object() error
handling
[Testcase]
The user has run ~100 hours of NFS stress tests and have not seen these bugs
recur.
[Regression Potential]
- Limited to fscache/cachefiles.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Daniel Axtens (daxtens)
Status: Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784864
Title:
Various fscache/cachefiles bugs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784864/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781038] Re: KVM guest hash page table failed to allocate contiguous memory (CMA)
Yes, we have closed the support case on our end at their request. Apparently increasing the reservation ratio has helped. Paulus - Hi! Thanks for the info and clearing up some of my misunderstandings. Great to hear from you and I hope things are going well at OzLabs :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781038 Title: KVM guest hash page table failed to allocate contiguous memory (CMA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1781038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750392] Re: nplan cannot enable IPv6 privacy extensions
Hmm, maybe it needs to be explicitly set for NM when the user sets it to off. I'll look into it at some point soon, hopefully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750392 Title: nplan cannot enable IPv6 privacy extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1750392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768006] Re: netplan apply breaks SR-IOV
I can't reproduce this with a bnx2x card. What card are you using? ** Also affects: netplan Importance: Undecided Status: New ** Changed in: netplan Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768006 Title: netplan apply breaks SR-IOV To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1768006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781203] Re: Bonding "parameters" not supported
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781203 Title: Bonding "parameters" not supported To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1781203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726695] Re: Routes are not correctly documented in man pages
** Changed in: netplan Status: Fix Committed => 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/1726695 Title: Routes are not correctly documented in man pages To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1726695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781203] Re: Bonding "parameters" not supported
Sorry, I meant duplicate of LP: #1746419 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781203 Title: Bonding "parameters" not supported To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1781203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781203] Re: Bonding "parameters" not supported
I agree it is a bug. It is an unfortunate mix of netplan and systemd decisions/features/bugs causing the issue. Do you mind if we mark this as a duplicate of LP: #1781203? It's the same root cause (netplan apply cannot change bond parameters) just with a different presentation (netplan try). Once we fix netplan apply, netplan try should work too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781203 Title: Bonding "parameters" not supported To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1781203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701434] Re: netplan apply always exits with status 0
It looks like at least some of this changed between Bionic and Cosmic - here with a netplan 0.39: root@netplan:~# netplan apply Error in network definition /etc/netplan/50-cloud-init.yaml line 5 column 0: unknown key xxnetwork root@netplan:~# echo $? 78 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701434 Title: netplan apply always exits with status 0 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1701434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783246] [NEW] Cephfs + fscache: unable to handle kernel NULL pointer dereference at 0000000000000000 IP: jbd2__journal_start+0x22/0x1f0
Public bug reported: SRU Justification - [Impact] Certain sequences of file system operations on a cephfs volume backed by fscache with an ext4 store can cause a kernel BUG: [ 5818.932770] BUG: unable to handle kernel NULL pointer dereference at [ 5818.934354] IP: jbd2__journal_start+0x33/0x1e0 ... [ 5818.962490] Call Trace: [ 5818.963055] ? ext4_writepages+0x5d5/0xf40 [ 5818.963884] __ext4_journal_start_sb+0x6d/0x120 [ 5818.964994] ext4_writepages+0x5d5/0xf40 [ 5818.965991] ? __enqueue_entity+0x5c/0x60 [ 5818.966791] ? check_preempt_wakeup+0x130/0x240 [ 5818.967679] do_writepages+0x4b/0xe0 [ 5818.968625] ? ext4_mark_inode_dirty+0x1d0/0x1d0 [ 5818.969526] ? do_writepages+0x4b/0xe0 [ 5818.970493] ? ext4_statfs+0x114/0x260 [ 5818.971267] __filemap_fdatawrite_range+0xc1/0x100 [ 5818.972425] ? __filemap_fdatawrite_range+0xc1/0x100 [ 5818.973385] filemap_write_and_wait+0x31/0x90 [ 5818.974461] ext4_bmap+0x8c/0xe0 [ 5818.975150] cachefiles_read_or_alloc_pages+0x1bf/0xd90 [cachefiles] [ 5818.976718] ? _cond_resched+0x19/0x40 [ 5818.977482] ? wake_up_bit+0x42/0x50 [ 5818.978227] ? fscache_run_op.isra.8+0x4c/0x80 [fscache] [ 5818.979249] __fscache_read_or_alloc_pages+0x1d3/0x2e0 [fscache] [ 5818.980397] ceph_readpages_from_fscache+0x6c/0xe0 [ceph] [ 5818.981630] ceph_readpages+0x49/0x100 [ceph] [ 5818.982691] __do_page_cache_readahead+0x1c9/0x2c0 [ 5818.983628] ? __cap_is_valid+0x21/0xb0 [ceph] [ 5818.984526] ondemand_readahead+0x11a/0x2a0 [ 5818.985374] ? ondemand_readahead+0x11a/0x2a0 [ 5818.986825] page_cache_async_readahead+0x71/0x80 [ 5818.987751] generic_file_read_iter+0x784/0xbf0 [ 5818.988663] ? ceph_put_cap_refs+0x1c4/0x330 [ceph] [ 5818.989620] ? page_cache_tree_insert+0xe0/0xe0 [ 5818.990519] ceph_read_iter+0x106/0x820 [ceph] [ 5818.991818] new_sync_read+0xe4/0x130 [ 5818.992588] __vfs_read+0x29/0x40 [ 5818.993504] vfs_read+0x8e/0x130 [ 5818.994192] SyS_read+0x55/0xc0 [ 5818.994870] do_syscall_64+0x73/0x130 [ 5818.995632] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [Fix] Cherry-pick 5d988308283ecf062fa88f20ae05c52cce0bcdca from upstream. This patch stops cephfs from reusing current->journal for its own internal use, which means that it's valid when ext4 uses it via fscache. [Testcase] A user has been using the following test case: ( cat /proc/fs/fscache/stats > ~/test.log; i=0; while true; do touch small; echo 3 > /proc/sys/vm/drop_caches & md5sum small; let "i++"; if ! (( $i % 1000 )); then echo "Test iteration $i done" >> ~/test.log; cat /proc/fs/fscache/stats >> ~/test.log; fi; done ) > ~/nohup.out 2>&1 (It boils down to "touch file; drop caches; read file") Without the patch, this fails very quickly - usually the first time, always within a few iterations. With the patch, the user ran this loop for over 60 hours without incident. [Regression potential] The change is not trivial, but is limited to cephfs, and has been in mainline since v4.16. So the risk of regression is well contained. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Daniel Axtens (daxtens) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783246 Title: Cephfs + fscache: unable to handle kernel NULL pointer dereference at IP: jbd2__journal_start+0x22/0x1f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701434] Re: netplan apply always exits with status 0
I'm marking this as confirmed as the behaviour has come up in LP: #1735318. ** Changed in: netplan Status: Incomplete => Confirmed ** Changed in: nplan (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701434 Title: netplan apply always exits with status 0 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1701434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746419] Re: bond parameters are not changed by 'netplan apply'
Should it though? That will, for example, terminate any tcpdump processes bound to the bond, it will disrupt currently running connections, etc. Maybe we could do it but we'd want to put it behind a --force option or something, I think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746419 Title: bond parameters are not changed by 'netplan apply' To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1746419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781652] Re: should be possible to specify static routes on a dhcp-configured interface
This hit me too. I'm not sure how netplan can fix this - it looks like it's generating pretty sensible configuration files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781652 Title: should be possible to specify static routes on a dhcp-configured interface To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1781652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750392] Re: nplan cannot enable IPv6 privacy extensions
** Changed in: nplan (Ubuntu) Status: Confirmed => 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/1750392 Title: nplan cannot enable IPv6 privacy extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1750392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746419] Re: bond parameters are not changed by 'netplan apply'
** Also affects: netplan Importance: Undecided Status: New ** Changed in: netplan Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746419 Title: bond parameters are not changed by 'netplan apply' To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1746419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781203] Re: Bonding "parameters" not supported
Netplan apply cannot change bond parameters either. You would either need to delete the bond and then run netplan apply, or just reboot. See LP: #1746419 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781203 Title: Bonding "parameters" not supported To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1781203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743302] Re: wrong paths in systemd units
This all seems to work on Bionic, so closing this issue. ** Changed in: nfs-ganesha (Ubuntu) Status: New => 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/1743302 Title: wrong paths in systemd units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/1743302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783030] [NEW] Incorrect man page generation (fixed upstream)
Public bug reported: Hi, I've run in to a problem in man page generation to do with fonts. Something like: Note that **``rdnssd``**(8) is required to use RDNSS with networkd. No extra software is required for NetworkManager. gets rendered wrongly: the bold text goes right to the end of the line, rather than ending when rdnssd does. You can see this by doing 'man netplan' on a bionic box and searching for rdnssd. This is reported upstream: https://github.com/jgm/pandoc/issues/3568 It was fixed in https://github.com/jgm/pandoc/commit/31a36cf186353dd7c18533b42a88424145b12dcc Please could you backport that commit to bionic? Regards, Daniel ** Affects: pandoc (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, I've run in to a problem in man page generation to do with fonts. Something like: + Note that **``rdnssd``**(8) is required to use RDNSS with networkd. No extra + software is required for NetworkManager. - Note that **``rdnssd``**(8) is required to use RDNSS with networkd. No extra - software is required for NetworkManager. - - gets rendered wrongly: the bold text goes write to the end of the line, + gets rendered wrongly: the bold text goes right to the end of the line, rather than ending when rdnssd does. You can see this by doing 'man netplan' on a bionic box and searching for rdnssd. This is reported upstream: https://github.com/jgm/pandoc/issues/3568 It was fixed in https://github.com/jgm/pandoc/commit/31a36cf186353dd7c18533b42a88424145b12dcc Please could you backport that commit to bionic? Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783030 Title: Incorrect man page generation (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pandoc/+bug/1783030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
** Changed in: netplan Status: Confirmed => 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/1770082 Title: systemd-networkd not renaming devices on boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768560] Re: Netplan generates systemd-networkd config files with incorrect file permissions
*** This bug is a duplicate of bug 1736965 *** https://bugs.launchpad.net/bugs/1736965 It looks like this and bug LP: #1736965 are duplicates. I have proposed https://github.com/CanonicalLtd/netplan/pull/36 as a fix. Regards, Daniel ** This bug has been marked a duplicate of bug 1736965 "netplan apply" does not set file mode, umask 077 causes systemd-networkd to be unable to start -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768560 Title: Netplan generates systemd-networkd config files with incorrect file permissions To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1768560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735944] Re: cannot route IPv6 addresses
Hmm, that's really odd. I'm sorry you haven't had a solution yet. I have a set of test containers to test ipv6 networking. My netplan config for a static IPv6 address is https://github.com/daxtens/ipv6 -config-demos/blob/master/static-networkd/60-ipv6.yaml and it looks a lot like yours. It can definitely get past the next hop. If I enter that container and dump the same info as you have: root@static-networkd:~# ip -6 route fd8f:1d7d:b141::/64 dev eth0 proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium default via fd8f:1d7d:b141::1 dev eth0 proto static metric 1024 pref medium Interestingly here I'm missing all the nexthop stuff you have... root@static-networkd:~# route -6 Kernel IPv6 routing table DestinationNext Hop Flag Met Ref Use If fd8f:1d7d:b141::/64[::] U256 2 5 eth0 fe80::/64 [::] U256 1 0 eth0 [::]/0 _gateway UG 1024 218 eth0 ip6-localhost/128 [::] Un 0 3 4 lo static-networkd/128[::] Un 0 320 eth0 static-networkd/128[::] Un 0 3 8 eth0 ip6-mcastprefix/8 [::] U256 276 eth0 [::]/0 [::] !n -1 1 1 lo And again here I don't have a bunch of routes you do. I wonder how you're ending up with the nexthop stuff. Do you have any virtual networking stuff on your host? VMs? openvswitch? Anything else that would mess with routes? Regards, Daniel ** Changed in: nplan (Ubuntu) Assignee: MOHAMMED FAHAD MUSHAHID (89mfahad) => Daniel Axtens (daxtens) ** Changed in: nplan (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735944 Title: cannot route IPv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1735944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736965] Re: "netplan apply" does not set file mode, umask 077 causes systemd-networkd to be unable to start
Hi, I have reproduced this on bionic, and proposed the following patch to fix it: https://github.com/CanonicalLtd/netplan/pull/36 Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736965 Title: "netplan apply" does not set file mode, umask 077 causes systemd- networkd to be unable to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1736965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750392] Re: nplan cannot enable IPv6 privacy extensions
OK, I have it working for me using my ipv6 test bench (https://github.com/daxtens/ipv6-config-demos) Systemd-networkd: root@slaac-rdnss-networkd:~# ip a list temporary root@slaac-rdnss-networkd:~# sudo nano /etc/netplan/60-ipv6.yaml # add ip6-privacy: true root@slaac-rdnss-networkd:~# sudo netplan apply root@slaac-rdnss-networkd:~# ip a list temporary 113: eth0@if114: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:6c:32:b7 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fd8f:1d7d:b142:0:c9f6:a048:7d3d:d7b0/64 scope global temporary dynamic valid_lft 86399sec preferred_lft 14399sec NetworkManager: root@slaac-rdnss-network-manager:~# ip a list temporary root@slaac-rdnss-network-manager:~# nano /etc/netplan/60-ipv6.yaml root@slaac-rdnss-network-manager:~# sudo netplan apply # add ip6-privacy: true # wait a couple of secs root@slaac-rdnss-network-manager:~# ip a list temporary 69: eth0@if70: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:be:4c:e9 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fd8f:1d7d:b142:0:55c8:3d0f:558d:2f20/64 scope global temporary dynamic valid_lft 86392sec preferred_lft 14392sec The package is in the same ppa at version 0.39+dja2.2, and I'll submit a PR shortly. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750392 Title: nplan cannot enable IPv6 privacy extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1750392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741910] Re: ath6kl_sdio does not support unbinding
** Changed in: netplan Status: Fix Committed => 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/1741910 Title: ath6kl_sdio does not support unbinding To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1741910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748629] Re: 'netplan help' doesn't work as expected
** Changed in: netplan Status: Fix Committed => 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/1748629 Title: 'netplan help' doesn't work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1748629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735317] Re: Invalid YAML in docs
** Changed in: netplan Status: Fix Committed => 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/1735317 Title: Invalid YAML in docs To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1735317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619258] Re: netplan should allow NICs to be disconnected and not stall the boot
Thanks, done. ** Changed in: nplan (Ubuntu) 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/1619258 Title: netplan should allow NICs to be disconnected and not stall the boot To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1619258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751151] Re: Installing via IPv6 results in invalid netplan yaml
** Changed in: nplan (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751151 Title: Installing via IPv6 results in invalid netplan yaml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1751151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773071] Re: Netplan unknown key bridges
Hi, I'm trying to triage some old bugs so apologies if this comes out of the blue. Line numbers being wrong is a known issue - see LP: #1752956. >From what you've posted, it looks like your bridges stanza isn't sufficiently indented - it should be at the same level of indent as ethernets. Do things work if you line that up? Regards, Daniel ** Changed in: nplan (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773071 Title: Netplan unknown key bridges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1773071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750392] Re: nplan cannot enable IPv6 privacy extensions
Hi, Are you able to test a package for me? I have uploaded netplan.io 0.39+dja1 to https://launchpad.net/~daxtens/+archive/ubuntu/builder - if you could add the ppa and install that version of netplan, it adds a `ip6-privacy` key. Currently I've only wired up the networkd backend, but if that works (or if you need NM for testing), I'll wire up NM. I've also pushed the WIP patch to https://github.com/daxtens/netplan/tree/ip6privacy if you would like to see it. I haven't got a good ipv6 network on hand, but I verified that with ip6-privacy: yes for ens3, I saw that /proc/sys/net/ipv6/conf/ens3/use_tempaddr contained 2. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750392 Title: nplan cannot enable IPv6 privacy extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1750392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750392] Re: nplan cannot enable IPv6 privacy extensions
Hmm, this will need a YAML key added. I'll see if I can whip something up. ** Changed in: nplan (Ubuntu) Assignee: (unassigned) => Daniel Axtens (daxtens) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750392 Title: nplan cannot enable IPv6 privacy extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1750392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768006] Re: netplan apply breaks SR-IOV
Hi, I wonder if this is the replug code doing stupid stuff. That code is not long for this world anyway, but we can probably get it kicked out faster if it is indeed at fault. Could you run 'netplan --debug apply' and provide its output please? And the network card/driver that you're using (lspci -vv is probably the simplest/best way to get this.) Regards, Daniel ** Changed in: nplan (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768006 Title: netplan apply breaks SR-IOV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1768006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726478] Re: Netplan not creating .network file under certain conditions
*** This bug is a duplicate of bug 1736975 *** https://bugs.launchpad.net/bugs/1736975 Hi, (I'm trying to tidy up some old bugs so apologies if this seems a bit out of the blue!) This is a known issue and I'm pretty sure what you describe is an exact duplicate of LP: #1736975. (perhaps looking at the dates it would be fairer to say that that issue is a duplicate of this, as this was filed first! oh well.) I'm going to mark it as a duplicate for now but if that's wrong please let me know. Regards, Daniel ** This bug has been marked a duplicate of bug 1736975 netplan does not bring up anonymous bridge on boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726478 Title: Netplan not creating .network file under certain conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1726478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706680] Re: add config file to list drivers that do not support unbind
Hi! (I'm going through and trying to clean up some old bugs, so apologies if this is a bit out of the blue.) There's some work in progress to do this. I originally had a PR that would make it configurable but cyphermox has a WIP commit that will just tear out the replugging entirely: https://github.com/CanonicalLtd/netplan/commit/80c56e9f5dfcbd46d65e0bff7a7d5de46f080fe1 So there has been some thought on this and stuff will eventually happen :) Regards, Daniel ** Changed in: nplan (Ubuntu) Status: New => 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/1706680 Title: add config file to list drivers that do not support unbind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1706680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751151] Re: Installing via IPv6 results in invalid netplan yaml
Hi! (I'm going through and trying to clean up some old bugs, so apologies if this is a bit out of the blue.) I just want to confirm how you got this /etc/netplan/01-netcfg.yaml. If I understand you correctly it was created by the installer and you had to insert the quotes manually. Is that right? Or did you create it manually and it just didn't work until you inserted quotes? Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751151 Title: Installing via IPv6 results in invalid netplan yaml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1751151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619258] Re: netplan should allow NICs to be disconnected and not stall the boot
This has been in a released version of netplan.io since 0.32. Are we right to mark this as Fix Released for nplan? It looks like LP: #1664844 has been marked as Fix Released too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619258 Title: netplan should allow NICs to be disconnected and not stall the boot To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1619258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1781038] Comment bridged from LTC Bugzilla
Hi, I am told that this is the same machine but not while it was currently showing symptoms - due to the intermittent nature of the problem it was taken some time later. This matches what I see in the logs so I have no reason to doubt it. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781038 Title: KVM guest hash page table failed to allocate contiguous memory (CMA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1781038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
