[arch-general] ntfs3 kenel module: permissions not consistent with dmask=0027 from /etc/fstab
Hello, With the ntfs3 linux module, some, but not all, directories of the ntfs partition do not have permissions that are consistent with dmask 027. dmask=0027 is from /etc/fstab. Based on a small set, the files permissions are consistent with the fmask setting. As an aside, as of 5.15.10-arch1-1, I believe arch didn't apply https://lore.kernel.org/ntfs3/20211127135105.27795-1-ales.astone@gmail.com/T... , or some other solution. Which is why I think it is expected to have the 37777600 prefix issue with the ntfs3 linux module. -- u34
Is the ntfs3 module in the standard "linux" package, or is it packaged separately? If it's packaged with the kernel, then you will probably have to wait until it reaches the stable kernel. On Mon, Dec 20, 2021, 4:25 PM u34--- via arch-general < arch-general@lists.archlinux.org> wrote:
Hello,
With the ntfs3 linux module, some, but not all, directories of the ntfs partition do not have permissions that are consistent with dmask 027. dmask=0027 is from /etc/fstab. Based on a small set, the files permissions are consistent with the fmask setting.
As an aside, as of 5.15.10-arch1-1, I believe arch didn't apply
https://lore.kernel.org/ntfs3/20211127135105.27795-1-ales.astone@gmail.com/T... , or some other solution. Which is why I think it is expected to have the 37777600 prefix issue with the ntfs3 linux module.
-- u34
It has been added to the kernel in 5.15. On Tue, Dec 21, 2021 at 5:14 PM Isaac R. via arch-general < arch-general@lists.archlinux.org> wrote:
Is the ntfs3 module in the standard "linux" package, or is it packaged separately? If it's packaged with the kernel, then you will probably have to wait until it reaches the stable kernel.
On Mon, Dec 20, 2021, 4:25 PM u34--- via arch-general < arch-general@lists.archlinux.org> wrote:
Hello,
With the ntfs3 linux module, some, but not all, directories of the ntfs partition do not have permissions that are consistent with dmask 027. dmask=0027 is from /etc/fstab. Based on a small set, the files permissions are consistent with the fmask setting.
As an aside, as of 5.15.10-arch1-1, I believe arch didn't apply
https://lore.kernel.org/ntfs3/20211127135105.27795-1-ales.astone@gmail.com/T...
, or some other solution. Which is why I think it is expected to have the 37777600 prefix issue with the ntfs3 linux module.
-- u34
Hello, I, who started this thread, have posted https://lore.kernel.org/ntfs3/E1n0BSg-0001lD-UY@mx1.net9.ga/ . No followup so far. With a mounted ntfs3 C:, Preferbly of MS Windows 10, can you post the output of $ ls -ld /<mount directory>'/Users/Default/My Documents' and $ ls -ld /<mount directory>/Users/Default/Documents and the umask and dmask of the mount options? My results are: $ ls -ld /<mount directory>'/Users/Default/My Documents' lrwxrwxrwx 1 user user 26 Mar 12 2020 '/mount directory/Users/Default/My Documents' -> C:/Users/Default/Documents $ ls -ld /<mount directory>/Users/Default/Documents dr-xr-x--- 1 user user 4096 Jul 25 2019 /mount directory/Users/Default/Documents umask is not explicitly set. dmask=0027. Thank you. -- u34 nihilistzsche via arch-general <arch-general@lists.archlinux.org> wrote:
It has been added to the kernel in 5.15.
On Tue, Dec 21, 2021 at 5:14 PM Isaac R. via arch-general < arch-general@lists.archlinux.org> wrote:
Is the ntfs3 module in the standard "linux" package, or is it packaged separately? If it's packaged with the kernel, then you will probably have to wait until it reaches the stable kernel.
On Mon, Dec 20, 2021, 4:25 PM u34--- via arch-general < arch-general@lists.archlinux.org> wrote:
Hello,
With the ntfs3 linux module, some, but not all, directories of the ntfs partition do not have permissions that are consistent with dmask 027. dmask=0027 is from /etc/fstab. Based on a small set, the files permissions are consistent with the fmask setting.
As an aside, as of 5.15.10-arch1-1, I believe arch didn't apply
https://lore.kernel.org/ntfs3/20211127135105.27795-1-ales.astone@gmail.com/T...
, or some other solution. Which is why I think it is expected to have the 37777600 prefix issue with the ntfs3 linux module.
-- u34
participants (3)
-
Isaac R.
-
nihilistzsche
-
u34＠net9.ga