Bug#1063422: [regression 6.1.y] f2fs: invalid zstd compress level: 6

2024-02-08 Thread Jaegeuk Kim
Hi,

Let me check this soon.

Thanks,

On 02/08, Salvatore Bonaccorso wrote:
> Hi Jaegeuk Kim, Chao Yu,
> 
> In Debian the following regression was reported after a Dhya updated
> to 6.1.76:
> 
> On Wed, Feb 07, 2024 at 10:43:47PM -0500, Dhya wrote:
> > Package: src:linux
> > Version: 6.1.76-1
> > Severity: critical
> > Justification: breaks the whole system
> > 
> > Dear Maintainer,
> > 
> > After upgrade to linux-image-6.1.0-18-amd64 6.1.76-1 F2FS filesystem
> > fails to mount rw.  Message in the boot journal:
> > 
> >   kernel: F2FS-fs (nvme0n1p6): invalid zstd compress level: 6
> > 
> > There was recently an f2fs patch to the 6.1 kernel tree which might be
> > related: https://www.spinics.net/lists/stable-commits/msg329957.html
> > 
> > Was able to recover the system by doing:
> > 
> > sudo mount -o 
> > remount,rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,compress_algorithm=lz4,compress_log_size=2,compress_mode=fs,atgc,discard_unit=block,memory=normal
> >  /dev/nvme0n1p6 /
> > 
> > under the running bad 6.1.0-18-amd64 kernel, then editing
> > /etc/default/grub:
> > 
> >   GRUB_DEFAULT="Advanced options for Debian GNU/Linux>Debian GNU/Linux, 
> > with Linux 6.1.0-17-amd64"
> > 
> > and running 'update-grub' and rebooting to boot the 6.1.0-17-amd64
> > kernel.
> 
> The issue is easily reproducible by:
> 
> # dd if=/dev/zero of=test.img count=100 bs=1M
> # mkfs.f2fs -f -O compression,extra_attr ./test.img
> # mount -t f2fs -o 
> compress_algorithm=zstd:6,compress_chksum,atgc,gc_merge,lazytime ./test.img 
> /mnt
> 
> resulting in
> 
> [   60.789982] F2FS-fs (loop0): invalid zstd compress level: 6
> 
> A bugzilla report has been submitted in
> https://bugzilla.kernel.org/show_bug.cgi?id=218471
> 
> #regzbot introduced: v6.1.69..v6.1.76
> #regzbot link: https://bugs.debian.org/1063422
> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=218471
> 
> Regards,
> Salvatore



Bug#1063338: [regression 6.1.76] dlm: cannot start dlm midcomms -97 after backport of e9cdebbe23f1 ("dlm: use kernel_connect() and kernel_bind()")

2024-02-08 Thread Jordan Rife
Hi Valentin,

Would you be able to confirm that the attached patch fixes your issue as well?

-Jordan

