Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
Control: tag -1 wontfix On Fri, Aug 28, 2020 at 10:41:42PM +0100, Ben Hutchings wrote: > On Fri, 2020-08-28 at 14:43 +0800, Hamish Moffatt wrote: > > Could you please enable CONFIG_F2FS_FS in the cloud kernel? > What makes you think f2fs will be commonly used in cloud deployments? Marking it was wontfix as the OP was not able to persuade as we it might be needed. Bastian -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
On 29/8/20 1:01 pm, Noah Meyerhans wrote: On Sat, Aug 29, 2020 at 11:43:21AM +1000, Hamish Moffatt wrote: Could you please enable CONFIG_F2FS_FS in the cloud kernel? [...] What makes you think f2fs will be commonly used in cloud deployments? I don't know that it will be, but as it supports encryption and compression and benchmarks shows it performs at least as well as ext4, I don't see why it couldn't be a good choice for virtual machines. It seems at least as useful in a cloud deployment as minix and hpfs which are included in this flavour. This sounds like a good argument for turning off minix and hpfs to me. ;) I thought you might say that :) Is F2FS usable as a Debian root filesystem? Does it support all the features (file capabilities and POSIX ACLs, for example) that are commonly used on Debian systems? The cloud team, for what it's worth, does not have any plans to switch from ext4 in the forseeable future. (We probably would not do so unless Debian made the change distro-wide.) That doesn't mean we shouldn't consider enabling it, but I'd like to see a clearer use case. My small amount of research into it (mostly reading wikipedia and a couple of the reference sources) suggests that it's most popular on phones and similar devices, not cloud instances. Do you see use cases involving manipulating filesystems for those type of devices in cloud VMs? Or something else? How are crypto keys handled for its encryption functionality? The cloud kernel is not expected to be useful for 100% of people, even in cloud environments. In cases where specific functionality is needed that isn't available in the cloud kernel, the generic kernel is available and I'd probably recommend that. I envisage using f2fs on cloud instances for their own storage, with the benefit of encryption and compression (without the performance penalty of eg ZFS). f2fs appears to be available in Clear Linux as the root file system since March (https://github.com/clearlinux/distribution/issues/1522, https://www.phoronix.com/scan.php?page=news_item&px=Clear-Linux-F2FS-Root-Option ). Debian is working on this too according to https://www.phoronix.com/scan.php?page=news_item&px=Debian-F2FS-Root-File-System . Crypto setup is handled with fscrypt just as per ext4. thanks Hamish
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
On Fri, 2020-08-28 at 20:01 -0700, Noah Meyerhans wrote: > On Sat, Aug 29, 2020 at 11:43:21AM +1000, Hamish Moffatt wrote: > > > > Could you please enable CONFIG_F2FS_FS in the cloud kernel? > > > [...] > > > > > > What makes you think f2fs will be commonly used in cloud deployments? > > > > > I don't know that it will be, but as it supports encryption and compression > > and benchmarks shows it performs at least as well as ext4, I don't see why > > it couldn't be a good choice for virtual machines. It seems at least as > > useful in a cloud deployment as minix and hpfs which are included in this > > flavour. > > This sounds like a good argument for turning off minix and hpfs to me. > ;) [...] I agree with that; I didn't realise they were enabled. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
On Sat, Aug 29, 2020 at 11:43:21AM +1000, Hamish Moffatt wrote: > > > Could you please enable CONFIG_F2FS_FS in the cloud kernel? > > [...] > > > > What makes you think f2fs will be commonly used in cloud deployments? > > > I don't know that it will be, but as it supports encryption and compression > and benchmarks shows it performs at least as well as ext4, I don't see why > it couldn't be a good choice for virtual machines. It seems at least as > useful in a cloud deployment as minix and hpfs which are included in this > flavour. This sounds like a good argument for turning off minix and hpfs to me. ;) Is F2FS usable as a Debian root filesystem? Does it support all the features (file capabilities and POSIX ACLs, for example) that are commonly used on Debian systems? The cloud team, for what it's worth, does not have any plans to switch from ext4 in the forseeable future. (We probably would not do so unless Debian made the change distro-wide.) That doesn't mean we shouldn't consider enabling it, but I'd like to see a clearer use case. My small amount of research into it (mostly reading wikipedia and a couple of the reference sources) suggests that it's most popular on phones and similar devices, not cloud instances. Do you see use cases involving manipulating filesystems for those type of devices in cloud VMs? Or something else? How are crypto keys handled for its encryption functionality? The cloud kernel is not expected to be useful for 100% of people, even in cloud environments. In cases where specific functionality is needed that isn't available in the cloud kernel, the generic kernel is available and I'd probably recommend that. noah
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
On 29/8/20 7:41 am, Ben Hutchings wrote: Control: tag -1 moreinfo On Fri, 2020-08-28 at 14:43 +0800, Hamish Moffatt wrote: Package: src:linux Version: 5.7.10-1~bpo10+1 Severity: wishlist Hi, Could you please enable CONFIG_F2FS_FS in the cloud kernel? [...] What makes you think f2fs will be commonly used in cloud deployments? I don't know that it will be, but as it supports encryption and compression and benchmarks shows it performs at least as well as ext4, I don't see why it couldn't be a good choice for virtual machines. It seems at least as useful in a cloud deployment as minix and hpfs which are included in this flavour. thanks Hamish
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
Control: tag -1 moreinfo On Fri, 2020-08-28 at 14:43 +0800, Hamish Moffatt wrote: > Package: src:linux > Version: 5.7.10-1~bpo10+1 > Severity: wishlist > > Hi, > Could you please enable CONFIG_F2FS_FS in the cloud kernel? [...] What makes you think f2fs will be commonly used in cloud deployments? Ben. -- Ben Hutchings It is impossible to make anything foolproof because fools are so ingenious. signature.asc Description: This is a digitally signed message part
Bug#969140: linux-image-5.7.0-0.bpo.2-amd64: Please enable CONFIG_F2FS_FS in the cloud image kernel
Package: src:linux Version: 5.7.10-1~bpo10+1 Severity: wishlist Hi, Could you please enable CONFIG_F2FS_FS in the cloud kernel? thanks, Hamish -- Package-specific info: ** Version: Linux version 5.7.0-0.bpo.2-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6), GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Debian 5.7.10-1~bpo10+1 (2020-07-30) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.0-0.bpo.2-amd64 root=/dev/sda ro quiet nosplash console=tty1 console=ttyS0 ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: QEMU product_name: Standard PC (Q35 + ICH9, 2009) product_version: pc-q35-4.1 chassis_vendor: QEMU chassis_version: pc-q35-4.1 bios_vendor: SeaBIOS bios_version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org ** Loaded modules: f2fs crc32_generic cts sha512_ssse3 sha512_generic tun nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt nf_log_ipv4 nf_log_common xt_LOG ipt_REJECT nf_reject_ipv4 nft_limit xt_limit bochs_drm crc32_pclmul drm_vram_helper xt_addrtype drm_ttm_helper ghash_clmulni_intel xt_tcpudp ttm drm_kms_helper xt_conntrack nft_compat cec aesni_intel nft_counter joydev drm libaes evdev crypto_simd cryptd iTCO_wdt glue_helper serio_raw iTCO_vendor_support watchdog sg qemu_fw_cfg button nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink ecryptfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sd_mod t10_pi crc_t10dif crct10dif_generic virtio_net net_failover failover ahci virtio_scsi libahci libata psmouse crct10dif_pclmul crct10dif_common scsi_mod crc32c_intel i2c_i801 lpc_ich virtio_pci mfd_core virtio_ring virtio ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: 10.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.7.0-0.bpo.2-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-5.7.0-0.bpo.2-amd64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-5.7.0-0.bpo.2-amd64 suggests: pn debian-kernel-handbook ii grub-pc 2.02+dfsg1-20+deb10u2 pn linux-doc-5.7 Versions of packages linux-image-5.7.0-0.bpo.2-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information -- debsums errors found: debsums: missing file /usr/share/doc/linux-image-5.7.0-0.bpo.2-amd64/changelog.gz (from linux-image-5.7.0-0.bpo.2-amd64 package) debsums: missing file /usr/share/doc/linux-image-5.7.0-0.bpo.2-amd64/copyright (from linux-image-5.7.0-0.bpo.2-amd64 package)
