[Kernel-packages] [Bug 2060919] Re: cifs: Copying file to same directory results in page fault
I tested two systems with different samba servers and can no longer reproduce the error. Kernel 6.5.0-35 works for me. Many thanks! :-) -- 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/2060919 Title: cifs: Copying file to same directory results in page fault Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2060919 [Impact] Copying or modifying a file to the same directory within a cifs mount results in a page fault, and the process that initiated the copy being killed. This could be cp, nautilus, etc. This results in the following oops: BUG: unable to handle page fault for address: fffe #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 Oops: [#1] PREEMPT SMP NOPTI CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 RAX: RBX: fffe RCX: RDX: RSI: RDI: RBP: aab6865ffc28 R08: 0001 R09: R10: 00023854 R11: R12: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 FS: 7bd4d594b6c0() GS:90753f80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: fffe CR3: 00017022a000 CR4: 00750ef0 PKRU: 5554 Call Trace: ? show_regs+0x6d/0x80 ? __die+0x24/0x80 ? page_fault_oops+0x99/0x1b0 ? kernelmode_fixup_or_oops+0xb2/0x140 ? __bad_area_nosemaphore+0x1a5/0x2c0 ? bad_area_nosemaphore+0x16/0x30 ? do_kern_addr_fault+0x7b/0xa0 ? exc_page_fault+0x1a4/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? cifs_flush_folio+0x41/0xf0 [cifs] ? cifs_flush_folio+0x37/0xf0 [cifs] cifs_remap_file_range+0x172/0x660 [cifs] do_clone_file_range+0x101/0x2d0 vfs_clone_file_range+0x3f/0x150 ioctl_file_clone+0x52/0xc0 do_vfs_ioctl+0x68f/0x910 ? __fget_light+0xa5/0x120 __x64_sys_ioctl+0x7d/0xf0 do_syscall_64+0x59/0x90 ? kmem_cache_free+0x22/0x3e0 ? putname+0x5b/0x80 ? exit_to_user_mode_prepare+0x30/0xb0 ? syscall_exit_to_user_mode+0x37/0x60 ? do_syscall_64+0x68/0x90 ? do_syscall_64+0x68/0x90 ? do_syscall_64+0x68/0x90 There is no known workaround. [Fix] The stacktrace is very similar to a regression reported to upstream 6.1.y: https://lore.kernel.org/linux- mm/a76b370f93cb928c049b94e1fde0d2da506dfcb2.ca...@amazon.com/T/ The thread mentions that: commit 7b2404a886f8b91250c31855d287e632123e1746 Author: David Howells Date: Fri Dec 1 00:22:00 2023 + Subject: cifs: Fix flushing, invalidation and file size with copy_file_range() Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b2404a886f8b91250c31855d287e632123e1746 introduced the issue to Debian's 6.1 kernel. This got backported to Ubuntu in: commit 3adbe2ccd8b9b8fde93e03958d6176945794d288 Author: David Howells Date: Fri Dec 1 00:22:00 2023 + Subject: cifs: Fix flushing, invalidation and file size with copy_file_range() $ git describe --contains 3adbe2ccd8b9b8fde93e03958d6176945794d288 Ubuntu-6.5.0-20.20~107 Which we have been using for some time now, and is not the culprit. Reading the regression mailing list thread, they mention that things work differently in 6.1: > Yeah. __filemap_get_folio() works differently in v6.1.y. There it returns a > folio or NULL. In 6.7 it returns a folio or a negative error code. The error > check in cifs_flush_folio() needs to change to something like: > > folio = filemap_get_folio(inode->i_mapping, index); > if (!folio) > return -ENOMEM; > > David 6.1.y then got a specific patch to fix the issue in 6.1, which is: commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1 Author: Steve French Date: Fri Jan 12 23:08:51 2024 -0600 Subject: cifs: fix flushing folio regression for 6.1 backport Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/mantic/commit/?id=21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1 $ git describe --contains 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1 Ubuntu-6.5.0-27.28~162 Since the Ubuntu mantic kernel consumes both 6.1.y and 6.7.y / 6.8.y stable patches, this patch was applied to mantic's 6.5 kernel by mistake, and contains the wrong logic for how __filemap_get_folio() works in 6.5. The
[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
I can produce the error with two fresh installed VMs. Server - Debian 12 installed from debian-12.5.0-amd64-netinst.iso with current updates - kernel "Linux cifstest-server 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 GNU/Linux" - cifs share as in #14 Client - Ubuntu 23.10 installed from ubuntu-23.10.1-desktop-amd64.iso with current updates - kernel "Linux cifs-client 6.5.0-28-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 28 23:46:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux" - cifs mount as in #14 - cd ~/share; touch abc; cp abc xyz -> "Killed" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Bug description: Remote filesystems mounted as CIFS are not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64). The remote filesystem is correctly mounted and seems to work but trying to write data to the filesystem ends in a kernel error exception. After that error the CIFS filesystem just became unusable. Previous Kernel version works correctly. = Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64) = # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 # uname -a Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 6.5.0-27.28-generic 6.5.13 How to reproduce the problem For instance, I'm using KeePassXC (https://launchpad.net/ubuntu/+source/keepassxc) to update a database located at CIFS filesystem. Any change done to that database causes this Kernel error exception: abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: fffe abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 abr 11 09:34:59 fpgmsi kernel: Oops: [#1] PREEMPT SMP NOPTI abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022 abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 abr 11 09:34:59 fpgmsi kernel: RAX: RBX: fffe RCX: abr 11 09:34:59 fpgmsi kernel: RDX: RSI: RDI: abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 R09: abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11: R12: abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0() GS:90753f80() knlGS: abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0: 80050033 abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 CR4: 00750ef0 abr 11 09:34:59 fpgmsi kernel: PKRU: 5554 abr 11 09:34:59 fpgmsi kernel: Call Trace: abr 11 09:34:59 fpgmsi kernel: abr 11 09:34:59 fpgmsi kernel: ? show_regs+0x6d/0x80 abr 11 09:34:59 fpgmsi kernel: ? __die+0x24/0x80 abr 11 09:34:59 fpgmsi kernel: ? page_fault_oops+0x99/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? kernelmode_fixup_or_oops+0xb2/0x140 abr 11 09:34:59 fpgmsi kernel: ? __bad_area_nosemaphore+0x1a5/0x2c0 abr 11 09:34:59 fpgmsi kernel: ? bad_area_nosemaphore+0x16/0x30 abr 11 09:34:59 fpgmsi kernel: ? do_kern_addr_fault+0x7b/0xa0 abr 11 09:34:59 fpgmsi kernel: ? exc_page_fault+0x1a4/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? asm_exc_page_fault+0x27/0x30 abr 11 09:34:59 fpgmsi
[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
Many thanks for the successful investigation! Running the ppa test kernel I can't reproduce the problem anymore. :-) I use two cifs servers running Debian 11, with a couple of shares. With both standard kernels (6.5.0-27, 6.5.0-28) copying inside a share fails immediately on any server. My fstab mounts look like this: //server/store /mnt/store cifs credentials=/home/xxx/.smbpass,uid=1000,gid=1000,_netdev 0 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Bug description: Remote filesystems mounted as CIFS are not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64). The remote filesystem is correctly mounted and seems to work but trying to write data to the filesystem ends in a kernel error exception. After that error the CIFS filesystem just became unusable. Previous Kernel version works correctly. = Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64) = # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 # uname -a Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 6.5.0-27.28-generic 6.5.13 How to reproduce the problem For instance, I'm using KeePassXC (https://launchpad.net/ubuntu/+source/keepassxc) to update a database located at CIFS filesystem. Any change done to that database causes this Kernel error exception: abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: fffe abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 abr 11 09:34:59 fpgmsi kernel: Oops: [#1] PREEMPT SMP NOPTI abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022 abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 abr 11 09:34:59 fpgmsi kernel: RAX: RBX: fffe RCX: abr 11 09:34:59 fpgmsi kernel: RDX: RSI: RDI: abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 R09: abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11: R12: abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0() GS:90753f80() knlGS: abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0: 80050033 abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 CR4: 00750ef0 abr 11 09:34:59 fpgmsi kernel: PKRU: 5554 abr 11 09:34:59 fpgmsi kernel: Call Trace: abr 11 09:34:59 fpgmsi kernel: abr 11 09:34:59 fpgmsi kernel: ? show_regs+0x6d/0x80 abr 11 09:34:59 fpgmsi kernel: ? __die+0x24/0x80 abr 11 09:34:59 fpgmsi kernel: ? page_fault_oops+0x99/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? kernelmode_fixup_or_oops+0xb2/0x140 abr 11 09:34:59 fpgmsi kernel: ? __bad_area_nosemaphore+0x1a5/0x2c0 abr 11 09:34:59 fpgmsi kernel: ? bad_area_nosemaphore+0x16/0x30 abr 11 09:34:59 fpgmsi kernel: ? do_kern_addr_fault+0x7b/0xa0 abr 11 09:34:59 fpgmsi kernel: ? exc_page_fault+0x1a4/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? asm_exc_page_fault+0x27/0x30 abr 11 09:34:59 fpgmsi kernel: ? cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: ? cifs_flush_folio+0x37/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel:
[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
Same problem on Debian 12 with kernel 6.1.0-17-amd64 (OK with kernel 6.1.0-16-amd64). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Bug description: Remote filesystems mounted as CIFS are not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64). The remote filesystem is correctly mounted and seems to work but trying to write data to the filesystem ends in a kernel error exception. After that error the CIFS filesystem just became unusable. Previous Kernel version works correctly. = Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64) = # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 # uname -a Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/version_signature Ubuntu 6.5.0-27.28-generic 6.5.13 How to reproduce the problem For instance, I'm using KeePassXC (https://launchpad.net/ubuntu/+source/keepassxc) to update a database located at CIFS filesystem. Any change done to that database causes this Kernel error exception: abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: fffe abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 abr 11 09:34:59 fpgmsi kernel: Oops: [#1] PREEMPT SMP NOPTI abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022 abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 abr 11 09:34:59 fpgmsi kernel: RAX: RBX: fffe RCX: abr 11 09:34:59 fpgmsi kernel: RDX: RSI: RDI: abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 R09: abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11: R12: abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0() GS:90753f80() knlGS: abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0: 80050033 abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 CR4: 00750ef0 abr 11 09:34:59 fpgmsi kernel: PKRU: 5554 abr 11 09:34:59 fpgmsi kernel: Call Trace: abr 11 09:34:59 fpgmsi kernel: abr 11 09:34:59 fpgmsi kernel: ? show_regs+0x6d/0x80 abr 11 09:34:59 fpgmsi kernel: ? __die+0x24/0x80 abr 11 09:34:59 fpgmsi kernel: ? page_fault_oops+0x99/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? kernelmode_fixup_or_oops+0xb2/0x140 abr 11 09:34:59 fpgmsi kernel: ? __bad_area_nosemaphore+0x1a5/0x2c0 abr 11 09:34:59 fpgmsi kernel: ? bad_area_nosemaphore+0x16/0x30 abr 11 09:34:59 fpgmsi kernel: ? do_kern_addr_fault+0x7b/0xa0 abr 11 09:34:59 fpgmsi kernel: ? exc_page_fault+0x1a4/0x1b0 abr 11 09:34:59 fpgmsi kernel: ? asm_exc_page_fault+0x27/0x30 abr 11 09:34:59 fpgmsi kernel: ? cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: ? cifs_flush_folio+0x37/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: cifs_remap_file_range+0x172/0x660 [cifs] abr 11 09:34:59 fpgmsi kernel: do_clone_file_range+0x101/0x2d0 abr 11 09:34:59 fpgmsi kernel: vfs_clone_file_range+0x3f/0x150 abr 11 09:34:59 fpgmsi kernel: ioctl_file_clone+0x52/0xc0 abr 11 09:34:59 fpgmsi kernel: do_vfs_ioctl+0x68f/0x910 abr 11 09:34:59 fpgmsi kernel: ? __fget_light+0xa5/0x120 abr 11 09:34:59 fpgmsi kernel:
[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
I can mount cifs shares with kernel 6.5.0-27, but when copying files from the share to the same share the process is killed everytime. Same effect using bash "cp" or KDE kio copy via Krusader. Running with kernel 6.5.0-26 anything works perfect. Syslog says: 2024-04-14T16:06:01.997083+02:00 monster kernel: [ 42.667380] BUG: unable to handle page fault for address: fffe 2024-04-14T16:06:01.997099+02:00 monster kernel: [ 42.667391] #PF: supervisor read access in kernel mode 2024-04-14T16:06:01.997100+02:00 monster kernel: [ 42.667393] #PF: error_code(0x) - not-present page 2024-04-14T16:06:01.997101+02:00 monster kernel: [ 42.667396] PGD 1afa3f067 P4D 1afa3f067 PUD 1afa41067 PMD 0 2024-04-14T16:06:01.997101+02:00 monster kernel: [ 42.667411] Oops: [#1] PREEMPT SMP PTI 2024-04-14T16:06:01.997102+02:00 monster kernel: [ 42.667414] CPU: 0 PID: 4326 Comm: cp Tainted: P O 6.5.0-27-generic #28-Ubuntu 2024-04-14T16:06:01.997104+02:00 monster kernel: [ 42.667418] Hardware name: System manufacturer System Product Name/P8B75-V, BIOS 1608 03/18/2014 2024-04-14T16:06:01.997104+02:00 monster kernel: [ 42.667420] RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] 2024-04-14T16:06:01.997105+02:00 monster kernel: [ 42.667495] Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 13 ed 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 2024-04-14T16:06:01.997107+02:00 monster kernel: [ 42.667498] RSP: 0018:9f2c835bbcb0 EFLAGS: 00010282 2024-04-14T16:06:01.997107+02:00 monster kernel: [ 42.667501] RAX: RBX: fffe RCX: 2024-04-14T16:06:01.997108+02:00 monster kernel: [ 42.667503] RDX: RSI: RDI: 2024-04-14T16:06:01.997109+02:00 monster kernel: [ 42.667505] RBP: 9f2c835bbce0 R08: 0001 R09: 2024-04-14T16:06:01.997110+02:00 monster kernel: [ 42.667507] R10: 0028 R11: R12: 2024-04-14T16:06:01.997110+02:00 monster kernel: [ 42.667509] R13: 9f2c835bbd30 R14: 89ca1f3d8d60 R15: 9f2c835bbd28 2024-04-14T16:06:01.997111+02:00 monster kernel: [ 42.667511] FS: 7a893d461540() GS:89cb15c0() knlGS: 2024-04-14T16:06:01.997112+02:00 monster kernel: [ 42.667513] CS: 0010 DS: ES: CR0: 80050033 2024-04-14T16:06:01.997113+02:00 monster kernel: [ 42.667516] CR2: fffe CR3: 00017f140006 CR4: 001706f0 2024-04-14T16:06:01.997113+02:00 monster kernel: [ 42.667518] Call Trace: 2024-04-14T16:06:01.997114+02:00 monster kernel: [ 42.667521] 2024-04-14T16:06:01.997115+02:00 monster kernel: [ 42.667524] ? show_regs+0x6d/0x80 2024-04-14T16:06:01.997116+02:00 monster kernel: [ 42.667532] ? __die+0x24/0x80 2024-04-14T16:06:01.997116+02:00 monster kernel: [ 42.667536] ? page_fault_oops+0x99/0x1b0 2024-04-14T16:06:01.997117+02:00 monster kernel: [ 42.667541] ? kernelmode_fixup_or_oops+0xb2/0x140 2024-04-14T16:06:01.997117+02:00 monster kernel: [ 42.667544] ? __bad_area_nosemaphore+0x1a5/0x2c0 2024-04-14T16:06:01.997118+02:00 monster kernel: [ 42.667556] ? bad_area_nosemaphore+0x16/0x30 2024-04-14T16:06:01.997119+02:00 monster kernel: [ 42.667558] ? do_kern_addr_fault+0x7b/0xa0 2024-04-14T16:06:01.997119+02:00 monster kernel: [ 42.667561] ? exc_page_fault+0x1a4/0x1b0 2024-04-14T16:06:01.997120+02:00 monster kernel: [ 42.667567] ? asm_exc_page_fault+0x27/0x30 2024-04-14T16:06:01.997121+02:00 monster kernel: [ 42.667575] ? cifs_flush_folio+0x41/0xf0 [cifs] 2024-04-14T16:06:01.997121+02:00 monster kernel: [ 42.667639] cifs_remap_file_range+0x172/0x660 [cifs] 2024-04-14T16:06:01.997122+02:00 monster kernel: [ 42.667703] do_clone_file_range+0x104/0x2d0 2024-04-14T16:06:01.997122+02:00 monster kernel: [ 42.667708] vfs_clone_file_range+0x3f/0x150 2024-04-14T16:06:01.997123+02:00 monster kernel: [ 42.667713] ioctl_file_clone+0x52/0xc0 2024-04-14T16:06:01.997123+02:00 monster kernel: [ 42.667718] do_vfs_ioctl+0x68f/0x910 2024-04-14T16:06:01.997124+02:00 monster kernel: [ 42.667721] ? switch_fpu_return+0x55/0xf0 2024-04-14T16:06:01.997125+02:00 monster kernel: [ 42.667726] ? exit_to_user_mode_prepare+0x9b/0xb0 2024-04-14T16:06:01.997125+02:00 monster kernel: [ 42.667730] __x64_sys_ioctl+0x7d/0xf0 2024-04-14T16:06:01.997126+02:00 monster kernel: [ 42.667734] do_syscall_64+0x5c/0x90 2024-04-14T16:06:01.997126+02:00 monster kernel: [ 42.667739] ? do_syscall_64+0x68/0x90 2024-04-14T16:06:01.997127+02:00 monster kernel: [ 42.667742] ? irqentry_exit_to_user_mode+0x17/0x20 2024-04-14T16:06:01.997128+02:00 monster kernel: [ 42.667747] ? irqentry_exit+0x43/0x50 2024-04-14T16:06:01.997128+02:00 monster kernel: [ 42.667751] ?
