1. Please describe the problem:
Since the implementation of O_TMPFILE support in the cifs driver, openat() system calls using the O_TMPFILE flag are failing on valid, reachable SMB/CIFS mounts. The driver returns -1 ENOENT (No such file or directory), even though the parent directory is accessible via standard open() calls. Applications attempting to use O_TMPFILE for atomic/safe file creation (e.g., Krita) fail to save files to the network share, reporting that the file could not be opened or the directory does not exist.


2. What is the Version-Release number of the kernel:
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.2
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.1.3-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Yes, kernels before 7.1


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
1. Mount a CIFS/SMB share (e.g., /mnt/vault/).
2. Use strace to monitor an openat call using the O_TMPFILE flag on a subdirectory of that mount.

Example: 
openat(AT_FDCWD, "/mnt/vault/home/Drive/Sketchbook/Studies/6.07.26.kra", O_RDONLY|O_CLOEXEC) = 37
openat(AT_FDCWD, "/mnt/vault/home/Drive/Sketchbook/Studies", O_RDWR|O_CLOEXEC|O_TMPFILE, 0600) = -1 ENOENT (No such file or directory)


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes, kernel 7.2.0-rc2



6. Are you running any modules that not shipped with directly Fedora's kernel?:
No


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Reproducible: Always