June 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1186884] New: Launching Tumbleweed under SEV-ES currently fails when kernel parses MOVVar EFI table
by bugzilla_noreply＠suse.com 04 Jun '21

04 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186884 Bug ID: 1186884 Summary: Launching Tumbleweed under SEV-ES currently fails when kernel parses MOVVar EFI table Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jroedel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 849947 --> https://bugzilla.suse.com/attachment.cgi?id=849947&action=edit Full guest boot log with efi=debug Launching TW as an SEV-ES guest currently fails with this kernel panic: [ 2.907677] general protection fault, probably for non-canonical address 0x43a3c02ebe2b54c6: 0000 [#1] SMP NOPTI [ 2.910048] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.12.4-2-default #1 openSUSE Tumbleweed [ 2.911636] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 [ 2.911636] RIP: 0010:efi_mokvar_entry_next+0x34/0x40 [ 2.911636] Code: c5 01 48 8b 17 48 c7 07 00 00 00 00 48 85 c0 74 24 48 85 d2 74 14 80 3a 00 74 18 48 8b 82 00 01 00 00 48 8d 84 02 08 01 00 00 <80> 38 00 74 04 48 89 07 c3 31 c0 c3 0f 1f 44 00 00 41 54 4c 8b 25 [ 2.911636] RSP: 0018:ffffbca30001fe48 EFLAGS: 00010286 [ 2.911636] RAX: 43a3c02ebe2b54c6 RBX: 0000000000000000 RCX: 0000000000000000 [ 2.911636] RDX: ffffbca300294000 RSI: ffff9e8fc417b448 RDI: ffffbca30001fe50 [ 2.911636] RBP: ffff9e8fc4005a80 R08: 0000000000000000 R09: ffff9e8fc011ad90 [ 2.911636] R10: ffff9e8fc1294270 R11: 0000000000000000 R12: 0000000000000000 [ 2.911636] R13: ffffffff96e88774 R14: 0000000000000000 R15: 0000000000000000 [ 2.911636] FS: 0000000000000000(0000) GS:ffff9e903bc00000(0000) knlGS:0000000000000000 [ 2.911636] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2.911636] CR2: 0000000000000000 CR3: 000080001fc10000 CR4: 00000000003506f0 [ 2.911636] Call Trace: [ 2.911636] efi_mokvar_sysfs_init+0x12a/0x172 [ 2.911636] ? efi_mokvar_table_init+0x18a/0x18a [ 2.911636] do_one_initcall+0x44/0x1d0 [ 2.911636] ? __kmalloc+0xc0/0x2d0 [ 2.911636] kernel_init_freeable+0x1ef/0x24b [ 2.911636] ? rest_init+0xb4/0xb4 [ 2.911636] kernel_init+0xa/0x10c [ 2.911636] ret_from_fork+0x22/0x30 [ 2.911636] Modules linked in: [ 2.944868] ---[ end trace 7fa546069e99e464 ]--- [ 2.946173] RIP: 0010:efi_mokvar_entry_next+0x34/0x40 [ 2.947389] Code: c5 01 48 8b 17 48 c7 07 00 00 00 00 48 85 c0 74 24 48 85 d2 74 14 80 3a 00 74 18 48 8b 82 00 01 00 00 48 8d 84 02 08 01 00 00 <80> 38 00 74 04 48 89 07 c3 31 c0 c3 0f 1f 44 00 00 41 54 4c 8b 25 [ 2.951803] RSP: 0018:ffffbca30001fe48 EFLAGS: 00010286 [ 2.953227] RAX: 43a3c02ebe2b54c6 RBX: 0000000000000000 RCX: 0000000000000000 [ 2.954899] RDX: ffffbca300294000 RSI: ffff9e8fc417b448 RDI: ffffbca30001fe50 [ 2.956397] RBP: ffff9e8fc4005a80 R08: 0000000000000000 R09: ffff9e8fc011ad90 [ 2.957987] R10: ffff9e8fc1294270 R11: 0000000000000000 R12: 0000000000000000 [ 2.959624] R13: ffffffff96e88774 R14: 0000000000000000 R15: 0000000000000000 [ 2.961414] FS: 0000000000000000(0000) GS:ffff9e903bc00000(0000) knlGS:0000000000000000 [ 2.963132] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2.964493] CR2: 0000000000000000 CR3: 000080001fc10000 CR4: 00000000003506f0 [ 2.965970] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 2.967745] Kernel Offset: 0x13c00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) The reason for this is an upstream bug where the MOKVar EFI table is mapped as u nencrypted memory while it needs to be mapped encrypted. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1186846] New: negative used size reported for ext4 file system without journal
by bugzilla_noreply＠suse.com 04 Jun '21

