Processed: forcibly merging 974921 1057619
Processing commands for cont...@bugs.debian.org: > forcemerge 974921 1057619 Bug #974921 [src:linux] Could you consider CONFIG_VDPA=m Bug #974921 [src:linux] Could you consider CONFIG_VDPA=m Marked as found in versions linux/6.6.4-1~exp1. Bug #1057619 [src:linux] linux-image-6.6-amd64-unsigned: Enable VDUSE (vdpa-user) modules (vdpa, virtio-vdpa, vduse) Marked as found in versions linux/5.9.6-1. Merged 974921 1057619 > thanks Stopping processing here. Please contact me if you need assistance. -- 1057619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057619 974921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 974921 to Could you consider CONFIG_VDPA=m
Processing commands for cont...@bugs.debian.org: > retitle 974921 Could you consider CONFIG_VDPA=m Bug #974921 [src:linux] linux-image-5.9.0-2-arm64: Could you consider CONFIG_VDPA=m and CONFIG_VFIO_MDEV=m ? Changed Bug title to 'Could you consider CONFIG_VDPA=m' from 'linux-image-5.9.0-2-arm64: Could you consider CONFIG_VDPA=m and CONFIG_VFIO_MDEV=m ?'. > thanks Stopping processing here. Please contact me if you need assistance. -- 974921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1057619 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1057619 src:linux 6.6.4-1~exp1 Bug #1057619 [linux-image-6.6-amd64-unsigned] linux-image-6.6-amd64-unsigned: Enable VDUSE (vdpa-user) modules (vdpa, virtio-vdpa, vduse) Bug reassigned from package 'linux-image-6.6-amd64-unsigned' to 'src:linux'. No longer marked as found in versions linux/6.6.4-1~exp1. Ignoring request to alter fixed versions of bug #1057619 to the same values previously set Bug #1057619 [src:linux] linux-image-6.6-amd64-unsigned: Enable VDUSE (vdpa-user) modules (vdpa, virtio-vdpa, vduse) Marked as found in versions linux/6.6.4-1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1057619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057619: linux-image-6.6-amd64-unsigned: Enable VDUSE (vdpa-user) modules (vdpa, virtio-vdpa, vduse)
Package: linux-image-6.6-amd64-unsigned Version: 6.6.4-1~exp1 Severity: wishlist Dear Maintainer, Linux 5.15+ has a cool new userspace block device interface: VDUSE. https://docs.kernel.org/userspace-api/vduse.html https://www.phoronix.com/news/Linux-5.15-VDUSE-vDPA My testing shows that it's a real breakthrough in the userspace block device area: https://git.yourcmc.ru/vitalif/vitastor/src/branch/master/docs/usage/qemu.en.md#vduse But all current Debian Linux kernels have CONFIG_VDPA, CONFIG_VDPA_USER, CONFIG_VIRTIO_VDPA disabled. Ubuntu, Proxmox, Fedora, kernel-mainline for RHEL all have it enabled. Please enable them in Debian too! -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'oldstable-debug'), (500, 'oldoldstable-debug'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.34-060134-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-6.6-amd64-unsigned depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.6-amd64-unsigned recommends: pn apparmor ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.6-amd64-unsigned suggests: pn debian-kernel-handbook ii grub-efi-amd64 2.06-7 pn linux-doc-6.6
Bug#1057040: firmware-qcom-soc: please add qcom/sc8280xp/LENOVO/21BX/audioreach-tplg.bin and symlink
On Tuesday, 5 December 2023 18:30:39 CET Diederik de Haas wrote: > > Link: qcom/sc8280xp/SC8280XP-LENOVO-X13S-tplg.bin -> > > LENOVO/21BX/audioreach-tplg.bin > > Added upstream in commit f9a35b3f0779844aa686b76506344db70a72820d and part > of upstream's 20230804 release. Link was added in 7d94e0fa84701f0c01877c21cf4857f94fd367ab, part of 20230919 signature.asc Description: This is a digitally signed message part.
Bug#1057040: firmware-qcom-soc: please add qcom/sc8280xp/LENOVO/21BX/audioreach-tplg.bin and symlink
On Tuesday, 28 November 2023 14:29:28 CET Emanuele Rocca wrote: > Package: firmware-qcom-soc > Version: 20230515-3 > > The file qcom/sc8280xp/LENOVO/21BX/audioreach-tplg.bin and its symlink > qcom/sc8280xp/SC8280XP-LENOVO-X13S-tplg.bin are needed by the Lenovo > Thinkpad X13s. Please consider adding them to firmware-qcom-soc. > > File: qcom/sc8280xp/LENOVO/21BX/audioreach-tplg.bin > Link: qcom/sc8280xp/SC8280XP-LENOVO-X13S-tplg.bin -> > LENOVO/21BX/audioreach-tplg.bin Added upstream in commit f9a35b3f0779844aa686b76506344db70a72820d and part of upstream's 20230804 release. signature.asc Description: This is a digitally signed message part.
Re: Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Hi,
On Tue, Dec 05, 2023 at 05:14:20PM +0100, Salvatore Bonaccorso wrote:
> Control: reassign -1 src:cryptsetup 2:2.6.1-5
>
> Hi
>
> On Tue, Dec 05, 2023 at 04:55:58PM +0100, Salvatore Bonaccorso wrote:
> > Hi,
> >
> > On Tue, Dec 05, 2023 at 04:38:19PM +0100, Salvatore Bonaccorso wrote:
> > > Control: tags -1 + confirmed
> > >
> > > On Tue, Dec 05, 2023 at 06:23:45AM +0100, Michael Ott wrote:
> > > > Package: src:linux
> > > > Version: 6.6.4-1~exp1
> > > > Severity: important
> > > >
> > > > Dear Maintainer,
> > > >
> > > > After updating to the 6.6 kernel the password for my encryption does
> > > > not longer
> > > > work
> > > >
> > > > Please unlock disk nvme0n1p3_crypt: **
> > > > device-mapper: table: 253:0: crypt: Error allocation crypto tfm
> > > > (_ENOENT)
> > > > device-mapper: ioctl: error adding target to table
> > > > device-mapper: reload ioctl on nvme0n1p3_crypt (253:0) failed: No such
> > > > file or
> > > > directory
> > > > cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or
> > > > options?
> > > >
> > > > Everything works with 6.5. I also downgrade systemd and cryptosetup but
> > > > no
> > > > changes
> > >
> > > I suspect this is related to changes around
> > > https://git.kernel.org/linus/68cf01760bc0891074e813b9bb06d2696cac1c01
> > > (but not verified, nor tracked down).
> >
> > Actually after a more closer look on what is in the initrd: Bastian
> > can be this due to switching to compressed modules? If this claim is
> > correct then likely initramfs-tools would not copy them to the initrd.
>
> It looks that we only consider *.ko uncompressed in
> debian/initramfs/hooks/cryptroot:
>
> add_modules() {
> local glob="$1" found=n
> shift
> for mod in $(find -H "$@" -name "$glob.ko" -type f -printf '%f\n'); do
> manual_add_modules "${mod%.ko}"
> found=y
> done
> [ "$found" = y ] && return 0 || return 1
> }
>
> but various modules are now with 6.6.4-1~exp1 compressed:
>
> a relatively quick woraround would be to change the function to:
>
> add_modules() {
> local glob="$1" found=n
> shift
> for mod in $(find -H "$@" -name "$glob.ko*" -type f -printf '%f\n'); do
> manual_add_modules "${mod%.ko*}"
> found=y
> done
> [ "$found" = y ] && return 0 || return 1
> }
>
> Is this the correct approach though? Which other hook functions might
> be affected by the change in linux by switching to compressed modules?
And in fact this is the solution proposed in #1036049.
Regards,
Salvatore
Processed: Re: Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Processing control commands: > reassign -1 src:cryptsetup 2:2.6.1-5 Bug #1057441 [src:linux] linux-image-6.6-amd64: Crypt does not longer work Bug reassigned from package 'src:linux' to 'src:cryptsetup'. No longer marked as found in versions linux/6.6.4-1~exp1. Ignoring request to alter fixed versions of bug #1057441 to the same values previously set Bug #1057441 [src:cryptsetup] linux-image-6.6-amd64: Crypt does not longer work Marked as found in versions cryptsetup/2:2.6.1-5. -- 1057441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Control: reassign -1 src:cryptsetup 2:2.6.1-5
Hi
On Tue, Dec 05, 2023 at 04:55:58PM +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Tue, Dec 05, 2023 at 04:38:19PM +0100, Salvatore Bonaccorso wrote:
> > Control: tags -1 + confirmed
> >
> > On Tue, Dec 05, 2023 at 06:23:45AM +0100, Michael Ott wrote:
> > > Package: src:linux
> > > Version: 6.6.4-1~exp1
> > > Severity: important
> > >
> > > Dear Maintainer,
> > >
> > > After updating to the 6.6 kernel the password for my encryption does not
> > > longer
> > > work
> > >
> > > Please unlock disk nvme0n1p3_crypt: **
> > > device-mapper: table: 253:0: crypt: Error allocation crypto tfm (_ENOENT)
> > > device-mapper: ioctl: error adding target to table
> > > device-mapper: reload ioctl on nvme0n1p3_crypt (253:0) failed: No such
> > > file or
> > > directory
> > > cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or
> > > options?
> > >
> > > Everything works with 6.5. I also downgrade systemd and cryptosetup but no
> > > changes
> >
> > I suspect this is related to changes around
> > https://git.kernel.org/linus/68cf01760bc0891074e813b9bb06d2696cac1c01
> > (but not verified, nor tracked down).
>
> Actually after a more closer look on what is in the initrd: Bastian
> can be this due to switching to compressed modules? If this claim is
> correct then likely initramfs-tools would not copy them to the initrd.
It looks that we only consider *.ko uncompressed in
debian/initramfs/hooks/cryptroot:
add_modules() {
local glob="$1" found=n
shift
for mod in $(find -H "$@" -name "$glob.ko" -type f -printf '%f\n'); do
manual_add_modules "${mod%.ko}"
found=y
done
[ "$found" = y ] && return 0 || return 1
}
but various modules are now with 6.6.4-1~exp1 compressed:
a relatively quick woraround would be to change the function to:
add_modules() {
local glob="$1" found=n
shift
for mod in $(find -H "$@" -name "$glob.ko*" -type f -printf '%f\n'); do
manual_add_modules "${mod%.ko*}"
found=y
done
[ "$found" = y ] && return 0 || return 1
}
Is this the correct approach though? Which other hook functions might
be affected by the change in linux by switching to compressed modules?
Regards,
Salvatore
Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Hi, On Tue, Dec 05, 2023 at 04:38:19PM +0100, Salvatore Bonaccorso wrote: > Control: tags -1 + confirmed > > On Tue, Dec 05, 2023 at 06:23:45AM +0100, Michael Ott wrote: > > Package: src:linux > > Version: 6.6.4-1~exp1 > > Severity: important > > > > Dear Maintainer, > > > > After updating to the 6.6 kernel the password for my encryption does not > > longer > > work > > > > Please unlock disk nvme0n1p3_crypt: ** > > device-mapper: table: 253:0: crypt: Error allocation crypto tfm (_ENOENT) > > device-mapper: ioctl: error adding target to table > > device-mapper: reload ioctl on nvme0n1p3_crypt (253:0) failed: No such file > > or > > directory > > cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or > > options? > > > > Everything works with 6.5. I also downgrade systemd and cryptosetup but no > > changes > > I suspect this is related to changes around > https://git.kernel.org/linus/68cf01760bc0891074e813b9bb06d2696cac1c01 > (but not verified, nor tracked down). Actually after a more closer look on what is in the initrd: Bastian can be this due to switching to compressed modules? If this claim is correct then likely initramfs-tools would not copy them to the initrd. Regards, Salvatore
Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Control: tags -1 + confirmed On Tue, Dec 05, 2023 at 06:23:45AM +0100, Michael Ott wrote: > Package: src:linux > Version: 6.6.4-1~exp1 > Severity: important > > Dear Maintainer, > > After updating to the 6.6 kernel the password for my encryption does not > longer > work > > Please unlock disk nvme0n1p3_crypt: ** > device-mapper: table: 253:0: crypt: Error allocation crypto tfm (_ENOENT) > device-mapper: ioctl: error adding target to table > device-mapper: reload ioctl on nvme0n1p3_crypt (253:0) failed: No such file or > directory > cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or > options? > > Everything works with 6.5. I also downgrade systemd and cryptosetup but no > changes I suspect this is related to changes around https://git.kernel.org/linus/68cf01760bc0891074e813b9bb06d2696cac1c01 (but not verified, nor tracked down). Regards, Salvatore
Processed: Re: Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Processing control commands: > tags -1 + confirmed Bug #1057441 [src:linux] linux-image-6.6-amd64: Crypt does not longer work Added tag(s) confirmed. -- 1057441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053503: closed by Debian FTP Masters (reply to Bastian Blank ) (Bug#1053503: fixed in linux 6.6.3-1~exp1)
Hi John, On 2023-12-04 09:48, John Vincent wrote: > I tested today's daily installer (2023-12-04 10:14) but the changes > are seeming to be not included in this installer. Indeed, 6.6.3-1~exp1 is in experimental. The changes will be included in the daily installer build once the relevant kernel version enters testing. First it will have to be uploaded to unstable though, and there is no fixed date for when that will happen. "Soonish", I think. :-) You can check the kernel versions for unstable/testing and more on: https://tracker.debian.org/pkg/linux For details on when exactly packages are allowed to migrate into testing after entering unstable, please see: https://www.debian.org/devel/testing Emanuele
Processed: severity of 1057441 is serious
Processing commands for cont...@bugs.debian.org: > # as to be considered a considereable regression > severity 1057441 serious Bug #1057441 [src:linux] linux-image-6.6-amd64: Crypt does not longer work Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1057441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
