Processed: retitle 1000804 to linux: Intel bluetooth regression in 5.15.3, closing 1000804

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1000804 linux: Intel bluetooth regression in 5.15.3
Bug #1000804 [src:linux] (no subject)
Changed Bug title to 'linux: Intel bluetooth regression in 5.15.3' from '(no 
subject)'.
> close 1000804 5.15.5-1
Bug #1000804 [src:linux] linux: Intel bluetooth regression in 5.15.3
Marked as fixed in versions linux/5.15.5-1.
Bug #1000804 [src:linux] linux: Intel bluetooth regression in 5.15.3
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1000804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#998627: linux: please enable the new NTFS3 driver in 5.15

[Heinz Repp]

On Tue, 23 Nov 2021 22:34:25 +0100 Salvatore Bonaccorso 
 wrote:

Are tools available to handle creation and checking of such NTFS3
filesystems? The last time I went to the paragon software site it
mentioned it was planning. This is not a must, but kept me for
slightly on the on hold position for enabling it.


You mean you are holding back the DRIVER because you are missing 
USERSPACE utilities to handle and examine NTFS 3.1 filesystems?!?


One has nothing to do with the other. There are a lot of NTFS utilities 
available with the ntfs-3g package, namely:



mkntfs
ntfscat
ntfsclone
ntfscluster
ntfscmp
ntfscp
ntfsdecrypt
ntfsfallocate
ntfsfix
ntfsinfo
ntfslabel
ntfsls
ntfsrecover
ntfsresize
ntfssecaudit
ntfstruncate
ntfsundelete
ntfswipe


Nearly all of them (apart from ntfssecaudit cases) work on devices, not 
on mounted file systems, so the NTFS driver used is not in involved. An 
idea would be to split the ntfs-3g package into

ntfs-3g-tools
ntfs-3g-fusedriver
libntfs-3g (on which the former depends)

A Paragon donated mkfs.ntfs would be a nice thing, but mkntfs from 
ntfs-3g already fits for nearly all purposes. And I guess most people 
would want the new ntfs3 driver for filesystems created with Windows.



On Sat, 27 Nov 2021 14:14:53 +0100 Salvatore Bonaccorso 
 wrote:

Apart from Ted Ts'o comments, I looked up the mailinglist,
https://lore.kernel.org/ntfs3/ which relatively quiet. The same
goes for commits in fs/ntfs3 in mainline, since the merge in 5.15
there ws almost no activity, which is slightly unusual for something
new entering.


Looking on the same mailinglist, I think they recently did a lot to fix 
the test issues and much more, as can be seen:



[PATCH] ntfs3: Fix showing umask option
 2021-11-27 13:51 UTC 


[PATCH 1/2] fs/ntfs3: clarify why $Extend init is being skipped
 2021-11-26 12:04 UTC  (2+ messages)

[PATCH] Doc/fs/ntfs3: Fix a trivial typo
 2021-11-26 11:52 UTC  (2+ messages)

[ramfs] 0858d7da8a: canonical_address#:#[##]
 2021-11-26 11:36 UTC  (2+ messages)

[PATCH] fs/ntfs3: Fix some memory leaks in an error handling path of 
'log_replay()'
 2021-11-23 15:47 UTC  (2+ messages)

Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
 2021-11-19 14:19 UTC  (3+ messages)

No more accessible (compromised) NTFS volume
 2021-11-16 17:16 UTC 


[PATCH v2 0/4] fs/ntfs3: Various fixes for xattr and files
 2021-11-15 15:50 UTC  (11+ messages)
` [PATCH 1/4] fs/ntfs3: Keep preallocated only if option prealloc enabled
` [PATCH 2/4] fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl 
functions
` [PATCH 3/4] fs/ntfs3: Update i_ctime when xattr is added
` [PATCH 4/4] fs/ntfs3: Optimize locking in ntfs_save_wsl_perm

