Blacklisted file systems update
Many of you will be aware of the fact that some file systems are blacklisted by default on openSUSE. With the forthcoming update of suse-module-tools, the list of disabled file systems will grow: f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs will then be blacklisted, too. This means that the respective kernel modules will not be auto-loaded, and that the system won't be able to access media with such file systems immediately when they are inserted. To override this, run "sudo modprobe $FS_MODULE" in a terminal. You will have the option to load the module just once, or un-blacklist it for future use. I've created https://en.opensuse.org/SDB:FilesystemBlacklisting with more details and a rationale. Regards Martin
Dec 15, 2023 20:07:42 Martin Wilck via openSUSE Factory <factory@lists.opensuse.org>:
Many of you will be aware of the fact that some file systems are blacklisted by default on openSUSE. With the forthcoming update of suse-module-tools, the list of disabled file systems will grow:
f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs
will then be blacklisted, too. This means that the respective kernel modules will not be auto-loaded, and that the system won't be able to access media with such file systems immediately when they are inserted.
To override this, run "sudo modprobe $FS_MODULE" in a terminal. You will have the option to load the module just once, or un-blacklist it for future use.
I've created https://en.opensuse.org/SDB:FilesystemBlacklisting with more details and a rationale.
Regards Martin Hello
f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs
Unless I am mistaken, ntfs3 kmod is needed to mount NTFS then why would we blacklist it? Preventing anyone from reading/wrtiting Windows disks by default is honestly a lunar idea, especially if you want new users to onboard the distro from Windows I would love to hear the reasoning about blacklisting that (considering we do not blacklist apfs for ex.) Thanks Nicolas FORMICHELLA
On 2023-12-15 21:42, Nicolas FORMICHELLA wrote:
Dec 15, 2023 20:07:42 Martin Wilck via openSUSE Factory <factory@lists.opensuse.org>:
Many of you will be aware of the fact that some file systems are blacklisted by default on openSUSE. With the forthcoming update of suse-module-tools, the list of disabled file systems will grow:
f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs
will then be blacklisted, too. This means that the respective kernel modules will not be auto-loaded, and that the system won't be able to access media with such file systems immediately when they are inserted.
To override this, run "sudo modprobe $FS_MODULE" in a terminal. You will have the option to load the module just once, or un-blacklist it for future use.
I've created https://en.opensuse.org/SDB:FilesystemBlacklisting with more details and a rationale.
I don't see information about what is wrong with each one, what are the specific dangers if one enables one of those filesystems. The list is incomplete, because reiserfs is not listed, and it can not be mounted. The installation DVD refuses to upgrade a machine if it sees reiserfs in the fstab, even if it is a data partition. It must be an evil one, not even named, like Voldemort >:-)
f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs
Unless I am mistaken, ntfs3 kmod is needed to mount NTFS then why would we blacklist it?
Preventing anyone from reading/wrtiting Windows disks by default is honestly a lunar idea, especially if you want new users to onboard the distro from Windows
I would love to hear the reasoning about blacklisting that (considering we do not blacklist apfs for ex.)
There are several implementations of ntfs in Linux. I know of ntfs and ntfs-3g, but not of ntfs3 -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Op 16-12-2023 om 13:03 schreef Carlos E. R.:
There are several implementations of ntfs in Linux. I know of ntfs and ntfs-3g, but not of ntfs3
ntfs3 is paragon's contribution of the ntfs driver in the kernel, the kernel version of ntfs-3g. It has a "3" because it implements ntfs 3.1. The older ntfs is read-only, this one is rw and faster than the fuse implementation of ntfs-3g. see: https://www.paragon-software.com/home/ntfs3-driver-faq/ Regards, Cor
On 2023-12-16 15:39, Cor Blom wrote:
Op 16-12-2023 om 13:03 schreef Carlos E. R.:
There are several implementations of ntfs in Linux. I know of ntfs and ntfs-3g, but not of ntfs3
ntfs3 is paragon's contribution of the ntfs driver in the kernel, the kernel version of ntfs-3g. It has a "3" because it implements ntfs 3.1. The older ntfs is read-only, this one is rw and faster than the fuse implementation of ntfs-3g.
see: https://www.paragon-software.com/home/ntfs3-driver-faq/
Ah, yes, now I remember. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Sat, 2023-12-16 at 13:03 +0100, Carlos E. R. wrote:
On 2023-12-15 21:42, Nicolas FORMICHELLA wrote:
Dec 15, 2023 20:07:42 Martin Wilck via openSUSE Factory <factory@lists.opensuse.org>:
Many of you will be aware of the fact that some file systems are blacklisted by default on openSUSE. With the forthcoming update of suse-module-tools, the list of disabled file systems will grow:
f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs
will then be blacklisted, too. This means that the respective kernel modules will not be auto-loaded, and that the system won't be able to access media with such file systems immediately when they are inserted.
To override this, run "sudo modprobe $FS_MODULE" in a terminal. You will have the option to load the module just once, or un- blacklist it for future use.
I've created https://en.opensuse.org/SDB:FilesystemBlacklisting with more details and a rationale.
I don't see information about what is wrong with each one, what are the specific dangers if one enables one of those filesystems.
That's not the point. I thought I had explained that in the Wiki page (read the FAQ section, please). The point is that these file systems are not supported by the SUSE kernel team. A blacklist entry does *NOT* imply anything negative about a specific module.
The list is incomplete, because reiserfs is not listed, and it can not be mounted.
Thanks for mentioning it. Reiserfs hasn't been shipped for TW since more than a year. But it's true, the list contains some other FS modules which we aren't shipping, so arguably we should add reiserfs as well.
The installation DVD refuses to upgrade a machine if it sees reiserfs in the fstab, even if it is a data partition. It must be an evil one, not even named, like Voldemort >:-)
f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs
Unless I am mistaken, ntfs3 kmod is needed to mount NTFS then why would we blacklist it?
Please read the wiki page. It is very easy to undo the blacklisting if you want.
Preventing anyone from reading/wrtiting Windows disks by default is honestly a lunar idea, especially if you want new users to onboard the distro from Windows
I would love to hear the reasoning about blacklisting that (considering we do not blacklist apfs for ex.)
There are several implementations of ntfs in Linux. I know of ntfs and ntfs-3g, but not of ntfs3
"modinfo ntfs3" ? Martin
On 2023-12-18 18:29, Martin Wilck via openSUSE Factory wrote:
On Sat, 2023-12-16 at 13:03 +0100, Carlos E. R. wrote:
On 2023-12-15 21:42, Nicolas FORMICHELLA wrote:
Dec 15, 2023 20:07:42 Martin Wilck via openSUSE Factory <factory@lists.opensuse.org>:
Many of you will be aware of the fact that some file systems are blacklisted by default on openSUSE. With the forthcoming update of suse-module-tools, the list of disabled file systems will grow:
f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs
will then be blacklisted, too. This means that the respective kernel modules will not be auto-loaded, and that the system won't be able to access media with such file systems immediately when they are inserted.
To override this, run "sudo modprobe $FS_MODULE" in a terminal. You will have the option to load the module just once, or un- blacklist it for future use.
I've created https://en.opensuse.org/SDB:FilesystemBlacklisting with more details and a rationale.
I don't see information about what is wrong with each one, what are the specific dangers if one enables one of those filesystems.
That's not the point. I thought I had explained that in the Wiki page (read the FAQ section, please). The point is that these file systems are not supported by the SUSE kernel team. A blacklist entry does *NOT* imply anything negative about a specific module.
"wrong" doesn't really mean "wrong" :-) The thing is, it would be interesting to know the rationale behind the decision to no longer support each filesystem, so that the admin that is considering enabling one can make an informed decision.
The list is incomplete, because reiserfs is not listed, and it can not be mounted.
Thanks for mentioning it. Reiserfs hasn't been shipped for TW since more than a year. But it's true, the list contains some other FS modules which we aren't shipping, so arguably we should add reiserfs as well.
The installation DVD refuses to upgrade a machine if it sees reiserfs in the fstab, even if it is a data partition. It must be an evil one, not even named, like Voldemort >:-)
f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, and zonefs
Unless I am mistaken, ntfs3 kmod is needed to mount NTFS then why would we blacklist it?
Please read the wiki page. It is very easy to undo the blacklisting if you want.
That question was posed by Nicola, and Cor explained it very well, for that question and the next :-)
Preventing anyone from reading/wrtiting Windows disks by default is honestly a lunar idea, especially if you want new users to onboard the distro from Windows
I would love to hear the reasoning about blacklisting that (considering we do not blacklist apfs for ex.)
There are several implementations of ntfs in Linux. I know of ntfs and ntfs-3g, but not of ntfs3
"modinfo ntfs3" ?
Telcontar:~ # modinfo ntfs3 modinfo: ERROR: Module ntfs3 not found. Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Mon, 2023-12-18 at 18:52 +0100, Carlos E. R. wrote:
On 2023-12-18 18:29, Martin Wilck via openSUSE Factory wrote:
On Sat, 2023-12-16 at 13:03 +0100, Carlos E. R. wrote:
I've created https://en.opensuse.org/SDB:FilesystemBlacklisting with more details and a rationale.
I don't see information about what is wrong with each one, what are the specific dangers if one enables one of those filesystems.
That's not the point. I thought I had explained that in the Wiki page (read the FAQ section, please). The point is that these file systems are not supported by the SUSE kernel team. A blacklist entry does *NOT* imply anything negative about a specific module.
"wrong" doesn't really mean "wrong" :-)
The thing is, it would be interesting to know the rationale behind the decision to no longer support each filesystem, so that the admin that is considering enabling one can make an informed decision.
There are no particular reasons for blacklisting specific file systems. It's rather the other way around: The file systems that are supported, aka not blacklisted, have been picked individually by SUSE either because they are the state-of-the art Linux filesystems (e.g. btrfs, xfs), or otherwise indispensable (iso9660, vfat), or have been requested by customers.
Telcontar:~ # modinfo ntfs3 modinfo: ERROR: Module ntfs3 not found. Telcontar:~ #
So you're on Leap? This was a posting for the factory ML, and targeted at Factory users. On Leap, it's simpler than on TW, as all supported file system modules are shipped in the kernel-default package; iow, every file system module in the -extra and -optional packages is blacklisted by default. Martin
On 2023-12-18 20:56, Martin Wilck via openSUSE Factory wrote:
On Mon, 2023-12-18 at 18:52 +0100, Carlos E. R. wrote:
On 2023-12-18 18:29, Martin Wilck via openSUSE Factory wrote:
On Sat, 2023-12-16 at 13:03 +0100, Carlos E. R. wrote:
I've created https://en.opensuse.org/SDB:FilesystemBlacklisting with more details and a rationale.
I don't see information about what is wrong with each one, what are the specific dangers if one enables one of those filesystems.
That's not the point. I thought I had explained that in the Wiki page (read the FAQ section, please). The point is that these file systems are not supported by the SUSE kernel team. A blacklist entry does *NOT* imply anything negative about a specific module.
"wrong" doesn't really mean "wrong" :-)
The thing is, it would be interesting to know the rationale behind the decision to no longer support each filesystem, so that the admin that is considering enabling one can make an informed decision.
There are no particular reasons for blacklisting specific file systems. It's rather the other way around: The file systems that are supported, aka not blacklisted, have been picked individually by SUSE either because they are the state-of-the art Linux filesystems (e.g. btrfs, xfs), or otherwise indispensable (iso9660, vfat), or have been requested by customers.
Reiserfs had reasons for being blacklisted, as I remember.
Telcontar:~ # modinfo ntfs3 modinfo: ERROR: Module ntfs3 not found. Telcontar:~ #
So you're on Leap? This was a posting for the factory ML, and targeted at Factory users. On Leap, it's simpler than on TW, as all supported file system modules are shipped in the kernel-default package; iow, every file system module in the -extra and -optional packages is blacklisted by default.
AFAIR, the wiki page doesn't mention it is only for factory. Now that I check, it says "verified on 15.5" ;-) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Mon, 2023-12-18 at 21:06 +0100, Carlos E. R. wrote:
On 2023-12-18 20:56, Martin Wilck via openSUSE Factory wrote:
There are no particular reasons for blacklisting specific file systems. It's rather the other way around: The file systems that are supported, aka not blacklisted, have been picked individually by SUSE either because they are the state-of-the art Linux filesystems (e.g. btrfs, xfs), or otherwise indispensable (iso9660, vfat), or have been requested by customers.
Reiserfs had reasons for being blacklisted, as I remember.
Yes. Feel free to add them to the Wiki page :-)
Telcontar:~ # modinfo ntfs3 modinfo: ERROR: Module ntfs3 not found. Telcontar:~ #
So you're on Leap? This was a posting for the factory ML, and targeted at Factory users. On Leap, it's simpler than on TW, as all supported file system modules are shipped in the kernel-default package; iow, every file system module in the -extra and -optional packages is blacklisted by default.
AFAIR, the wiki page doesn't mention it is only for factory. Now that I check, it says "verified on 15.5" ;-)
Yeah, that's wrong. I'll remove it. Thanks for noting it. Martin
On Mon, 2023-12-18 at 21:49 +0100, Martin Wilck wrote:
On Mon, 2023-12-18 at 21:06 +0100, Carlos E. R. wrote:
AFAIR, the wiki page doesn't mention it is only for factory. Now that I check, it says "verified on 15.5" ;-)
Yeah, that's wrong. I'll remove it. Thanks for noting it.
Well, we've had blacklisted modules since 15.1, and the "unblacklist" mechanism since 15.4. We now just changed the list to make it consistent with the actual situation. So 15.5 is not completely wrong. The "Verified on" is a pitfall of the openSUSE Wiki. You add a link to a distro version, and it adds the text "Verified on" behind your back. Martin
participants (4)
-
Carlos E. R. -
Cor Blom -
Martin Wilck -
Nicolas FORMICHELLA