[Touch-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
sudo snap refresh should refresh the kernel snap. However the suspected fix will not be in any snap kernel, nor can I atm build you a kernel snap to test with. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8 0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7 [ 508.564156] RIP [] strlen+0x0/0x20 [ 508.624889] RSP [ 508.96] CR2: fff3 [ 508.706425] ---[ end trace 9a8196367a1a3630 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Actually, this bug was found with Ubuntu all-snap version. So I am not able to try the kernel.deb. Could you tell me how to get the latest version of the kernel snap for 16.04? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8 0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7 [ 508.564156] RIP [] strlen+0x0/0x20 [ 508.624889] RSP [ 508.96] CR2: fff3 [ 508.706425] ---[ end trace 9a8196367a1a3630 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Ignore the request to test the upstream kernel, for the moment. In this case the apparmor code that is in the trace does not exist upstream. Instead could you test the kernel in http://people.canonical.com/~jj/lp1648143/ While listed as being for bug 1648143, it contains several fixes including a fix to the bind mount code. That will be pushed up to the ubuntu kernel this week. If this still exhibits the fault then, please test the upstream kernel to verify that the bug is indeed in apparmor, and not being triggered else where and showing up in apparmor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00
[Touch-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc2 ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48
[Touch-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
I added linux back due to the uncanny resemblance to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508737 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586997 Thanks ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: New Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8 0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7 [ 508.564156] RIP [] strlen+0x0/0x20 [ 508.624889] RSP [ 508.96] CR2: fff3 [ 508.706425] ---[ end trace 9a8196367a1a3630 ]--- To manage notifications about this bug go to:
[Touch-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Changed the target to be apparmor because the kernel panic is triggered by apparmor. ** Package changed: linux (Ubuntu) => apparmor (Ubuntu) ** Also affects: apparmor Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8 0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7 [ 508.564156] RIP [] strlen+0x0/0x20 [ 508.624889] RSP [ 508.96] CR2: fff3 [ 508.706425] ---[ end trace 9a8196367a1a3630 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