[BUG] Unable to mount NTFS drive, no error in dmesg
 2021-11-11  4:39 UTC 


Readahead for compressed data
 2021-10-29  6:15 UTC  (16+ messages)

[PATCH v2] checkpatch: Improve CVS revision marker check
 2021-10-27 10:56 UTC 


[PATCH] checkpatch: Remove cvs keyword check
 2021-10-27  9:21 UTC  (4+ messages)

[PATCH 0/4] fs/ntfs3: Various fixes for xfstests problems
 2021-10-26 21:37 UTC  (11+ messages)
` [PATCH 1/4] fs/ntfs3: In function ntfs_set_acl_ex do not change inode->i_mode 
if called from function ntfs_init_acl
` [PATCH 2/4] fs/ntfs3: Fix fiemap + fix shrink file size (to remove 
preallocated space)
` [PATCH 3/4] fs/ntfs3: Check new size for limits
` [PATCH 4/4] fs/ntfs3: Update valid size if -EIOCBQUEUED

[PATCH] fs/ntfs3: clarify emitted log message when marking volumes as dirty
 2021-10-26 20:56 UTC  (3+ messages)

[PATCH 2/2] fs/ntfs3: clarify emitted log message when marking volumes as dirty
 2021-10-26 20:55 UTC 


[PATCH] fs/ntfs3: clarify why $Extend init is being skipped
 2021-10-26 20:49 UTC  (2+ messages)

(very low importance) NTFS version message
 2021-10-26 18:03 UTC  (2+ messages)

[PATCH 0/4] fs/ntfs3: Various fixes for xattr and files
 2021-10-24 11:13 UTC  (12+ messages)
` [PATCH 1/4] fs/ntfs3: Keep preallocated only if option prealloc enabled
` [PATCH 2/4] fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl 
functions
` [PATCH 3/4] fs/ntfs3: Optimize locking in ntfs_save_wsl_perm
` [PATCH 4/4] fs/ntfs3: Update i_ctime when xattr is added

NTFS3: junctions are not properly resolved
 2021-10-22 12:50 UTC 


[PATCH 0/2] Removing of old code
 2021-10-19 17:11 UTC  (4+ messages)
` [PATCH 1/2] fs/ntfs3: Remove unnecessary functions

cleanup block device inode syncing
 2021-10-19 13:54 UTC  (14+ messages)
` [PATCH 1/7] fs: remove __sync_filesystem
` [PATCH 2/7] block: remove __sync_blockdev
` [PATCH 3/7] xen-blkback: use sync_blockdev
` [PATCH 4/7] btrfs: "
` [PATCH 5/7] fat: use sync_blockdev_nowait
` [PATCH 6/7] ntfs3: "
` [PATCH 7/7] block: simplify the block device syncing code

don't use ->bd_inode to access the block device size v3
 2021-10-19  1:04 UTC  (40+ messages)