04 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186846 Bug ID: 1186846 Summary: negative used size reported for ext4 file system without journal Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Creating a ext4 with approx. 256 GiB it is possible to get a negative used size reported with df. Steps to reproduce: - Create one partition on 256 GiB disk /dev/sdc. - mkfs.ext4 /dev/sdc1 - tune2fs -O ^has_journal /dev/sdc1 - mount /dev/sdc1 /mnt # parted /dev/sdc unit s print [...] Number Start End Size File system Name Flags 1 2048s 536868863s 536866816s ext2 # df Filesystem 1K-blocks Used Available Use% Mounted on [...] /dev/sdc1 263110724 -1048552 250721224 0% /mnt -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1185263] Lenovo TP E15 (2nd Gen): Display remains dark when resuming from suspend
by bugzilla_noreply＠suse.com 04 Jun '21

04 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185263 http://bugzilla.opensuse.org/show_bug.cgi?id=1185263#c12 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- Then I close as FIXED. As Leap 15.2 is based on much older code, it's very difficult to get the fix there, and the upgrade to Leap 15.3 is recommended in anyway. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185263] Lenovo TP E15 (2nd Gen): Display remains dark when resuming from suspend
by bugzilla_noreply＠suse.com 04 Jun '21

04 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185263 http://bugzilla.opensuse.org/show_bug.cgi?id=1185263#c11 --- Comment #11 from Ulrich Windl <Ulrich.Windl(a)rz.uni-regensburg.de> --- Confirmed to be fixed in Leap 15.3 with kernel 5.3.18-57-default. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185649] [Build 20210504] openQA test fails in kdump_and_crash
by bugzilla_noreply＠suse.com 04 Jun '21

04 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1185649 https://bugzilla.suse.com/show_bug.cgi?id=1185649#c3 --- Comment #3 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-extra@aarch64-HD24G https://openqa.opensuse.org/tests/1765515 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184924] [Build 134.3] openQA test fails in kdump_and_crash - forced crash didn't result into expected reboot
by bugzilla_noreply＠suse.com 04 Jun '21

04 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1184924 https://bugzilla.suse.com/show_bug.cgi?id=1184924#c2 --- Comment #2 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-extra@aarch64-HD24G https://openqa.opensuse.org/tests/1762625 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1177428] AMDGPU resume fail
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1177428 http://bugzilla.opensuse.org/show_bug.cgi?id=1177428#c99 --- Comment #99 from Nikolai Nikolaevskii <kaykaykay123(a)gmail.com> --- But maybe solution is in updating kernel to 5.12: https://forums.opensuse.org/showthread.php/553669-Display-Freeze-on-Laptop-… https://bugs.mageia.org/show_bug.cgi?id=25882 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186710] wrong/dead symlinks with kernel-default-devel-5.12.4-2.1.x86_64 (after usrmerge?)
by bugzilla_noreply＠suse.com 02 Jun '21

02 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186710 https://bugzilla.suse.com/show_bug.cgi?id=1186710#c18 --- Comment #18 from Ludwig Nussel <lnussel(a)suse.com> --- Rudi, do you want to push your proposal or should I take it from there? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186724] New: "kernel tried to execute NX-protected page" while deleting bluetooth HCI
by bugzilla_noreply＠suse.com 02 Jun '21

