Public bug reported: I have just installed cachefilesd and rebooted. The only change I made was the location of the cache - everything else is set to default. The cache location exists and is writable.
I thought I'd test so first attempt: $ cat /mnt/server/share/file > /dev/null No problem. Second attempt: $ cat /mnt/server/share/file > /dev/null [ 471.283546] ------------[ cut here ]------------ [ 471.288354] kernel BUG at /build/linux-hwe-IJy1zi/linux-hwe-4.10.0/fs/cachefiles/namei.c:164! [ 471.296977] invalid opcode: 0000 [#1] SMP [ 471.301172] Modules linked in: arc4 md4 cachefiles cifs ccm fscache ip6table_filter ip6_tables iptable_filter ip_tables x_tables ppdev pvpanic input_leds parport_pc serio_raw parport autofs4 btrfs xor raid6_pq crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_net virtio_scsi [ 471.332032] CPU: 0 PID: 5 Comm: kworker/u2:0 Not tainted 4.10.0-37-generic #41~16.04.1-Ubuntu [ 471.340656] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 471.350158] Workqueue: fscache_object fscache_object_work_func [fscache] [ 471.356972] task: ffff8ddee426ad00 task.stack: ffffbb3f401b0000 [ 471.363083] RIP: 0010:cachefiles_walk_to_object+0x718/0x890 [cachefiles] [ 471.370055] RSP: 0018:ffffbb3f401b3d18 EFLAGS: 00010202 [ 471.375385] RAX: ffff8ddee18a6201 RBX: ffff8ddee0b6bd28 RCX: 0000000000019523 [ 471.382897] RDX: 0000000000019522 RSI: ffff8ddee621c720 RDI: ffff8ddee4001280 [ 471.390234] RBP: ffffbb3f401b3dc8 R08: 000000000001c720 R09: ffffffffc0459068 [ 471.397468] R10: ffffe66040862980 R11: ffffffff97c487ed R12: ffff8ddee11750c0 [ 471.404704] R13: ffff8ddee0b6bd80 R14: ffff8ddee0b6bd28 R15: ffff8ddee1175780 [ 471.411991] FS: 0000000000000000(0000) GS:ffff8ddee6200000(0000) knlGS:0000000000000000 [ 471.420180] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 471.426037] CR2: 00000000025c4008 CR3: 0000000020b6a000 CR4: 00000000001406f0 [ 471.433359] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 471.440678] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 471.447921] Call Trace: [ 471.450478] ? wake_atomic_t_function+0x60/0x60 [ 471.455109] cachefiles_lookup_object+0x51/0xf0 [cachefiles] [ 471.460872] fscache_look_up_object+0xa6/0x1c0 [fscache] [ 471.466378] fscache_object_work_func+0x9d/0x200 [fscache] [ 471.472012] process_one_work+0x16b/0x4a0 [ 471.476118] worker_thread+0x4b/0x500 [ 471.479880] kthread+0x109/0x140 [ 471.483294] ? process_one_work+0x4a0/0x4a0 [ 471.487577] ? kthread_create_on_node+0x60/0x60 [ 471.492208] ret_from_fork+0x2c/0x40 [ 471.495879] Code: 78 ff ff ff 4c 89 f7 49 89 de 48 8b 00 ff 50 58 e9 b5 fc ff ff 48 c7 c7 68 b3 45 c0 e8 b5 75 75 d6 31 f6 4c 89 ef e8 bd 2c 00 00 <0f> 0b 41 bc ff ff ff ff 48 8b 90 98 00 00 00 48 8b bd 78 ff ff [ 471.514854] RIP: cachefiles_walk_to_object+0x718/0x890 [cachefiles] RSP: ffffbb3f401b3d18 [ 471.523171] ---[ end trace d57820f35931610a ]--- I tried with the following builds but the result is the same: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/linux-image-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc6/linux-image-4.14.0-041400rc6-generic_4.14.0-041400rc6.201710230731_amd64.deb I tried setting the cache back to the default of /var/cache/fscache and it seemed to start working. I ran the test three or four times. Then it failed in the same way. I'm running Ubuntu 16.04 on Google Cloud Compute. In case it's a filesystem issue: $ sudo dumpe2fs -h /dev/sda1 dumpe2fs 1.42.13 (17-May-2015) Filesystem volume name: cloudimg-rootfs Last mounted on: / Filesystem UUID: 67e1c0a6-cdc9-4247-b2e5-dd20ef042025 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 1280000 Block count: 2621179 Reserved block count: 0 Free blocks: 1076375 Free inodes: 1066233 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 127 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16000 Inode blocks per group: 1000 Flex block group size: 16 Filesystem created: Tue May 16 15:25:31 2017 Last mount time: Thu Oct 26 21:58:51 2017 Last write time: Thu Oct 26 21:58:44 2017 Mount count: 40 Maximum mount count: -1 Last checked: Tue May 16 21:30:38 2017 Check interval: 0 (<none>) Lifetime writes: 337 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 First orphan inode: 264319 Default directory hash: half_md4 Directory Hash Seed: d8fb3bde-69b0-4404-9797-471e5fffc1ba Journal backup: inode blocks Journal features: journal_incompat_revoke Journal size: 64M Journal length: 16384 Journal sequence: 0x00016c30 Journal start: 4274 $ sudo dumpe2fs -h /dev/sdb dumpe2fs 1.42.13 (17-May-2015) Filesystem volume name: <none> Last mounted on: /mnt/upload Filesystem UUID: 6eea1b82-bb0a-44fa-b091-a8ee534dfa08 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: not clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 13107200 Block count: 52428800 Reserved block count: 2621440 Free blocks: 50885632 Free inodes: 13107162 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1011 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Sun Oct 22 14:34:40 2017 Last mount time: Thu Oct 26 21:58:54 2017 Last write time: Thu Oct 26 21:58:54 2017 Mount count: 3 Maximum mount count: -1 Last checked: Thu Oct 26 21:28:19 2017 Check interval: 0 (<none>) Lifetime writes: 552 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Default directory hash: half_md4 Directory Hash Seed: 4d9800bc-b23f-4f2e-86e4-b42f37fc3288 $ mount | fgrep sd /dev/sda1 on / type ext4 (rw,relatime,discard,data=ordered) /dev/sdb on /mnt/upload type ext4 (rw,nosuid,nodev,noexec,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl) I don't know what else it could be unless it is a genuine kernel bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-virtual-hwe-16.04 4.10.0.37.39 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Oct 26 21:05:56 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug uec-images xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727861 Title: kernel BUG at /build/linux-hwe-IJy1zi/linux- hwe-4.10.0/fs/cachefiles/namei.c:164! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1727861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