` [PATCH 01/30] block: move the SECTOR_SIZE related definitions to blk_types.h
` [PATCH 02/30] block: add a bdev_nr_bytes helper
` [PATCH 03/30] bcache: remove 

Processing of linux_5.16~rc3-1~exp1_source.changes

[Debian FTP Masters]

linux_5.16~rc3-1~exp1_source.changes uploaded successfully to localhost
along with the files:
  linux_5.16~rc3-1~exp1.dsc
  linux_5.16~rc3.orig.tar.xz
  linux_5.16~rc3-1~exp1.debian.tar.xz
  linux_5.16~rc3-1~exp1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

linux_5.16~rc3-1~exp1_source.changes is NEW

[Debian FTP Masters]

binary:affs-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:affs-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:affs-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:affs-modules-5.16.0-rc3-octeon-di is NEW.
binary:ata-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:ata-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:ata-modules-5.16.0-rc3-armmp-di is NEW.
binary:ata-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:ata-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:btrfs-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:btrfs-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:btrfs-modules-5.16.0-rc3-armmp-di is NEW.
binary:btrfs-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:btrfs-modules-5.16.0-rc3-marvell-di is NEW.
binary:btrfs-modules-5.16.0-rc3-octeon-di is NEW.
binary:btrfs-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:btrfs-modules-5.16.0-rc3-s390x-di is NEW.
binary:cdrom-core-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:cdrom-core-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:cdrom-core-modules-5.16.0-rc3-armmp-di is NEW.
binary:cdrom-core-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:cdrom-core-modules-5.16.0-rc3-marvell-di is NEW.
binary:cdrom-core-modules-5.16.0-rc3-octeon-di is NEW.
binary:cdrom-core-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:cdrom-core-modules-5.16.0-rc3-s390x-di is NEW.
binary:crc-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:crc-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:crc-modules-5.16.0-rc3-armmp-di is NEW.
binary:crc-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:crc-modules-5.16.0-rc3-marvell-di is NEW.
binary:crc-modules-5.16.0-rc3-octeon-di is NEW.
binary:crc-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:crc-modules-5.16.0-rc3-s390x-di is NEW.
binary:crypto-dm-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:crypto-dm-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:crypto-dm-modules-5.16.0-rc3-armmp-di is NEW.
binary:crypto-dm-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:crypto-dm-modules-5.16.0-rc3-marvell-di is NEW.
binary:crypto-dm-modules-5.16.0-rc3-octeon-di is NEW.
binary:crypto-dm-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:crypto-dm-modules-5.16.0-rc3-s390x-di is NEW.
binary:crypto-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:crypto-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:crypto-modules-5.16.0-rc3-armmp-di is NEW.
binary:crypto-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:crypto-modules-5.16.0-rc3-marvell-di is NEW.
binary:crypto-modules-5.16.0-rc3-octeon-di is NEW.
binary:crypto-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:crypto-modules-5.16.0-rc3-s390x-di is NEW.
binary:dasd-extra-modules-5.16.0-rc3-s390x-di is NEW.
binary:dasd-modules-5.16.0-rc3-s390x-di is NEW.
binary:efi-modules-5.16.0-rc3-armmp-di is NEW.
binary:event-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:event-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:event-modules-5.16.0-rc3-armmp-di is NEW.
binary:event-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:event-modules-5.16.0-rc3-marvell-di is NEW.
binary:event-modules-5.16.0-rc3-octeon-di is NEW.
binary:event-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:ext4-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:ext4-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:ext4-modules-5.16.0-rc3-armmp-di is NEW.
binary:ext4-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:ext4-modules-5.16.0-rc3-marvell-di is NEW.
binary:ext4-modules-5.16.0-rc3-octeon-di is NEW.
binary:ext4-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:ext4-modules-5.16.0-rc3-s390x-di is NEW.
binary:f2fs-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:f2fs-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:f2fs-modules-5.16.0-rc3-armmp-di is NEW.
binary:f2fs-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:f2fs-modules-5.16.0-rc3-marvell-di is NEW.
binary:f2fs-modules-5.16.0-rc3-octeon-di is NEW.
binary:f2fs-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:f2fs-modules-5.16.0-rc3-s390x-di is NEW.
binary:fancontrol-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:fat-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:fat-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:fat-modules-5.16.0-rc3-armmp-di is NEW.
binary:fat-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:fat-modules-5.16.0-rc3-marvell-di is NEW.
binary:fat-modules-5.16.0-rc3-octeon-di is NEW.
binary:fat-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:fat-modules-5.16.0-rc3-s390x-di is NEW.
binary:fb-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:fb-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:fb-modules-5.16.0-rc3-armmp-di is NEW.
binary:fb-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:fb-modules-5.16.0-rc3-marvell-di is NEW.
binary:fb-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:firewire-core-modules-5.16.0-rc3-loongson-3-di is NEW.
binary:firewire-core-modules-5.16.0-rc3-powerpc64le-di is NEW.
binary:fuse-modules-5.16.0-rc3-4kc-malta-di is NEW.
binary:fuse-modules-5.16.0-rc3-5kc-malta-di is NEW.
binary:fuse-modules-5.16.0-rc3-armmp-di is NEW.
binary:fuse-modules-5.16.0-rc3-loongson-3-di is

Bug#997907: marked as done (linux-image-arm64: CONFIG_EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER unset in 5.14 kernel)

[Debian Bug Tracking System]

Your message dated Mon, 29 Nov 2021 19:00:09 +
with message-id 
and subject line Bug#997907: fixed in linux 5.16~rc3-1~exp1
has caused the Debian Bug report #997907,
regarding linux-image-arm64: CONFIG_EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER 
unset in 5.14 kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
997907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-arm64
Version: 5.14.9-2
Severity: important

Dear Maintainer,

In bullseye, version 5.10.70-1 has the 
CONFIG_EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER
kernel configuration set to 'y'. In bookworm it is unset which disable this 
feature.

This kernel configuration parameter allows for the EFI stub of the kernel to
parse and use a 'initrd=' parameter to set up an initrd when booting from EFI.
Boot loaders like 'systemd-boot' or 'refind' set this parameter if configured
to pass an initrd. If the kernel configuration parameter is unset, the
`initrd=` paramater is ignored, and can result in an unbootable system because
the initrd has not setup the root filesystem.

Without the kernel configuaration set, it is not possible to use 'systemd-boot'
or 'refind' on arm64 as both of these bootloaders assume the kernel will
handle the 'initrd=' flag and setup the initrd.

Please consider enabling CONFIG_EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER on
arm64 so using 'systemd-boot' or 'refind' can continue to work. Until these
bootloaders have been updated to use an alternative method of passing the
initrd to the EFI stub, it is not possible to have a booting system.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.16~rc3-1~exp1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Nov 2021 17:22:55 +0100
Source: linux
Architecture: source
Version: 5.16~rc3-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 997907
Changes:
 linux (5.16~rc3-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Salvatore Bonaccorso ]
   * [rt] Update to 5.16-rc2-rt4
   * [arm64] drivers/firmware/efi: Enable
 EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER (Closes: #997907)
   * liblockdep: Remove code to build liblockdep packages
   * [rt] Update to 5.16-rc3-rt5
 .
   [ Uwe Kleine-König ]
   * [arm*] Enable support for Raspberry Pi POE hat (PWM_RASPBERRYPI_POE)
   * [arm*] Enable suport for pinctrl-based I2C multiplexer (I2C_MUX_PINCTRL).
 These are used (among others) on the Raspberry Pi CM4 IO Board.
Checksums-Sha1:
 7101d2253446355a3d996856d33ae206d4931751 198878 linux_5.16~rc3-1~exp1.dsc
 d26d5227a90dd303b36617f195c20b712f502104 129109608 linux_5.16~rc3.orig.tar.xz
 21b9f2c2414e83d24730c494e8cbad669d86b7c5 1261348 
linux_5.16~rc3-1~exp1.debian.tar.xz
 1e9b81a416a0b2da4fa9f84548536c93fa0e0a20 6385 
linux_5.16~rc3-1~exp1_source.buildinfo
Checksums-Sha256:
 b4af41c5db5bbc232af7135978f11d1afa60b09fae2b072566638b97265fc4f7 198878 
linux_5.16~rc3-1~exp1.dsc
 20732ebc7dd1ae99fe624865a7c3ce82ccbd7bb470c6a33b81e66de05c99618d 129109608 
linux_5.16~rc3.orig.tar.xz
 bfbf38bf31d172423146942bb6378210feceb17a695e98ef9d85c1e43de47076 1261348 
linux_5.16~rc3-1~exp1.debian.tar.xz
 b1716a36a1752fb4fd343efdd1ab97cd9542d3decb016891b6b8d2d0ece091ff 6385 
linux_5.16~rc3-1~exp1_source.buildinfo
Files:
 29c661248e8c3456ff418fea27a301f3 198878 kernel optional 
linux_5.16~rc3-1~exp1.dsc
 e10cd219967e91f085dc89e4e2318b9a 129109608 kernel optional 
linux_5.16~rc3.orig.tar.xz
 bf1842d4c2dccca4ad0bd146832b1151 1261348 kernel optional 
linux_5.16~rc3-1~exp1.debian.tar.xz
 a313365bbf31d8578bec75b791313baf 6385 kernel optional 
linux_5.16~rc3-1~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAm

linux_5.16~rc3-1~exp1_source.changes ACCEPTED into experimental, experimental

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Nov 2021 17:22:55 +0100
Source: linux
Architecture: source
Version: 5.16~rc3-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 997907
Changes:
 linux (5.16~rc3-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Salvatore Bonaccorso ]
   * [rt] Update to 5.16-rc2-rt4
   * [arm64] drivers/firmware/efi: Enable
 EFI_GENERIC_STUB_INITRD_CMDLINE_LOADER (Closes: #997907)
   * liblockdep: Remove code to build liblockdep packages
   * [rt] Update to 5.16-rc3-rt5
 .
   [ Uwe Kleine-König ]
   * [arm*] Enable support for Raspberry Pi POE hat (PWM_RASPBERRYPI_POE)
   * [arm*] Enable suport for pinctrl-based I2C multiplexer (I2C_MUX_PINCTRL).
 These are used (among others) on the Raspberry Pi CM4 IO Board.
Checksums-Sha1:
 7101d2253446355a3d996856d33ae206d4931751 198878 linux_5.16~rc3-1~exp1.dsc
 d26d5227a90dd303b36617f195c20b712f502104 129109608 linux_5.16~rc3.orig.tar.xz
 21b9f2c2414e83d24730c494e8cbad669d86b7c5 1261348 
linux_5.16~rc3-1~exp1.debian.tar.xz
 1e9b81a416a0b2da4fa9f84548536c93fa0e0a20 6385 
linux_5.16~rc3-1~exp1_source.buildinfo
Checksums-Sha256:
 b4af41c5db5bbc232af7135978f11d1afa60b09fae2b072566638b97265fc4f7 198878 
linux_5.16~rc3-1~exp1.dsc
 20732ebc7dd1ae99fe624865a7c3ce82ccbd7bb470c6a33b81e66de05c99618d 129109608 
linux_5.16~rc3.orig.tar.xz
 bfbf38bf31d172423146942bb6378210feceb17a695e98ef9d85c1e43de47076 1261348 
linux_5.16~rc3-1~exp1.debian.tar.xz
 b1716a36a1752fb4fd343efdd1ab97cd9542d3decb016891b6b8d2d0ece091ff 6385 
linux_5.16~rc3-1~exp1_source.buildinfo
Files:
 29c661248e8c3456ff418fea27a301f3 198878 kernel optional 
linux_5.16~rc3-1~exp1.dsc
 e10cd219967e91f085dc89e4e2318b9a 129109608 kernel optional 
linux_5.16~rc3.orig.tar.xz
 bf1842d4c2dccca4ad0bd146832b1151 1261348 kernel optional 
linux_5.16~rc3-1~exp1.debian.tar.xz
 a313365bbf31d8578bec75b791313baf 6385 kernel optional 
linux_5.16~rc3-1~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmGk/qhfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EfOMP/RPjfJ2Qfc7Pjv43YN3nMLDILXv9bh/B
rJW4qGUUq4lZ3FSC4/WggMuGBPr5FEKNsgQhxPZDOHYfbX6pGBC+woJzNryNvYVd
Y42u5TuT+hRGcGbtpB3kQ34MgRsejbvhrKd5UCD1uvvFnatE5L3PJU6gBPRC5Xm/
RFOmXG73e7Ww5/GSgHsTj6ALo6iSbI0hum/Q4Pk0xNRemgpmUJCKMp5DStUfJZ6E
gM9RiRkssAf7qsrgnod18POu2GYKBWQTkAoequrnT/tp4e/7y+vtdLzGFVf4fRsH
esfKO2sVbeLhmMth1jZFPeP01RtoOq0cx1OSHYIdK74//weNZuKlZlmkfnvYervq
zg/1sjL08XH93feh8jgC4xaXMKM/YLPRoDSxdJaM8TKN2NbVe5scqGtszLa5gtNC
/6G+gT1tGipoEucC6tokzfnFTaCofRb5gvEOSi+RPKzEeyYHPTFQUxbCeQuFBHIC
WKQmuVapvl8kc+vHkSQU9VeL7LplfXZ3E+DgU8DmEHWJ7u86eu6c0/K1h92Sj4co
8cPkSonNtHjzsa9s3hS9CqDB2IjlcEQH+86xDZqPWhMRY0IMG2EoQh09iSRREn9c
7xchQWonFIsUlxJQeJPbdg7A2xWLeqrwGKSOgW0ghs6TR2mUq16zcM/kIIqHOaNa
R0ccrsfTzn14
=VK/B
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Upcoming stable point release (11.2)

[Adam D. Barratt]

Hi,

The next point release for "bullseye" (11.2) is scheduled for Saturday,
December 18th. Processing of new uploads into bullseye-proposed-updates 
will be frozen during the preceding weekend.

Regards,

Adam

Bug#998716: linux-image-5.14.0-2-amd64: The package size has grown a lot compared to 5.8/5.10 releases

[Ben Hutchings]

On Sun, 07 Nov 2021 03:52:13 +0200 Bohdan Horbeshko
 wrote:
> Package: linux-image-5.14.0-2-amd64
> Severity: minor
> 
> Dear Maintainer,
> 
> the Installed-Size of the package has occasionally grown up to 375 MB,
> which is about 30% larger than several minor releases before. A kindful
> anonymous person has collected some more information here:
> https://www.linux.org.ru/forum/general/16628666?cid=16628797 , and found
> out that virtually every module has been grown in size. So this is
> likely related to compilation options, rather than to some added modules
> as I suspected before.
> 
> Please investigate the actual reason and report if this can/would be
> fixed in further packages, thanks.
[...]

The linked thread mentioned floppy.ko as an exmaple. Comparing the
versions I have installed here:

~$ ls -l /lib/modules/*/kernel/drivers/block/floppy.ko
-rw-r--r-- 1 root root 182555 Aug  3 07:50 
/lib/modules/5.10.0-8-amd64/kernel/drivers/block/floppy.ko
-rw-r--r-- 1 root root 196947 Nov 26 06:33 
/lib/modules/5.15.0-2-amd64/kernel/drivers/block/floppy.ko

there's about a 14 KiB increase from 5.10 to 5.15.

The code and static data sizes are roughly the same, actually slightly
smaller:

~$ size /lib/modules/*/kernel/drivers/block/floppy.ko
   textdata bss dec hex filename
  642134893   14660   83766   14736 
/lib/modules/5.10.0-8-amd64/kernel/drivers/block/floppy.ko
  636194836   16516   84971   14beb 
/lib/modules/5.15.0-2-amd64/kernel/drivers/block/floppy.ko

The bss can be ignored as it doesn't take up disk space.

Listing the sections with "objdump -h", I see a new section in 5.15:

Idx Name  Size  VMA   LMA   File off  Algn
[...]
 26 .BTF  2b58      00010c40  2**0
  CONTENTS, READONLY

That's a size of about 11 KiB, so most of the increase.

After that I compared *all* the modules installed by these versions:

~$ du --bytes --summ /lib/modules/5.10.0-8-amd64/kernel
294650546 /lib/modules/5.10.0-8-amd64/kernel
~$ du --bytes --summ /lib/modules/5.15.0-2-amd64/kernel
371262312 /lib/modules/5.15.0-2-amd64/kernel

About a 73 MiB increase.

I calculated the total size of .BTF sections:

$ find /lib/modules/5.15.0-2-amd64/ -name '*.ko' | xargs objdump -h -j .BTF | 
awk 'BEGIN { total = 0 } $2 == ".BTF" { total = total + strtonum("0x" $3) } END 
{ print total }'
objdump: Warning: Separate debug info file 
/usr/lib/modules/5.15.0-2-amd64/kernel/sound/usb/usx2y/snd-usb-us122l.ko found, 
but CRC does not match - ignoring
objdump: Warning: Separate debug info file 
/usr/lib/modules/5.15.0-2-amd64/kernel/drivers/leds/leds-gpio.ko found, but CRC 
does not match - ignoring
objdump: Warning: Separate debug info file 
/usr/lib/modules/5.15.0-2-amd64/kernel/fs/nls/nls_cp862.ko found, but CRC does 
not match - ignoring
61693267

About 59 MiB, so again most of the increase.

It appears that BTF in modules was enabled in Linux 5.11 by


I also compared the total sizes of code and static data:

$ find /lib/modules/5.10.0-8-amd64/ -name '*.ko' | xargs objdump -h  | awk 
'BEGIN { total = 0 } $2 ~ /^\..*(text|data)/ { total = total + strtonum("0x" 
$3) } END { print total }'
objdump: Warning: Separate debug info file 
/usr/lib/modules/5.10.0-8-amd64/kernel/sound/usb/usx2y/snd-usb-us122l.ko found, 
but CRC does not match - ignoring
objdump: Warning: Separate debug info file 
/usr/lib/modules/5.10.0-8-amd64/kernel/drivers/hid/hid-macally.ko found, but 
CRC does not match - ignoring
objdump: Warning: Separate debug info file 
/usr/lib/modules/5.10.0-8-amd64/kernel/fs/fat/vfat.ko found, but CRC does not 
match - ignoring
88844481
$ find /lib/modules/5.15.0-2-amd64/ -name '*.ko' | xargs objdump -h  | awk 
'BEGIN { total = 0 } $2 ~ /^\..*(text|data)/ { total = total + strtonum("0x" 
$3) } END { print total }'
objdump: Warning: Separate debug info file 
/usr/lib/modules/5.15.0-2-amd64/kernel/sound/usb/usx2y/snd-usb-us122l.ko found, 
but CRC does not match - ignoring
objdump: Warning: Separate debug info file 
/usr/lib/modules/5.15.0-2-amd64/kernel/drivers/leds/trigger/ledtrig-default-on.ko
 found, but CRC does not match - ignoring
objdump: Warning: Separate debug info file 
/usr/lib/modules/5.15.0-2-amd64/kernel/fs/nls/mac-roman.ko found, but CRC does 
not match - ignoring
93202503

About 4 MiB increase. This is probably a combination of changes in code
generation between gcc 10 and 11, increases in complexity of existing
code modules, and a few new drivers and features being enabled. Without
doing some full rebuilds it's not possible to separate these.

That leaves about 10 MiB of the increase in installed module size not
yet explained.

Ben.

-- 
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.



signature.asc
Description: This is a digitally signed message part

Bug#998716: linux-image-5.14.0-2-amd64: The package size has grown a lot compared to 5.8/5.10 releases

[Горбешко Богдан]

On 30.11.2021 01:57, Ben Hutchings wrote:


About 59 MiB, so again most of the increase.

It appears that BTF in modules was enabled in Linux 5.11 by



So the patch that was supposed to drastically reduce the size of modules 
by extracting the debugging info to a separate deduplicated file, 
actually increased it even more? Sounds pretty ironic.


Or did the deduplication finally make BTFs reasonably small to be 
included by default, as they were much larger before and thus were disabled?