Bug 30700

Summary: Samba does not mount with the new backport desktop kernel
Product: Mageia Reporter: andre salaun <andresalaun>
Component: BackportsAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: lewyssmith
Version: 8   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kernel-desktop-5.18.12 CVE:
Status comment:

Description andre salaun 2022-08-03 14:52:53 CEST 
Description of problem:

Samba does not mount with the new backport desktop kernel

Version-Release number of selected component (if applicable):

samba-4.14.12-1.mga8
5.18.12-desktop-1.mga8




Steps to Reproduce:
1.Install kernel-desktop-5.18.12
2.Reboot
3.Some samba mountages cannot be mounted. Samba mountage on a box  (like this : //192.168.x.x/box /mnt/smb-box cifs noexec,nosuid,nodev,user=xxxxxx,password=xxxxxxxxxxxxxxxx,nofail 0 0) is mounted.

But nas mountage (like this : //diskstation/homes /mnt/dst-smb-homes-diskstation cifs credentials=/xxx/xxxx/xxxx.x.xxxxx,nosuid,nodev,noexec,nofail 0 0 does not mount even manually after booting).

dmesg says :

CIFS: Attempting to mount \\diskstation\homes
[  245.780689] CIFS: VFS: cifs_mount failed w/return code = -22
[  245.782226] CIFS: Attempting to mount \\diskstation\homes
[  245.857914] CIFS: VFS: cifs_mount failed w/return code = -22
[  293.879158] CIFS: Attempting to mount \\diskstation\homes
[  294.131279] CIFS: VFS: cifs_mount failed w/return code = -22
[  294.132814] CIFS: Attempting to mount \\diskstation\homes
[  294.209404] CIFS: VFS: cifs_mount failed w/return code = -22

And if I reboot on the kernel-desktop-5.18.7-1.mga8-1-1.mga8 all is well.
Comment 1 Thomas Backlund 2022-08-03 15:01:04 CEST 
please  test the 5.18.15-1.mga8 in backports_testing.

there was a cifs bugfix that landed in upstream 5.18.8 that broke mounting for some, and  a fix for that landed in upstream 5.18.13
Lewis Smith 2022-08-03 21:45:10 CEST

Source RPM: (none) => kernel-desktop-5.18.12
CC: (none) => lewyssmith

Comment 2 Lewis Smith 2023-06-02 20:37:19 CEST 
@André
Please say whether the original problem persists, or whether tmb's comment 1 resolved the issue.
Comment 3 Lewis Smith 2024-01-22 15:03:02 CET 
No reponse, closing. Re-open if necessary.

Resolution: (none) => OLD
Status: NEW => RESOLVED