Error running program on cifs filesystem

Bug #2052835 reported by Naveed Khan
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux-signed-hwe-6.5 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi

When I try and run a shell script which is on a cifs mounted system I get an error. This is on a 22.04 system - Linux bicr-compression 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

nkhan@bicr-compression:/mnt/cephfs/home/users/nkhan$ ~/data/NKHAN/linux-home/date.sh
bash: /nfs/home/users/nkhan/data/NKHAN/linux-home/date.sh: /usr/bin/bash: bad interpreter: Input/output error

In the kernel log there is:
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014745] ------------[ cut here ]------------
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014761] WARNING: CPU: 16 PID: 5834 at fs/smb/client/file.c:3341 cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs]
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014849] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 nfsv3 nfs_acl nfs lockd grace fscache netfs vsock_loopback vmw_vsock_virtio_transport_common intel_rapl_msr vmw_vsock_vmci_transport intel_rapl_common vsock intel_uncore_frequency_common binfmt_misc coretemp rapl nls_iso8859_1 vmw_balloon input_leds joydev serio_raw vmw_vmci mac_hid sch_fq_codel msr parport_pc auth_rpcgss ppdev lp parport efi_pstore sunrpc ip_tables x_tables autofs4 vmwgfx crct10dif_pclmul drm_ttm_helper crc32_pclmul polyval_clmulni ttm polyval_generic ghash_clmulni_intel drm_kms_helper aesni_intel crypto_simd mptspi mptscsih cryptd mptbase ahci drm psmouse libahci vmxnet3 scsi_transport_spi i2c_piix4 pata_acpi
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014910] CPU: 16 PID: 5834 Comm: bash Tainted: G W 6.5.0-17-generic #17~22.04.1-Ubuntu
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014914] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/30/2014
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014916] RIP: 0010:cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs]
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014969] Code: c0 48 29 c2 75 c4 41 89 0b 4c 89 c0 48 8b 5d f8 c9 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 45 31 db c3 cc cc cc cc <0f> 0b 45 31 c0 4c 89 c0 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014971] RSP: 0018:ffffb4ee07117b90 EFLAGS: 00010297
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014974] RAX: ffff9de487836418 RBX: ffff9de4878363c0 RCX: 0000000000000000
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014975] RDX: ffffb4ee07117bdc RSI: 0000000000000100 RDI: ffff9de487836418
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014977] RBP: ffffb4ee07117c18 R08: 0000000000000100 R09: 0000000000000000
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014978] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9de48f998000
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014979] R13: ffff9de48f982400 R14: 0000000000000100 R15: ffff9de49ba32000
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014981] FS: 00007f8f2ae67740(0000) GS:ffff9dfb5e200000(0000) knlGS:0000000000000000
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014982] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 9 20:10:01 bicr-compression kernel: [ 1421.014984] CR2: 0000558a1cb1bf98 CR3: 00000001abfd4001 CR4: 00000000003706e0
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015030] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015033] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015034] Call Trace:
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015036] <TASK>
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015040] ? show_regs+0x6d/0x80
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015116] ? __warn+0x89/0x160
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015127] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs]
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015181] ? report_bug+0x17e/0x1b0
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015198] ? handle_bug+0x46/0x90
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015212] ? exc_invalid_op+0x18/0x80
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015215] ? asm_exc_invalid_op+0x1b/0x20
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015226] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs]
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015277] ? cifs_send_async_read+0x11f/0x510 [cifs]
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015330] __cifs_readv+0x271/0x480 [cifs]
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015383] cifs_strict_readv+0x173/0x180 [cifs]
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015436] __kernel_read+0x132/0x2f0
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015449] kernel_read+0x58/0xb0
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015451] search_binary_handler+0x75/0x260
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015458] exec_binprm+0x59/0x1c0
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015461] bprm_execve.part.0+0x198/0x250
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015464] bprm_execve+0x5d/0xa0
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015467] do_execveat_common.isra.0+0x1a9/0x260
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015471] __x64_sys_execve+0x37/0x60
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015474] do_syscall_64+0x5b/0x90
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015477] ? irqentry_exit_to_user_mode+0x17/0x20
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015481] ? irqentry_exit+0x43/0x50
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015484] ? exc_page_fault+0x94/0x1b0
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015487] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015490] RIP: 0033:0x7f8f2aceb08b
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015511] Code: f8 01 0f 8e bd fe ff ff 5b 48 8d 3d 4f 6a 13 00 5d 41 5c e9 87 62 fa ff 0f 1f 80 00 00 00 00 f3 0f 1e fa b8 3b 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 75 ed 12 00 f7 d8 64 89 01 48
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015513] RSP: 002b:00007ffcb53e7028 EFLAGS: 00000246 ORIG_RAX: 000000000000003b
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015515] RAX: ffffffffffffffda RBX: 0000558a1aa0bff0 RCX: 00007f8f2aceb08b
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015517] RDX: 0000558a1cb77040 RSI: 0000558a1cb1bf90 RDI: 0000558a1ca297e0
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015518] RBP: 0000558a1ca297e0 R08: 0000558a1cb5a8b0 R09: 0000000000000000
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015520] R10: 0000000000000008 R11: 0000000000000246 R12: 0000558a1ca297e0
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015522] R13: 0000558a1cb1bf90 R14: 0000558a1cb77040 R15: 0000558a1aa0bf3c
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015524] </TASK>
Feb 9 20:10:01 bicr-compression kernel: [ 1421.015525] ---[ end trace 0000000000000000 ]---

This error did not occur until the kernel was upgraded to 6.5.0
The programs used to run fromthe cifs fs - the only difference is the upgrade of thernel to 6.5.0
Any ideas what might be going wrong?
Thanks

Naveed

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Feb 9 20:06:26 2024
InstallationDate: Installed on 2022-10-04 (493 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Naveed Khan (nksco) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-signed-hwe-6.5 (Ubuntu):
status: New → Confirmed
Revision history for this message
Andrés Hurtado Nogales (ahnogales) wrote :

Hi,
Is there any progress on this?
We're experiencing the exact same issue.
Thanks in advance

Revision history for this message
Jan Knutar (ilmarix) wrote :

mounting with

-o cache=loose

seems to circumvent the issue for me.
This is probably not safe if multiple machines are accessing the same files.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.