On Thu, Feb 8, 2024 at 9:42 AM Jordan Rife  wrote:
>
> On Thu, Feb 8, 2024 at 3:37 AM Valentin Kleibel  wrote:
> >
> > Hi Jordan, hi all
> >
> > > Just a quick look comparing dlm_tcp_listen_bind between the latest 6.1
> > > and 6.6 stable branches,
> > > it looks like there is a mismatch here with the dlm_local_addr[0] 
> > > parameter.
> > >
> > > 6.1
> > > 
> > >
> > > static int dlm_tcp_listen_bind(struct socket *sock)
> > > {
> > > int addr_len;
> > >
> > > /* Bind to our port */
> > > make_sockaddr(dlm_local_addr[0], dlm_config.ci_tcp_port, _len);
> > > return kernel_bind(sock, (struct sockaddr *)_local_addr[0],
> > > addr_len);
> > > }
> > >
> > > 6.6
> > > 
> > > static int dlm_tcp_listen_bind(struct socket *sock)
> > > {
> > > int addr_len;
> > >
> > > /* Bind to our port */
> > > make_sockaddr(_local_addr[0], dlm_config.ci_tcp_port, _len);
> > > return kernel_bind(sock, (struct sockaddr *)_local_addr[0],
> > > addr_len);
> > > }
> > >
> > > 6.6 contains commit c51c9cd8 (fs: dlm: don't put dlm_local_addrs on heap) 
> > > which
> > > changed
> > >
> > > static struct sockaddr_storage *dlm_local_addr[DLM_MAX_ADDR_COUNT];
> > >
> > > to
> > >
> > > static struct sockaddr_storage dlm_local_addr[DLM_MAX_ADDR_COUNT];
> > >
> > > It looks like kernel_bind() in 6.1 needs to be modified to match.
> >
> > We tried to apply commit c51c9cd8 (fs: dlm: don't put dlm_local_addrs on
> > heap) to the debian kernel 6.1.76 and came up with the attached patch.
> > Besides the different offsets there is a slight change dlm_tcp_bind()
> > where in 6.1.76 kernel_bind() is used instead of sock->ops->bind() in
> > the original commit.
> >
> > This patch solves the issue we experienced.
> >
> > Thanks for your help,
> > Valentin
>
> Good to hear that works for you! We should fix this in the 6.1 stable
> kernel as well.
>
> IMO it may be less risky and simpler to fix the backport of my patch
> e9cdebbe23f1 ("dlm: use kernel_connect() and
> kernel_bind()") and just switch (struct sockaddr *)_local_addr[0]
> to (struct sockaddr *)dlm_local_addr[0]
> in the call to kernel_bind() rather than backporting c51c9cd8 (fs:
> dlm: don't put dlm_local_addrs on
> heap) to 6.1.
>
> I will have some time soon to fix the 6.1 backport, but it may make
> sense just to revert in the meantime.
>
> -Jordan
From dec5ffd309967e429b616a9d498037a5eb437c54 Mon Sep 17 00:00:00 2001
From: Jordan Rife 
Date: Thu, 8 Feb 2024 12:09:55 -0600
Subject: [PATCH] dlm: Treat dlm_local_addr[0] as sockaddr_storage *

Backport e11dea8 ("dlm: use kernel_connect() and kernel_bind()") to
Linux stable 6.1 caused a regression. The original patch expected
dlm_local_addrs[0] to be of type sockaddr_storage, because c51c9cd ("fs:
dlm: don't put dlm_local_addrs on heap") changed its type from
sockaddr_storage* to sockaddr_storage in Linux 6.5+ while in older Linux
versions this is still the original sockaddr_storage*.

Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063338
Fixes: e11dea8 ("dlm: use kernel_connect() and kernel_bind()")
Signed-off-by: Jordan Rife 
---
 fs/dlm/lowcomms.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
index 72f34f96d0155..8426073e73cf2 100644
--- a/fs/dlm/lowcomms.c
+++ b/fs/dlm/lowcomms.c
@@ -1900,7 +1900,7 @@ static int dlm_tcp_listen_bind(struct socket *sock)
 
 	/* Bind to our port */
 	make_sockaddr(dlm_local_addr[0], dlm_config.ci_tcp_port, _len);
-	return kernel_bind(sock, (struct sockaddr *)_local_addr[0],
+	return kernel_bind(sock, (struct sockaddr *)dlm_local_addr[0],
 			   addr_len);
 }
 
-- 
2.43.0.687.g38aa6559b0-goog



Processed: tagging 1063161

2024-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # moreinfo provided by Mario Limonciello
> tags 1063161 - moreinfo
Bug #1063161 [src:linux] Add amd_pmf module
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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



Processed: bug 1063422 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=218471 https://lore.kernel.org/regressions/zcu3vcrt9vopu...@eldamar.lan/T/#u

2024-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1063422 https://bugzilla.kernel.org/show_bug.cgi?id=218471 
> https://lore.kernel.org/regressions/zcu3vcrt9vopu...@eldamar.lan/T/#u
Bug #1063422 [src:linux] linux-image-6.1.0-18-amd64: F2FS rw mount at boot 
fails with "invalid zstd compress level: 6"
Changed Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=218471 
https://lore.kernel.org/regressions/zcu3vcrt9vopu...@eldamar.lan/T/#u' from 
'https://bugzilla.kernel.org/show_bug.cgi?id=218471'.
> thanks
Stopping processing here.

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



Bug#1063422: [regression 6.1.y] f2fs: invalid zstd compress level: 6

2024-02-08 Thread Salvatore Bonaccorso
Hi Jaegeuk Kim, Chao Yu,

In Debian the following regression was reported after a Dhya updated
to 6.1.76:

On Wed, Feb 07, 2024 at 10:43:47PM -0500, Dhya wrote:
> Package: src:linux
> Version: 6.1.76-1
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> After upgrade to linux-image-6.1.0-18-amd64 6.1.76-1 F2FS filesystem
> fails to mount rw.  Message in the boot journal:
> 
>   kernel: F2FS-fs (nvme0n1p6): invalid zstd compress level: 6
> 
> There was recently an f2fs patch to the 6.1 kernel tree which might be
> related: https://www.spinics.net/lists/stable-commits/msg329957.html
> 
> Was able to recover the system by doing:
> 
> sudo mount -o 
> remount,rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,checkpoint_merge,fsync_mode=posix,compress_algorithm=lz4,compress_log_size=2,compress_mode=fs,atgc,discard_unit=block,memory=normal
>  /dev/nvme0n1p6 /
> 
> under the running bad 6.1.0-18-amd64 kernel, then editing
> /etc/default/grub:
> 
>   GRUB_DEFAULT="Advanced options for Debian GNU/Linux>Debian GNU/Linux, with 
> Linux 6.1.0-17-amd64"
> 
> and running 'update-grub' and rebooting to boot the 6.1.0-17-amd64
> kernel.

The issue is easily reproducible by:

# dd if=/dev/zero of=test.img count=100 bs=1M
# mkfs.f2fs -f -O compression,extra_attr ./test.img
# mount -t f2fs -o 
compress_algorithm=zstd:6,compress_chksum,atgc,gc_merge,lazytime ./test.img /mnt

resulting in

[   60.789982] F2FS-fs (loop0): invalid zstd compress level: 6

A bugzilla report has been submitted in
https://bugzilla.kernel.org/show_bug.cgi?id=218471

#regzbot introduced: v6.1.69..v6.1.76
#regzbot link: https://bugs.debian.org/1063422
#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=218471

Regards,
Salvatore



Bug#1063483: linux-headers-amd64:amd64: Can't install on 32bit system

2024-02-08 Thread Stefan Monnier
Package: linux-headers-amd64
Severity: normal

Dear Maintainer,

I've been using a i386 install running on an amd64 kernel for many
years, and recently a new problem showed up: to build kernel modules
`dkms` needs `linux-headers-amd64(:amd64)` and this package conflicts
with the 32bit GCC toolchain forcing me to install gcc-13:amd64 instead,
which in turns forces me to move to the amd64 version of many other
packages (such as `ocaml`, `ghc`, `emacs`, ...).

I suspect this is linked to bug#1042993


Stefan


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-security'), (100, 'stable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 6.4.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-headers-amd64:amd64 depends on:
ii  linux-headers-6.5.0-5-amd64  6.5.13-1

linux-headers-amd64:amd64 recommends no packages.

linux-headers-amd64:amd64 suggests no packages.

-- no debconf information
--



Bug#1060706: linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable)

2024-02-08 Thread Arno Lehmann

Hi all,

so, latest news.

System lost access to the NVMe again and could recover from that only 
after powercycling. Pings, until that powercycle, worked so I assume the 
NIC and software above it were still functional.


Rebooted into the 6.5 backported kernel, downloaded the newest BIOS, 
noticed the NIC getting lost, wrote the BIOS image to USB key, rebooted 
into the UEFI / BIOS control tool, flashed the newest firmware, set all 
defaults and conservative power saving settings and booted into Debian 
again.


Kernel is
# uname -a
Linux Zwerg 6.5.0-0.deb12.4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.5.10-1~bpo12+1 (2023-11-23) x86_64 GNU/Linux


These are the latest such events:
Jan 27 09:44:53 Zwerg kernel: igc :0a:00.0 eno1: PCIe link lost, 
device now detached
Jan 27 09:48:05 Zwerg kernel: igc :0a:00.0 (unnamed net_device) 
(uninitialized): PCIe link lost, device now detached
Jan 27 09:52:16 Zwerg kernel: igc :0a:00.0 (unnamed net_device) 
(uninitialized): PCIe link lost, device now detached
Feb 01 04:19:17 Zwerg kernel: igc :0a:00.0 eno1: PCIe link lost, 
device now detached
Feb 01 14:43:03 Zwerg kernel: igc :0a:00.0 (unnamed net_device) 
(uninitialized): PCIe link lost, device now detached
Feb 08 18:33:38 Zwerg kernel: igc :0a:00.0 eno1: PCIe link lost, 
device now detached
Feb 08 19:00:32 Zwerg kernel: igc :0b:00.0 eno1: PCIe link lost, 
device now detached
Feb 08 19:02:38 Zwerg kernel: igc :0b:00.0 (unnamed net_device) 
(uninitialized): PCIe link lost, device now detached


I think it's safe to say that the actual kernel version does not have an 
effect on those events.


Naturally, the NVMe connectivity losses are not logged but I believe it 
might be an interesting thing to see if I can capture that. Perhaps 
sending system logs to USB storage might work. However, I think it would 
be important to understand if this ticket's topic is a matter of the igc 
module, or perhaps about the power or PCIe management functionality (of 
which I know even less).


The big question: What can I do to help further pinpointing this problem?

Thanks,

Arno

--
Arno Lehmann

IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück



Bug#1063338: [regression 6.1.76] dlm: cannot start dlm midcomms -97 after backport of e9cdebbe23f1 ("dlm: use kernel_connect() and kernel_bind()")

2024-02-08 Thread Jordan Rife
On Thu, Feb 8, 2024 at 3:37 AM Valentin Kleibel  wrote:
>
> Hi Jordan, hi all
>
> > Just a quick look comparing dlm_tcp_listen_bind between the latest 6.1
> > and 6.6 stable branches,
> > it looks like there is a mismatch here with the dlm_local_addr[0] parameter.
> >
> > 6.1
> > 
> >
> > static int dlm_tcp_listen_bind(struct socket *sock)
> > {
> > int addr_len;
> >
> > /* Bind to our port */
> > make_sockaddr(dlm_local_addr[0], dlm_config.ci_tcp_port, _len);
> > return kernel_bind(sock, (struct sockaddr *)_local_addr[0],
> > addr_len);
> > }
> >
> > 6.6
> > 
> > static int dlm_tcp_listen_bind(struct socket *sock)
> > {
> > int addr_len;
> >
> > /* Bind to our port */
> > make_sockaddr(_local_addr[0], dlm_config.ci_tcp_port, _len);
> > return kernel_bind(sock, (struct sockaddr *)_local_addr[0],
> > addr_len);
> > }
> >
> > 6.6 contains commit c51c9cd8 (fs: dlm: don't put dlm_local_addrs on heap) 
> > which
> > changed
> >
> > static struct sockaddr_storage *dlm_local_addr[DLM_MAX_ADDR_COUNT];
> >
> > to
> >
> > static struct sockaddr_storage dlm_local_addr[DLM_MAX_ADDR_COUNT];
> >
> > It looks like kernel_bind() in 6.1 needs to be modified to match.
>
> We tried to apply commit c51c9cd8 (fs: dlm: don't put dlm_local_addrs on
> heap) to the debian kernel 6.1.76 and came up with the attached patch.
> Besides the different offsets there is a slight change dlm_tcp_bind()
> where in 6.1.76 kernel_bind() is used instead of sock->ops->bind() in
> the original commit.
>
> This patch solves the issue we experienced.
>
> Thanks for your help,
> Valentin

Good to hear that works for you! We should fix this in the 6.1 stable
kernel as well.

IMO it may be less risky and simpler to fix the backport of my patch
e9cdebbe23f1 ("dlm: use kernel_connect() and
kernel_bind()") and just switch (struct sockaddr *)_local_addr[0]
to (struct sockaddr *)dlm_local_addr[0]
in the call to kernel_bind() rather than backporting c51c9cd8 (fs:
dlm: don't put dlm_local_addrs on
heap) to 6.1.

I will have some time soon to fix the 6.1 backport, but it may make
sense just to revert in the meantime.

-Jordan



linux_6.7.4-1~exp1_source.changes ACCEPTED into experimental

2024-02-08 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Feb 2024 16:01:07 +0100
Source: linux
Architecture: source
Version: 6.7.4-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1057272 1061521
Changes:
 linux (6.7.4-1~exp1) experimental; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.2
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.3
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.4
 .
   [ Aurelien Jarno ]
   * [riscv64] Add clock, MFD, PCIe PHYs, regulator and RTC drivers to
 kernel-image udeb.
   * [riscv64] Disable CRYPTO_DEV_JH7110, it is broken.
 .
   [ Bastian Blank ]
   * Make linux-libc-dev provide all cross packages.
 .
   [ Salvatore Bonaccorso ]
   * Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID
 (Closes: #1061521)
 .
   [ Emanuele Rocca ]
   * [arm64] drivers/thermal/qcom: enable QCOM_SPMI_ADC_TM5 as module for
 thermal throttling on the Lenovo ThinkPad X13s.
 .
   [ Vincent Blut ]
   * drivers/hwmon: Enable SENSORS_IIO_HWMON as module (Closes: #1057272)
Checksums-Sha1:
 d1d05bffa666a3227d87b0a3a700cf094e036a72 216329 linux_6.7.4-1~exp1.dsc
 aede57f397934ee11d17930f95a105b79da055ae 144129724 linux_6.7.4.orig.tar.xz
 301f63b0bc48bf7def6fd2439edb3eff44b7857a 1509712 
linux_6.7.4-1~exp1.debian.tar.xz
 63e21c950380eee9f3203198ff63e7b4aafee8fe 7376 
linux_6.7.4-1~exp1_source.buildinfo
Checksums-Sha256:
 929f916924e3ce3736bef2cc4fa45032dff82b8e67d8a39a8394b013661825a3 216329 
linux_6.7.4-1~exp1.dsc
 dd2d3e4b4b87acdf8dc9e01625fc5589de973fda775f4ddc843686cc1a64bf36 144129724 
linux_6.7.4.orig.tar.xz
 9e41523f59ae84e66c04ea5bbf66e57bac9a83d0280ebf6699b67883e55a3736 1509712 
linux_6.7.4-1~exp1.debian.tar.xz
 c6101b209a1c3b3bb69c9e08ea851adf37b7cfa5907f43f7b98e1db7f9abdd3f 7376 
linux_6.7.4-1~exp1_source.buildinfo
Files:
 7a5bbbe94b236d5cd6b120c5b3377239 216329 kernel optional linux_6.7.4-1~exp1.dsc
 76d45e7291e74504d4b20ff42e5b8983 144129724 kernel optional 
linux_6.7.4.orig.tar.xz
 ee2b7df40c75effd0b6097f85e1c4bd7 1509712 kernel optional 
linux_6.7.4-1~exp1.debian.tar.xz
 c7ed48d96826186ce61431724878cfeb 7376 kernel optional 
linux_6.7.4-1~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmXE8WpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EJbwP/3ZwhnyEdbz6eOtFDBFYVPv1ZkKGOxPO
6vppU/KpQXE1c0brdKSx+2jli56dbmRUoJjdBqfMScjWqideDmWOV8v1xoaPm0Q0
KWsL9u6Iq6Zp2H7tg8iShINKNkGz6sTHQ8T2WF1p1SGSQh0tNJqdPGBSrPbImuIq
whi/YPQSZr6ZFKqcpRIotnGVhJzGLKV/3iGPiT2Ahyz+NYoB6fnn3ALbvucuInQt
f/SVHulxr1AsFpYx2/UjcZF8f+HonxJxbSrQqQrLT4ASqLTTWBouux3ds/NBsNwV
ZkqWLojVsIoOQ/X9numwBARW01wwxO/J7+zpgQnQkPZY0K2LKGy3gDxpNPkGFQ53
PSvi1L7ZXN7iDzqJF0d5F64oIo9HD3sVoMcv4ann9wlffuT3y7rt5AbGfmJIBNw9
4jRDaCxk0nNrPNhq2ip1SRH6g8r5j/QS4uUiWe7eKYQavGg/9WI3WAhhVc4mgdyN
OLxgtEKQ5VtFRfPdplWxYI8xZIjXE1tNlKdJAGNSn/N2eLmO760vkN1NZzt4Rb9n
9v5ToqhSQM/tndc6HquYZvPIdrR1p6mzOJyRmRuuVfTQqBv8yzY3LsSnk62yvY9Q
BOZuibVOQy2NvW0daHKH5xRq6Mjp7ho/mTW1hWQkmylcQEIxtf8soVWLYUpZxKJ6
Yp2o2kaHbUuN
=H16c
-END PGP SIGNATURE-



Bug#1063468: linux-image-6.1.0-17-amd64: Loud squeals/crackles from Steelseries 2 Channel HD Audio chipset after restarting from Windows 11

2024-02-08 Thread Luke Feetham
Package: src:linux
Version: 6.1.69-1
Severity: important
X-Debbugs-Cc: l.feet...@live.co.uk

Dear Maintainer,


I have a Recoil 16 Laptop (less than 6 months old) from PC Specialist 
(https://www.pcspecialist.co.uk/notebooks/recoil-16) that has a
Nahimic Steelseries 2 Channel HD Audio chipset (full laptop specs provided 
below). I have installed Debian 12 Bookworm with KDE Plasma
under a dual-boot setup with Windows 11. When thelaptop is off and I power it 
up and boot straight into Deebian, everything seems to
be fine, but when the laptop is powered-up and running Windows, if I then click 
restart and then boot into Debian (without powering 
down) I experience some significant audio issues, consisting of loud 
high-pitched squeals, crackling and pops that cannot be stopped
(volume controls and muting does nothing). An example of this behaviour can be 
seen here:

https://youtu.be/6w9foiCE6ek

This problem has been discussed on the Debian User Forum 
(https://forums.debian.net/viewtopic.php?t=158192), where it was suggested
that it may be that Windows' settings might be persisting within the sound card 
after the restart and causing issues within Debian.
It seems like this could be a plausible explanation since the problem only 
seems to happen when switching from Windows to Debian, 
and the only way to avoid the problem is to do a full shutdown, wait for some 
amount of time, and then power back up and boot into
Debian. While this approach works, and I can kind-of live with it for now, it 
is far from convenient (especially when I keep 
forgetting to clilck shut down instad of restart) and so is not really an 
acceptable solution in the long term.

While I have not been able to exhaustively test it, I can confirm that this 
problem is present on newer version of the linux kernel.
I have tested this problem within live environments of both Kubuntu 23.10 
(kernel 6.5.0-9-generic) and Fedora 39 (kernel 
6.5.6-300.fc39.x86_64). Again, this is whenever I restart from Windows 11.

Please let me know if you need further information.
 
Best regards

Luke


Laptop Specs:

Chassis & Display   Recoil Series: 16" Matte QHD 240Hz sRGB 100% LED 
Widescreen (2560x1600)
Processor (CPU) Intel® Core™ i9 24 Core Processor 13900HX (5.4GHz Turbo)
Memory (RAM)64GB Corsair 4800MHz SODIMM DDR5 (2 x 32GB)
Graphics Card   NVIDIA® GeForce® RTX 4090 - 16.0GB GDDR6 Video RAM - 
DirectX® 12.1
Laptop Cooling  PCS Liquid Series® Laptop Cooler
1st M.2 SSD Drive   4TB CORSAIR MP600 PRO NVMe PCIe M.2 SSD (up to 7000 
MB/R, 6850 MB/W)
2nd M.2 SSD Drive   4TB CORSAIR MP600 PRO NVMe PCIe M.2 SSD (up to 7000 
MB/R, 6850 MB/W)
Memory Card Reader  Integrated SD Memory Card Reader
Sound Card  Nahimic by SteelSeries 2 Channel HD Audio
Bluetooth & WirelessGIGABIT LAN & WIRELESS INTEL® Wi-Fi 6E AX211 (2.4 Gbps) 
+ BT 5.3
USB/Thunderbolt 1 x THUNDERBOLT 4 PORT + 3 x USB 3.2 PORTS
Keyboard Language   RECOIL 16 SERIES RGB BACKLIT UK KEYBOARD
Operating SystemWindows 11 Professional 64 Bit - inc. Single Licence
Notebook Mouse  LOGITECH WIRELESS MOUSE M510
Webcam  INTEGRATED 1MP HD WEBCAM




-- Package-specific info:
** Version:
Linux version 6.1.0-17-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-17-amd64 
root=UUID=b2a6dfe8-a825-4f45-bc0f-d6768d6f5db2 ro quiet

** Not tainted

** Kernel log:
[6.218497] iwlwifi :00:14.3 wlo1: renamed from wlan0
[6.414427] usb 1-14: new full-speed USB device number 9 using xhci_hcd
[6.427507] EXT4-fs (nvme1n1p1): mounted filesystem with ordered data mode. 
Quota mode: none.
[6.443558] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input31
[6.443615] input: HDA Intel PCH Front Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input32
[6.443792] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input33
[6.443938] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input34
[6.445172] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input35
[6.445564] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input36
[6.451101] EXT4-fs (nvme1n1p4): mounted filesystem with ordered data mode. 
Quota mode: none.
[6.506822] audit: type=1400 audit(1707398432.452:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=975 comm="apparmor_parser"
[6.506901] audit: type=1400 audit(1707398432.452:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=973 comm="apparmor_parser"
[6.507683] audit: type=1400 audit(1707398432.452:6): apparmor="STATUS" 

Bug#1061521: marked as done (linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from suspend)

2024-02-08 Thread Debian Bug Tracking System
Your message dated Thu, 08 Feb 2024 15:40:42 +
with message-id 
and subject line Bug#1061521: fixed in linux 6.7.4-1~exp1
has caused the Debian Bug report #1061521,
regarding linux-image-6.6.13-amd64: 6.6.13-1 no more keyboard resuming from 
suspend
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.)


-- 
1061521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-6.6.13-amd64
Version: 6.6.13-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: deb...@r2rien.net

Resuming from suspend keyboard totally unresponsive, thus no sysrq, no tty to
the rescue, only power button.
Stuck in gdm3 login screen,
thus impossible to type password to unlock gnome-session
I tagged it as grave so people with apt-listbugs could be informed


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (991, 'testing'), (990, 'unstable'), (600, 'stable'), (90, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.11-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-6.6.13-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod31-1
ii  linux-base  4.9

Versions of packages linux-image-6.6.13-amd64 recommends:
pn  apparmor 
ii  firmware-linux-free  20200122-2

Versions of packages linux-image-6.6.13-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.12-1
pn  linux-doc-6.6   
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.7.4-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 1061...@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: Thu, 08 Feb 2024 16:01:07 +0100
Source: linux
Architecture: source
Version: 6.7.4-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1057272 1061521
Changes:
 linux (6.7.4-1~exp1) experimental; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.2
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.3
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.4
 .
   [ Aurelien Jarno ]
   * [riscv64] Add clock, MFD, PCIe PHYs, regulator and RTC drivers to
 kernel-image udeb.
   * [riscv64] Disable CRYPTO_DEV_JH7110, it is broken.
 .
   [ Bastian Blank ]
   * Make linux-libc-dev provide all cross packages.
 .
   [ Salvatore Bonaccorso ]
   * Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID
 (Closes: #1061521)
 .
   [ Emanuele Rocca ]
   * [arm64] drivers/thermal/qcom: enable QCOM_SPMI_ADC_TM5 as module for
 thermal throttling on the Lenovo ThinkPad X13s.
 .
   [ Vincent Blut ]
   * drivers/hwmon: Enable SENSORS_IIO_HWMON as module (Closes: #1057272)
Checksums-Sha1:
 d1d05bffa666a3227d87b0a3a700cf094e036a72 216329 linux_6.7.4-1~exp1.dsc
 aede57f397934ee11d17930f95a105b79da055ae 144129724 linux_6.7.4.orig.tar.xz
 301f63b0bc48bf7def6fd2439edb3eff44b7857a 1509712 
linux_6.7.4-1~exp1.debian.tar.xz
 63e21c950380eee9f3203198ff63e7b4aafee8fe 7376 
linux_6.7.4-1~exp1_source.buildinfo
Checksums-Sha256:
 929f916924e3ce3736bef2cc4fa45032dff82b8e67d8a39a8394b013661825a3 216329 
linux_6.7.4-1~exp1.dsc
 dd2d3e4b4b87acdf8dc9e01625fc5589de973fda775f4ddc843686cc1a64bf36 144129724 
linux_6.7.4.orig.tar.xz
 9e41523f59ae84e66c04ea5bbf66e57bac9a83d0280ebf6699b67883e55a3736 1509712 
linux_6.7.4-1~exp1.debian.tar.xz
 

Bug#1057272: marked as done (Enable SENSORS_IIO_HWMON support)

2024-02-08 Thread Debian Bug Tracking System
Your message dated Thu, 08 Feb 2024 15:40:42 +
with message-id 
and subject line Bug#1057272: fixed in linux 6.7.4-1~exp1
has caused the Debian Bug report #1057272,
regarding Enable SENSORS_IIO_HWMON support
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.)


-- 
1057272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.5.13-1
Severity: wishlist

Please, enable SENSORS_IIO_HWMON support. Without it I'm unable to
fetch the AXP209 internal temperature sensor.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.7.4-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 1057...@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: Thu, 08 Feb 2024 16:01:07 +0100
Source: linux
Architecture: source
Version: 6.7.4-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1057272 1061521
Changes:
 linux (6.7.4-1~exp1) experimental; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.2
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.3
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.4
 .
   [ Aurelien Jarno ]
   * [riscv64] Add clock, MFD, PCIe PHYs, regulator and RTC drivers to
 kernel-image udeb.
   * [riscv64] Disable CRYPTO_DEV_JH7110, it is broken.
 .
   [ Bastian Blank ]
   * Make linux-libc-dev provide all cross packages.
 .
   [ Salvatore Bonaccorso ]
   * Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID
 (Closes: #1061521)
 .
   [ Emanuele Rocca ]
   * [arm64] drivers/thermal/qcom: enable QCOM_SPMI_ADC_TM5 as module for
 thermal throttling on the Lenovo ThinkPad X13s.
 .
   [ Vincent Blut ]
   * drivers/hwmon: Enable SENSORS_IIO_HWMON as module (Closes: #1057272)
Checksums-Sha1:
 d1d05bffa666a3227d87b0a3a700cf094e036a72 216329 linux_6.7.4-1~exp1.dsc
 aede57f397934ee11d17930f95a105b79da055ae 144129724 linux_6.7.4.orig.tar.xz
 301f63b0bc48bf7def6fd2439edb3eff44b7857a 1509712 
linux_6.7.4-1~exp1.debian.tar.xz
 63e21c950380eee9f3203198ff63e7b4aafee8fe 7376 
linux_6.7.4-1~exp1_source.buildinfo
Checksums-Sha256:
 929f916924e3ce3736bef2cc4fa45032dff82b8e67d8a39a8394b013661825a3 216329 
linux_6.7.4-1~exp1.dsc
 dd2d3e4b4b87acdf8dc9e01625fc5589de973fda775f4ddc843686cc1a64bf36 144129724 
linux_6.7.4.orig.tar.xz
 9e41523f59ae84e66c04ea5bbf66e57bac9a83d0280ebf6699b67883e55a3736 1509712 
linux_6.7.4-1~exp1.debian.tar.xz
 c6101b209a1c3b3bb69c9e08ea851adf37b7cfa5907f43f7b98e1db7f9abdd3f 7376 
linux_6.7.4-1~exp1_source.buildinfo
Files:
 7a5bbbe94b236d5cd6b120c5b3377239 216329 kernel optional linux_6.7.4-1~exp1.dsc
 76d45e7291e74504d4b20ff42e5b8983 144129724 kernel optional 
linux_6.7.4.orig.tar.xz
 ee2b7df40c75effd0b6097f85e1c4bd7 1509712 kernel optional 
linux_6.7.4-1~exp1.debian.tar.xz
 c7ed48d96826186ce61431724878cfeb 7376 kernel optional 
linux_6.7.4-1~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmXE8WpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EJbwP/3ZwhnyEdbz6eOtFDBFYVPv1ZkKGOxPO
6vppU/KpQXE1c0brdKSx+2jli56dbmRUoJjdBqfMScjWqideDmWOV8v1xoaPm0Q0
KWsL9u6Iq6Zp2H7tg8iShINKNkGz6sTHQ8T2WF1p1SGSQh0tNJqdPGBSrPbImuIq
whi/YPQSZr6ZFKqcpRIotnGVhJzGLKV/3iGPiT2Ahyz+NYoB6fnn3ALbvucuInQt
f/SVHulxr1AsFpYx2/UjcZF8f+HonxJxbSrQqQrLT4ASqLTTWBouux3ds/NBsNwV
ZkqWLojVsIoOQ/X9numwBARW01wwxO/J7+zpgQnQkPZY0K2LKGy3gDxpNPkGFQ53
PSvi1L7ZXN7iDzqJF0d5F64oIo9HD3sVoMcv4ann9wlffuT3y7rt5AbGfmJIBNw9
4jRDaCxk0nNrPNhq2ip1SRH6g8r5j/QS4uUiWe7eKYQavGg/9WI3WAhhVc4mgdyN
OLxgtEKQ5VtFRfPdplWxYI8xZIjXE1tNlKdJAGNSn/N2eLmO760vkN1NZzt4Rb9n

Processing of linux_6.7.4-1~exp1_source.changes

2024-02-08 Thread Debian FTP Masters
linux_6.7.4-1~exp1_source.changes uploaded successfully to localhost
along with the files:
  linux_6.7.4-1~exp1.dsc
  linux_6.7.4.orig.tar.xz
  linux_6.7.4-1~exp1.debian.tar.xz
  linux_6.7.4-1~exp1_source.buildinfo

Greetings,

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



Processed: bug 1063338 has a patch available

2024-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1063338 + patch
Bug #1063338 [src:linux] dlm: cannot start dlm midcomms -97
Added tag(s) patch.
>
End of message, stopping processing here.

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



Bug#1063338: [regression 6.1.76] dlm: cannot start dlm midcomms -97 after backport of e9cdebbe23f1 ("dlm: use kernel_connect() and kernel_bind()")

2024-02-08 Thread Valentin Kleibel

Hi Jordan, hi all


Just a quick look comparing dlm_tcp_listen_bind between the latest 6.1
and 6.6 stable branches,
it looks like there is a mismatch here with the dlm_local_addr[0] parameter.

6.1


static int dlm_tcp_listen_bind(struct socket *sock)
{
int addr_len;

/* Bind to our port */
make_sockaddr(dlm_local_addr[0], dlm_config.ci_tcp_port, _len);
return kernel_bind(sock, (struct sockaddr *)_local_addr[0],
addr_len);
}

6.6

static int dlm_tcp_listen_bind(struct socket *sock)
{
int addr_len;

/* Bind to our port */
make_sockaddr(_local_addr[0], dlm_config.ci_tcp_port, _len);
return kernel_bind(sock, (struct sockaddr *)_local_addr[0],
addr_len);
}

6.6 contains commit c51c9cd8 (fs: dlm: don't put dlm_local_addrs on heap) which
changed

static struct sockaddr_storage *dlm_local_addr[DLM_MAX_ADDR_COUNT];

to

static struct sockaddr_storage dlm_local_addr[DLM_MAX_ADDR_COUNT];

It looks like kernel_bind() in 6.1 needs to be modified to match.


We tried to apply commit c51c9cd8 (fs: dlm: don't put dlm_local_addrs on 
heap) to the debian kernel 6.1.76 and came up with the attached patch. 
Besides the different offsets there is a slight change dlm_tcp_bind() 
where in 6.1.76 kernel_bind() is used instead of sock->ops->bind() in 
the original commit.


This patch solves the issue we experienced.

Thanks for your help,
Valentin--- a/fs/dlm/lowcomms.c	2024-02-08 10:42:19.328861479 +0100
+++ b/fs/dlm/lowcomms.c	2024-02-08 10:57:22.900463149 +0100
@@ -174,7 +174,7 @@
 static DEFINE_SPINLOCK(dlm_node_addrs_spin);
 
 static struct listen_connection listen_con;
-static struct sockaddr_storage *dlm_local_addr[DLM_MAX_ADDR_COUNT];
+static struct sockaddr_storage dlm_local_addr[DLM_MAX_ADDR_COUNT];
 static int dlm_local_count;
 int dlm_allow_conn;
 
@@ -398,7 +398,7 @@
 	if (!sa_out)
 		return 0;
 
-	if (dlm_local_addr[0]->ss_family == AF_INET) {
+	if (dlm_local_addr[0].ss_family == AF_INET) {
 		struct sockaddr_in *in4  = (struct sockaddr_in *) 
 		struct sockaddr_in *ret4 = (struct sockaddr_in *) sa_out;
 		ret4->sin_addr.s_addr = in4->sin_addr.s_addr;
@@ -727,7 +727,7 @@
 static void make_sockaddr(struct sockaddr_storage *saddr, uint16_t port,
 			  int *addr_len)
 {
-	saddr->ss_family =  dlm_local_addr[0]->ss_family;
+	saddr->ss_family =  dlm_local_addr[0].ss_family;
 	if (saddr->ss_family == AF_INET) {
 		struct sockaddr_in *in4_addr = (struct sockaddr_in *)saddr;
 		in4_addr->sin_port = cpu_to_be16(port);
@@ -1167,7 +1167,7 @@
 	int i, addr_len, result = 0;
 
 	for (i = 0; i < dlm_local_count; i++) {
-		memcpy(, dlm_local_addr[i], sizeof(localaddr));
+		memcpy(, _local_addr[i], sizeof(localaddr));
 		make_sockaddr(, port, _len);
 
 		if (!i)
@@ -1187,7 +1187,7 @@
 /* Get local addresses */
 static void init_local(void)
 {
-	struct sockaddr_storage sas, *addr;
+	struct sockaddr_storage sas;
 	int i;
 
 	dlm_local_count = 0;
@@ -1195,21 +1195,10 @@
 		if (dlm_our_addr(, i))
 			break;
 
-		addr = kmemdup(, sizeof(*addr), GFP_NOFS);
-		if (!addr)
-			break;
-		dlm_local_addr[dlm_local_count++] = addr;
+		memcpy(_local_addr[dlm_local_count++], , sizeof(sas));
 	}
 }
 
-static void deinit_local(void)
-{
-	int i;
-
-	for (i = 0; i < dlm_local_count; i++)
-		kfree(dlm_local_addr[i]);
-}
-
 static struct writequeue_entry *new_writequeue_entry(struct connection *con)
 {
 	struct writequeue_entry *entry;
@@ -1575,7 +1564,7 @@
 	}
 
 	/* Create a socket to communicate with */
-	result = sock_create_kern(_net, dlm_local_addr[0]->ss_family,
+	result = sock_create_kern(_net, dlm_local_addr[0].ss_family,
   SOCK_STREAM, dlm_proto_ops->proto, );
 	if (result < 0)
 		goto socket_err;
@@ -1786,7 +1775,6 @@
 	foreach_conn(free_conn);
 	srcu_read_unlock(_srcu, idx);
 	work_stop();
-	deinit_local();
 
 	dlm_proto_ops = NULL;
 }
@@ -1803,7 +1791,7 @@
 	if (result < 0)
 		return result;
 
-	result = sock_create_kern(_net, dlm_local_addr[0]->ss_family,
+	result = sock_create_kern(_net, dlm_local_addr[0].ss_family,
   SOCK_STREAM, dlm_proto_ops->proto, );
 	if (result < 0) {
 		log_print("Can't create comms socket: %d", result);
@@ -1842,7 +1830,7 @@
 	/* Bind to our cluster-known address connecting to avoid
 	 * routing problems.
 	 */
-	memcpy(_addr, dlm_local_addr[0], sizeof(src_addr));
+	memcpy(_addr, _local_addr[0], sizeof(src_addr));
 	make_sockaddr(_addr, 0, _len);
 
 	result = kernel_bind(sock, (struct sockaddr *)_addr,
@@ -1899,7 +1887,7 @@
 	int addr_len;
 
 	/* Bind to our port */
-	make_sockaddr(dlm_local_addr[0], dlm_config.ci_tcp_port, _len);
+	make_sockaddr(_local_addr[0], dlm_config.ci_tcp_port, _len);
 	return kernel_bind(sock, (struct sockaddr *)_local_addr[0],
 			   addr_len);
 }
@@ -1992,7 +1980,7 @@
 
 	error = work_start();
 	if (error)
-		goto fail_local;
+		goto fail;
 
 	dlm_allow_conn = 1;
 
@@ -2022,8 +2010,6 @@
 fail_proto_ops:
 	dlm_allow_conn = 0;
 	work_stop();
-fail_local:
-	deinit_local();
 fail:
 	return error;
 }


Processed: bug 1063422 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=218471

2024-02-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1063422 https://bugzilla.kernel.org/show_bug.cgi?id=218471
Bug #1063422 [src:linux] linux-image-6.1.0-18-amd64: F2FS rw mount at boot 
fails with "invalid zstd compress level: 6"
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=218471'.
> thanks
Stopping processing here.

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