02 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186724 Bug ID: 1186724 Summary: "kernel tried to execute NX-protected page" while deleting bluetooth HCI Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- DISCLAIMER: This was a one-time event, I can't tell whether it's reproducible. kernel 5.3.18-lp152.66-default # What was happening I am not sure exactly sure what happened at the time, but I have an educated guess. "artemis" is my private laptop which shares keyboard/video/mouse with my work laptop ("apollon") with the "barrier" KVM software. Typically at this time of the day (20:50) I get back to work, and unlock the screen saver on "apollon" ("artemis" screen is usually not locked because the barrier server disables locking). There was no activity until the following messages, which makes it likely that that happened also on the day in question (April 1st, 2021). > [362024.111857] artemis.mittagstun.de barriers[5693]: [2021-04-01T20:51:45] INFO: switch from "artemis" to "apollon" at 0,1348 > [362024.416997] artemis.mittagstun.de barriers[5693]: [2021-04-01T20:51:46] INFO: switch from "apollon" to "artemis" at 3541,1486 > [362035.435054] artemis.mittagstun.de systemd[4983]: Started Application launched by gnome-shell. A bit later a monitor wakes up, all looks fine > [362035.949269] artemis.mittagstun.de /usr/lib/gdm/gdm-x-session[5011]: (II) modeset(0): EDID vendor "DEL", prod id 41116 > [362035.949737] artemis.mittagstun.de /usr/lib/gdm/gdm-x-session[5011]: (II) modeset(0): Using hsync ranges from config file > ... > [362035.951463] artemis.mittagstun.de /usr/lib/gdm/gdm-x-session[5011]: (II) modeset(0): Modeline "1600x900"x60.0 119.00 1600 1696 1864 2128 900 901 904 932 -hsync +> I'm positive that the system was NOT waking up from a sleep state. Wrt bluetooth, there had been some error messages ~4h earlier, nothing alarming: > [344671.880598] artemis.mittagstun.de bluetoothd[1319]: Unable to get Headset Voice gateway SDP record: Device or resource busy > [344671.921654] artemis.mittagstun.de bluetoothd[1319]: connect error: Device or resource busy (16) > [348731.893932] artemis.mittagstun.de bluetoothd[1319]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) > [353527.936713] artemis.mittagstun.de bluetoothd[1319]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) # "sysfs: cannot create duplicate filename" 15s later, we see the issue unfolding with an issue related to registering the bluetooth HCI in sysfs: > [362050.118483] artemis.mittagstun.de kernel: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256' > [362050.118488] artemis.mittagstun.de kernel: CPU: 0 PID: 2888 Comm: kworker/u17:1 Not tainted 5.3.18-lp152.66-default #1 openSUSE Leap 15.2 > [362050.118489] artemis.mittagstun.de kernel: Hardware name: FUJITSU LIFEBOOK S904/FJNB272, BIOS Version 1.20 07/25/2014 > [362050.118515] artemis.mittagstun.de kernel: Workqueue: hci0 hci_rx_work [bluetooth] > [362050.118517] artemis.mittagstun.de kernel: Call Trace: > [362050.118524] artemis.mittagstun.de kernel: dump_stack+0x66/0x8b > [362050.118529] artemis.mittagstun.de kernel: sysfs_warn_dup+0x56/0x70 > [362050.118531] artemis.mittagstun.de kernel: sysfs_create_dir_ns+0xc9/0xe0 > [362050.118535] artemis.mittagstun.de kernel: kobject_add_internal+0xad/0x2c0 > [362050.118538] artemis.mittagstun.de kernel: kobject_add+0x71/0xd0 > [362050.118541] artemis.mittagstun.de kernel: ? kobject_set_name_vargs+0x6f/0x90 > [362050.118544] artemis.mittagstun.de kernel: device_add+0x11e/0x630 > [362050.118568] artemis.mittagstun.de kernel: hci_conn_add_sysfs+0x43/0xb0 [bluetooth] > [362050.118586] artemis.mittagstun.de kernel: hci_event_packet+0x15a8/0x2c50 [bluetooth] > [362050.118590] artemis.mittagstun.de kernel: ? __switch_to_asm+0x34/0x70 > [362050.118592] artemis.mittagstun.de kernel: ? __switch_to_asm+0x40/0x70 > [362050.118594] artemis.mittagstun.de kernel: ? __switch_to_asm+0x34/0x70 > [362050.118596] artemis.mittagstun.de kernel: ? __switch_to_asm+0x40/0x70 > [362050.118598] artemis.mittagstun.de kernel: ? __switch_to_asm+0x34/0x70 > [362050.118611] artemis.mittagstun.de kernel: ? hci_rx_work+0x189/0x350 [bluetooth] > [362050.118624] artemis.mittagstun.de kernel: hci_rx_work+0x189/0x350 [bluetooth] > [362050.118629] artemis.mittagstun.de kernel: process_one_work+0x1f4/0x3e0 > [362050.118632] artemis.mittagstun.de kernel: worker_thread+0x2d/0x3e0 > [362050.118635] artemis.mittagstun.de kernel: ? process_one_work+0x3e0/0x3e0 > [362050.118636] artemis.mittagstun.de kernel: kthread+0x10d/0x130 > [362050.118639] artemis.mittagstun.de kernel: ? kthread_park+0xa0/0xa0 > [362050.118641] artemis.mittagstun.de kernel: ret_from_fork+0x35/0x40 > [362050.118645] artemis.mittagstun.de kernel: kobject_add_internal failed for hci0:256 with -EEXIST, don't try to register things with the same name in the same directo> > [362050.118647] artemis.mittagstun.de kernel: Bluetooth: hci0: failed to register connection device > [362054.923495] artemis.mittagstun.de kernel: Bluetooth: hci0: failed to disable LE scan: status 0x0c # "kernel tried to execute NX-protected page - exploit attempt?" The real problem starts now, as the bluetooth subsystem ist trying to reset the HCI. 1501 is my user ID. > [362065.479497] artemis.mittagstun.de kernel: Bluetooth: hci0: HCI reset during shutdown failed > [362065.479588] artemis.mittagstun.de kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 1501) > [362065.479605] artemis.mittagstun.de kernel: BUG: unable to handle page fault for address: ffff9267aa8d7158 > [362065.479614] artemis.mittagstun.de kernel: #PF: supervisor instruction fetch in kernel mode > [362065.479623] artemis.mittagstun.de kernel: #PF: error_code(0x0011) - permissions violation > [362065.479631] artemis.mittagstun.de kernel: PGD 25fa01067 P4D 25fa01067 PUD 107562063 PMD 136c27063 PTE 800000012a8d7063 > [362065.479645] artemis.mittagstun.de kernel: Oops: 0011 [#1] SMP PTI > [362065.479655] artemis.mittagstun.de kernel: CPU: 1 PID: 5548 Comm: gsd-rfkill Not tainted 5.3.18-lp152.66-default #1 openSUSE Leap 15.2 > [362065.479664] artemis.mittagstun.de kernel: Hardware name: FUJITSU LIFEBOOK S904/FJNB272, BIOS Version 1.20 07/25/2014 > [362065.479675] artemis.mittagstun.de kernel: RIP: 0010:0xffff9267aa8d7158 > [362065.479684] artemis.mittagstun.de kernel: Code: 00 00 00 01 00 00 00 00 00 00 58 71 8d aa 67 92 ff ff 38 00 00 00 05 00 00 00 90 71 8d aa 67 92 ff ff 60 00 00 00 06> > [362065.479696] artemis.mittagstun.de kernel: RSP: 0018:ffffad3d8217fd18 EFLAGS: 00010282 > [362065.479705] artemis.mittagstun.de kernel: RAX: ffff9267aa8d7158 RBX: ffff92698d5038d0 RCX: 00000000801e0014 > [362065.479713] artemis.mittagstun.de kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff9267b6e4c228 > [362065.479721] artemis.mittagstun.de kernel: RBP: ffff92698d503950 R08: 0000000000000000 R09: 0000000000000001 > [362065.479730] artemis.mittagstun.de kernel: R10: 0000000000000001 R11: ffff926787c53300 R12: ffff9267aab8ea68 > [362065.479738] artemis.mittagstun.de kernel: R13: ffffffffc0cf4020 R14: ffff92698d504af0 R15: ffffffffc0cf4040 > [362065.479747] artemis.mittagstun.de kernel: FS: 00007f228ecb9880(0000) GS:ffff926992040000(0000) knlGS:0000000000000000 > [362065.479756] artemis.mittagstun.de kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > [362065.479763] artemis.mittagstun.de kernel: CR2: ffff9267aa8d7158 CR3: 00000002a7ba8002 CR4: 00000000001606e0 > [362065.479771] artemis.mittagstun.de kernel: Call Trace: > [362065.479784] artemis.mittagstun.de kernel: ? device_del+0x97/0x3a0 > [362065.479796] artemis.mittagstun.de kernel: ? hid_destroy_device+0x22/0x60 > [362065.479807] artemis.mittagstun.de kernel: ? hidp_session_remove+0x48/0xb0 [hidp] > [362065.479848] artemis.mittagstun.de kernel: ? l2cap_conn_del+0x9d/0x200 [bluetooth] > [362065.479878] artemis.mittagstun.de kernel: ? new_settings+0x4e/0x70 [bluetooth] > [362065.479906] artemis.mittagstun.de kernel: ? hci_conn_hash_flush+0x73/0xe0 [bluetooth] > [362065.479932] artemis.mittagstun.de kernel: ? hci_dev_do_close+0x1f5/0x510 [bluetooth] > [362065.479959] artemis.mittagstun.de kernel: ? hci_rfkill_set_block+0x4a/0x90 [bluetooth] > [362065.479971] artemis.mittagstun.de kernel: ? rfkill_set_block+0x93/0x150 [rfkill] > [362065.479981] artemis.mittagstun.de kernel: ? rfkill_fop_write+0xef/0x1d0 [rfkill] > [362065.479991] artemis.mittagstun.de kernel: ? vfs_write+0xad/0x1b0 > [362065.479999] artemis.mittagstun.de kernel: ? ksys_write+0x50/0xe0 > [362065.480008] artemis.mittagstun.de kernel: ? __x64_sys_poll+0x37/0x130 > [362065.480018] artemis.mittagstun.de kernel: ? do_syscall_64+0x65/0x1f0 > [362065.480027] artemis.mittagstun.de kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 > [362065.480035] artemis.mittagstun.de kernel: Modules linked in: uinput uas usb_storage binfmt_misc cp210x loop mmc_block nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv> > [362065.480095] artemis.mittagstun.de kernel: mac80211 btbcm btintel kvm hid_generic snd_hda_codec_realtek bluetooth irqbypass libarc4 snd_hda_codec_generic ledtrig_au> > [362065.480226] artemis.mittagstun.de kernel: CR2: ffff9267aa8d7158 > [362065.480235] artemis.mittagstun.de kernel: ---[ end trace cbb6cb70eba67992 ]--- The register dump is repeated. After this, I see XFS log messages which hint at data corruption. This will be described in another bug. > [362090.001636] artemis.mittagstun.de kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 > [362091.622962] artemis.mittagstun.de kernel: XFS (dm-0): xlog_space_left: head behind tail > [362091.622973] artemis.mittagstun.de kernel: XFS (dm-0): tail_cycle = 2348, tail_bytes = 1957888 > [362091.622978] artemis.mittagstun.de kernel: XFS (dm-0): GH cycle = 2348, GH bytes = 1933664 > [362091.622982] artemis.mittagstun.de kernel: XFS (dm-0): xlog_space_left: head behind tail > [362091.622987] artemis.mittagstun.de kernel: XFS (dm-0): tail_cycle = 2348, tail_bytes = 1957888 > [362091.622991] artemis.mittagstun.de kernel: XFS (dm-0): GH cycle = 2348, GH bytes = 1933664 > [362091.623082] artemis.mittagstun.de kernel: XFS (dm-0): xlog_space_left: head behind tail -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1186710] wrong/dead symlinks with kernel-default-devel-5.12.4-2.1.x86_64 (after usrmerge?)
by bugzilla_noreply＠suse.com 02 Jun '21

02 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186710 https://bugzilla.suse.com/show_bug.cgi?id=1186710#c17 --- Comment #17 from Takashi Iwai <tiwai(a)suse.com> --- OK, makes sense. We have already links in Kernel:stable:KMP, so just need to set up similar (a bunch of) links in Kernel:stable:Backport. -- You are receiving this mail because: You are the assignee for the bug.

1 0