Public bug reported:

Found one of my VMs with dmesg many such traces:

general protection fault: 0000 [#1] SMP 
Modules linked in: ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
iptable_filter ip_tables x_tables zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) 
spl(O) zavl(PO) input_leds sch_fq_codel nf_conntrack_ipv
CPU: 0 PID: 5110 Comm: sshd Tainted: P           O    4.4.0-116-generic 
#140-Ubuntu
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
task: ffff88007867e600 ti: ffff8800787d8000 task.ti: ffff8800787d8000
RIP: 0010:[<ffffffff8922da28>]  [<ffffffff8922da28>] __d_lookup+0x68/0x150
RSP: 0018:ffff8800787dbc00  EFLAGS: 00010206
RAX: ffffc900000659b8 RBX: 0020000000000000 RCX: 000000000000000e
RDX: ffffc90000007000 RSI: ffff8800787dbd40 RDI: ffff88006bc06300
RBP: ffff8800787dbc40 R08: ffff88006bc06300 R09: ffff88006b1ca01d
R10: 00000000c2223581 R11: 8080808080808080 R12: ffff88006bc06300
R13: ffff8800787dbd40 R14: 000000006cdac1d0 R15: ffff8800793a8020
FS:  00007f43b8a238c0(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561b09c1aed8 CR3: 0000000074498000 CR4: 0000000000000670
Stack:
 ffffffff8922b3d4 ffff88006b1ca039 0000000c00000000 ffff8800787dbd30
 0000000000000000 ffff8800787dbcb8 ffff8800787dbcb0 ffff8800793a8020
 ffff8800787dbc98 ffffffff8921ed04 ffff88006b1ca039 ffff8800787dbcac
Call Trace:
 [<ffffffff8922b3d4>] ? dput+0x34/0x230
 [<ffffffff8921ed04>] lookup_fast+0xe4/0x340
 [<ffffffff8921e488>] ? __inode_permission+0x48/0xc0
 [<ffffffff89220549>] walk_component+0x49/0x310
 [<ffffffff8921ff3b>] ? path_init+0x1eb/0x3c0
 [<ffffffff892220ad>] path_lookupat+0x5d/0x110
 [<ffffffff892225a4>] ? path_openat+0x1b4/0x1340
 [<ffffffff89223d01>] filename_lookup+0xb1/0x180
 [<ffffffff891f2109>] ? kmem_cache_alloc+0x189/0x1f0
 [<ffffffff89223906>] ? getname_flags+0x56/0x1f0
 [<ffffffff89223ea6>] user_path_at_empty+0x36/0x40
 [<ffffffff89218d76>] vfs_fstatat+0x66/0xc0
 [<ffffffff891b8aed>] ? kzfree+0x2d/0x40
 [<ffffffff89219331>] SYSC_newlstat+0x31/0x60
 [<ffffffff89212e7f>] ? do_sys_open+0x1bf/0x2a0
 [<ffffffff8921946e>] SyS_newlstat+0xe/0x10
 [<ffffffff8984efc8>] entry_SYSCALL_64_fastpath+0x1c/0xbb
Code: 45 c8 48 89 f8 48 c1 e8 06 44 01 f0 69 c0 01 00 37 9e d3 e8 48 8d 04 c2 
48 8b 18 48 83 e3 fe 75 0a eb 32 48 8b 1b 48 85 db 74 2a <44> 3b 73 18 75 f2 4c 
8d 7b 50 4c 89 ff e8 86 12 62 00 4c 3b 63 
RIP  [<ffffffff8922da28>] __d_lookup+0x68/0x150
 RSP <ffff8800787dbc00>
---[ end trace d60d4c228fda67f5 ]---

The problem was apparently triggered by a SFTP transfer to the VM and
files were (tentatively) saved to a ZFS mount. This has been working for
over a year and it's the first time I see such traces.

I don't know if that matters but the VM also suffered from one
occurrence of LP: #1749715 a month ago and under different conditions.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete


** Tags: 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/1756099

Title:
  general protection fault in __d_lookup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Found one of my VMs with dmesg many such traces:

  general protection fault: 0000 [#1] SMP 
  Modules linked in: ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
iptable_filter ip_tables x_tables zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) 
spl(O) zavl(PO) input_leds sch_fq_codel nf_conntrack_ipv
  CPU: 0 PID: 5110 Comm: sshd Tainted: P           O    4.4.0-116-generic 
#140-Ubuntu
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  task: ffff88007867e600 ti: ffff8800787d8000 task.ti: ffff8800787d8000
  RIP: 0010:[<ffffffff8922da28>]  [<ffffffff8922da28>] __d_lookup+0x68/0x150
  RSP: 0018:ffff8800787dbc00  EFLAGS: 00010206
  RAX: ffffc900000659b8 RBX: 0020000000000000 RCX: 000000000000000e
  RDX: ffffc90000007000 RSI: ffff8800787dbd40 RDI: ffff88006bc06300
  RBP: ffff8800787dbc40 R08: ffff88006bc06300 R09: ffff88006b1ca01d
  R10: 00000000c2223581 R11: 8080808080808080 R12: ffff88006bc06300
  R13: ffff8800787dbd40 R14: 000000006cdac1d0 R15: ffff8800793a8020
  FS:  00007f43b8a238c0(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000
  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
  CR2: 0000561b09c1aed8 CR3: 0000000074498000 CR4: 0000000000000670
  Stack:
   ffffffff8922b3d4 ffff88006b1ca039 0000000c00000000 ffff8800787dbd30
   0000000000000000 ffff8800787dbcb8 ffff8800787dbcb0 ffff8800793a8020
   ffff8800787dbc98 ffffffff8921ed04 ffff88006b1ca039 ffff8800787dbcac
  Call Trace:
   [<ffffffff8922b3d4>] ? dput+0x34/0x230
   [<ffffffff8921ed04>] lookup_fast+0xe4/0x340
   [<ffffffff8921e488>] ? __inode_permission+0x48/0xc0
   [<ffffffff89220549>] walk_component+0x49/0x310
   [<ffffffff8921ff3b>] ? path_init+0x1eb/0x3c0
   [<ffffffff892220ad>] path_lookupat+0x5d/0x110
   [<ffffffff892225a4>] ? path_openat+0x1b4/0x1340
   [<ffffffff89223d01>] filename_lookup+0xb1/0x180
   [<ffffffff891f2109>] ? kmem_cache_alloc+0x189/0x1f0
   [<ffffffff89223906>] ? getname_flags+0x56/0x1f0
   [<ffffffff89223ea6>] user_path_at_empty+0x36/0x40
   [<ffffffff89218d76>] vfs_fstatat+0x66/0xc0
   [<ffffffff891b8aed>] ? kzfree+0x2d/0x40
   [<ffffffff89219331>] SYSC_newlstat+0x31/0x60
   [<ffffffff89212e7f>] ? do_sys_open+0x1bf/0x2a0
   [<ffffffff8921946e>] SyS_newlstat+0xe/0x10
   [<ffffffff8984efc8>] entry_SYSCALL_64_fastpath+0x1c/0xbb
  Code: 45 c8 48 89 f8 48 c1 e8 06 44 01 f0 69 c0 01 00 37 9e d3 e8 48 8d 04 c2 
48 8b 18 48 83 e3 fe 75 0a eb 32 48 8b 1b 48 85 db 74 2a <44> 3b 73 18 75 f2 4c 
8d 7b 50 4c 89 ff e8 86 12 62 00 4c 3b 63 
  RIP  [<ffffffff8922da28>] __d_lookup+0x68/0x150
   RSP <ffff8800787dbc00>
  ---[ end trace d60d4c228fda67f5 ]---

  The problem was apparently triggered by a SFTP transfer to the VM and
  files were (tentatively) saved to a ZFS mount. This has been working
  for over a year and it's the first time I see such traces.

  I don't know if that matters but the VM also suffered from one
  occurrence of LP: #1749715 a month ago and under different conditions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756099/+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

Reply via email to