verification for noble:

1- created a CIFS share and added file to it following the steps in 
https://ubuntu.com/tutorials/install-and-configure-samba#1-overview:
  
$ sudo systemctl status samba       
● samba-ad-dc.service - LSB: Samba daemons for the AD DC
     Loaded: loaded (/etc/init.d/samba-ad-dc; generated)
     Active: active (exited) since Mon 2024-11-25 20:51:33 EET; 23min ago
 Invocation: 6d74229c380c41f2a068a646d452cde6
       Docs: man:systemd-sysv-generator(8)
    Process: 1993190 ExecStart=/etc/init.d/samba-ad-dc start (code=exited, 
status=0/SUCCESS)
   Mem peak: 1.7M
        CPU: 4ms

Nov 25 20:51:33 XPS-17-9720 systemd[1]: Starting samba-ad-dc.service - LSB: 
Samba daemons for the AD DC...
Nov 25 20:51:33 XPS-17-9720 systemd[1]: Started samba-ad-dc.service - LSB: 
Samba daemons for the AD DC.

$ ls ~/sambashare 
smbfile2.txt  smbfile3.txt  smbfile4.txt  smbfile.txt


$  tail /etc/samba/smb.conf
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

[sambashare]
    comment = Samba on Ubuntu
    path = /home/ghadi/sambashare
    read only = no
    browsable = yes

3- connect the noble machine to the samba share using the proposed
kernel and create a mount point folder in ~/cifs-mnt:

$ apt list --installed linux-generic
Listing... Done
linux-generic/noble-proposed,now 6.8.0-50.51 amd64 [installed]
N: There are 2 additional versions. Please use the '-a' switch to see them.

$ tail -n1 /etc/fstab
//192.168.1.126/sambashare /home/ghadi/cifs-mnt cifs 
username=<username>,password=<password> 0 0

Used a placeholder username and password in the above output.

$ sudo mount cifs-mnt/

4- verify that the files are visible with ls:

$ ls cifs-mnt/
smbfile.txt  smbfile2.txt  smbfile3.txt  smbfile4.txt

Files are now correctly being displayed!

** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux

-- 
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/2082423

Title:
  Unable to list directories using CIFS on 6.8 kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  Fix Committed

Bug description:
  [impact]

  Currently on the latest version of the 6.8 kernel, there is an issue where 
listing directories with CIFS fails and returns an error stating that the 
operation is not permitted.
  There is an upstream patch to fix the issue: 
https://git.kernel.dk/?p=linux-block.git;a=commitdiff;h=ec686804117a0421cf31d54427768aaf93aa0069
  And I have back ported to Noble 6.8. Note that the same issue also affects 
jammy HWE 6.8.

  [Test Plan]

  1. Create a CIFS share.
  2. Populate the CIFS share directory with files.
  3. connect to the CIFS share using a ubuntu noble machine or a jammy machine 
running 6.8 HWE. Steps to connect to a CIFS share can be found here: 
https://ubuntu.com/server/docs/how-to-mount-cifs-shares-permanently
  4. Once mounted, access the share and try listing the content of the 
directory with "ls".
  5. This will result in the following errors:
  ls: cannot access 'file1': Operation not supported
  ls: cannot access 'file2': Operation not supported
  ls: cannot access 'file3': Operation not supported
  ls: cannot access 'file4': Operation not supported

  6. Looking at dmesg, the following traces can be seen:
  CIFS: VFS: parse_reparse_point: unhandled reparse tag: 0x0000001b
  CIFS: fs/smb/client/dir.c: Unexpected lookup error -95

  7. The expected output would be to have the files listed wihtout any
  "operation not supported" errors or dmesg CIFS related error logs.

  [Fix]

  The fix is already upstream and is provided by:
  * ec686804117a smb: client: ignore unhandled reparse tags
   
  The patch does not apply cleanly due to the following missing commit: 
c520ba7573a8 smb: client: move most of reparse point handling code to common 
file
  So I had to do a few modifications. 

  [where problems could occur]
  * The patch might not fix the issue and it might still be present in some 
scenarios. 
  * Other CIFS commands might break.

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