| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 23 Aug 2016 13:01:53 -0300 From: Marcos Mello <marcosfrm@...il.com> To: tytso@....edu Cc: linux-ext4@...r.kernel.org Subject: Re: Kernel does not respect tune2fs -E mount_opts=foo 2016-08-23 12:48 GMT-03:00 <tytso@....edu>: > The problem you are running into is not something we can fix, > unfortunately, or at least not in a full and general way. The problem > is that there are certain mount options which are parsed by the mount > command (in userspace) and then translated to a mount flag, which is > then passed to the mount command as a bitmask, and which is > interpreted by the VFS layer before calling the file system. > > The mount options field in the superblock is parsed by the ext4 file > system along with options that were not parsed by the mount binary, > passed to the VFS, which then passed it to ext4 file system driver. > > In theory, we could interpret relatime in ext4 and replicate its > effects. For relatime, this is trivial to do. There may be other > mount options which are interepted by the mount userspace program, and > implemented in the VFS, where this would be much less easy to do. > >> Other options like noacl, nouser_xattr, are ignored too. This >> filesystem is not listed in fstab. > > This is exactly the same issue. > Thanks for the explanation. A hint about this limitation in tune2fs man page would help. Marcos -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists