[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
This bug was fixed in the package linux - 4.4.0-208.240 --- linux (4.4.0-208.240) xenial; urgency=medium * xenial/linux: 4.4.0-208.240 -proposed tracker (LP: #1922069) * linux ADT test failure with linux/4.4.0-207.239 - ubuntu_qrt_kernel_security.test-kernel-security.py (LP: #1922200) // CVE-2018-5953 // CVE-2018-5995 // CVE-2018-7754 - SAUCE: Revert "printk: hash addresses printed with %p" * lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239 (LP: #1921969) - SAUCE: Fix fuse regression in 4.4.0-207.239 linux (4.4.0-207.239) xenial; urgency=medium * xenial/linux: 4.4.0-207.239 -proposed tracker (LP: #1919558) * Xenial update: v4.4.262 upstream stable release (LP: #1920221) - uapi: nfnetlink_cthelper.h: fix userspace compilation error - ath9k: fix transmitting to stations in dynamic SMPS mode - net: Fix gro aggregation for udp encaps with zero csum - can: skb: can_skb_set_owner(): fix ref counting if socket was closed before setting skb ownership - can: flexcan: assert FRZ bit in flexcan_chip_freeze() - can: flexcan: enable RX FIFO after FRZ/HALT valid - netfilter: x_tables: gpf inside xt_find_revision() - cifs: return proper error code in statfs(2) - floppy: fix lock_fdc() signal handling - Revert "mm, slub: consider rest of partial list if acquire_slab() fails" - futex: Change locking rules - futex: Cure exit race - futex: fix dead code in attach_to_pi_owner() - net/mlx4_en: update moderation when config reset - net: lapbether: Remove netif_start_queue / netif_stop_queue - net: davicom: Fix regulator not turned off on failed probe - net: davicom: Fix regulator not turned off on driver removal - media: usbtv: Fix deadlock on suspend - mmc: mxs-mmc: Fix a resource leak in an error handling path in 'mxs_mmc_probe()' - mmc: mediatek: fix race condition between msdc_request_timeout and irq - powerpc/perf: Record counter overflow always if SAMPLE_IP is unset - PCI: xgene-msi: Fix race in installing chained irq handler - s390/smp: __smp_rescan_cpus() - move cpumask away from stack - scsi: libiscsi: Fix iscsi_prep_scsi_cmd_pdu() error handling - ALSA: hda/hdmi: Cancel pending works before suspend - ALSA: hda: Avoid spurious unsol event handling during S3/S4 - ALSA: usb-audio: Fix "cannot get freq eq" errors on Dell AE515 sound bar - s390/dasd: fix hanging DASD driver unbind - mmc: core: Fix partition switch time for eMMC - scripts/recordmcount.{c,pl}: support -ffunction-sections .text.* section names - Goodix Fingerprint device is not a modem - usb: gadget: f_uac2: always increase endpoint max_packet_size by one audio slot - usb: renesas_usbhs: Clear PIPECFG for re-enabling pipe with other EPNUM - xhci: Improve detection of device initiated wake signal. - USB: serial: io_edgeport: fix memory leak in edge_startup - USB: serial: ch341: add new Product ID - USB: serial: cp210x: add ID for Acuity Brands nLight Air Adapter - USB: serial: cp210x: add some more GE USB IDs - usbip: fix stub_dev to check for stream socket - usbip: fix vhci_hcd to check for stream socket - usbip: fix stub_dev usbip_sockfd_store() races leading to gpf - staging: rtl8192u: fix ->ssid overflow in r8192_wx_set_scan() - staging: rtl8188eu: prevent ->ssid overflow in rtw_wx_set_scan() - staging: rtl8712: unterminated string leads to read overflow - staging: rtl8188eu: fix potential memory corruption in rtw_check_beacon_data() - staging: rtl8712: Fix possible buffer overflow in r8712_sitesurvey_cmd - staging: rtl8192e: Fix possible buffer overflow in _rtl92e_wx_set_scan - staging: comedi: addi_apci_1032: Fix endian problem for COS sample - staging: comedi: addi_apci_1500: Fix endian problem for command sample - staging: comedi: adv_pci1710: Fix endian problem for AI command data - staging: comedi: das6402: Fix endian problem for AI command data - staging: comedi: das800: Fix endian problem for AI command data - staging: comedi: dmm32at: Fix endian problem for AI command data - staging: comedi: me4000: Fix endian problem for AI command data - staging: comedi: pcl711: Fix endian problem for AI command data - staging: comedi: pcl818: Fix endian problem for AI command data - NFSv4.2: fix return value of _nfs4_get_security_label() - block: rsxx: fix error return code of rsxx_pci_probe() - alpha: add $(src)/ rather than $(obj)/ to make source file path - alpha: merge build rules of division routines - alpha: make short build log available for division routines - alpha: Package string routines together - alpha: move exports to actual definitions - alpha: get rid of tail-zeroing in __copy_user() - alpha: switch __copy_user() and __do_clean_user() to normal calling conventions - powerpc/64s:
[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921969 Title: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz Starting c1 action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror msg="Failed starting container" name=c1 stateful=false t=2021-03-30T02:42:14+ error: Error calling 'lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': err='Failed to run: /usr/bin/lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: ' lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script exited with status 137. lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to run mount hooks for container 'c1'. lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to setup container "c1". lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error occurred in another process (expected sequence number 5) lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed to spawn container "c1". lxc 20210330024214.663 ERROR lxc_container - lxccontainer.c:wait_on_daemonized_start:804 - Received container state "ABORTING" instead of "RUNNING" Try `lxc info --show-log lxd2:c1` for more info ==> Cleaning up ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> TEST DONE: remote usage ==> Test result: failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921969 Title: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz Starting c1 action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror msg="Failed starting container" name=c1 stateful=false t=2021-03-30T02:42:14+ error: Error calling 'lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': err='Failed to run: /usr/bin/lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: ' lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script exited with status 137. lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to run mount hooks for container 'c1'. lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to setup container "c1". lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error occurred in another process (expected sequence number 5) lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed to spawn container "c1". lxc 20210330024214.663 ERROR lxc_container - lxccontainer.c:wait_on_daemonized_start:804 - Received container state "ABORTING" instead of "RUNNING" Try `lxc info --show-log lxd2:c1` for more info ==> Cleaning up ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> TEST DONE: remote usage ==> Test result: failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921969 Title: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz Starting c1 action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror msg="Failed starting container" name=c1 stateful=false t=2021-03-30T02:42:14+ error: Error calling 'lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': err='Failed to run: /usr/bin/lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: ' lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script exited with status 137. lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to run mount hooks for container 'c1'. lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to setup container "c1". lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error occurred in another process (expected sequence number 5) lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed to spawn container "c1". lxc 20210330024214.663 ERROR lxc_container - lxccontainer.c:wait_on_daemonized_start:804 - Received container state "ABORTING" instead of "RUNNING" Try `lxc info --show-log lxd2:c1` for more info ==> Cleaning up ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> TEST DONE: remote usage ==> Test result: failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921969 Title: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Triaged Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz Starting c1 action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror msg="Failed starting container" name=c1 stateful=false t=2021-03-30T02:42:14+ error: Error calling 'lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': err='Failed to run: /usr/bin/lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: ' lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script exited with status 137. lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to run mount hooks for container 'c1'. lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to setup container "c1". lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error occurred in another process (expected sequence number 5) lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed to spawn container "c1". lxc 20210330024214.663 ERROR lxc_container - lxccontainer.c:wait_on_daemonized_start:804 - Received container state "ABORTING" instead of "RUNNING" Try `lxc info --show-log lxd2:c1` for more info ==> Cleaning up ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> TEST DONE: remote usage ==> Test result: failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
Confirmed that on a working system, just updating to the new kernel breaks it. So that SRU kernel is definitely broken and should not be shipped. [8.996651] BUG: unable to handle kernel NULL pointer dereference at e12c1a77 [8.998738] IP: [] fuse_do_setattr+0x52/0x640 [9.000546] PGD 8002717c7067 PUD 270e5d067 PMD 0 [9.001915] Oops: [#1] SMP [9.003041] Modules linked in: binfmt_misc veth ip6table_filter ip6_tables xt_CHECKSUM iptable_mangle xt_comment xt_tcpudp iptable_filter ip_tables x_tables kvm_intel kvm irqbypass bridge stp llc joydev input_leds serio_raw lpc_ich 9pnet_virtio 9pnet virtio_rng virtio_input shpchp 8250_fintek mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel virtio_gpu ttm aesni_intel drm_kms_helper aes_x86_64 lrw syscopyarea gf128mul glue_helper ablk_helper sysfillrect ahci sysimgblt cryptd fb_sys_fops psmouse drm libahci virtio_scsi [9.019982] CPU: 2 PID: 1929 Comm: mount Not tainted 4.4.0-207-generic #239-Ubuntu [9.021887] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS 0.0.0 02/06/2015 [9.023893] task: b85f1580 ti: 46f8cfc7 task.ti: 46f8cfc7 [9.025775] RIP: 0010:[] [ ] fuse_do_setattr+0x52/0x640 [9.027974] RSP: 0018:880272eb7c20 EFLAGS: 00010246 [9.029627] RAX: RBX: 880272eb7e28 RCX: 000e [9.031507] RDX: RSI: 880272eb7e28 RDI: 880272eb7cf8 [9.033447] RBP: 880272eb7d98 R08: 00019580 R09: 8122c764 [9.035159] R10: ea0009cd8400 R11: 88027203c300 R12: [9.037004] R13: 880272eb7e28 R14: 88027203c470 R15: 88027203c300 [9.038737] FS: 7f01e82d9840() GS:88027fd0() knlGS: [9.040811] CS: 0010 DS: ES: CR0: 80050033 [9.042470] CR2: 0458 CR3: 000273654000 CR4: 00160670 [9.044488] Stack: [9.045578] 81227c54 880272eb7c84 0001 00028186639d [9.047599] 5318e6f4d6b61d94 880272eb7d70 880272eb7d80 880272eb7d70 [9.049606] 880272eb7cf8 880272eb7cf0 880270e50320 [9.051576] Call Trace: [9.052746] [<4f4fb5e7>] ? lookup_fast+0x184/0x340 [9.054366] [<4f4fb5e7>] ? lookup_fast+0x184/0x340 [9.055970] [ ] ? unlazy_walk+0xc1/0x150 [9.057542] [ ] ? terminate_walk+0x66/0xd0 [9.059307] [<51dc2989>] ? putname+0x54/0x60 [9.060934] [<5d276838>] fuse_setattr+0xa5/0xf0 [9.062454] [ ] notify_change+0x2dc/0x430 [9.064177] [<8ae20288>] utimes_common+0xd1/0x1b0 [9.065694] [<3571704c>] do_utimes+0x125/0x160 [9.067102] [ ] SyS_utimensat+0x67/0xa0 [9.068721] [ ] entry_SYSCALL_64_fastpath+0x22/0xd0 [9.070383] Code: 4c 8b 77 30 65 48 8b 04 25 28 00 00 00 48 89 84 24 48 01 00 00 31 c0 48 8d bc 24 d8 00 00 00 c7 44 24 14 00 00 00 00 49 8b 46 28 <4c> 8b b8 58 04 00 00 31 c0 f3 48 ab 41 0f b6 9f 2c 01 00 00 c0 [9.076396] RIP [ ] fuse_do_setattr+0x52/0x640 [9.078006] RSP [9.079316] CR2: 0458 [9.080677] ---[ end trace 05c28a02c4628343 ]--- ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921969 Title: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239 Status in linux package in Ubuntu: Triaged Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz Starting c1 action=start creation
[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
When a single test fails occasionally, it can be an issue with LXD or with the test, but when a bugfix release of a stable kernel suddenly causes one of the most trivial tests to fail on all architectures, this strongly suggests that the kernel is the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921969 Title: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239 Status in linux package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz Starting c1 action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror msg="Failed starting container" name=c1 stateful=false t=2021-03-30T02:42:14+ error: Error calling 'lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': err='Failed to run: /usr/bin/lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: ' lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script exited with status 137. lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to run mount hooks for container 'c1'. lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to setup container "c1". lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error occurred in another process (expected sequence number 5) lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed to spawn container "c1". lxc 20210330024214.663 ERROR lxc_container - lxccontainer.c:wait_on_daemonized_start:804 - Received container state "ABORTING" instead of "RUNNING" Try `lxc info --show-log lxd2:c1` for more info ==> Cleaning up ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> TEST DONE: remote usage ==> Test result: failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921969] Re: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
This looks like a kernel regression to me. ** Package changed: lxd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921969 Title: lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239 Status in linux package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz Starting c1 action=start creation date=2021-03-30T02:42:13+ ephemeral=false lvl=eror msg="Failed starting container" name=c1 stateful=false t=2021-03-30T02:42:14+ error: Error calling 'lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf': err='Failed to run: /usr/bin/lxd forkstart c1 /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: ' lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script exited with status 137. lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to run mount hooks for container 'c1'. lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to setup container "c1". lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error occurred in another process (expected sequence number 5) lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed to spawn container "c1". lxc 20210330024214.663 ERROR lxc_container - lxccontainer.c:wait_on_daemonized_start:804 - Received container state "ABORTING" instead of "RUNNING" Try `lxc info --show-log lxd2:c1` for more info ==> Cleaning up ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> Deleting all containers ==> Deleting all images ==> Deleting all profiles Profile default deleted Profile docker deleted ==> Checking for locked DB tables ==> Checking for leftover files ==> Checking for leftover DB entries ==> Tearing down directory backend in /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt ==> TEST DONE: remote usage ==> Test result: failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp