[Bug 1947046] Re: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
Hi Julian, Just inquire about the 2.12 backport, is there anything I can update the customers? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947046 Title: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045322] Re: linux-image-5.4.0-1024-fips - boots to kernel panic on AMD EPYC 7262 CPU - drbg_nopr_sha512
I've sent out the SRU to fix the issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069715 will keep you posted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045322 Title: linux-image-5.4.0-1024-fips - boots to kernel panic on AMD EPYC 7262 CPU - drbg_nopr_sha512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069715] [NEW] DRBG initialization failed on some AMD EPYC series CPU and lead to kernel panic
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/2069715 [Impact] Install Focal with FIPS enabled on AMD EPYC 7262 8-Core Processor, kernel panic happens during boot: [3.430477] ima: Allocated hash algorithm: sha1 [3.433358] ima: No architecture policies found [3.435785] evm: Initialising EVM extended attributes: [3.438271] evm: security.selinux [3.440265] evm: security.SMACK64 [3.442532] evm: security.SMACK64EXEC [3.444753] evm: security.SMACK64TRANSMUTE [3.446900] evm: security.SMACK64MMAP [3.448912] evm: security.apparmor [3.452277] evm: security.ima [3.455549] evm: security.capability [3.457537] evm: HMAC attrs: 0x1 [3.461049] PM: Magic number: 12:438:677 [3.463502] rtc_cmos 00:03: setting system clock to 2024-06-18T09:40:59 UTC (1718703659) [3.467750] Kernel panic - not syncing: random: Failed to reset DRBG (drbg_nopr_ctr_aes256): -2 [3.471060] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.4.0-1100-fips #110-Ubuntu [3.474288] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS 0.0.0 02/06/2015 [3.478191] Call Trace: [3.480175] dump_stack+0x6d/0x8b [3.482652] panic+0x114/0x2f6 [3.490069] fips_drbg_init+0xa7/0xbd [3.492169] ? chr_dev_init+0x148/0x148 [3.494330] do_one_initcall+0x4a/0x200 [3.496396] kernel_init_freeable+0x1e6/0x289 [3.498967] ? rest_init+0xb0/0xb0 [3.500965] kernel_init+0xe/0x110 [3.502983] ret_from_fork+0x35/0x40 [3.505305] Kernel Offset: 0x35c0 from 0x8100 (relocation range: 0x8000-0xbfff) [3.509544] ACPI MEMORY or I/O RESET_REG. It fails to initialize DRBG, this issue doesn't happen on Intel CPU, only on some AMD EPYC series CPU. Also Jammy with FIPS enabled doesn't have this issue. [Fix] It's been fixed by this upstream commit: commit 552d03a223eda3df84526ab2c1f4d82e15eaee7a Author: Stephan Mller Date: Sun Nov 21 15:14:20 2021 +0100 crypto: jitter - consider 32 LSB for APT The APT compares the current time stamp with a pre-set value. The current code only considered the 4 LSB only. Yet, after reviews by mathematicians of the user space Jitter RNG version >= 3.1.0, it was concluded that the APT can be calculated on the 32 LSB of the time delta. Thi change is applied to the kernel. This fixes a bug where an AMD EPYC fails this test as its RDTSC value contains zeros in the LSB. The most appropriate fix would have been to apply a GCD calculation and divide the time stamp by the GCD. Yet, this is a significant code change that will be considered for a future update. Note, tests showed that constantly the GCD always was 32 on these systems, i.e. the 5 LSB were always zero (thus failing the APT since it only considered the 4 LSB for its calculation). Signed-off-by: Stephan Mueller Signed-off-by: Herbert Xu [Testcase] On AMD EPYC 7262 8-Core Processor, create a VM and enable FIPS can also reproduce the issue. I've backport the upstream commit to Focal FIPS kernel (5.4.0-1100.110-fips), the DRBG init failed message is gone: [3.267954] rtc_cmos 00:03: setting system clock to 2024-06-18T06:58:53 UTC (1718693933) [3.275683] random: random: DRBG (drbg_nopr_ctr_aes256) initialized! [3.279309] md: Waiting for all devices to be available before autodetect [Where problems could occur] This commit considers AMD EPYC CPU's RDTSC contains zero in LSB, this won't affect other cases. [Other Info] Users also reported the issue here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045322 https://askubuntu.com/questions/1509977/fips-kernel-panics-with-failed-to-reset-drbg-during-boot ** Affects: linux (Ubuntu) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Description changed: + BugLink: https://bugs.launchpad.net/bugs/2069715 + [Impact] Install Focal with FIPS enabled on AMD EPYC 7262 8-Core Processor, kernel panic happens during boot: [3.430477] ima: Allocated hash algorithm: sha1 [3.433358] ima: No architecture policies found [3.435785] evm: Initialising EVM extended attributes: [3.438271] evm: security.selinux [3.440265] evm: security.SMACK64 [3.442532] evm: security.SMACK64EXEC [3.444753] evm: security.SMACK64TRANSMUTE [3.446900] evm: security.SMACK64MMAP [3.448912] evm: security.apparmor [3.452277] evm: security.ima [3.455549] evm: security.capability [3.457537] evm: HMAC attrs: 0x1 [3.461049] PM: Magic number: 12:438:677 [3.463502] rtc_cmos 00:03: setting sys
[Bug 2045322] Re: linux-image-5.4.0-1024-fips - boots to kernel panic on AMD EPYC 7262 CPU - drbg_nopr_sha512
** Changed in: linux (Ubuntu) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (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/2045322 Title: linux-image-5.4.0-1024-fips - boots to kernel panic on AMD EPYC 7262 CPU - drbg_nopr_sha512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054343] Re: CVE-2023-4039: ARM64 GCC
Hi Matthias, Could you help to take a look into this backport for focal and jammy? really appreciate! Thanks, Gerald -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054343 Title: CVE-2023-4039: ARM64 GCC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/2054343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054343] Re: CVE-2023-4039: ARM64 GCC
The patches can be found here (re-post from comment #3): https://developer.arm.com/Arm%20Security%20Center/GCC%20Stack%20Protector%20Vulnerability%20AArch64#Technical-Specifications -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054343 Title: CVE-2023-4039: ARM64 GCC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/2054343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054343] Re: CVE-2023-4039: ARM64 GCC
I have organized the affected GCC version on Focal, Jammy and Noble. All GCC versions (10, 11, 12, 13) on Noble already include the fix. Could we also backport the fix to GCC versions on Jammy and Focal? At least GCC-9 is in main on Focal and GCC-11 is in main on Jammy. Thanks, Gerald -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054343 Title: CVE-2023-4039: ARM64 GCC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/2054343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054343] Re: CVE-2023-4039: ARM64 GCC
** Summary changed: - arm64 build of gcc-10 10.5.0-3ubuntu1 still broken (CVE-2023-4039 still open) + CVE-2023-4039: ARM64 GCC ** Also affects: gcc-11 (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-12 (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-13 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gcc-13 (Ubuntu Focal) ** No longer affects: gcc-11 (Ubuntu Focal) ** No longer affects: gcc-12 (Ubuntu Focal) ** Also affects: gcc-10 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gcc-11 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gcc-12 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gcc-13 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: gcc-10 (Ubuntu Noble) Status: New => Fix Released ** Changed in: gcc-11 (Ubuntu Noble) Status: New => Fix Committed ** Changed in: gcc-12 (Ubuntu Noble) Status: New => Fix Released ** Changed in: gcc-13 (Ubuntu Noble) Status: New => Fix Released ** Also affects: gcc-10 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gcc-11 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gcc-12 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gcc-13 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: gcc-13 (Ubuntu Jammy) ** Changed in: gcc-13 (Ubuntu) Status: New => Fix Released ** Also affects: gcc-9 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gcc-9 (Ubuntu Noble) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054343 Title: CVE-2023-4039: ARM64 GCC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/2054343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947046] Re: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
Hi Julian, Thank you very much for the info, I will update our customers about this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947046 Title: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947046] Re: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
Hi Julian, Is there any way that we can check the grub 2.12 backport status/progress, so we can keep our customers posted? Thanks, Gerald -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947046 Title: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953431] Re: [SRU] fix unsafe access in unregister_conn()
Hello @mywh The fix is merged into 15.2.16 which is currently in focal-proposed for testing if there is no regression, it will be published to focal-updates soon If you would like to run some tests to confirm the issue you are hitting has been fixed please enable focal-proposed and install 15.2.16 from there Thanks Gerald -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953431 Title: [SRU] fix unsafe access in unregister_conn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
** Changed in: linux (Ubuntu) Status: Invalid => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
Thanks a lot for the help Kleber -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
the fix in Impish is still in progress here LP: #1966021 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
This one has been merged in the last upstream stable patch set ** No longer affects: linux (Ubuntu Impish) ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Bionic) ** Changed in: linux (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
** No longer affects: linux (Ubuntu Jammy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
** Also affects: linux (Ubuntu Jammy) Importance: Critical Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** 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/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965723] [NEW] audit: improve audit queue handling when "audit=1" on cmdline
Public bug reported: SRU Justification [Impact] When an admin enables audit at early boot via the "audit=1" kernel command line the audit queue behavior is slightly different; the audit subsystem goes to greater lengths to avoid dropping records, which unfortunately can result in problems when the audit daemon is forcibly stopped for an extended period of time. [Fix] upstream discussion: https://lore.kernel.org/all/cahc9vhqgx070poxzk_pusawgzppdqvpezvfybse2dnryrbw...@mail.gmail.com/T/ upstream commit: f26d04331360d42dbd6b58448bd98e4edbfbe1c5 [Test] configurations: auditctl -b 64 auditctl --backlog_wait_time 6 auditctl -r 0 auditctl -w /root/aaa -p wrx shell scripts： #!/bin/bash i=0 while [ $i -le 66 ] do touch /root/aaa let i++ done mandatory conditions: add "audit=1" to the cmdline, and kill -19 pid_number(for /sbin/auditd). As long as we keep the audit_hold_queue non-empty, flush the hold queue will fall into an infinite loop. This could also trigger soft lockup when it drops into a infinite loop, e.g. kernel: [ 94.186433] watchdog: BUG: soft lockup - CPU#2 stuck for 11s! [kauditd:34] kernel: [ 94.187736] Modules linked in: xfs iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_ conntrack libcrc32c iptable_filter isofs xt_cgroup xt_tcpudp iptable_mangle ip_tables x_tables sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 pp dev crypto_simd glue_helper joydev vmwgfx ttm cryptd vmw_balloon drm_kms_helper intel_rapl_perf input_leds psmouse drm fb_sys_fops syscopyarea vmxnet3 sysfillrect parport_pc parport m ac_hid shpchp i2c_piix4 vmw_vsock_vmci_transport vsock sysimgblt vmw_vmci serio_raw mptspi mptscsih mptbase scsi_transport_spi pata_acpi floppy autofs4 kernel: [ 94.187757] CPU: 2 PID: 34 Comm: kauditd Not tainted 4.15.0-171-generic #180~16.04.1-Ubuntu kernel: [ 94.187757] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 kernel: [ 94.187800] skb_queue_head+0x47/0x50 kernel: [ 94.187803] kauditd_rehold_skb+0x18/0x20 kernel: [ 94.187805] kauditd_send_queue+0xcd/0x100 kernel: [ 94.187806] ? kauditd_retry_skb+0x20/0x20 kernel: [ 94.187808] ? kauditd_send_multicast_skb+0x80/0x80 kernel: [ 94.187809] kauditd_thread+0xa7/0x240 kernel: [ 94.187812] ? wait_woken+0x80/0x80 kernel: [ 94.187815] kthread+0x105/0x140 kernel: [ 94.187817] ? auditd_reset+0x90/0x90 kernel: [ 94.187818] ? kthread_bind+0x40/0x40 kernel: [ 94.187820] ret_from_fork+0x35/0x40 [Other Info] SF: #00330803 ** Affects: linux (Ubuntu) Importance: Critical Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Critical Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Critical Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Impish) Importance: Critical Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Critical Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Tags: sts ** Changed in: linux (Ubuntu) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (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/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953431] Re: [SRU] fix unsafe access in unregister_conn()
** Description changed: [Impact] without holding sufficient locks, accept_conn and shutdown_connections in AsyncMessenger could cause OSD processes crash [Test plan] + run ceph_test_async_networkstack repeatedly, this will trigger many async messenger events and make sure + 1. OSD process not crash + 2. no deadlock [Where problems could occur] hold sufficient locks and decrement l_msgr_active_connections can avoid OSD processes to crash due to race condition The only problem I can imagine is deadlock if one process is holding lock A and wait for lock B, the there is another process holding lock B and wait for lock A - [Other info] from upstream: octopus backport tracker https://tracker.ceph.com/issues/50482 octopus backport PR https://github.com/ceph/ceph/pull/43325 ** Patch added: "0001-msgr-async-fix-unsafe-access-in-unregister_conn.patch" https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953431/+attachment/5546429/+files/0001-msgr-async-fix-unsafe-access-in-unregister_conn.patch ** Tags added: sts sts-sru-needed verification-needed-focal ** Also affects: ceph (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ceph (Ubuntu Focal) Status: New => In Progress ** Changed in: ceph (Ubuntu Focal) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953431 Title: [SRU] fix unsafe access in unregister_conn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945555] Re: [SRU] accept undecodable multi-block bluefs transactions on log
** Description changed:
[Impact]
Multi-block transaction could fail during unexpected power down
in this case, it should be stop replaying this log instead of throwing
unrecoverable error
[Test Case]
It's too difficult to simulate power outage during multi-block transaction on
disk, so the way I test this patch is to simulate a multi-block transaction and
trigger a decode error in
try {
- auto p = bl.cbegin();
- decode(t, p);
- seen_recs = true;
- }
+ auto p = bl.cbegin();
+ decode(t, p);
+ seen_recs = true;
+ }
Add the following line right after decode(t, p) to throw an error
throw buffer::malformed_input("error test");
According to the patch description https://github.com/ceph/ceph/pull/42830
this error will be considered as a normal bluefs log reply stop condition and
will *not* prevent OSD from starting
After the error test is triggered, OSD can still be started normally
[Where problems could occur]
- This upstream PR was created 2 months ago and Luminous was EOL upstream for a
while
- so Luminous Bluefs code is outdated, in order to backport this commit
- it might also need to backport some dependencies
+ This upstream PR was created 2 months ago and Luminous was EOL upstream for a
while, so no backport and test by upstream
+ In order to backport this commit, it also needs to backport some dependencies
[Other Info]
upstream tracker: https://tracker.ceph.com/issues/52079
PR: https://github.com/ceph/ceph/pull/42830
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194
Title:
[SRU] accept undecodable multi-block bluefs transactions on log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/194/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953426] Re: [SRU] configurable threshold for reaping dead connections and add a unit test
** Description changed: [Impact] add a configurable threshold for reaping dead connections and fix cephfs test case [Test plan] run ceph qa tests in: qa/tasks/cephfs/test_sessionmap.py this also verifies the configurable threshold steps to run: 1. build ceph from source folder 2. go to build folder 3. run all tests in test_sessionmap.py, e.g. python ../qa/tasks/vstart_runner.py tasks.cephfs.test_sessionmap.TestSessionMap.test_mount_conn_close python ../qa/tasks/vstart_runner.py tasks.cephfs.test_sessionmap.TestSessionMap.test_tell_session_drop ... [Where problems could occur] these patches only add a configuration and fix the test case - it can also be tested by ceph qa tests explained above - and they also passed all the qa tests upstream and been merged by upstream, I don't think there will be any regression + the only problem I can imagine is someone set this config to a non-sense value [Other info] from upstream: octopus backport tracker https://tracker.ceph.com/issues/51199 octopus backport PR https://github.com/ceph/ceph/pull/43310 ** Description changed: [Impact] add a configurable threshold for reaping dead connections and fix cephfs test case [Test plan] run ceph qa tests in: qa/tasks/cephfs/test_sessionmap.py this also verifies the configurable threshold steps to run: 1. build ceph from source folder 2. go to build folder 3. run all tests in test_sessionmap.py, e.g. python ../qa/tasks/vstart_runner.py tasks.cephfs.test_sessionmap.TestSessionMap.test_mount_conn_close python ../qa/tasks/vstart_runner.py tasks.cephfs.test_sessionmap.TestSessionMap.test_tell_session_drop ... [Where problems could occur] these patches only add a configuration and fix the test case - the only problem I can imagine is someone set this config to a non-sense value + the only problem I can imagine is someone sets this config to a non-sense value [Other info] from upstream: octopus backport tracker https://tracker.ceph.com/issues/51199 octopus backport PR https://github.com/ceph/ceph/pull/43310 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953426 Title: [SRU] configurable threshold for reaping dead connections and add a unit test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953431] Re: [SRU] fix unsafe access in unregister_conn()
** Description changed: [Impact] without holding sufficient locks, accept_conn and shutdown_connections in AsyncMessenger could cause OSD processes crash - [Test case] + [Test plan] + + [Where problems could occur] + hold sufficient locks and decrement l_msgr_active_connections can avoid OSD processes to crash due to race condition + The only problem I can imagine is deadlock if one process is holding lock A and wait for lock B, the there is another process holding lock B and wait for lock A - [Regression potential] - low, hold sufficient locks and decrement l_msgr_active_connections shouldn't cause any regressions - - [Additional information] + [Other info] from upstream: octopus backport tracker https://tracker.ceph.com/issues/50482 octopus backport PR https://github.com/ceph/ceph/pull/43325 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953431 Title: [SRU] fix unsafe access in unregister_conn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953426] Re: [SRU] configurable threshold for reaping dead connections and add a unit test
** Description changed: [Impact] add a configurable threshold for reaping dead connections and fix cephfs test case [Test plan] run ceph qa tests in: qa/tasks/cephfs/test_sessionmap.py this also verifies the configurable threshold steps to run: 1. build ceph from source folder 2. go to build folder 3. run all tests in test_sessionmap.py, e.g. python ../qa/tasks/vstart_runner.py tasks.cephfs.test_sessionmap.TestSessionMap.test_mount_conn_close python ../qa/tasks/vstart_runner.py tasks.cephfs.test_sessionmap.TestSessionMap.test_tell_session_drop ... [Where problems could occur] - None, only add a configuration and also be tested by ceph qa tests + these patches only add a configuration and fix the test case + it can also be tested by ceph qa tests explained above + and they also passed all the qa tests upstream and been merged by upstream, I don't think there will be any regression [Other info] from upstream: octopus backport tracker https://tracker.ceph.com/issues/51199 octopus backport PR https://github.com/ceph/ceph/pull/43310 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953426 Title: [SRU] configurable threshold for reaping dead connections and add a unit test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953426] Re: [SRU] configurable threshold for reaping dead connections and add a unit test
** Description changed: [Impact] add a configurable threshold for reaping dead connections and fix cephfs test case - - [Test case] + [Test plan] run ceph qa tests in: qa/tasks/cephfs/test_sessionmap.py this also verifies the configurable threshold steps to run: 1. build ceph from source folder 2. go to build folder 3. run all tests in test_sessionmap.py, e.g. python ../qa/tasks/vstart_runner.py tasks.cephfs.test_sessionmap.TestSessionMap.test_mount_conn_close python ../qa/tasks/vstart_runner.py tasks.cephfs.test_sessionmap.TestSessionMap.test_tell_session_drop ... + [Where problems could occur] + None, only add a configuration and also be tested by ceph qa tests - [Regression potential] - only add a configuration, no regression potential - - [Additional information] + [Other info] from upstream: octopus backport tracker https://tracker.ceph.com/issues/51199 octopus backport PR https://github.com/ceph/ceph/pull/43310 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953426 Title: [SRU] configurable threshold for reaping dead connections and add a unit test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953426] Re: [SRU] configurable threshold for reaping dead connections and add a unit test
** Tags added: sts sts-sru-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953426 Title: [SRU] configurable threshold for reaping dead connections and add a unit test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953431] [NEW] [SRU] fix unsafe access in unregister_conn()
Public bug reported: [Impact] without holding sufficient locks, accept_conn and shutdown_connections in AsyncMessenger could cause OSD processes crash [Test case] [Regression potential] low, hold sufficient locks and decrement l_msgr_active_connections shouldn't cause any regressions [Additional information] from upstream: octopus backport tracker https://tracker.ceph.com/issues/50482 octopus backport PR https://github.com/ceph/ceph/pull/43325 ** Affects: ceph (Ubuntu) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Changed in: ceph (Ubuntu) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: ceph (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/1953431 Title: [SRU] fix unsafe access in unregister_conn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953426] Re: [SRU] configurable threshold for reaping dead connections and add a unit test
** Changed in: ceph (Ubuntu Focal) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: ceph (Ubuntu Focal) 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/1953426 Title: [SRU] configurable threshold for reaping dead connections and add a unit test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953426] Re: [SRU] configurable threshold for reaping dead connections and add a unit test
first patch ** Patch added: "0001-msg-async-configurable-threshold-for-reaping-dead-co.patch" https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953426/+attachment/5545880/+files/0001-msg-async-configurable-threshold-for-reaping-dead-co.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953426 Title: [SRU] configurable threshold for reaping dead connections and add a unit test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953426] Re: [SRU] configurable threshold for reaping dead connections and add a unit test
second patch ** Patch added: "0002-qa-tasks-cephfs-test_sessionmap-reap-connections-imm.patch" https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953426/+attachment/5545881/+files/0002-qa-tasks-cephfs-test_sessionmap-reap-connections-imm.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953426 Title: [SRU] configurable threshold for reaping dead connections and add a unit test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953426] [NEW] [SRU] configurable threshold for reaping dead connections and add a unit test
Public bug reported: [Impact] add a configurable threshold for reaping dead connections and fix cephfs test case [Test case] run ceph qa tests in: qa/tasks/cephfs/test_sessionmap.py this also verifies the configurable threshold steps to run: 1. build ceph from source folder 2. go to build folder 3. run all tests in test_sessionmap.py, e.g. python ../qa/tasks/vstart_runner.py tasks.cephfs.test_sessionmap.TestSessionMap.test_mount_conn_close python ../qa/tasks/vstart_runner.py tasks.cephfs.test_sessionmap.TestSessionMap.test_tell_session_drop ... [Regression potential] only add a configuration, no regression potential [Additional information] from upstream: octopus backport tracker https://tracker.ceph.com/issues/51199 octopus backport PR https://github.com/ceph/ceph/pull/43310 ** Affects: ceph (Ubuntu) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: ceph (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ceph (Ubuntu) Status: New => In Progress ** Changed in: ceph (Ubuntu) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Also affects: ceph (Ubuntu Focal) 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/1953426 Title: [SRU] configurable threshold for reaping dead connections and add a unit test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945555] Re: [SRU] accept undecodable multi-block bluefs transactions on log
Update test case
It's too difficult to simulate power outage during multi-block transaction on
disk, so the way I test this patch is to simulate a multi-block transaction and
trigger a decode error in
try {
auto p = bl.cbegin();
decode(t, p);
seen_recs = true;
}
Add the following line right after decode(t, p) to throw an error
throw buffer::malformed_input("error test");
According to the patch description https://github.com/ceph/ceph/pull/42830
this error will be considered as a normal bluefs log reply stop condition and
will *not* prevent OSD from starting
After the error test is triggered, OSD can still be started normally
** Description changed:
[Impact]
Multi-block transaction could fail during unexpected power down
in this case, it should be stop replaying this log instead of throwing
unrecoverable error
[Test Case]
- need to simulate power outage to reproduce this issue
+ It's too difficult to simulate power outage during multi-block transaction on
disk, so the way I test this patch is to simulate a multi-block transaction and
trigger a decode error in
+ try {
+ auto p = bl.cbegin();
+ decode(t, p);
+ seen_recs = true;
+ }
+
+ Add the following line right after decode(t, p) to throw an error
+ throw buffer::malformed_input("error test");
+
+ According to the patch description https://github.com/ceph/ceph/pull/42830
+ this error will be considered as a normal bluefs log reply stop condition and
will *not* prevent OSD from starting
+ After the error test is triggered, OSD can still be started normally
[Where problems could occur]
This upstream PR was created 2 months ago and Luminous was EOL upstream for a
while
so Luminous Bluefs code is outdated, in order to backport this commit
it might also need to backport some dependencies
[Other Info]
upstream tracker: https://tracker.ceph.com/issues/52079
PR: https://github.com/ceph/ceph/pull/42830
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194
Title:
[SRU] accept undecodable multi-block bluefs transactions on log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/194/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945555] Re: [SRU] accept undecodable multi-block bluefs transactions on log
second patch ** Patch added: "bionic2.patch" https://bugs.launchpad.net/ubuntu/bionic/+source/ceph/+bug/194/+attachment/5533790/+files/bionic2.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/194 Title: [SRU] accept undecodable multi-block bluefs transactions on log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945555] Re: [SRU] accept undecodable multi-block bluefs transactions on log
This PR https://github.com/ceph/ceph/pull/42830 need an additional dependency (bionic1.patch) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/194 Title: [SRU] accept undecodable multi-block bluefs transactions on log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945555] Re: [SRU] accept undecodable multi-block bluefs transactions on log
first patch ** Tags added: sts sts-sru-needed verification-needed-bionic ** Patch added: "bionic1.patch" https://bugs.launchpad.net/ubuntu/bionic/+source/ceph/+bug/194/+attachment/5533789/+files/bionic1.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/194 Title: [SRU] accept undecodable multi-block bluefs transactions on log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945555] Re: [SRU] accept undecodable multi-block bluefs transactions on log
** Changed in: ceph (Ubuntu Bionic) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: ceph (Ubuntu) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: ceph (Ubuntu Bionic) Status: New => In Progress ** Changed in: ceph (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/194 Title: [SRU] accept undecodable multi-block bluefs transactions on log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945555] [NEW] [SRU] accept undecodable multi-block bluefs transactions on log
Public bug reported: [Impact] Multi-block transaction could fail during unexpected power down in this case, it should be stop replaying this log instead of throwing unrecoverable error [Test Case] need to simulate power outage to reproduce this issue [Where problems could occur] This upstream PR was created 2 months ago and Luminous was EOL upstream for a while so Luminous Bluefs code is outdated, in order to backport this commit it might also need to backport some dependencies [Other Info] upstream tracker: https://tracker.ceph.com/issues/52079 PR: https://github.com/ceph/ceph/pull/42830 ** Affects: ceph (Ubuntu) Importance: Undecided Status: New ** Affects: ceph (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ceph (Ubuntu Bionic) 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/194 Title: [SRU] accept undecodable multi-block bluefs transactions on log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910976] Re: Cherry-pick dm-crypt performance improvement patch from Linux 5.9
** Description changed: === SRU Justification === [Impact] - To get better performance for dm-crypt in some cases, bypass kcryptd workqueue can reduce the overhead in context switch between workers, cherry-pick commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 from mainline kernel, and this is not enabled by default + To get better performance for dm-crypt in some cases, bypass kcryptd workqueue can reduce the overhead in context switch between workers, cherry-pick commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 from mainline kernel, and bypass kcryptd workqueue is not enabled by default [Fix] Add flags to bypass kcryptd workqueue [Test] create dm-crypt and setup DM_CRYPT_NO_READ_WORKQUEUE and DM_CRYPT_NO_WRITE_WORKQUEUE, read/write data and run perf record to see if read/write to the encrypted device will bypass kcryptd workqueue [Regression Potential] Low, this feature is disabled by default, need to enable manually = original bug description = Hi, I'm asking if it would be possible to cherry-pick patch "dm crypt: add flags to optionally bypass kcryptd workqueues" into the 5.4 Ubuntu kernel. This patch has been merged in mainline kernel 5.9 https://github.com/torvalds/linux/commit/39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 but was not tagged for the stable tree. This patch provides important performance gains for some workloads using dm-crypt / LUKS and cherry-picking it would be very beneficial for dm- crypt users. You can find details on the expected gain in the following links: * https://www.redhat.com/archives/dm-devel/2020-July/msg00138.html * https://blog.cloudflare.com/speeding-up-linux-disk-encryption/ The patch mostly applies cleanly on the Ubuntu 5.4 kernel, the only merge conflict is due to the module version at the end of the patch. I can provide a backport patch if needed. Thanks, ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910976 Title: Cherry-pick dm-crypt performance improvement patch from Linux 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910976] Re: Cherry-pick dm-crypt performance improvement patch from Linux 5.9
** Description changed: + === SRU Justification === + [Impact] + To get better performance for dm-crypt in some cases, bypass kcryptd workqueue can reduce the overhead in context switch between workers, cherry-pick commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 from mainline kernel, and this is not enabled by default + + [Fix] + Add flags to bypass kcryptd workqueue + + [Test] + create dm-crypt and setup DM_CRYPT_NO_READ_WORKQUEUE and DM_CRYPT_NO_WRITE_WORKQUEUE, read/write data and run perf record to see if read/write to the encrypted device will bypass kcryptd workqueue + + [Regression Potential] + Low, this feature is disabled by default, need to enable manually + + = original bug description = Hi, I'm asking if it would be possible to cherry-pick patch "dm crypt: add flags to optionally bypass kcryptd workqueues" into the 5.4 Ubuntu kernel. This patch has been merged in mainline kernel 5.9 https://github.com/torvalds/linux/commit/39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 but was not tagged for the stable tree. This patch provides important performance gains for some workloads using dm-crypt / LUKS and cherry-picking it would be very beneficial for dm- crypt users. You can find details on the expected gain in the following links: * https://www.redhat.com/archives/dm-devel/2020-July/msg00138.html * https://blog.cloudflare.com/speeding-up-linux-disk-encryption/ The patch mostly applies cleanly on the Ubuntu 5.4 kernel, the only merge conflict is due to the module version at the end of the patch. I can provide a backport patch if needed. Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910976 Title: Cherry-pick dm-crypt performance improvement patch from Linux 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910976] Re: Cherry-pick dm-crypt performance improvement patch from Linux 5.9
** Changed in: linux (Ubuntu) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** 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/1910976 Title: Cherry-pick dm-crypt performance improvement patch from Linux 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
** Changed in: cloud-archive/train Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
The ceph package in groovy-proposed fixes this issue Detail steps: 1. deploy grovvy+octopus 2. add grovvy-proposed 3. upgrade to 15.2.8-0ubuntu0.20.10.1 4. set osd_op_complaint_time to 0.1 for generating slow requests 5. run rados bench 6. check there are slow requests in OSD logs 7. check there is NO slow request details in ceph.log ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
The ceph package in focal-proposed fixes this issue Detail steps: 1. deploy focal+octopus 2. add focal-proposed 3. upgrade to 15.2.8-0ubuntu0.20.04.1 4. set osd_op_complaint_time to 0.1 for generating slow requests 5. run rados bench 6. check there are slow requests in OSD logs 7. check there is NO slow request details in ceph.log ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
In comment #15, the detail step 4 is 4. add cloud-archive:ussuri-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
The ceph package in ussuri-proposed fixes this issue Detail steps: 1. deploy bionic+luminous 2. add cloud-archive:train 3. upgrade ceph to nautilus 4. add cloud-archive:ussuri 5. upgrade ceph to octopus 6. set osd_op_complaint_time to 0.1 for generating slow requests 7. run rados bench 8. check there are slow requests in OSD logs 9. check there is NO slow request details in ceph.log ** Tags removed: verification-ussuri-needed ** Tags added: verification-ussuri-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
Open a upstream ceph tracker for further discussion: https://tracker.ceph.com/issues/48909 ** Bug watch added: tracker.ceph.com/issues #48909 http://tracker.ceph.com/issues/48909 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
ussuri patch ** Patch added: "ussuri.patch" https://bugs.launchpad.net/cloud-archive/+bug/1909162/+attachment/5449906/+files/ussuri.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
train patch ** Patch added: "train.patch" https://bugs.launchpad.net/cloud-archive/+bug/1909162/+attachment/5449905/+files/train.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
hirsute patch ** Patch added: "hirsute.patch" https://bugs.launchpad.net/cloud-archive/+bug/1909162/+attachment/5449904/+files/hirsute.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
groovy patch ** Patch added: "groovy.patch" https://bugs.launchpad.net/cloud-archive/+bug/1909162/+attachment/5449903/+files/groovy.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
focal patch ** Patch added: "focal.patch" https://bugs.launchpad.net/cloud-archive/+bug/1909162/+attachment/5449902/+files/focal.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
Add patch ** Patch added: "0001-Remove-logging-every-slow-request-details-to-monito.patch" https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1909162/+attachment/5448256/+files/0001-Remove-logging-every-slow-request-details-to-monito.patch ** Tags added: sts-sru-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909162] Re: cluster log slow request spam
** Changed in: cloud-archive/train Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: cloud-archive/ussuri Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: ceph (Ubuntu Focal) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: ceph (Ubuntu Groovy) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: ceph (Ubuntu Hirsute) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909162 Title: cluster log slow request spam To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1909162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861793] Re: [SRU] ceph 12.2.13
Hi James, Do you have any idea when this will be released? thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861793 Title: [SRU] ceph 12.2.13 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1861793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
The new kernel in xenial-proposed fixes this issue, i40evf is included in linux-modules kernel version: 4.4.0-171 old in xenial-update: dpkg -L linux-modules-4.4.0-170-generic | grep 'i40e' /lib/modules/4.4.0-170-generic/kernel/drivers/net/ethernet/intel/i40e /lib/modules/4.4.0-170-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko new in xenial-proposed: dpkg -L linux-modules-4.4.0-171-generic | grep i40e /lib/modules/4.4.0-171-generic/kernel/drivers/net/ethernet/intel/i40evf /lib/modules/4.4.0-171-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko /lib/modules/4.4.0-171-generic/kernel/drivers/net/ethernet/intel/i40e /lib/modules/4.4.0-171-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko ** 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847822] Re: CephFS authorize fails with unknown cap type
The ceph packages in bionic-proposed fixes this issue Some details on different nodes On ceph-mon node: ubuntu@juju-aad762-246395-1-0:~$ apt-cache policy ceph ceph: Installed: 12.2.12-0ubuntu0.18.04.4 Candidate: 12.2.12-0ubuntu0.18.04.4 Version table: *** 12.2.12-0ubuntu0.18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 12.2.12-0ubuntu0.18.04.3 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 12.2.12-0ubuntu0.18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 12.2.4-0ubuntu1 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ubuntu@juju-aad762-246395-1-0:~$ ceph fs authorize ceph-fs client.foo / rw [client.foo] key = AQC8EuZdrBm7ERAA7ZaAruEDz3glRMDnPvmWRQ== ubuntu@juju-aad762-246395-1-0:~$ ceph fs authorize ceph-fs client.bar /bar rw [client.bar] key = AQA+E+ZdoyyENxAAqNXma0Pdq9CaG0rlLL0otQ== On ceph-fs node: ubuntu@juju-aad762-246395-1-7:~$ apt-cache policy ceph ceph: Installed: 12.2.12-0ubuntu0.18.04.4 Candidate: 12.2.12-0ubuntu0.18.04.4 Version table: *** 12.2.12-0ubuntu0.18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 12.2.12-0ubuntu0.18.04.3 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 12.2.12-0ubuntu0.18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 12.2.4-0ubuntu1 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ubuntu@juju-aad762-246395-1-7:~$ sudo ceph-fuse -c ceph.conf --id foo -k client.foo.keyring mnt ceph-fuse[2553]: starting ceph client 2019-12-03 07:47:40.128237 7f423c183500 -1 init, newargv = 0x55a9692d02e0 newargc=9 ceph-fuse[2553]: starting fuse ubuntu@juju-aad762-246395-1-7:~$ ls mnt ubuntu@juju-aad762-246395-1-7:~$ sudo mkdir mnt/bar ubuntu@juju-aad762-246395-1-7:~$ ls mnt/ bar ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847822 Title: CephFS authorize fails with unknown cap type To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1847822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847822] Re: CephFS authorize fails with unknown cap type
** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847822 Title: CephFS authorize fails with unknown cap type To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1847822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847822] Re: CephFS authorize fails with unknown cap type
The ceph packages in queens-proposed fixes this issue Some details on different nodes On ceph-mon node: ubuntu@juju-590627-246395-0:~$ apt-cache policy ceph ceph: Installed: 12.2.12-0ubuntu0.18.04.4 Candidate: 12.2.12-0ubuntu0.18.04.4 Version table: *** 12.2.12-0ubuntu0.18.04.4 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 12.2.12-0ubuntu0.18.04.3 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 12.2.12-0ubuntu0.18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 12.2.4-0ubuntu1 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ubuntu@juju-590627-246395-0:~$ ceph fs authorize ceph-fs client.foo / rw [client.foo] key = AQCiAeZd+PTmHhAAh2VDxBu1JJR7qr5lfLavaw== ubuntu@juju-590627-246395-0:~$ ceph fs authorize ceph-fs client.bar /bar rw [client.bar] key = AQC2COZdxTytDxAAtY3oVcjK8XqzlFf0oRlzWQ== On ceph-fs node: ubuntu@juju-590627-246395-7:~$ apt-cache policy ceph ceph: Installed: 12.2.12-0ubuntu0.18.04.4 Candidate: 12.2.12-0ubuntu0.18.04.4 Version table: *** 12.2.12-0ubuntu0.18.04.4 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 12.2.12-0ubuntu0.18.04.3 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 12.2.12-0ubuntu0.18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 12.2.4-0ubuntu1 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ubuntu@juju-590627-246395-7:~$ sudo ceph-fuse -c ceph.conf --id foo -k client.foo.keyring mnt ceph-fuse[4198]: starting ceph client 2019-12-03 07:01:22.855304 7fb6a87f6500 -1 init, newargv = 0x559f708262e0 newargc=9 ceph-fuse[4198]: starting fuse ubuntu@juju-590627-246395-7:~$ ls mnt/ ubuntu@juju-590627-246395-7:~$ sudo mkdir mnt/bar ubuntu@juju-590627-246395-7:~$ ls mnt bar ** Tags removed: verification-needed verification-queens-needed ** Tags added: verification-done verification-queens-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847822 Title: CephFS authorize fails with unknown cap type To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1847822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847544] Re: backport: S3 policy evaluated incorrectly
bionic patch ** Patch added: "bionic.patch" https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1847544/+attachment/5309188/+files/bionic.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847544 Title: backport: S3 policy evaluated incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1847544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847544] Re: backport: S3 policy evaluated incorrectly
** Changed in: cloud-archive Status: New => In Progress ** Changed in: cloud-archive Assignee: (unassigned) => gerald.yang (gerald-yang-tw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847544 Title: backport: S3 policy evaluated incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1847544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847544] Re: backport: S3 policy evaluated incorrectly
Disco, Eoan and Focal has already included this fix ** Changed in: ceph (Ubuntu Focal) Status: In Progress => Won't Fix ** Changed in: ceph (Ubuntu Eoan) Status: New => Won't Fix ** Changed in: ceph (Ubuntu Disco) Status: New => Won't Fix ** Changed in: ceph (Ubuntu Focal) Assignee: gerald.yang (gerald-yang-tw) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847544 Title: backport: S3 policy evaluated incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1847544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847544] Re: backport: S3 policy evaluated incorrectly
** Also affects: ceph (Ubuntu Focal) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Also affects: ceph (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: ceph (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Tags removed: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847544 Title: backport: S3 policy evaluated incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1847544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Xenial) 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852663] Re: i40e: general protection fault in i40e_config_vf_promiscuous_mode
** 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/1852663 Title: i40e: general protection fault in i40e_config_vf_promiscuous_mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852663] [NEW] i40e: general protection fault in i40e_config_vf_promiscuous_mode
Public bug reported: SRU Justification [Impact] Assign some VFs to VMs, when deleting VMs, a general protection fault occurs in i40e_config_vf_promiscuous_mode general protection fault: [#1] SMP PTI CPU: 54 PID: 6200 Comm: libvirtd Not tainted 5.3.0-21-generic #22~18.04.1-UbuntuHardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 05/21/2019 RIP: 0010:i40e_config_vf_promiscuous_mode+0x172/0x330 [i40e] Code: 48 8b 00 83 d1 00 48 85 c0 75 ef 49 83 c4 08 4c 39 e6 75 dd 85 c9 74 73 0f b6 45 c0 45 31 d2 89 45 d0 4d 8b 3e 4d 85 ff 74 53 <41> 0f b7 4f 16 66 81 f9 ff 0f 77 3f 0f b7 b3 ea 0c 00 00 8b 55 d0 RSP: 0018:b987b5c77760 EFLAGS: 00010202 RAX: RBX: 9bb5df5a9000 RCX: RDX: RSI: 0600 RDI: 9bace4bce350 RBP: b987b5c777b0 R08: R09: 9bace56a9da0 R10: R11: 0100 R12: 9bb5df5a9a28 R13: 9bace4bce008 R14: 9bb5df5a9338 R15: 26c2b975d54f5980 FS: 7f9f07fff700() GS:9bfcff48() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fa73c9c0e10 CR3: 00f6ab37a002 CR4: 007626e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: i40e_ndo_set_vf_port_vlan+0x1a2/0x440[i40e] do_setlink+0x53f/0xee0 ?update_load_avg+0x596/0x620 ?update_curr+0x7a/0x1d0 ?__switch_to_asm+0x40/0x70 ?__switch_to_asm+0x34/0x70 ?__switch_to_asm+0x40/0x70 ?__switch_to_asm+0x34/0x70 rtnl_setlink+0x113/0x150 rtnetlink_rcv_msg+0x296/0x340 ?aa_label_sk_perm.part.4+0x10f/0x160 ?_cond_resched+0x19/0x40 ?rtnl_calcit.isra.30+0x120/0x120 netlink_rcv_skb+0x51/0x120 rtnetlink_rcv+0x15/0x20 netlink_unicast+0x1a4/0x250 netlink_sendmsg+0x2d7/0x3d0 sock_sendmsg+0x63/0x70 ___sys_sendmsg+0x2a9/0x320 ?aa_label_sk_perm.part.4+0x10f/0x160 ?_raw_spin_unlock_bh+0x1e/0x20 ?release_sock+0x8f/0xa0 __sys_sendmsg+0x63/0xa0 ?__sys_sendmsg+0x63/0xa0 __x64_sys_sendmsg+0x1f/0x30 do_syscall_64+0x5a/0x130 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This issue also happens when deleting k8s pod if VF is used by k8s pod, there was a bug reported in the e1000-devel mailing list https://sourceforge.net/p/e1000/mailman/message/36766306/ The fix is suggested by Billy McFall, to add protection when accessing the hash list(vsi->mac_filter_hash), but it's not upstream yet [Test Case] Spin up some VMs with VFs, then delete all VMs [Regression Potential] Low, the fix is to add a protection for a hash list, shouldn't have potential regression ** Affects: linux (Ubuntu) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) 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/1852663 Title: i40e: general protection fault in i40e_config_vf_promiscuous_mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847544] Re: backport: S3 policy evaluated incorrectly
** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847544 Title: backport: S3 policy evaluated incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1847544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847544] Re: backport: S3 policy evaluated incorrectly
** Description changed: [Impact] If a user tries to access a non-existent bucket, it should get a 'NoSuchBucket' error message (404) But if there is such a bucket which is belonged to another user, radosgw will return 'AccessDenied' error (403) This is an incorrect error message, radosgw should return 404 - [Test Case] Create a user by radosgw-admin, then create a bucket through S3 by this user Create another user and try to access the bucket created by the above user The error message must be 'NoSuchBucket', not 'AccessDenied' [Regression Potential] - Low + Low, this patch checks + 1. 'is_admin_of' and 'verify_permission' separately instead of 'and' the results of them + 2. if the bucket policy allow the user to access this bucket + to make sure it returns the correct error code, so basically it checks the same thing as before but in the correct order [Other Information] Backport Ceph issue 38638 to Luminous. If a user different from the owner (or even an anonymous user) does a GetObject/HeadObject on a non existing object, Radosgw returns status code 403, rather than the correct status 404. A version of this was merged into Ceph master: https://tracker.ceph.com/issues/38638 https://github.com/ceph/ceph/commit/5eb50b7d10da51db72f705807c87775562b79b63 And backported to luminous has been accepted: https://tracker.ceph.com/issues/39272 https://github.com/ceph/ceph/commit/a752b21f549cc83745e35324387b85b3d039dfd2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847544 Title: backport: S3 policy evaluated incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1847544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847544] Re: backport: S3 policy evaluated incorrectly
** Description changed: - ## DRAFT ## + [Impact] + If a user tries to access a non-existent bucket, it should get a 'NoSuchBucket' error message (404) + But if there is such a bucket which is belonged to another user, radosgw will return 'AccessDenied' error (403) + This is an incorrect error message, radosgw should return 404 - [Impact] [Test Case] + Create a user by radosgw-admin, then create a bucket through S3 by this user + Create another user and try to access the bucket created by the above user + The error message must be 'NoSuchBucket', not 'AccessDenied' [Regression Potential] + Low - [Other Info] - - [Original Description] + [Other Information] Backport Ceph issue 38638 to Luminous. If a user different from the owner (or even an anonymous user) does a GetObject/HeadObject on a non existing object, Radosgw returns status code 403, rather than the correct status 404. A version of this was merged into Ceph master: https://tracker.ceph.com/issues/38638 https://github.com/ceph/ceph/commit/5eb50b7d10da51db72f705807c87775562b79b63 - And backported (acceptance pending): + And backported to luminous has been accepted: https://tracker.ceph.com/issues/39272 https://github.com/ceph/ceph/commit/a752b21f549cc83745e35324387b85b3d039dfd2 ** Tags added: sts-sru-needed ** Also affects: ceph (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ceph (Ubuntu Bionic) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: ceph (Ubuntu Bionic) 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/1847544 Title: backport: S3 policy evaluated incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1847544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847544] Re: backport: S3 policy evaluated incorrectly
** Changed in: ceph (Ubuntu) Assignee: Jesse Williamson (chardan) => gerald.yang (gerald-yang-tw) ** Changed in: ceph (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/1847544 Title: backport: S3 policy evaluated incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1847544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
** Changed in: linux (Ubuntu Bionic) 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
** Description changed: - For example with bionic, i40evf module is in linux-modules- - extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra - seeded: + === SRU Justification === + [Impact] + Intel's VF drivers such as igbvf and ixgbevf are already available in + generic. It makes sense to add i40evf especially for SR-IOV enabled clouds with Intel X710/XXV710/XL710. + + [Fix] + Add i40evf to linux-modules package + + [Test] + Extract linux-modules to check if i40evf is there + + [Regression Potential] + Low + + = original bug description = + For example with bionic, i40evf module is in linux-modules-extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR- IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Nobuto Murata (nobuto) Status: Fix Committed ** Also affects: livecd-rootfs (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718388] Re: Fix OpenNSL GPL bugs found by CoverityScan static analysis
Verified linux-image-4.4.0-100-generic on AS7712, it works find, all broadcom modules are loaded and bcm0 interface is created successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718388 Title: Fix OpenNSL GPL bugs found by CoverityScan static analysis To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696162] Re: brcmfmac does not support unbinding
Verify the new nplan_0.23~16.04.1_amd64.deb on Ubuntu Core 16 (download from xenial-proposed), Test pass. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696162 Title: brcmfmac does not support unbinding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1696162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1497883] Re: cat of long files breaks dropbear ssh connection
This debdiff comes from comment #10 to fix the bug ** Patch added: "dropbear_2013.60-1ubuntu2.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1497883/+attachment/4870747/+files/dropbear_2013.60-1ubuntu2.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1497883 Title: cat of long files breaks dropbear ssh connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1497883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642118] Re: Several TPM2.0 tests fail
For the three failures, the meaning of error code: 1. test_tpm2_unseal.sh u@u-Embedded-Box-PC-3000:~/tpm2.0-tools/test/system$ tpm2_rc_decode 0x9a2 error layer hex: 0x0 identifier: TSS2_TPM_ERROR_LEVEL description: Error produced by the TPM format 1 error code hex: 0x22 identifier: TPM_RC_BAD_AUTH description: authorization failure without DA implications session hex: 0x100 identifier: TPM_RC_1 description: (null) Not sure if this error 0x9a2 relates to comment #3 2. test_tpm2_encryptdecrypt.sh u@u-Embedded-Box-PC-3000:~/tpm2.0-tools/test/system$ tpm2_rc_decode 0x143 error layer hex: 0x0 identifier: TSS2_TPM_ERROR_LEVEL description: Error produced by the TPM format 0 error code hex: 0x43 name: TPM_RC_COMMAND_CODE description: command code not supported 0x143 means command code not supported. 3. test_tpm2_quote.sh u@u-Embedded-Box-PC-3000:~/tpm2.0-tools/test/system$ tpm2_rc_decode 0x1d5 error layer hex: 0x0 identifier: TSS2_TPM_ERROR_LEVEL description: Error produced by the TPM format 1 error code hex: 0x15 identifier: TPM_RC_SIZE description: structure is the wrong size parameter hex: 0x100 identifier: TPM_RC_1 description: (null) Not sure if it's a bug in tool for 0x1d5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642118 Title: Several TPM2.0 tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1642118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen
@Zygmunt So does it mean even I add a configure hook in meta/hooks/ to copy those binaries to boot partition (/boot/uboot/), there is no such interface in snapd to allow this? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647936 Title: Raspberry Pi 3: a small rainbow square on the top right of screen To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
I am seeing this issue too, but in my case, it seems there is something wrong in bbswitch-dkms, if I remove it manually by 'sudo rm /lib/modules/4.4.0-xx-generic/updates/dkms/bbswitch.ko' I can boot into system with both intel and nvidia mode (prime-select intel or prime- select nvidia). Since nvidia-prime depends on bbswitch-dkms, I can not remove bbswitch- dkms by 'apt remove', so the temporary solution for me is to remove the kernel module. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642118] Re: Several TPM2.0 tests fail
I tried the latest tpm2.0-tools on github, but most of tests are failed cat test_all_fail.log test_tpm2_takeownership_all.sh fail test_tpm2_nv.sh fail test_tpm2_listpcrs.sh fail test_tpm2_load.sh fail test_tpm2_loadexternal.sh fail test_tpm2_evictcontrol.sh fail test_tpm2_hmac.sh fail test_tpm2_quote.sh fail test_tpm2_unseal.sh fail test_tpm2_akparse.sh fail test_tpm2_certify.sh fail test_tpm2_evictcontrol.sh fail test_tpm2_getpubek.sh fail test_tpm2_getpubak.sh fail test_tpm2_makecredential.sh fail test_tpm2_activecredential.sh fail test_tpm2_readpublic.sh fail test_tpm2_rsaencrypt.sh fail test_tpm2_rsadecrypt.sh fail test_tpm2_encryptdecrypt.sh fail test_tpm2_sign.sh fail test_tpm2_verifysignature.sh fail cat test_all_pass.log test_tpm2_getrandom.sh pass test_tpm2_hash.sh pass -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642118 Title: Several TPM2.0 tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1642118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634236] Re: [SRU] Dependency on snap-confine too weak
Verified pass, the new snapd (2.16ubuntu3) depends on the right version of snap-confine (>= 1.0.43). Thanks ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634236 Title: [SRU] Dependency on snap-confine too weak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1634236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634236] Re: [SRU] Dependency on snap-confine too weak
Hello Michael, The new snapd in proposed updates the dependency of ubuntu-core-launcher, but not snap-confine, I just upgraded snapd, but the snap-confine is still the old version (1.0.38-0ubuntu0.16.04.4), only ubuntu-core-launcher is upgraded to the latest one (1.0.43-0ubuntu1~16.04.1), could you please help to check the dependency? thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634236 Title: [SRU] Dependency on snap-confine too weak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1634236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326257] Re: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution
This package fixes backlight issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326257 Title: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1326257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326257] Re: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326257 Title: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1326257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326257] Re: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution
Tested with ubuntu-drivers-common 1:0.2.91.6 in trusty-proposed, it's fixes the backlight issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326257 Title: [nvidia-prime] Cannot adjust brightness in guest session and results in black screen while changing the resolution To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1326257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676166] Re: Unity Launcher corruption when resuming from suspend/hibernate
** Also affects: oem-priority 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/676166 Title: Unity Launcher corruption when resuming from suspend/hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/676166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
