Processed: Re: Bug#1054345: linux-image-6.5.0-2-amd64: Segfault with USB Mass storage

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 procps
Bug #1054345 [src:linux] linux-image-6.5.0-2-amd64: Segfault with USB Mass 
storage
Bug #1054346 [src:linux] linux-image-6.5.0-2-amd64: Segfault with USB Mass 
storage
Bug reassigned from package 'src:linux' to 'procps'.
Bug reassigned from package 'src:linux' to 'procps'.
No longer marked as found in versions linux/6.5.6-1.
No longer marked as found in versions linux/6.5.6-1.
Ignoring request to alter fixed versions of bug #1054345 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1054346 to the same values 
previously set
> retitle -1 w -s segfaults
Bug #1054345 [procps] linux-image-6.5.0-2-amd64: Segfault with USB Mass storage
Bug #1054346 [procps] linux-image-6.5.0-2-amd64: Segfault with USB Mass storage
Changed Bug title to 'w -s segfaults' from 'linux-image-6.5.0-2-amd64: Segfault 
with USB Mass storage'.
Changed Bug title to 'w -s segfaults' from 'linux-image-6.5.0-2-amd64: Segfault 
with USB Mass storage'.

-- 
1054345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054345
1054346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1072573: marked as done (rpc.idmapd runs out of file descriptors)

[Debian Bug Tracking System]

Your message dated Fri, 20 Sep 2024 18:50:31 +
with message-id 
and subject line Bug#1072573: fixed in nfs-utils 1:2.7.1-3
has caused the Debian Bug report #1072573,
regarding rpc.idmapd runs out of file descriptors
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.)


-- 
1072573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 2.6.2-4
Severity: important
Tags: patch upstream

On some of our bookworm systems I've seen what looked like a file descriptor 
leak. Sample lsof output:

[...]
rpc.idmap 675 root  126r  DIR   0,400  10813 
/run/rpc_pipefs/nfs/clnt11e6 (deleted)
rpc.idmap 675 root  127u FIFO   0,40  0t0  10817 
/run/rpc_pipefs/nfs/clnt11e6/idmap (deleted)
rpc.idmap 675 root  128r  DIR   0,400  10834 
/run/rpc_pipefs/nfs/clnt11ef (deleted)
rpc.idmap 675 root  129u FIFO   0,40  0t0  10838 
/run/rpc_pipefs/nfs/clnt11ef/idmap (deleted)
rpc.idmap 675 root  130r  DIR   0,400  10855 
/run/rpc_pipefs/nfs/clnt11f8 (deleted)
rpc.idmap 675 root  131u FIFO   0,40  0t0  10859 
/run/rpc_pipefs/nfs/clnt11f8/idmap (deleted)

Cranking up the verbosity level to 3 showed that dirscancb never reaps stale 
entries in its queue (no "Stale client" lines). The reason turns out to be that 
the scan terminates on the first directory entry that doesn't contain an 
"idmap" file. Applying the attached patch seems to have solved the problem for 
me.

As far as I can tell the bug is still present upstream, and has been for many 
years (that "goto out" is from 2007 and replaced a "return" so the bug is even 
older than that).

Marking "important" since this has actually caused observable problems in our 
environment.From: Sergio Gelato 
Date: Tue, 4 Jun 2024 16:02:59 +0200
Subject: rpc.idmapd: nfsopen() failures should not be fatal

dirscancb() loops over all clnt* subdirectories of /run/rpc_pipefs/nfs/.
Some of these directories contain /idmap files, others don't. nfsopen()
returns -1 for the latter; we then want to skip the directory, not abort
the entire scan.
---
 utils/idmapd/idmapd.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/utils/idmapd/idmapd.c b/utils/idmapd/idmapd.c
index e79c124..f3c540d 100644
--- a/utils/idmapd/idmapd.c
+++ b/utils/idmapd/idmapd.c
@@ -556,7 +556,7 @@ dirscancb(int fd, short UNUSED(which), void *data)
 			if (nfsopen(ic) == -1) {
 close(ic->ic_dirfd);
 free(ic);
-goto out;
+continue;
 			}
 
 			if (verbose > 2)
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:2.7.1-3
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
nfs-utils, 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 1072...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated nfs-utils 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: Fri, 20 Sep 2024 20:36:56 +0200
Source: nfs-utils
Architecture: source
Version: 1:2.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team 
Changed-By: Salvatore Bonaccorso 
Closes: 1072573
Changes:
 nfs-utils (1:2.7.1-3) unstable; urgency=medium
 .
   * rpc.idmapd: nfsopen() failures should not be fatal (Closes: #1072573)
Checksums-Sha1: 
 0a7972bc75b9af9bb7cc041d0ea352740fae03db 2633 nfs-utils_2.7.1-3.dsc
 c6a5bffb2f3f63672615cfbb6a3b31ea29005f63 49756 nfs-utils_2.7.1-3.debian.tar.xz
Checksums-Sha256: 
 71075db32e8f4347356d34a1a28ef2356954be1541687f788b0b387dbeffa349 2633 
nfs-utils_2.7.1-3.dsc
 95c6d028fccab2714efe089d4a6935abd377690209cc4a96e7c5d4ba2d9bbbe3 49756 
nfs-utils_2.7.1-3.debian.tar.xz
Files: 
 fc48f12be58f9dbbac1bb5e3e7de3220 2633 net optional nfs-utils_2.7.1-3.dsc
 2811cb28323a6546ac5cf945334ae93e 49756 net optional 
nfs-utils_2.7.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE

Processed: severity of 857043 is wishlist

[Debian Bug Tracking System]

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

> severity 857043 wishlist
Bug #857043 [nfs-common] nfs-common: Can nfsstat be made to show timeouts per 
mount point or globally for the machine?
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

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

Processed: limit source to nfs-utils, tagging 1072573

[Debian Bug Tracking System]

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

> limit source nfs-utils
Limiting to bugs with field 'source' containing at least one of 'nfs-utils'
Limit currently set to 'source':'nfs-utils'

> tags 1072573 + pending
Bug #1072573 [nfs-common] rpc.idmapd runs out of file descriptors
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#980555: marked as done (Missing ec_sys module)

[Debian Bug Tracking System]

Your message dated Fri, 20 Sep 2024 11:00:10 +
with message-id 
and subject line Bug#980555: fixed in linux 6.11-1~exp1
has caused the Debian Bug report #980555,
regarding Missing ec_sys module
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.)


-- 
980555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 5.9.6-1~bpo10+1
Severity: normal

Dear Maintainer,

The kernel missed ec_sys module, as ec_sys.ko.gz in archlinux here:
https://wiki.archlinux.org/index.php/ACPI_modules
Could you please add this module to the kernel package?

I'll close duplicated bug report here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980553

Thanks,
Rao



-- System Information:
Debian Release: 10.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-0.bpo.2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-amd64 depends on:
ii  linux-image-5.9.0-0.bpo.2-amd64  5.9.6-1~bpo10+1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.11-1~exp1
Done: Ben Hutchings 

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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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, 19 Sep 2024 18:42:39 +0200
Source: linux
Architecture: source
Version: 6.11-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 980555 1036714 1079272 1079501 1079755 1081114
Changes:
 linux (6.11-1~exp1) experimental; urgency=medium
 .
   * New upstream release: https://kernelnewbies.org/Linux_6.11
 .
   [ Marcin Juszkiewicz ]
   * [arm64] udeb: Add kernel modules to get USB/SATA/PCIe working on Rockchip
 RK3588
 .
   [ Alper Nebi Yasak ]
   * [arm64] Enable modules for MT8186 Chromebooks
 - Enable DRM_ITE_IT6505 and I2C_HID_OF_GOODIX as modules
 - Enable SND_SOC_MT8186_MT6366, SND_SOC_SOF_MT8186 and SND_SOC_MT8186 as
   modules
 - Enable SX9324 as a module
   * udeb: Move i2c-hid-of-goodix module to fb-modules
 .
   [ Dylan Aïssi ]
   * [arm64] drivers/gpu/drm/panthor: Enable DRM_PANTHOR as module
 .
   [ Dmitry Baryshkov ]
   * [arm64] Enable SC_CAMCC_8280XP as module, camera clock controller on
 Lenovo ThinkPad X13s laptop.
   * [arm64] Enable SC_GCC_8180X, SM_GPUCC_8150, INTERCONNECT_QCOM_SC8180X and
 PINCTRL_SC8180X as modules in order to support Lenovo Flex 5G laptops.
   * [arm64] Include modules for Lenovo Flex 5G (Snapdragon SC8180X)
   * [arm64] enable Qualcomm X Elite modules: CLK_X1E80100_GCC and
 INTERCONNECT_QCOM_X1E80100 as built-in and CLK_X1E80100_CAMCC,
 CLK_X1E80100_DISPCC, CLK_X1E80100_GPUCC, CLK_X1E80100_TCSRCC,
 DRM_PANEL_SAMSUNG_ATNA33XC20, PHY_QCOM_SNPS_EUSB2,
 PHY_QCOM_EUSB2_REPEATER, PINCTRL_X1E80100 and SND_SOC_X1E80100 as modules.
   * [arm64] Include modules for Qualcomm X Elite laptops
 .
   [ Diederik de Haas ]
   * [arm64] Enable additional modules for rk356x devices:
 - [arm64] drivers/gpu/drm/panel: Enable DRM_PANEL_SITRONIX_ST7789V as
   module
 - [arm64] drivers/input/touchscreen: Enable TOUCHSCREEN_ST1232 as module
 - [arm64] drivers/pci/controller/dwc: Enable PCIE_ROCKCHIP_DW_EP
 - [arm64] drivers/regulator: Enable REGULATOR_TPS6286X as module
 - [arm64] drivers/rtc: Enable RTC_DRV_PCF85363 as module
 - [arm64] drivers/usb/typec: Enable TYPEC_WUSB3801 as module
 - [arm64] drivers/video/backlight: En

Bug#1079501: marked as done (linux-image-6.11-rc4-riscv64: Linux kernel config INPUT_AXP20X_PEK=m missing INPUT_MISC=y dependency)

[Debian Bug Tracking System]

Your message dated Fri, 20 Sep 2024 11:00:10 +
with message-id 
and subject line Bug#1079501: fixed in linux 6.11-1~exp1
has caused the Debian Bug report #1079501,
regarding linux-image-6.11-rc4-riscv64: Linux kernel config INPUT_AXP20X_PEK=m 
missing INPUT_MISC=y dependency
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.)


-- 
1079501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.11~rc4-1~exp1
Severity: normal
X-Debbugs-Cc: luc...@gmail.com

Dear Maintainer,

Dependency INPUT_MISC=y is missing from Kconfig options needed by 
CONFIG_INPUT_AXP20X_PEK=m in debian/config/config

This makes built Linux kernels fail to have CONFIG_INPUT_AXP20X_PEK=m (and 
probably other options are washed out too).

-- Package-specific info:
** Version:
Linux version 6.11-rc4-riscv64 (debian-kernel@lists.debian.org) 
(riscv64-linux-gnu-gcc-14 (Debian 14.2.0-1) 14.2.0, GNU ld (GNU Binutils for 
Debian) 2.43.1) #1 SMP Debian 6.11~rc4-1~exp1 (2024-08-21)

** Command line:
BOOT_IMAGE=/boot/vmlinux-6.11-rc4-riscv64 
root=UUID=e7f17542-3ac6-4d3b-8457-b3fc416051cf ro quiet

** Not tainted

** Kernel log:
[   17.950647] systemd[1]: Reached target paths.target - Path Units.
[   17.950767] systemd[1]: Reached target remote-fs.target - Remote File 
Systems.
[   17.950894] systemd[1]: Reached target slices.target - Slice Units.
[   17.951117] systemd[1]: Reached target veritysetup.target - Local Verity 
Protected Volumes.
[   17.958002] systemd[1]: Listening on systemd-creds.socket - Credential 
Encryption/Decryption.
[   17.958482] systemd[1]: Listening on systemd-initctl.socket - initctl 
Compatibility Named Pipe.
[   17.959028] systemd[1]: Listening on systemd-journald-dev-log.socket - 
Journal Socket (/dev/log).
[   17.959554] systemd[1]: Listening on systemd-journald.socket - Journal 
Sockets.
[   17.959781] systemd[1]: systemd-pcrextend.socket - TPM PCR Measurements was 
skipped because of an unmet condition check (ConditionSecurity=measured-uki).
[   17.959913] systemd[1]: systemd-pcrlock.socket - Make TPM PCR Policy was 
skipped because of an unmet condition check (ConditionSecurity=measured-uki).
[   17.960468] systemd[1]: Listening on systemd-udevd-control.socket - udev 
Control Socket.
[   17.960881] systemd[1]: Listening on systemd-udevd-kernel.socket - udev 
Kernel Socket.
[   17.966309] systemd[1]: Mounting dev-hugepages.mount - Huge Pages File 
System...
[   17.971454] systemd[1]: Mounting dev-mqueue.mount - POSIX Message Queue File 
System...
[   17.977558] systemd[1]: Mounting run-lock.mount - Legacy Locks Directory 
/run/lock...
[   17.988842] systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File 
System...
[   18.001009] systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace 
File System...
[   18.037084] systemd[1]: Starting kmod-static-nodes.service - Create List of 
Static Device Nodes...
[   18.043218] systemd[1]: Starting modprobe@configfs.service - Load Kernel 
Module configfs...
[   18.053601] systemd[1]: Starting modprobe@drm.service - Load Kernel Module 
drm...
[   18.065203] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel 
Module efi_pstore...
[   18.073561] systemd[1]: Starting modprobe@fuse.service - Load Kernel Module 
fuse...
[   18.074355] systemd[1]: systemd-fsck-root.service - File System Check on 
Root Device was skipped because of an unmet condition check 
(ConditionPathExists=!/run/initramfs/fsck-root).
[   18.074606] systemd[1]: systemd-hibernate-clear.service - Clear Stale 
Hibernate Storage Info was skipped because of an unmet condition check 
(ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
[   18.089120] systemd[1]: Starting systemd-journald.service - Journal 
Service...
[   18.101753] systemd[1]: Starting systemd-modules-load.service - Load Kernel 
Modules...
[   18.101895] systemd[1]: systemd-pcrmachine.service - TPM PCR Machine ID 
Measurement was skipped because of an unmet condition check 
(ConditionSecurity=measured-uki).
[   18.108304] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
[   18.108731] systemd[1]: systemd-tpm2-setup-early.service - Early TPM SRK 
Setup was skipped because of an unmet condition check 
(ConditionSecurity=measured-uki).
[   18.117484] systemd[1]: Starting systemd-udev-load-credentials.service - 
Load udev Rules from Credentials...
[   18.161727] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All 
udev Devices

Bug#1081114: marked as done (linux: Please enable CONFIG_MT7925E=m, CONFIG_MT7925U=m)

[Debian Bug Tracking System]

Your message dated Fri, 20 Sep 2024 11:00:10 +
with message-id 
and subject line Bug#1081114: fixed in linux 6.11-1~exp1
has caused the Debian Bug report #1081114,
regarding linux: Please enable CONFIG_MT7925E=m, CONFIG_MT7925U=m
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.)


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

Dear maintainers,

Please enable support for MediaTek Wi-Fi 7 adapters based on the
mt7925 driver. These adapters can be purchased now (e.g. the AzureWave
AW-EB600NF M.2 module) but the driver for these adapters is not enabled
in the Debian kernel:

$ grep -i mt7925 /boot/config-6.10.7-amd64
# CONFIG_MT7925E is not set
# CONFIG_MT7925U is not set

The Bluetooth functionality on the module that I have is provided by
a USB device with ID 13d3:3604, which needs a patch to add the device
ID [0]. It looks like this is in bluetooth-next and will probably be
in 6.12.

The firmware-mediatek package already ships firmware for the mt7925
driver:

$ dpkg -L firmware-mediatek | grep mt7925
/usr/lib/firmware/mediatek/mt7925
/usr/lib/firmware/mediatek/mt7925/BT_RAM_CODE_MT7925_1_1_hdr.bin
/usr/lib/firmware/mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin
/usr/lib/firmware/mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin

Ubuntu enabled the mt7925 driver some time ago [1].

Thanks!

[0] 
https://patchwork.kernel.org/project/linux-mediatek/patch/20240715061508.14077-1-jiande...@mediatek.com/

[1] https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2043542

-- 
Robert Edmonds
edmo...@debian.org
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.11-1~exp1
Done: Ben Hutchings 

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 1081...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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, 19 Sep 2024 18:42:39 +0200
Source: linux
Architecture: source
Version: 6.11-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 980555 1036714 1079272 1079501 1079755 1081114
Changes:
 linux (6.11-1~exp1) experimental; urgency=medium
 .
   * New upstream release: https://kernelnewbies.org/Linux_6.11
 .
   [ Marcin Juszkiewicz ]
   * [arm64] udeb: Add kernel modules to get USB/SATA/PCIe working on Rockchip
 RK3588
 .
   [ Alper Nebi Yasak ]
   * [arm64] Enable modules for MT8186 Chromebooks
 - Enable DRM_ITE_IT6505 and I2C_HID_OF_GOODIX as modules
 - Enable SND_SOC_MT8186_MT6366, SND_SOC_SOF_MT8186 and SND_SOC_MT8186 as
   modules
 - Enable SX9324 as a module
   * udeb: Move i2c-hid-of-goodix module to fb-modules
 .
   [ Dylan Aïssi ]
   * [arm64] drivers/gpu/drm/panthor: Enable DRM_PANTHOR as module
 .
   [ Dmitry Baryshkov ]
   * [arm64] Enable SC_CAMCC_8280XP as module, camera clock controller on
 Lenovo ThinkPad X13s laptop.
   * [arm64] Enable SC_GCC_8180X, SM_GPUCC_8150, INTERCONNECT_QCOM_SC8180X and
 PINCTRL_SC8180X as modules in order to support Lenovo Flex 5G laptops.
   * [arm64] Include modules for Lenovo Flex 5G (Snapdragon SC8180X)
   * [arm64] enable Qualcomm X Elite modules: CLK_X1E80100_GCC and
 INTERCONNECT_QCOM_X1E80100 as built-in and CLK_X1E80100_CAMCC,
 CLK_X1E80100_DISPCC, CLK_X1E80100_GPUCC, CLK_X1E80100_TCSRCC,
 DRM_PANEL_SAMSUNG_ATNA33XC20, PHY_QCOM_SNPS_EUSB2,
 PHY_QCOM_EUSB2_REPEATER, PINCTRL_X1E80100 and SND_SOC_X1E80100 as modules.
   * [arm64] Include modules for Qualcomm X Elite laptops
 .
   [ Diederik de Haas ]
   * [arm64] Enable additional modules for rk356x devices:
 - [arm64] drivers/gpu/drm/panel: Enable DRM_PANEL_SITRONIX_ST7789V as
   module
 - [arm64] drivers/input/touchscreen: Enable TOUCHSCREEN_ST1232 as module
 - [arm64] drivers/pci/controller/dwc: Enable PCIE_ROCKCHIP_DW_EP
 - [arm64] drivers/regulator: Enable

Bug#1079725: marked as done (linux: powerpc: 6.9+ kernel fails to boot from Open Firmware with CONFIG_CRASH_DUMP=y)

[Debian Bug Tracking System]

Your message dated Fri, 20 Sep 2024 11:00:10 +
with message-id 
and subject line Bug#1079755: fixed in linux 6.11-1~exp1
has caused the Debian Bug report #1079755,
regarding linux: powerpc: 6.9+ kernel fails to boot from Open Firmware with 
CONFIG_CRASH_DUMP=y
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.)


-- 
1079755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.10.4-1
Severity: normal
File: linux
X-Debbugs-Cc: d...@vasilevsky.ca

Debian kernels 6.9 and higher fail to boot on most PowerPC 32-bit systems.
These kernels have CONFIG_CRASH_DUMP=y set. This yields the message:

> Error: You can't boot a kdump kernel from OF!

See discussion on the debian-powerpc list:

* Initial report: https://lists.debian.org/debian-powerpc/2024/07/msg1.html
* Verification that CONFIG_CRASH_DUMP is indeed the problem: 
https://lists.debian.org/debian-powerpc/2024/08/msg00018.html

This occurs due to a change upstream, that makes CRASH_DUMP enabled by default.
We're working on fixing this upstream: 
https://lore.kernel.org/lkml/87frqsghws.fsf@mail.lhotse/T/

In the meantime, Debian's kernel config should explicitly disable 
CONFIG_CRASH_DUMP on
32-bit powerpc.

-- Package-specific info:

** Kernel log: boot messages should be attached

Error: You can't boot a kdump kernel from OF!

** Model information
revision: 2.9 (pvr 000c 0209)
platform: PowerMac
model   : PowerMac3,1
machine : PowerMac3,1
motherboard : PowerMac3,1 MacRISC MacRISC2 Power Macintosh
Device Tree model: PowerMac3,1

** PCI devices:
00:0b.0 Host bridge [0600]: Apple Inc. UniNorth PCI [106b:001f]
Subsystem: Red Hat, Inc. Device [1af4:1100]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- 
SERR- 

Versions of packages linux-image-6.10.4-powerpc suggests:
pn  debian-kernel-handbook  
pn  firmware-linux-free 
ii  grub-ieee1275   2.12-5
pn  linux-doc-6.10  
pn  mkvmlinuz   

Versions of packages linux-image-6.10.4-powerpc 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
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.11-1~exp1
Done: Ben Hutchings 

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 1079...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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, 19 Sep 2024 18:42:39 +0200
Source: linux
Architecture: source
Version: 6.11-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 980555 1036714 1079272 1079501 1079755 1081114
Changes:
 linux (6.11-1~exp1) experimental; urgency=medium
 .
   * New upstream release: https://kernelnewbies.org/Linux_6.11
 .
   [ Marcin Juszkiewicz ]
   * [arm64] udeb: Add kernel modules to get USB/SATA/PCIe working on Rockchip
 RK3588
 .
   [ Alper Nebi Yasak ]
   * [arm64] Enable modules for MT8186 Chromebooks
 - Enable DRM_ITE_IT6505 and I2C_HID_OF_GOODIX as modules
 - Enable SND_SOC_MT8186_MT6366, SND_SOC_SOF

Bug#1036714: marked as done (linux: Add Intel Speed Select Tool to linux-cpupower)

[Debian Bug Tracking System]

Your message dated Fri, 20 Sep 2024 11:00:10 +
with message-id 
and subject line Bug#1036714: fixed in linux 6.11-1~exp1
has caused the Debian Bug report #1036714,
regarding linux: Add Intel Speed Select Tool to linux-cpupower
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.)


-- 
1036714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 6.3.2-1~exp1
Severity: wishlist
Tags: patch
X-Debbugs-Cc: miguel.bernal.ma...@linux.intel.com, jair.gonza...@linux.intel.com

Dear Maintainer,

The Intel Speed Select Technology [1] was requested at Bug #1028344, and
enabled at 5a0e7e75be81 ("[x86] Enable Intel Speed Select Technology") in
salsa. This technology can be set via sysfs, but there is a tool [2] which
helps on this setup.

The tool can be integrated in the actual linux-cpupower package.

A MR was created with this proposal:

https://salsa.debian.org/kernel-team/linux/-/merge_requests/732

[1] 
https://www.intel.la/content/www/xl/es/architecture-and-technology/speed-select-technology-article.html
[2] https://docs.kernel.org/admin-guide/pm/intel-speed-select.html

Thanks,
Miguel
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.11-1~exp1
Done: Ben Hutchings 

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 1036...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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, 19 Sep 2024 18:42:39 +0200
Source: linux
Architecture: source
Version: 6.11-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 980555 1036714 1079272 1079501 1079755 1081114
Changes:
 linux (6.11-1~exp1) experimental; urgency=medium
 .
   * New upstream release: https://kernelnewbies.org/Linux_6.11
 .
   [ Marcin Juszkiewicz ]
   * [arm64] udeb: Add kernel modules to get USB/SATA/PCIe working on Rockchip
 RK3588
 .
   [ Alper Nebi Yasak ]
   * [arm64] Enable modules for MT8186 Chromebooks
 - Enable DRM_ITE_IT6505 and I2C_HID_OF_GOODIX as modules
 - Enable SND_SOC_MT8186_MT6366, SND_SOC_SOF_MT8186 and SND_SOC_MT8186 as
   modules
 - Enable SX9324 as a module
   * udeb: Move i2c-hid-of-goodix module to fb-modules
 .
   [ Dylan Aïssi ]
   * [arm64] drivers/gpu/drm/panthor: Enable DRM_PANTHOR as module
 .
   [ Dmitry Baryshkov ]
   * [arm64] Enable SC_CAMCC_8280XP as module, camera clock controller on
 Lenovo ThinkPad X13s laptop.
   * [arm64] Enable SC_GCC_8180X, SM_GPUCC_8150, INTERCONNECT_QCOM_SC8180X and
 PINCTRL_SC8180X as modules in order to support Lenovo Flex 5G laptops.
   * [arm64] Include modules for Lenovo Flex 5G (Snapdragon SC8180X)
   * [arm64] enable Qualcomm X Elite modules: CLK_X1E80100_GCC and
 INTERCONNECT_QCOM_X1E80100 as built-in and CLK_X1E80100_CAMCC,
 CLK_X1E80100_DISPCC, CLK_X1E80100_GPUCC, CLK_X1E80100_TCSRCC,
 DRM_PANEL_SAMSUNG_ATNA33XC20, PHY_QCOM_SNPS_EUSB2,
 PHY_QCOM_EUSB2_REPEATER, PINCTRL_X1E80100 and SND_SOC_X1E80100 as modules.
   * [arm64] Include modules for Qualcomm X Elite laptops
 .
   [ Diederik de Haas ]
   * [arm64] Enable additional modules for rk356x devices:
 - [arm64] drivers/gpu/drm/panel: Enable DRM_PANEL_SITRONIX_ST7789V as
   module
 - [arm64] drivers/input/touchscreen: Enable TOUCHSCREEN_ST1232 as module
 - [arm64] drivers/pci/controller/dwc: Enable PCIE_ROCKCHIP_DW_EP
 - [arm64] drivers/regulator: Enable REGULATOR_TPS6286X as module
 - [arm64] drivers/rtc: Enable RTC_DRV_PCF85363 as module
 - [arm64] drivers/usb/typec: Enable TYPEC_WUSB3801 as module
 - [arm64] drivers/video/backlight: Enable BACKLIGHT_LM3630A as module
 - [arm64] sound/soc/codecs: Enable SND_SOC_DMIC and SND_SOC_TAS2562 as
   module
   * [arm64] Update rk3588 platform support:
 - [arm64] drivers/clocksource: Enable ROCKCHIP_TIMER
 - [arm64] drivers/iommu: Enable IOMMU_IO_PGTABLE_LPAE
   

Bug#1079755: marked as done (linux: Please disable CONFIG_CRASH_DUMP on powerpc)

[Debian Bug Tracking System]

Your message dated Fri, 20 Sep 2024 11:00:10 +
with message-id 
and subject line Bug#1079755: fixed in linux 6.11-1~exp1
has caused the Debian Bug report #1079755,
regarding linux: Please disable CONFIG_CRASH_DUMP on powerpc
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.)


-- 
1079755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 6.10.6-1
Severity: normal
User: debian-powe...@lists.debian.org
Usertags: powerpc
X-Debbugs-Cc: debian-powe...@lists.debian.org

Hello,

in 75bc255a7444 [1] CONFIG_CRASH_DUMP was enabled by default for all 
architectures
which made the kernel unbootable on 32-bit PowerPC (powerpc) since crash dump 
kernels
cannot be booted from Open Firmware on this target [2].

Thus, please disable CONFIG_CRASH_DUMP on powerpc by default.

We may have to disable it on m68k and sh4 as well, but I haven't verified that 
yet.

Thanks,
Adrian

> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=75bc255a7444801d64c7a7bd09e3f452f86b3585
> [2] https://lists.debian.org/debian-powerpc/2024/07/msg1.html

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.11-1~exp1
Done: Ben Hutchings 

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 1079...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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, 19 Sep 2024 18:42:39 +0200
Source: linux
Architecture: source
Version: 6.11-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 980555 1036714 1079272 1079501 1079755 1081114
Changes:
 linux (6.11-1~exp1) experimental; urgency=medium
 .
   * New upstream release: https://kernelnewbies.org/Linux_6.11
 .
   [ Marcin Juszkiewicz ]
   * [arm64] udeb: Add kernel modules to get USB/SATA/PCIe working on Rockchip
 RK3588
 .
   [ Alper Nebi Yasak ]
   * [arm64] Enable modules for MT8186 Chromebooks
 - Enable DRM_ITE_IT6505 and I2C_HID_OF_GOODIX as modules
 - Enable SND_SOC_MT8186_MT6366, SND_SOC_SOF_MT8186 and SND_SOC_MT8186 as
   modules
 - Enable SX9324 as a module
   * udeb: Move i2c-hid-of-goodix module to fb-modules
 .
   [ Dylan Aïssi ]
   * [arm64] drivers/gpu/drm/panthor: Enable DRM_PANTHOR as module
 .
   [ Dmitry Baryshkov ]
   * [arm64] Enable SC_CAMCC_8280XP as module, camera clock controller on
 Lenovo ThinkPad X13s laptop.
   * [arm64] Enable SC_GCC_8180X, SM_GPUCC_8150, INTERCONNECT_QCOM_SC8180X and
 PINCTRL_SC8180X as modules in order to support Lenovo Flex 5G laptops.
   * [arm64] Include modules for Lenovo Flex 5G (Snapdragon SC8180X)
   * [arm64] enable Qualcomm X Elite modules: CLK_X1E80100_GCC and
 INTERCONNECT_QCOM_X1E80100 as built-in and CLK_X1E80100_CAMCC,
 CLK_X1E80100_DISPCC, CLK_X1E80100_GPUCC, CLK_X1E80100_TCSRCC,
 DRM_PANEL_SAMSUNG_ATNA33XC20, PHY_QCOM_SNPS_EUSB2,
 PHY_QCOM_EUSB2_REPEATER, PINCTRL_X1E80100 and SND_SOC_X1E80100 as modules.
   * [arm64] Include modules for Qualcomm X Elite laptops
 .
   [ Diederik de Haas ]
   * [arm64] Enable additional modules for rk356x devices:
 - [arm64] drivers/gpu/drm/panel: Enable DRM_PANEL_SITRONIX_ST7789V as
   module
 - [arm64] drivers/input/touchscreen: Enable TOUCHSCREEN_ST1232 as module
 - [arm64] drivers/pci/controller/dwc: Enable PCIE_ROCKCHIP_DW_EP
 - [arm64] drivers/regulator: Enable REGULATOR_TPS6286X as module
 - [arm64] drivers/rtc: Enable RTC_DRV_PCF85363 as module
 - [arm64] drivers/usb/typec: Enable TYPEC_WUSB3801 as module
 - [arm64] drivers/video/backlight: Enable BACKLIGHT_LM3630A as module
 - [arm64] sound/soc/codecs: Enable SND_SOC_DMIC and SND_SOC_TAS2562 as
   module
   * [arm64] Update rk35

Bug#1079272: marked as done (linux [amd64]: Enable CRYPTO_DEV_IAA_CRYPTO)

[Debian Bug Tracking System]

Your message dated Fri, 20 Sep 2024 11:00:10 +
with message-id 
and subject line Bug#1079272: fixed in linux 6.11-1~exp1
has caused the Debian Bug report #1079272,
regarding linux [amd64]: Enable CRYPTO_DEV_IAA_CRYPTO
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.)


-- 
1079272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 6.11~rc4-1~exp1
Severity: wishlist
Tags: patch
X-Debbugs-Cc: jair.gonza...@linux.intel.com,
miguel.bernal.ma...@linux.intel.com

Dear Maintainer,

Please enable the support for Intel(R) IAA Compression Accelerator
(CONFIG_CRYPTO_DEV_IAA_CRYPTO).

The IAA (Intel(R) Analytics Accelerator) crypto driver supports
compression/decompression compatible with the DEFLATE compression
standard described in RFC 1951, which is the
compression/decompression algorithm exported by this module.

The IAA Compression Accelerator Crypto Driver documentation can be
found here:
https://docs.kernel.org/driver-api/crypto/iaa/iaa-crypto.html

A MR was created with this proposal at:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/1166

Thanks,
Jair Gonzalez
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.11-1~exp1
Done: Ben Hutchings 

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 1079...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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, 19 Sep 2024 18:42:39 +0200
Source: linux
Architecture: source
Version: 6.11-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 980555 1036714 1079272 1079501 1079755 1081114
Changes:
 linux (6.11-1~exp1) experimental; urgency=medium
 .
   * New upstream release: https://kernelnewbies.org/Linux_6.11
 .
   [ Marcin Juszkiewicz ]
   * [arm64] udeb: Add kernel modules to get USB/SATA/PCIe working on Rockchip
 RK3588
 .
   [ Alper Nebi Yasak ]
   * [arm64] Enable modules for MT8186 Chromebooks
 - Enable DRM_ITE_IT6505 and I2C_HID_OF_GOODIX as modules
 - Enable SND_SOC_MT8186_MT6366, SND_SOC_SOF_MT8186 and SND_SOC_MT8186 as
   modules
 - Enable SX9324 as a module
   * udeb: Move i2c-hid-of-goodix module to fb-modules
 .
   [ Dylan Aïssi ]
   * [arm64] drivers/gpu/drm/panthor: Enable DRM_PANTHOR as module
 .
   [ Dmitry Baryshkov ]
   * [arm64] Enable SC_CAMCC_8280XP as module, camera clock controller on
 Lenovo ThinkPad X13s laptop.
   * [arm64] Enable SC_GCC_8180X, SM_GPUCC_8150, INTERCONNECT_QCOM_SC8180X and
 PINCTRL_SC8180X as modules in order to support Lenovo Flex 5G laptops.
   * [arm64] Include modules for Lenovo Flex 5G (Snapdragon SC8180X)
   * [arm64] enable Qualcomm X Elite modules: CLK_X1E80100_GCC and
 INTERCONNECT_QCOM_X1E80100 as built-in and CLK_X1E80100_CAMCC,
 CLK_X1E80100_DISPCC, CLK_X1E80100_GPUCC, CLK_X1E80100_TCSRCC,
 DRM_PANEL_SAMSUNG_ATNA33XC20, PHY_QCOM_SNPS_EUSB2,
 PHY_QCOM_EUSB2_REPEATER, PINCTRL_X1E80100 and SND_SOC_X1E80100 as modules.
   * [arm64] Include modules for Qualcomm X Elite laptops
 .
   [ Diederik de Haas ]
   * [arm64] Enable additional modules for rk356x devices:
 - [arm64] drivers/gpu/drm/panel: Enable DRM_PANEL_SITRONIX_ST7789V as
   module
 - [arm64] drivers/input/touchscreen: Enable TOUCHSCREEN_ST1232 as module
 - [arm64] drivers/pci/controller/dwc: Enable PCIE_ROCKCHIP_DW_EP
 - [arm64] drivers/regulator: Enable REGULATOR_TPS6286X as module
 - [arm64] drivers/rtc: Enable RTC_DRV_PCF85363 as module
 - [arm64] drivers/usb/typec: Enable TYPEC_WUSB3801 as module
 - [arm64] drivers/video/backlight: Enable BACKLIGHT_LM3630A as module
 - [arm64] sound/soc/codecs: Enable SND_SOC_DMIC and SND_SOC_TAS2562 as
   module
   * [arm64] Update rk3588 platform support:
 - [arm64] drivers/clocksource: Enable ROCKCHIP_TIMER
 - [arm64] drivers/iommu: Enable IOMMU_IO_PGTABLE_LPAE
 - [arm64] drivers

Processed: bug 1076483 is forwarded to https://lore.kernel.org/linux-pm/20240919081121.10784-2-uklei...@debian.org

[Debian Bug Tracking System]

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

> forwarded 1076483 
> https://lore.kernel.org/linux-pm/20240919081121.10784-2-uklei...@debian.org
Bug #1076483 [src:linux] Call Trace on rt kernel, CPU Intel 13th Gen Intel(R) 
Core(TM) i5-1340P
Bug #1081705 [src:linux] Call Trace: dump_stack_lvl+0x64/0x80 RIP: 
0010:poll_idle+0x68/0xc0
Set Bug forwarded-to-address to 
'https://lore.kernel.org/linux-pm/20240919081121.10784-2-uklei...@debian.org'.
Set Bug forwarded-to-address to 
'https://lore.kernel.org/linux-pm/20240919081121.10784-2-uklei...@debian.org'.
> thanks
Stopping processing here.

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

Bug#1080414: marked as done (linux-image-amd64: Kernel 6.10.x login as user not possible)

[Debian Bug Tracking System]

Your message dated Thu, 19 Sep 2024 12:16:37 +0200
with message-id 
and subject line Re: Bug#1080414: linux-image-amd64: Kernel 6.10.x login as 
user not possible
has caused the Debian Bug report #1080414,
regarding linux-image-amd64: Kernel 6.10.x login as user not possible
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.)


-- 
1080414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-image-amd64
Version: 6.10.7-1
Severity: normal

Dear Maintainer,
for some reason, loging in as a normal (not the root user) user is not possible on one of my systems, running Gnome v46. Logging in through gdm3, logging in per ssh as root and then switching the user with 'su - ' or logging in to the user directly over ssh only loads forever without ever finishing. Tested with 6.10.4 and 6.10.6 (though only with Wayland session). Just updated to v6.10.7 from sid, where the issue looks slightly different. You don't get stuck in gdm3, but on a black screen showing only the mouse cursor that usually only appears for a short moment before loading the desktop. In this state, the UI seems to be completely frozen, not even switching tty is possible anymore. The systemd logs seem to show similar error messages from kernel though. For now the only fix I've found was to boot a self-compiled Kernel ov v6.9 (not sure on which Kernel version from Debian's repos I based the config for it, but I made no changes other than what's being done by 
'make olddefconfig'. So it would probably also work with v6.9 from Debian repos if I still had that version around.


I have a similar setup on my productive system (Gnome v46, Kernel 6.10.6, 
though no NFS mounts and no LDAP authentication) where I have no issues with 
logging in though.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9.11-falcot (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE=de_DE:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-amd64 depends on:
ii  linux-image-6.10.7-amd64  6.10.7-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information


These are the log messages that will show up when trying to log in:

Sep 03 14:08:48 gdm-password][1958]: pam_unix(gdm-password:auth): authentication 
failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost=  user=
Sep 03 14:08:48 gdm-password][1958]: gkr-pam: unable to locate daemon control 
file
Sep 03 14:08:48 gdm-password][1958]: gkr-pam: stashed password to try later in 
open session
Sep 03 14:08:48 accounts-daemon[710]: request by system-bus-name::1.64 
[gdm-session-worker [pam/gdm-password] pid:1958 uid:0]: cache user ''
Sep 03 14:08:48 gdm-password][1958]: pam_unix(gdm-password:session): session opened for 
user (uid=10121) by (uid=0)
Sep 03 14:08:48 gdm-password][1958]: pam_systemd(gdm-password:session): New 
sd-bus connection (system-bus-pam-systemd-1958) opened.
Sep 03 14:08:48 systemd[1]: Created slice user-10121.slice - User Slice of UID 
10121.
Sep 03 14:08:48 systemd[1]: Starting user-runtime-dir@10121.service - User 
Runtime Directory /run/user/10121...
Sep 03 14:08:48 systemd-logind[741]: New session 2 of user .
Sep 03 14:08:48 systemd[1]: Finished user-runtime-dir@10121.service - User 
Runtime Directory /run/user/10121.
Sep 03 14:08:48 systemd[1]: Starting user@10121.service - User Manager for UID 
10121...
Sep 03 14:08:48 (systemd)[1969]: pam_unix(systemd-user:session): session opened for user 
(uid=10121) by (uid=0)
Sep 03 14:08:48 systemd-logind[741]: New session 3 of user .
Sep 03 14:08:48 systemd[1]: Started user@10121.service - User Manager for UID 
10121.
Sep 03 14:08:48 systemd[1]: Started session-2.scope - Session 2 of User 
.
Sep 03 14:08:48 rtkit-daemon[1471]: Supervising 7 threads of 4 processes of 1 
users.
Sep 03 14:08:48 rtkit-daemon[1471]: Supervising 7 threads of 4 processes of 1 
users.
Sep 03 14:08:48 rtkit-daemon[1471]: Supervising 7 threads of 4 processes of 1 
users.
Sep 03 14:08:48 rtkit-daemon[1471]: Supervising 7 threads of 4 processes of 1 
users.
Sep 03 14:08:48 rtkit-daemon[1471]: Supervising 7 threads of 4 processes of 1 
users.
Sep 03 14:08:48 rtkit-daemon[1471]: Supervising 7

Processed: limit source to linux, tagging 1036714, tagging 1081114

[Debian Bug Tracking System]

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

> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'

> tags 1036714 + pending
Bug #1036714 [src:linux] linux: Add Intel Speed Select Tool to linux-cpupower
Added tag(s) pending.
> tags 1081114 + pending
Bug #1081114 [linux] linux: Please enable CONFIG_MT7925E=m, CONFIG_MT7925U=m
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1080414: linux-image-amd64: Kernel 6.10.x login as user not possible

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1080414 [src:linux] linux-image-amd64: Kernel 6.10.x login as user not 
possible
Added tag(s) moreinfo.

-- 
1080414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1080414 to src:linux

[Debian Bug Tracking System]

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

> reassign 1080414 src:linux 6.10.7-1
Bug #1080414 [linux-image-amd64] linux-image-amd64: Kernel 6.10.x login as user 
not possible
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/6.10.7+1.
Ignoring request to alter fixed versions of bug #1080414 to the same values 
previously set
Bug #1080414 [src:linux] linux-image-amd64: Kernel 6.10.x login as user not 
possible
Marked as found in versions linux/6.10.7-1.
> thanks
Stopping processing here.

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

Processed: severity of 1082081 is important

[Debian Bug Tracking System]

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

> severity 1082081 important
Bug #1082081 [src:linux] Performance issues on VM (virtio)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: Re: Bug#1079684: still issues in linux 6.1.106-3

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1079684 {Done: Salvatore Bonaccorso } [src:linux] 
Network errors on VM
Bug 1079684 cloned as bug 1082081
> reopen -2
Bug #1082081 {Done: Salvatore Bonaccorso } [src:linux] 
Network errors on VM
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions linux/6.1.106-3.
> found -2 linux/6.1.106-3
Bug #1082081 [src:linux] Network errors on VM
Marked as found in versions linux/6.1.106-3.
> retitle -2 Performance issues on VM (virtio)
Bug #1082081 [src:linux] Network errors on VM
Changed Bug title to 'Performance issues on VM (virtio)' from 'Network errors 
on VM'.

-- 
1079684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079684
1082081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: limit source to linux, tagging 980555, tagging 1079272, tagging 1079501, tagging 1079755

[Debian Bug Tracking System]

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

> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'

> tags 980555 + pending
Bug #980555 [src:linux] Missing ec_sys module
Added tag(s) pending.
> tags 1079272 + pending
Bug #1079272 [src:linux] linux [amd64]: Enable CRYPTO_DEV_IAA_CRYPTO
Added tag(s) pending.
> tags 1079501 + pending
Bug #1079501 [src:linux] linux-image-6.11-rc4-riscv64: Linux kernel config 
INPUT_AXP20X_PEK=m missing INPUT_MISC=y dependency
Added tag(s) pending.
> tags 1079755 + pending
Bug #1079755 [src:linux] linux: Please disable CONFIG_CRASH_DUMP on powerpc
Bug #1079725 [src:linux] linux: powerpc: 6.9+ kernel fails to boot from Open 
Firmware with CONFIG_CRASH_DUMP=y
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1081739: linux-headers-6.10.9-amd64: apt-get error when installing linux-headers

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 evdi-dkms 1.14.2+dfsg-1
Bug #1081739 [linux-headers-6.10.9-amd64] linux-headers-6.10.9-amd64: apt-get 
error when installing linux-headers
Bug reassigned from package 'linux-headers-6.10.9-amd64' to 'evdi-dkms'.
No longer marked as found in versions linux/6.10.9-1.
Ignoring request to alter fixed versions of bug #1081739 to the same values 
previously set
Bug #1081739 [evdi-dkms] linux-headers-6.10.9-amd64: apt-get error when 
installing linux-headers
Marked as found in versions evdi/1.14.2+dfsg-1.

-- 
1081739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reopening 857043, tagging 857043

[Debian Bug Tracking System]

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

> reopen 857043
Bug #857043 {Done: Salvatore Bonaccorso } [nfs-common] 
nfs-common: Can nfsstat be made to show timeouts per mount point or globally 
for the machine?
Bug reopened
Ignoring request to alter fixed versions of bug #857043 to the same values 
previously set
> tags 857043 + upstream
Bug #857043 [nfs-common] nfs-common: Can nfsstat be made to show timeouts per 
mount point or globally for the machine?
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1081563: Please consider adding the new Xe Graphics driver for Intel GPUs

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 6.10.9
Bug #1081563 [src:linux] Please consider adding the new Xe Graphics driver for 
Intel GPUs
The source 'linux' and version '6.10.9' do not appear to match any binary 
packages
Ignoring request to alter found versions of bug #1081563 to the same values 
previously set
> found -1 6.10.9-1
Bug #1081563 [src:linux] Please consider adding the new Xe Graphics driver for 
Intel GPUs
Ignoring request to alter found versions of bug #1081563 to the same values 
previously set

-- 
1081563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1081739: linux-headers-6.10.9-amd64: apt-get error when installing linux-headers

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1081739 [linux-headers-6.10.9-amd64] linux-headers-6.10.9-amd64: apt-get 
error when installing linux-headers
Added tag(s) moreinfo.

-- 
1081739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013868: marked as done (nfs-common makes Python required on NFS clients)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 08:38:44 +
with message-id 
and subject line Bug#1013868: fixed in nfs-utils 1:2.7.1-2
has caused the Debian Bug report #1013868,
regarding nfs-common makes Python required on NFS clients
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.)


-- 
1013868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---


Package: nfs-common
Version: 1:2.6.1-2

Dear maintainers of nfs-common,

could you please move the three Python scripts included in nfs-common to 
a separate -extras package?


Currently nfs-common Depends on `python3` and, on lean/containerized 
client systems, it is the only package that requires it. For this 
reason, in 2019 Fedora moved the scripts `mountstats`, `nfsiostat` and 
`nfsconvert` to a separate package [1,2], required on servers (for 
`nfsconver`) but not on clients.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1667889
[2] https://github.com/coreos/fedora-coreos-tracker/issues/121

Kind regards,

--
Gioele Barabucci
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:2.7.1-2
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
nfs-utils, 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 1013...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated nfs-utils 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: Sat, 14 Sep 2024 10:13:35 +0200
Source: nfs-utils
Architecture: source
Version: 1:2.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team 
Changed-By: Salvatore Bonaccorso 
Closes: 1013868
Changes:
 nfs-utils (1:2.7.1-2) unstable; urgency=medium
 .
   * d/control: nfs-common: Move python3 to Recommends (Closes: #1013868)
Checksums-Sha1: 
 8f76ee0bff1c678137b7a13529f84be4c438c013 2633 nfs-utils_2.7.1-2.dsc
 7f8c31d9e5eabd1585884c35141abc6972d79224 49196 nfs-utils_2.7.1-2.debian.tar.xz
Checksums-Sha256: 
 a6e7bbc26f700360df5da63452c2e6167cee6db37c3d02cb6456b25f34de3856 2633 
nfs-utils_2.7.1-2.dsc
 6618b797968de4806de83fe52194d900d2e52523e25075b9baa96fadb12d5756 49196 
nfs-utils_2.7.1-2.debian.tar.xz
Files: 
 88fcad7a9213ee108a80e8c3bbba8e20 2633 net optional nfs-utils_2.7.1-2.dsc
 82eff1f2f2b3b439e1c16b12b1b4b06a 49196 net optional 
nfs-utils_2.7.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmblRkRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89ED1wQAJmW5iOWtHHq1TDRqLj1MF0oBiMTyAAs
3aS8LqMnA7HSoc320sAjz58qavCHZRVFZ4c4OMsiJ14SP4ewgERMTEnJR0roqnU5
ndUjpsB1Ik33I6D/oN3PMUxryHm9qERi7w6OWNXBQdzGRJjK12ET05T72jIkRHHY
x79SO2BLdOItNI18rJAkAjmKe6IlbTsGgch3TPwSFKpCJuPlP8u0Gs2uFO8OSg4a
fObxLYUQ8au7g4YZZ3fPgiG6tyA0UWSafPMYCEFESYtuJlbeI0liQqQ9TkRT83wx
Y7FK2Xoqu8xBsII2riUPPK3sD9NvAv/KKUWVMqavo3QIvZPj+sFHmP3ngEzOVW5T
w6sXHboNwbdP7l3BHqCGvottJ/gstx2NUQ2UCt9MCYDdOoySSe19Uk5r34R2mKhh
ENKhAB7EWBIfE8dgFRip2N2K9XpEWHQW6YdsPPgrYxkzIrDeNtuQrD6gEW6pbbLf
L1aGv3aetqpGFDTaDgbzlEtJjeBw8XHTMInWQoEE61pvRjJO0sVsaivxBX9ncBim
kc9RDlwoJWV5tIZp8rKccjF/TZkq7Kzf0XWncEP0r8uk7sFmklWH6GIQctUNe9rp
+Zp0FHnofGuy/PGXOtoSlahQyK2164wC2St2/BBdnxhORX5QwIokn4R6Gq9KTD5C
bWGPBXdVkq9J
=vwYG
-END PGP SIGNATURE-



pgpRuEf4HVcW_.pgp
Description: PGP signature
--- End Message ---

Bug#904707: marked as done (fakeroot chown fails on kerberized NFSv4)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 10:05:13 +0200 (CEST)
with message-id <20240914080513.ef9fcbe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #904707,
regarding fakeroot chown fails on kerberized NFSv4
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.)


-- 
904707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.94

Hi,

When the Lintian test suite runs on a kerberized NFSv4 volume,
't/tests/files-wrong-owner' fails with this error message:

tests::files-wrong-owner: chown: changing ownership of
'debian/files-wrong-owner/usr/lib/filenames/wrong-owner-100:0':
Invalid argument
tests::files-wrong-owner: make[1]: *** [debian/rules:13:
override_dh_fixperms] Error 1

The full log is attached.

I can replicate the behavior by cloning Lintian from salsa and running
'./debian/rules runtests onlyrun=files-wrong-owner'. I isolated the
error in the shell script below (also attached). In a strange twist,
the script produces no error for some low uids here, including 0 and
1, but fails consistently for uids that don't exist. (The uid 100
exists but fails.) Please try a different uid if you do not get the
error right away.

#!/bin/sh
set -x
tmpdir="$(mktemp -d --tmpdir=.)"
tmpfile="$(mktemp --tmpdir=$tmpdir)"
fakeroot -- chown 17171:0 $tmpfile   # offending command
rm $tmpfile
rmdir $tmpdir

I do not see a workaround in Lintian, so the bug should probably be
reassigned to 'nfs-utils'. The bugs over there did not strike me
immediately as related. (I have other bugs open and would be happy to
help.) Here are my mount and export details:

/etc/exports (on server):
/srv/nfs
*(rw,sync,no_subtree_check,no_root_squash,sec=krb5i:krb5p,fsid=0)
/srv/nfs/acct
*(rw,sync,no_subtree_check,no_root_squash,sec=krb5i:krb5p,mountpoint)

/etc/fstab (on client):
server:/acct /acct nfs4 rw,sec=krb5i,fsc 0 0

Perhaps it is relevant that 'root' on the client is allowed to use the
machine credentials:

/etc/idmapd (on server):
[Translation]
Method = nsswitch
GSS-Methods = static,nsswitch
[Static]
host/client.domain@domain.tld = root
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup


Also,

(client) Linux client.domain.tld 4.17.0-1-amd64 #1 SMP Debian 4.17.8-1
(2018-07-20) x86_64 GNU/Linux
(server) Linux server.domain.tld 4.16.0-2-amd64 #1 SMP Debian
4.16.16-2 (2018-06-22) x86_64 GNU/Linux

and finally,

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lintian depends on:
ii  binutils   2.31.1-1
ii  bzip2  1.0.6-8.1
ii  diffstat   1.61-1+b1
ii  dpkg   1.19.0.5+b1
ii  file   1:5.33-3
ii  gettext0.19.8.1-6+b1
ii  intltool-debian0.35.0+20060710.4
ii  libapt-pkg-perl0.1.34
ii  libarchive-zip-perl1.60-1
ii  libclass-accessor-perl 0.51-1
ii  libclone-perl  0.39-1
ii  libdigest-sha-perl 6.02-1
ii  libdpkg-perl   1.19.0.5
ii  libemail-valid-perl1.202-1
ii  libfile-basedir-perl   0.08-1
ii  libipc-run-perl20180523.0-1
ii  liblist-moreutils-perl 0.416-1+b3
ii  libparse-debianchangelog-perl  1.2.0-12
ii  libtext-levenshtein-perl   0.13-1
ii  libtimedate-perl   2.3000-2
ii  liburi-perl1.74-1
ii  libxml-simple-perl 2.25-1
ii  libyaml-libyaml-perl   0.72+repack-1
ii  man-db 2.8.3-2
ii  patchutils 0.3.4-2
ii  perl [libdigest-sha-perl]  5.26.2-6
ii  t1utils1.41-2
ii  xz-utils   5.2.2-1.3

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b4

Versions of packages lintian suggests:
ii  binutils-multiarch 2.31.1-1
ii  dpkg-dev   1.19.0.5
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.53-1

-- no debconf information

Thank you!


lintia

Bug#693549: marked as done (nfs-kernel-server: NFS Exports with domain names don't load at reboot)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 10:05:38 +0200 (CEST)
with message-id <20240914080538.437d3be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #693549,
regarding nfs-kernel-server: NFS Exports with domain names don't load at reboot
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.)


-- 
693549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.2.2-4squeeze2
Severity: normal


Hi,

Similar to bug #598493.

Setup:
- NFS server with an export that has a DNS name in it
- Separate DNS server
- NFS server has allow-hotplug in /etc/network/interfaces

Problem:
On reboot, the NFS server doesn't have any exports. After reboot,
if you login and run exportfs -r then it will load them fine.

Errors:
exportfs complains that each name in /etc/exports "has non-inet addr"

Temporary Solution:
If you change allow-hotplug to auto in /etc/network/interfaces then
all works fine. Note allow-hotplug is default for fresh installs.

Is there some way to make the init script require that the network device
is up before running exportfs?

Cheers,

Hugh

-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nfs-kernel-server depends on:
ii  libblkid1   2.17.2-9 block device id library
ii  libc6   2.11.3-4 Embedded GNU C Library: Shared lib
ii  libcomerr2  1.41.12-4stable1 common error description library
ii  libgssapi-krb5-21.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - k
ii  libgssglue1 0.1-4mechanism-switch gssapi library
ii  libk5crypto31.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - C
ii  libkrb5-3   1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries
ii  libnfsidmap20.23-2   An nfs idmapping library
ii  librpcsecgss3   0.19-2   allows secure rpc communication us
ii  libwrap07.6.q-19 Wietse Venema's TCP wrappers libra
ii  lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii  nfs-common  1:1.2.2-4squeeze2NFS support files common to client
ii  ucf 3.0025+nmu1  Update Configuration File: preserv

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Bug#756885: marked as done (nfsidmap: request-key command line wrong arg count)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 10:07:23 +0200 (CEST)
with message-id <20240914080723.12b11be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #756885,
regarding nfsidmap: request-key command line wrong arg count
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.)


-- 
756885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.2.8-6
Severity: normal

idmapd does not work (fails to use correct domain depsite configure in 
idmap.conf) because
/etc/request-key.d/id_resolver.conf has incorrect number of arguments.  Syslog 
says:

Aug  2 22:19:04  nfsidmap[29796]: Bad arg count. Check 
/etc/request-key.conf
Aug  2 22:20:19  nfsidmap[32515]: nss_getpwnam: name 'root@local' does 
not map into domain ''
d

And no  and  are not the actual host and domain.

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  34716  status
1000241   tcp  42067  status
1000211   udp  40190  nlockmgr
1000213   udp  40190  nlockmgr
1000214   udp  40190  nlockmgr
1000211   tcp  51570  nlockmgr
1000213   tcp  51570  nlockmgr
1000214   tcp  51570  nlockmgr
-- /etc/default/nfs-common --
NEED_STATD=no
STATDOPTS=
NEED_IDMAPD=yes
NEED_GSSD=no
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
Domain = 
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
only relevant bit is sec=sys
-- /proc/mounts --
[no relavant bits]

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nfs-common depends on:
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-53.2
ii  libc6   2.19-7
ii  libcap2 1:2.24-3
ii  libcomerr2  1.42.11-2
ii  libdevmapper1.02.1  2:1.02.85-2
ii  libevent-2.0-5  2.0.21-stable-1
ii  libgssglue1 0.4-2
ii  libk5crypto31.12.1+dfsg-5
ii  libkeyutils11.5.9-4
ii  libkrb5-3   1.12.1+dfsg-5
ii  libmount1   2.20.1-5.8
ii  libnfsidmap20.25-5
ii  libtirpc1   0.2.3-2
ii  libwrap07.6.q-25
ii  lsb-base4.1+Debian13
ii  rpcbind 0.2.1-4
ii  ucf 3.0030

Versions of packages nfs-common recommends:
ii  python  2.7.8-1

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

-- Configuration Files:
/etc/default/nfs-common changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Processed: closing 848017

[Debian Bug Tracking System]

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

> close 848017 1:1.3.4-2
Bug #848017 [nfs-common] "unable to obtain root (machine) credentials" without 
gss/krb5i
Ignoring request to alter fixed versions of bug #848017 to the same values 
previously set
Bug #848017 [nfs-common] "unable to obtain root (machine) credentials" without 
gss/krb5i
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 832609

[Debian Bug Tracking System]

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

> close 832609 1:1.3.4-2
Bug #832609 [nfs-common] rpc-gssd.service: fails to start when keytab exists 
(ActiveDirectory member) but rpcsec_gss_krb5 module is not loaded
Ignoring request to alter fixed versions of bug #832609 to the same values 
previously set
Bug #832609 [nfs-common] rpc-gssd.service: fails to start when keytab exists 
(ActiveDirectory member) but rpcsec_gss_krb5 module is not loaded
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 575079

[Debian Bug Tracking System]

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

> close 575079
Bug #575079 [nfs-common] nfs-common: nfs I/O never fails with udp and soft 
mount options in case of network failure
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#994077: marked as done (nfs-server.service fails (because autofs hasn't been started yet?))

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 10:02:06 +0200 (CEST)
with message-id <20240914080206.a76f4be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #994077,
regarding nfs-server.service fails (because autofs hasn't been started yet?)
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.)


-- 
994077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.3.4-6

After boot the nfs-server is not ready yet:

# systemctl status nfs-server
* nfs-server.service - NFS server and services
 Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Sat 2021-09-11 08:22:29 CEST; 
4min 50s ago
Process: 1295 ExecStartPre=/usr/sbin/exportfs -r (code=exited, 
status=1/FAILURE)
Process: 1377 ExecStopPost=/usr/sbin/exportfs -au (code=exited, 
status=0/SUCCESS)
Process: 1390 ExecStopPost=/usr/sbin/exportfs -f (code=exited, 
status=0/SUCCESS)
CPU: 2ms

Sep 11 08:22:29 cecil.afaics.de systemd[1]: Starting NFS server and services...
Sep 11 08:22:29 cecil.afaics.de exportfs[1295]: exportfs: Failed to stat 
/misc/data10: No such file or directory
Sep 11 08:22:29 cecil.afaics.de systemd[1]: nfs-server.service: Control process 
exited, code=exited, status=1/FAILURE
Sep 11 08:22:29 cecil.afaics.de systemd[1]: nfs-server.service: Failed with 
result 'exit-code'.
Sep 11 08:22:29 cecil.afaics.de systemd[1]: Stopped NFS server and services.

# stat /misc/data10
  File: /misc/data10
  Size: 36864   Blocks: 72 IO Block: 4096   directory
Device: 802h/2050d  Inode: 2   Links: 25
Access: (0755/drwxr-xr-x)  Uid: ( 1000/   harri)   Gid: ( 1000/   harri)
Access: 2020-04-20 13:17:15.195197814 +0200
Modify: 2021-09-07 23:25:46.250845749 +0200
Change: 2021-09-07 23:25:46.250845749 +0200
 Birth: 2019-03-17 07:00:08.0 +0100


Problem is, /misc/data10 (as all other disks in /misc) is mounted using autofs.
The autofs service succeeds at boot time. If I manually restart 
nfs-server.service,
it works as well.


Regards
Harri
--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Bug#890099: marked as done (nfs-server: fails to start if export path has intermediate symlinks)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:59:56 +0200 (CEST)
with message-id <20240914075956.36e4cbe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #890099,
regarding nfs-server: fails to start if export path has intermediate symlinks
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.)


-- 
890099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.3.4-2.1+b1
Severity: normal

I have recently changed my NFS setup so that one of the intermediate paths for 
the
exported filesystem is a symlink. With this setup, trying to start the system 
with

systemctl start nfs-server

fails, with `systemctl status nfs-server` reporting:

● nfs-server.service - NFS server and services  

 
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-02-10 19:06:15 CET; 14h ago
  Process: 27521 ExecStopPost=/usr/sbin/exportfs -f (code=exited, 
status=0/SUCCESS)
  Process: 27520 ExecStopPost=/usr/sbin/exportfs -au (code=exited, 
status=0/SUCCESS)
  Process: 27519 ExecStartPre=/usr/sbin/exportfs -r (code=exited, 
status=1/FAILURE)

Feb 10 19:06:15 labrador systemd[1]: Starting NFS server and services...
Feb 10 19:06:15 labrador exportfs[27519]: exportfs: Failed to stat 
///: No such file or directory
Feb 10 19:06:15 labrador exportfs[27519]: exportfs: Failed to stat 
///: No such file or directory
Feb 10 19:06:15 labrador systemd[1]: nfs-server.service: Control process 
exited, code=exited status=1
Feb 10 19:06:15 labrador systemd[1]: nfs-server.service: Failed with result 
'exit-code'.
Feb 10 19:06:15 labrador systemd[1]: Stopped NFS server and services.

journalctl -u nfs-server-.service -b has exactly those lines too.

Running all the appropriate daemons manually, including the sequence exportfs 
-f, exportfs -au, exportfs -r works correctly,
with the final export being /// as expected.


-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
133   tcp   2049  nfs
134   tcp   2049  nfs
1002273   tcp   2049
133   udp   2049  nfs
1002273   udp   2049
1000211   udp  49410  nlockmgr
1000213   udp  49410  nlockmgr
1000214   udp  49410  nlockmgr
1000211   tcp  38281  nlockmgr
1000213   tcp  38281  nlockmgr
1000214   tcp  38281  nlockmgr
151   udp  44790  mountd
151   tcp  36505  mountd
152   udp  58345  mountd
152   tcp  40191  mountd
153   udp  50245  mountd
153   tcp  39943  mountd
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
/// (rw,sync,no_root_squash,no_subtree_check) 
(rw,sync,no_root_squash,no_subtree_check) (ro,sync,root_squash,no_subtree_check)
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nfs-kernel-server depends on:
ii  init-system-helpers  1.51
ii  keyutils 1.5.9-9.2
ii  libblkid12.30.2-0.1
ii  libc62.26-2
ii  libcap2  1:2.25-1.2
ii  libsqlite3-0 3.21.0-1
ii  libtirpc10.2.5-1.2
ii  libwrap0 7.6.q-27
ii  lsb-base 9.20170808
ii  netbase  5.4
ii  nfs-common   1:1.3.4-2.1+b1
ii  ucf  3.0036

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debco

Bug#809392: marked as done (showmount not showing IPv6 clients)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 10:00:04 +0200 (CEST)
with message-id <20240914080004.94d2cbe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #809392,
regarding showmount not showing IPv6 clients
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.)


-- 
809392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.2.8-9
Severity: normal

Dear Maintainer,

showmount does not show IPv6 clients.

Steps to reproduce:

1.) umount an NFS share on a client
2.) run "exportfs -f ; exportfs -a" to flush and re-read the kernel
export table on the server
3.) mount an NFS share on a client
4.) invoke "showmount" or "showmount -a" on the server -> no clients are listed

I tried different showmount invocations (being done on the NFS server
itself):

# showmount 
Hosts on servername:
-> no further output

# showmount -a
All mount points on servername:
-> no further output

# showmount -a localhost
All mount points on localhost:
-> no further output

# showmount localhost
Hosts on localhost:
-> no further output

In the kernel export table, the clients with mounted shares are properly
listed:

# wc -l /proc/fs/nfsd/exports
27 /proc/fs/nfsd/exports

One example:

# grep "::166/128" /proc/fs/nfsd/exports
/s2/sw  
fd40:9dc7:b528:8::/64,fd40:9dc7:b528:8::166/128(rw,no_root_squash,sync,wdelay,uuid=8d45a057:f2b448b9:8c3d26e7:f3a00e68,sec=1)

At least from the kernel side everything is fine and the issue seems
somewhere within the nfs-common package.

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  57671  status
1000241   tcp  41467  status
1000111   udp948  rquotad
1000112   udp948  rquotad
1000111   tcp948  rquotad
1000112   tcp948  rquotad
132   tcp   2049  nfs
133   tcp   2049  nfs
134   tcp   2049  nfs
1002272   tcp   2049
1002273   tcp   2049
132   udp   2049  nfs
133   udp   2049  nfs
134   udp   2049  nfs
1002272   udp   2049
1002273   udp   2049
1000211   udp  57659  nlockmgr
1000213   udp  57659  nlockmgr
1000214   udp  57659  nlockmgr
1000211   tcp  33764  nlockmgr
1000213   tcp  33764  nlockmgr
1000214   tcp  33764  nlockmgr
151   udp  33773  mountd
151   tcp  53433  mountd
152   udp  33580  mountd
152   tcp  53509  mountd
153   udp  41063  mountd
153   tcp  45829  mountd
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-common depends on:
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59
ii  libc6   2.19-18+deb8u1
ii  libcap2 1:2.24-8
ii  libcomerr2  1.42.12-1.1
ii  libdevmapper1.02.1  2:1.02.90-2.2
ii  libevent-2.0-5  2.0.21-stable-2
ii  libgssapi-krb5-21.12.1+dfsg-19+deb8u1
ii  libk5crypto31.12.1+dfsg-19+deb8u1
ii  libkeyutils11.5.9-5+b1
ii  libkrb5-3   1.12.1+dfsg-19+deb8u1
ii  libmount1   2.25.2-6
ii  libnfsidmap20.25-5
ii  libtirpc1   0.2.5-1
ii  libwrap07.6.q-25
ii  lsb-base4.1+Debian13+nmu1
ii  rpcbind 0.2.1-6+deb8u1
ii  ucf 3.0030

Versions of packages nfs-common recommends:
ii  python  2.7.9-1

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

Versions of packages nfs-kernel-server depends on:
ii  libblkid1 2.25.2-6
ii  libc6 2.19-18+deb8u1
ii  libca

Bug#753732: marked as done (NFS sec=krb5 does not work with cross-realm)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:59:42 +0200 (CEST)
with message-id <20240914075942.3e721be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #753732,
regarding NFS sec=krb5 does not work with cross-realm
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.)


-- 
753732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: nfs-common
Version: 1.2.6-4

NFS with sec=krb5i or sec=krb5p using MIT Kerberos does not work when  
cross-realm authentication is used -- only when clients have an  
Kerberos ticket for the same realm. This happens consistently and in  
cases when cross-realm authentication does work with other services on  
the same machine, such as SSH.


To illustrate, I've included two sets of NFS debug output from both a  
client (daboia.dapadam.nl) and a server (cerastes.dapadam.nl): one set  
with a successful authentication and the other with a failure. The  
first set involves a user, jwinius, with an MIT Kerberos ticket from  
the same realm, DAPADAM.NL, that results in a successful authentication:


=== Begin === Success, client log output =
Jul  1 16:08:37 daboia rpc.gssd[1422]: handling gssd upcall  
(/var/lib/nfs/rpc_pipefs/nfs/clnt0)
Jul  1 16:08:37 daboia rpc.gssd[1422]: handle_gssd_upcall: 'mech=krb5  
uid=1 enctypes=18,17,16,23,3,1,2 '
Jul  1 16:08:37 daboia rpc.gssd[1422]: handling krb5 upcall  
(/var/lib/nfs/rpc_pipefs/nfs/clnt0)
Jul  1 16:08:37 daboia rpc.gssd[1422]: process_krb5_upcall: service is  
''
Jul  1 16:08:37 daboia rpc.gssd[1422]: getting credentials for client  
with uid 1 for server cerastes.dapadam.nl
Jul  1 16:08:37 daboia rpc.gssd[1422]: CC file  
'/tmp/krb5cc_0_8TcUINGCct' being considered, with preferred realm  
'DAPADAM.NL'
Jul  1 16:08:37 daboia rpc.gssd[1422]: CC file  
'/tmp/krb5cc_0_8TcUINGCct' owned by 0, not 1
Jul  1 16:08:37 daboia rpc.gssd[1422]: CC file  
'/tmp/krb5cc_machine_DAPADAM.NL' being considered, with preferred  
realm 'DAPADAM.NL'
Jul  1 16:08:37 daboia rpc.gssd[1422]: CC file  
'/tmp/krb5cc_machine_DAPADAM.NL' owned by 0, not 1
Jul  1 16:08:37 daboia rpc.gssd[1422]: CC file  
'/tmp/krb5cc_1_HFd9c1oOJy' being considered, with preferred realm  
'DAPADAM.NL'
Jul  1 16:08:37 daboia rpc.gssd[1422]: CC file  
'/tmp/krb5cc_1_HFd9c1oOJy'(jwin...@dapadam.nl) passed all checks  
and has mtime of 1404223701
Jul  1 16:08:37 daboia rpc.gssd[1422]: CC file '/tmp/krb5cc_0' being  
considered, with preferred realm 'DAPADAM.NL'
Jul  1 16:08:37 daboia rpc.gssd[1422]: CC file '/tmp/krb5cc_0' owned  
by 0, not 1
Jul  1 16:08:37 daboia rpc.gssd[1422]: using  
FILE:/tmp/krb5cc_1_HFd9c1oOJy as credentials cache for client with  
uid 1 for server cerastes.dapadam.nl
Jul  1 16:08:37 daboia rpc.gssd[1422]: using environment variable to  
select krb5 ccache FILE:/tmp/krb5cc_1_HFd9c1oOJy
Jul  1 16:08:37 daboia rpc.gssd[1422]: creating context using fsuid  
1 (save_uid 0)
Jul  1 16:08:37 daboia rpc.gssd[1422]: creating tcp client for server  
cerastes.dapadam.nl

Jul  1 16:08:37 daboia rpc.gssd[1422]: DEBUG: port already set to 2049
Jul  1 16:08:37 daboia rpc.gssd[1422]: creating context with server  
n...@cerastes.dapadam.nl
Jul  1 16:08:37 daboia rpc.gssd[1422]: DEBUG: serialize_krb5_ctx:  
lucid version!

Jul  1 16:08:37 daboia rpc.gssd[1422]: prepare_krb5_rfc4121_buffer: protocol 1
Jul  1 16:08:37 daboia rpc.gssd[1422]: prepare_krb5_rfc4121_buffer:  
serializing key with enctype 18 and size 32

Jul  1 16:08:37 daboia rpc.gssd[1422]: doing downcall
Jul  1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_uid: calling  
nsswitch->name_to_uid
Jul  1 16:08:37 daboia rpc.idmapd[1417]: nss_getpwnam: name  
'jwin...@dapadam.nl' domain 'dapadam.nl': resulting localname 'jwinius'
Jul  1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_uid:  
nsswitch->name_to_uid returned 0
Jul  1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_uid: final  
return value is 0
Jul  1 16:08:37 daboia rpc.idmapd[1417]: Client 0: (user) name  
"jwin...@dapadam.nl" -> id "1"
Jul  1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_gid: calling  
nsswitch->name_to_gid
Jul  1 16:08:37 daboia rpc.idmapd[1417]: nfs4_name_to_gid:  
nsswitch->name_to_gid returned 0
Jul  1 16:08:37 daboia rpc.

Bug#616077: marked as done ("AUTH_GSS upcall timed out" in export with kerberos)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 10:00:45 +0200 (CEST)
with message-id <20240914080045.096cbbe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #616077,
regarding "AUTH_GSS upcall timed out" in export with kerberos
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.)


-- 
616077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server

Version: 1.2.2-4

Short description: kerberized nfs4 exports do work, but nevertheless
there are continuous kernel messages: "RPC: AUTH_GSS upcall timed
out."

Procedure to trigger the bug:

1. On the server machine, /etc/init.d/nfs-common and
/etc/init.d/nfs-kernel-server have already been run with argument
start.

2. On the client machine, the nfs-exported directories are not yet
mounted and /etc/init.d/nfs-common has been called with argument stop.

3. On the client machine, call /etc/init.d/nfs-common with argument
start.

4. On the client machine, mount nfs-exported directories.

As yet, nothing wrong happens.

5. From the server machine, log into the client machine with ssh as a
non-root user, thus forwarding kerberos credentials to the client
machine: the nfs-exported directories are normally accessible on the
client machine (according to the rights of this user).

After this, the kernel on the server machine logs this to
/var/log/messages every 30 seconds (too much output for the log
file!):

Mar  2 09:44:27 olaf kernel: [60989.928631] RPC: AUTH_GSS upcall timed out.
Mar  2 09:44:27 olaf kernel: [60989.928632] Please check user daemon is running.

But /usr/sbin/rpc.svcgssd is still running on the server, and the user
can still access the nfs-exported directories on the client.

Note that the kernel messages every 30 seconds continue even after
user logout from the client, unmounting all nfs-exported directories
on the client, stopping /etc/init.d/nfs-common on the client, and
stopping /etc/init.d/nfs-kernel-server and /etc/init.d/nfs-common on
the server. Stopping /etc/init.d/nfs-kernel-server and
/etc/init.d/nfs-common and starting it again (in opposite order) gives
these kernel messages:

Mar  2 09:49:15 olaf kernel: [61278.055487] svc: failed to register lockdv1 RPC 
service (errno 97).
Mar  2 09:49:15 olaf kernel: [61278.056254] NFSD: Using /var/lib/nfs/v4recovery 
as the NFSv4 state recovery directory
Mar  2 09:49:15 olaf kernel: [61278.056268] NFSD: starting 90-second grace 
period

(but these messages are there in each nfs-kernel-server start), and
then the above AUTH_GSS messages every 30 seconds continue. Only a
server reboot helps. (With a newer kernel on the server ---
linux-image-2.6.37-1-amd64 of sid, the messages do not seem to
continue, but are also present in the first place).

After downgrading nfs-common and nfs-kernel-server to the lenny
versions (1.1.2-6), this bug does not occur.

I would test nfs-utils-1.2.3 if it were available as debian packages
in sid, but hesitate to mess around and install it from source.

Other configuration:

- Debian squeeze amd64 system, linux-image-2.6.32-5-amd64 both on
server and client machine.

- /etc/exports on server:

/export gss/krb5p(rw,sync,fsid=0,no_subtree_check)
/export/nfs gss/krb5p(rw,sync,nohide,no_subtree_check)
/export/home gss/krb5p(rw,sync,nohide,no_subtree_check)
/export/mail gss/krb5p(rw,sync,nohide,no_subtree_check)

- /etc/fstab on client:

...
server.machine:/nfs/usr/nfsnfs4sec=krb5p   0  0
server.machine:/home   /home   nfs4sec=krb5p   0   0
server.machine:/mail   /var/mail   nfs4sec=krb5p   0  0

- /etc/default/nfs-common on server:


# If you do not set values for the NEED_ options, they will be attempted
# autodetected; this should be sufficient for most people. Valid alternatives
# for the NEED_ options are "yes" and "no".

# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=

# Options for rpc.statd.
#   Should rpc.statd listen on a specific port? This is especially useful
#   when you have a port-based firewall. To use a fixed port, set this
#   this variable to a statd argument like: "--port 4000 --outgoing-port 4001".
#   For more information, see rpc.statd(8) or 
http://wiki.debian.org/?SecuringNFS
STATDOPTS=

# Do you want to start the idmapd daemon? It is only needed for NFSv4.
NEED_IDMAPD=

# Do you want to start the gssd daemon? It is required for Kerberos mounts.
NEED_GSSD=

- /etc/defa

Bug#1030229: marked as done (nfs-common: Machines that mount an NFS drive hang)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 10:02:25 +0200 (CEST)
with message-id <20240914080225.6a880be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1030229,
regarding nfs-common: Machines that mount an NFS drive hang
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.)


-- 
1030229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.3.4-6
Severity: normal

Dear Maintainer,

Error: NFS: __nfs4_reclaim_open_state: Reclaim lock failed!

* What led to the situation?
  Migrate NFS server from debian 9 to debian 11.
* What exactly did you do (or didn't do) that was effective (or ineffective)?
  Apparently everything works correctly with few users, when I increase to more 
than 20 or 30 users the blockages begin in the machines.
* What was the result of this action?
 Error on clients: NFS: __nfs4_reclaim_open_state: Reclaim lock failed!
 The clients are blocked and the client machines cannot be used.
* What results did you expect instead?
 That the server will work without problems with the more than 50 users.

*** Cliente ***

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
doc-ajt:/srv/samba  /usr/local/samba/doc-ajtnfs 
auto,soft,nfsvers=4.0   0   0
#home-ajt:/srv/home-bullseye/home   nfs 
auto,soft,nfsvers=4.0   0   0
home-ajt:/srv/home-bullseye /home   nfs 
auto,soft   0   0
bullseye-ajt:/srv/bullseye  /usr/local/bullseye nfs 
auto,soft,nfsvers=4.0   0   0
si-ajt:/srv/si  /usr/local/si   nfs 
auto,soft,nfsvers=4.0   0   0
-- /proc/mounts --
doc-ajt:/srv/samba /usr/local/samba/doc-ajt nfs4 
rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=172.20.11.39,local_lock=none,addr=172.20.10.126
 0 0
doc-ajt:/srv/si /usr/local/si nfs4 
rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=172.20.11.39,local_lock=none,addr=172.20.10.126
 0 0
doc-ajt:/srv/bullseye /usr/local/bullseye nfs4 
rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=172.20.11.39,local_lock=none,addr=172.20.10.126
 0 0
home-ajt:/srv/home-bullseye /home nfs4 
rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=172.20.11.39,local_lock=none,addr=172.20.10.122
 0 0

-- System Information:
Debian Release: 11.6
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-0.deb11.4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to ca_ES.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 nfs-common depends on:
ii  adduser 3.118
ii  keyutils1.6.1-2
ii  libc6   2.34-8
ii  libcap2 1:2.44-1
ii  libcom-err2 1.46.2-2
ii  libdevmapper1.02.1  2:1.02.175-2.1
ii  libevent-2.1-7  2.1.12-stable-1
ii  libgssapi-krb5-21.18.3-6+deb11u3
ii  libkeyutils11.6.1-2
ii  libkrb5-3   1.18.3-6+deb11u3
ii  libmount1   2.36.1-8+deb11u1
ii  libnfsidmap20.25-6
ii  libtirpc3   1.3.1-1+deb11u1
ii  libwrap07.6.q-31
ii  lsb-base11.1.0
ii  rpcbind 1.2.5-9
ii  ucf 3.0043

Versions of packages nfs-common recommends:
ii  python3  3.9.2-3

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

-- no debconf information

root@et089601:/home/mgual# dmesg -T | tail
[dc. de febr.  1 08:46:44 2023]

Bug#504512: marked as done (nfs-common: expired kerberos credentials cause significant syslog spam)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 10:00:30 +0200 (CEST)
with message-id <20240914080030.e28bbbe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #504512,
regarding nfs-common: expired kerberos credentials cause significant syslog spam
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.)


-- 
504512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.1.3-2
Severity: normal

When the Kerberos credentials expire, and there are Kerberised-NFS mounts still 
present, rpc.gssd logs heavily:

Oct 8 17:05:18 swan rpc.gssd[4747]: WARNING: Failed to create krb5 context for 
user with uid 85153 for server *REDACTED*
Oct 8 17:05:18 swan rpc.gssd[4747]: ERROR: GSS-API: error in 
gss_acquire_cred(): Unspecified GSS failure. Minor code may provide more 
information - No credentials cache found
Oct 8 17:05:18 swan rpc.gssd[4747]: WARNING: Failed to create krb5 context for 
user with uid 85153 for server *REDACTED*
Oct 8 17:05:18 swan rpc.gssd[4747]: ERROR: GSS-API: error in 
gss_acquire_cred(): Unspecified GSS failure. Minor code may provide more 
information - No credentials cache found
Oct 8 17:05:18 swan rpc.gssd[4747]: WARNING: Failed to create krb5 context for 
user with uid 85153 for server *REDACTED*
Oct 8 17:05:18 swan rpc.gssd[4747]: ERROR: GSS-API: error in 
gss_acquire_cred(): Unspecified GSS failure. Minor code may provide more 
information - No credentials cache found
Oct 8 17:05:18 swan rpc.gssd[4747]: WARNING: Failed to create krb5 context for 
user with uid 85153 for server *REDACTED*
Oct 8 17:05:18 swan rpc.gssd[4747]: ERROR: GSS-API: error in 
gss_acquire_cred(): Unspecified GSS failure. Minor code may provide more 
information - No credentials cache found
Oct 8 17:05:18 swan rpc.gssd[4747]: WARNING: Failed to create krb5 context for 
user with uid 85153 for server *REDACTED*
Oct 8 17:05:18 swan rpc.gssd[4747]: ERROR: GSS-API: error in 
gss_acquire_cred(): Unspecified GSS failure. Minor code may provide more 
information - No credentials cache found
Oct 8 17:05:18 swan rpc.gssd[4747]: WARNING: Failed to create krb5 context for 
user with uid 85153 for server *REDACTED*
Oct 8 17:05:18 swan rpc.gssd[4747]: ERROR: GSS-API: error in 
gss_acquire_cred(): Unspecified GSS failure. Minor code may provide more 
information - No credentials cache found
Oct 8 17:05:18 swan rpc.gssd[4747]: WARNING: Failed to create krb5 context for 
user with uid 85153 for server *REDACTED*
Oct 8 17:05:18 swan rpc.gssd[4747]: ERROR: GSS-API: error in 
gss_acquire_cred(): Unspecified GSS failure. Minor code may provide more 
information - No credentials cache found

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages nfs-common depends on:
ii  add 3.102Add and remove users and groups
ii  lib 2.3.6.ds1-13etch7GNU C Library: Shared libraries
ii  lib 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 common error description library
ii  lib 1.1a-1   An asynchronous event notification
ii  lib 0.10-4   A mechanism-switch gssapi library
ii  lib 1.4.4-7etch6 MIT Kerberos runtime libraries
ii  lib 0.18-0   An nfs idmapping library
ii  lib 0.14-2etch3  allows secure rpc communication us
ii  lib 7.6.dbs-13   Wietse Venema's TCP wrappers libra
ii  lsb 3.1-23.2etch1Linux Standard Base 3.1 init scrip
ii  net 4.29 Basic TCP/IP networking system
ii  por 5-26 The RPC portmapper
ii  ucf 2.0020   Update Configuration File: preserv

nfs-common recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Processed: closing 687781

[Debian Bug Tracking System]

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

> close 687781
Bug #687781 [nfs-kernel-server] use fixed, IANA-registered port for rpc.mountd 
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: severity of 952412 is wishlist

[Debian Bug Tracking System]

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

> severity 952412 wishlist
Bug #952412 [nfs-common] Please provide mount.nfs4 and umount.nfs4 without 
requiring rpcbind and similar
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

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

Processed: notfixed 728255 in 1.3.4-2, closing 728255

[Debian Bug Tracking System]

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

> notfixed 728255 1.3.4-2
Bug #728255 [nfs-common] rpc.gssd: Cannot determine realm for numeric host 
address
There is no source info for the package 'nfs-common' at version '1.3.4-2' with 
architecture ''
Unable to make a source version for version '1.3.4-2'
No longer marked as fixed in versions 1.3.4-2.
> close 728255 1:1.3.4-2
Bug #728255 [nfs-common] rpc.gssd: Cannot determine realm for numeric host 
address
Ignoring request to alter fixed versions of bug #728255 to the same values 
previously set
Bug #728255 [nfs-common] rpc.gssd: Cannot determine realm for numeric host 
address
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#734322: marked as done (nfs-common: utils/mount/nfsumount.c incorrectly rpc pinging remote rpc.mountd on NFSv4 umounts)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:56:38 +0200 (CEST)
with message-id <20240914075638.4a7a6be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #734322,
regarding nfs-common: utils/mount/nfsumount.c incorrectly rpc pinging remote 
rpc.mountd on NFSv4 umounts
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.)


-- 
734322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.2.6-4
Severity: normal

Dear Maintainer,

I ran into a NFS umount bug, verified and patched in Redhat as per [0].

In my example setup, I have a Wheezy NFS server, using NFSv4 exports, to
a Wheezy client.

When I umount a mount, I receive precisely the same error line on the
server as in [0], e.g.:
Nov 14 09:35:16 saga mountd[3128]: refused unmount request from
cynosure.cora.nwra.com for /data1 (/): not exported

Precisely just as in that case, a RPC packet (NFSv2/v3) is incorrectly sent
from the client to the server.

My export options on the server are e.g.:
/exports/  
x.x.x.x(fsid=0,insecure,no_subtree_check,no_root_squash,crossmnt,rw)
[...]
/exports/foo/bar   
x.x.x.x(fsid=0,insecure,no_subtree_check,no_root_squash,crossmnt,rw)

My mount options, in /etc/fstab, on the client are:
x.x.x.x.:/foo/bar /mnt/barnfs4  ro,bg,soft,intr,_netdev,auto 0 2


In [0] (comment 7) there is a proposed patch for RH's nfs-utils.
Debian unstable nfs-common (1:1.2.8-4) lacks the patch, and I'd like to
leave it to professionals to verify whether the small changes of the RH
patch can be used for Debian's nfs-common.

Best regards,
Martin

[0] https://bugzilla.redhat.com/show_bug.cgi?id=215553#c7

-- Package-specific info:
-- rpcinfo --
   program vers proto   port
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  44435  status
1000241   tcp  41798  status
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup

/etc/fstab retained.
/proc/mounts retained.

-- System Information:
Debian Release: 7.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nfs-common depends on:
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-41+deb7u1
ii  libc6   2.13-38
ii  libcap2 1:2.22-1.2
ii  libcomerr2  1.42.5-1.1
ii  libdevmapper1.02.1  2:1.02.74-8
ii  libevent-2.0-5  2.0.19-stable-3
ii  libgssglue1 0.4-2
ii  libk5crypto31.10.1+dfsg-5+deb7u1
ii  libkeyutils11.5.5-3
ii  libkrb5-3   1.10.1+dfsg-5+deb7u1
ii  libmount1   2.20.1-5.3
ii  libnfsidmap20.25-4
ii  libtirpc1   0.2.2-5
ii  libwrap07.6.q-24
ii  lsb-base4.1+Debian8+deb7u1
ii  rpcbind 0.2.0-8
ii  ucf 3.0025+nmu3

Versions of packages nfs-common recommends:
ii  python  2.7.3-4+deb7u1

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Processed: closing 1050446

[Debian Bug Tracking System]

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

> close 1050446
Bug #1050446 [nfs-common,rdma-core] nfs over rdma between debian12 client and 
debian11 server can cause data corruption
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#860264: marked as done (nfs-kernel-server: NFS starts before DNS works, "exportfs: Failed to resolve ...")

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:51:51 +0200 (CEST)
with message-id <20240914075151.983eabe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #860264,
regarding nfs-kernel-server: NFS starts before DNS works, "exportfs: Failed to 
resolve ..."
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.)


-- 
860264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.3.4-2.1
Severity: normal

The NFS server starts before DNS is working, causing exportfs to fail:

wooledg:~$ sudo systemctl status nfs-kernel-server
[sudo] password for wooledg:
* nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor prese
  Drop-In: /etc/systemd/system/nfs-server.service.d
   `-waitlonger.conf
   Active: active (exited) since Wed 2017-04-12 16:39:29 EDT; 6min ago
 Main PID: 513 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
   CGroup: /system.slice/nfs-server.service

Apr 12 16:39:29 wooledg systemd[1]: Starting NFS server and services...
Apr 12 16:39:29 wooledg exportfs[510]: exportfs: Failed to resolve ebase
Apr 12 16:39:29 wooledg exportfs[510]: exportfs: Failed to resolve ebase
Apr 12 16:39:29 wooledg exportfs[510]: exportfs: Failed to resolve ebase-fla
Apr 12 16:39:29 wooledg systemd[1]: Started NFS server and services.

I attempted to work around this by creating a drop-in unit thing:

wooledg:~$ cat /etc/systemd/system/nfs-server.service.d/waitlonger.conf
[Unit]
Wants= network-online.target
After= network-online.target

But this didn't help.  With or without the drop-in thing, the exportfs
command fails at boot time.  If I login and manually run "exportfs -a"
or restart nfs-kernel-server (or nfs-server), then it's fine.

For now, I'm willing to entertain any kludge workarounds.  This is just
a desktop workstation.  But anyone experiencing this on a server may
want a more robust fix.

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
151   udp  40904  mountd
151   tcp  50855  mountd
152   udp  53578  mountd
152   tcp  40253  mountd
153   udp  33327  mountd
153   tcp  47879  mountd
133   tcp   2049  nfs
134   tcp   2049  nfs
1002273   tcp   2049
133   udp   2049  nfs
134   udp   2049  nfs
1002273   udp   2049
1000211   udp  56937  nlockmgr
1000213   udp  56937  nlockmgr
1000214   udp  56937  nlockmgr
1000211   tcp  41093  nlockmgr
1000213   tcp  41093  nlockmgr
1000214   tcp  41093  nlockmgr
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
/home   ebase(ro,sync,no_subtree_check) ebase-fla(ro,sync,no_subtree_check)
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs
/home   
ebase.eeg.ccf.org(ro,root_squash,sync,wdelay,no_subtree_check,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=1)
/home   
ebase-fla.eeg.ccf.org(ro,root_squash,sync,wdelay,no_subtree_check,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=1)
/   
ebase.eeg.ccf.org(ro,root_squash,sync,no_wdelay,no_subtree_check,v4root,fsid=0,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=390003:390004:390005:1)
/   
ebase-fla.eeg.ccf.org(ro,root_squash,sync,no_wdelay,no_subtree_check,v4root,fsid=0,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=390003:390004:390005:1)

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-kernel-server depends on:
ii  init-system-helpers  1.47
ii  keyutils 1.5.9-9
ii  libblkid12.29.2-1
ii  libc62.24-9
ii  libcap2  1:2.25-1
ii  libsqlite3-0 3.16.2-3
ii  libtirpc10.2.5-1.1
ii  libwrap0

Bug#814918: marked as done (nfs-common: krb5 mounts not working at boot time)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:51:27 +0200 (CEST)
with message-id <20240914075127.135c0be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #814918,
regarding nfs-common: krb5 mounts not working at boot time
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.)


-- 
814918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.2.8-9
Severity: important

Out of the box on a fresh stretch install nfs mounts fail because portmap is
unavailable. After adding fix from 806336 (DefaultDependencies=no) that problem
is fixed and mounts can be performed manually, but the mounts still fail at
boot time because the system doesn't start rpc.gssd until after attemping the
nfs mounts. There should be some ordering to ensure that the mounts aren't
attempted until after the nfs-common startup is complete.

Mike Stone

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  39314  status
1000241   tcp  59339  status
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
nfsserver.mathom.us:/home   /home   nfs sec=krb50   0
nfsserver.mathom.us:/scratch/scratchnfs sec=krb50   0
-- /proc/mounts --
nfsserver.mathom.us:/home /home nfs4 
rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=[ip],local_lock=none,addr=[ip]
 0 0
nfsserver.mathom.us:/scratch /scratch nfs4 
rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=[ip],local_lock=none,addr=[ip]
 0 0

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-common depends on:
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59.2
ii  libc6   2.21-7
ii  libcap2 1:2.24-12
ii  libcomerr2  1.42.13-1
ii  libdevmapper1.02.1  2:1.02.115-2
ii  libevent-2.0-5  2.0.21-stable-2+b1
ii  libgssapi-krb5-21.13.2+dfsg-4
ii  libk5crypto31.13.2+dfsg-4
ii  libkeyutils11.5.9-8
ii  libkrb5-3   1.13.2+dfsg-4
ii  libmount1   2.27.1-3
ii  libnfsidmap20.25-5
ii  libtirpc1   0.2.5-1
ii  libwrap07.6.q-25
ii  lsb-base9.20160110
ii  rpcbind 0.2.3-0.2
ii  ucf 3.0033

Versions of packages nfs-common recommends:
ii  python  2.7.11-1

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

-- Configuration Files:
/etc/default/nfs-common changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Bug#711421: marked as done (nfs-common: NFS4 mount with kerberos hangs forewer)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:52:32 +0200 (CEST)
with message-id <20240914075232.21b16be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #711421,
regarding nfs-common: NFS4 mount with kerberos hangs forewer
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.)


-- 
711421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: nfs-common
Version: 1:1.2.8-4
Severity: normal

Dear Maintainer,
After last update that should solve 705507 the rpc.gssd no longer
crashes, but mounting NFS share hangs forewer with syslog messages:
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
rpc.gssd[2059]: ERROR: GSS-API: error in gss_free_lucid_sec_context():
GSS_S_NO_CONTEXT (No context has been established) - Unknown error
rpc.gssd[2059]: WARN: failed to free lucid sec context

followed by:

nfs: server servername not responding, timed out

I use NFS4 with sec=krb5. Everything worked fine until Sid unfreeze,
after which I was hit by 705507.


-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  32765  status
1000241   tcp  32765  status
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS="--port 32765 --outgoing-port 32766"
NEED_IDMAPD=yes
NEED_GSSD=yes
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (650, 'unstable'), (10, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nfs-common depends on:
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-41
ii  libc6   2.17-5
ii  libcap2 1:2.22-1.2
ii  libcomerr2  1.42.5-1.1
ii  libdevmapper1.02.1  2:1.02.77-1
ii  libevent-2.0-5  2.0.21-stable-1
ii  libgssglue1 0.4-2
ii  libk5crypto31.10.1+dfsg-5
ii  libkeyutils11.5.5-7
ii  libkrb5-3   1.10.1+dfsg-5
ii  libmount1   2.20.1-5.4
ii  libnfsidmap20.25-5
ii  libtirpc1   0.2.2-5
ii  libwrap07.6.q-24
ii  lsb-base4.1+Debian12
ii  rpcbind 0.2.0-8
ii  ucf 3.0027

Versions of packages nfs-common recommends:
ii  python  2.7.3-5

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Bug#648155: marked as done (nfs-common: nfs mount hangs when kerberos ticket expires. Squeeze used to renew.)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:51:18 +0200 (CEST)
with message-id <20240914075118.7bdf2be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #648155,
regarding nfs-common: nfs mount hangs when kerberos ticket expires. Squeeze 
used to renew.
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.)


-- 
648155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common

Version: 1:1.2.5-2
Severity: normal

Dear Maintainer,

We use krb5 nfs4 for mounting our home directories.

On squeeze this worked well.

On a sid/wheezy system the nfs4 mount hangs when the kerberos ticket expires
(but is still renewable).

In the syslog on the client we see:

[59013.624087] nfs4_warn_keyexpired: 5427 callbacks suppressed
[59013.624093] Error: state manager encountered RPCSEC_GSS session expired 
against NFSv4 server olympic.calvaedi.com.
[59013.625000] Error: state manager encountered RPCSEC_GSS session expired 
against NFSv4 server olympic.calvaedi.com.
[59013.625870] Error: state manager encountered RPCSEC_GSS session expired 
against NFSv4 server olympic.calvaedi.com.
[59013.626759] Error: state manager encountered RPCSEC_GSS session expired 
against NFSv4 server olympic.calvaedi.com.



-- Package-specific info:
-- rpcinfo --
   program vers proto   port
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  55111  status
1000241   tcp  34799  status
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=yes
NEED_GSSD=yes
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = calvaedi.com
Local-Realm = CALVAEDI.COM
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
olympic:/local  /usr/local  nfs4sec=krb50   3
/test   /srv/nfs4/test  nonebind0   0
-- /proc/mounts --
/dev/disk/by-uuid/0934e0d8-0329-492c-a20d-48387a634479 /srv/nfs4/test ext3 
rw,relatime,errors=remount-ro,commit=5,barrier=0,data=ordered 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
olympic.calvaedi.com:/home/john /home/john nfs4 
rw,relatime,vers=4,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=192.168.6.99,minorversion=0,local_lock=none,addr=192.168.6.67
 0 0
olympic:/local/ /usr/local nfs4 
rw,relatime,vers=4,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=192.168.6.99,minorversion=0,local_lock=none,addr=192.168.6.67
 0 0

-- System Information:
Debian Release: wheezy/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nfs-common depends on:
ii  adduser 3.113
ii  initscripts 2.88dsf-13.13
ii  libc6   2.13-21  
ii  libcap2 1:2.22-1 
ii  libcomerr2  1.42~WIP-2011-10-16-1
ii  libdevmapper1.02.1  2:1.02.67-1  
ii  libevent-1.4-2  1.4.14b-stable-1 
ii  libgssapi-krb5-21.9.1+dfsg-3 
ii  libgssglue1 0.3-3.1  
ii  libk5crypto31.9.1+dfsg-3 
ii  libkeyutils11.5.2-2  
ii  libkrb5-3   1.9.1+dfsg-3 
ii  libnfsidmap20.24-1   
ii  libtirpc1   0.2.2-5  
ii  libwrap07.6.q-21 
ii  lsb-base3.2-28   
ii  rpcbind 0.2.0-6  
ii  ucf 3.0025+nmu2  

Versions of packages nfs-common recommends:
ii  python  2.7.2-9

nfs-common suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian

Bug#753407: marked as done (exportfs -r does not reexport shares for hosts with changed IPs)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:50:45 +0200 (CEST)
with message-id <20240914075045.ec444be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #753407,
regarding exportfs -r does not reexport shares for hosts with changed IPs
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.)


-- 
753407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.2.6-4

I have always been irritated when one of my computers changes IP address
and automount stops working. It always turns out that I don't have access
to the shares on the server. Even when I run exportfs -r or exportfs -a on
the server, I still can't mount the NFS shares on the computer that changed
IP address. The only way I can mount the NFS shares again is to remove the
host name from /etc/exports, run exportfs, put the host name back in
/etc/exports and then run exportfs once again.

Best regards,
Atanas
--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Processed: closing 857043

[Debian Bug Tracking System]

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

> close 857043
Bug #857043 [nfs-common] nfs-common: Can nfsstat be made to show timeouts per 
mount point or globally for the machine?
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#855051: marked as done (nfs-common: wrong shutdown sequence of wifi then nfs leaves nfs mounts hanging)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:45:57 +0200 (CEST)
with message-id <20240914074557.1afd3be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #855051,
regarding nfs-common: wrong shutdown sequence of wifi then nfs leaves nfs 
mounts hanging
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.)


-- 
855051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.3.4-2
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I use autofs to mount NFS

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I've noticed that when I shutdown, my wifi often goes down before the 
NFS volume is unmounted. This leads to a hang in the shutdown. I can 
provide journalctl logs if that would help.

   * What was the outcome of this action?

I usually get frustrated, search the web for work-arounds, and file bug 
reports. I've found some reports of this issue in various places. I 
wonder if there is already a debian bug to track this issue or, maybe, a 
fix is already known?

   * What outcome did you expect instead?

I expected a very rapid shutdown.

*** End of the template - remove these template lines ***


-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-common depends on:
ii  adduser  3.115
ii  init-system-helpers  1.47
ii  keyutils 1.5.9-9
ii  libc62.24-9
ii  libcap2  1:2.25-1
ii  libcomerr2   1.43.4-2
ii  libdevmapper1.02.1   2:1.02.137-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libgssapi-krb5-2 1.15-1
ii  libk5crypto3 1.15-1
ii  libkeyutils1 1.5.9-9
ii  libkrb5-31.15-1
ii  libmount12.29.1-1
ii  libnfsidmap2 0.25-5.1
ii  libtirpc10.2.5-1.1
ii  libwrap0 7.6.q-26
ii  lsb-base 9.20161125
ii  rpcbind  0.2.3-0.5
ii  ucf  3.0036

Versions of packages nfs-common recommends:
ii  python  2.7.13-2

Versions of packages nfs-common suggests:
pn  open-iscsi  
pn  watchdog

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Processed: closing 596767

[Debian Bug Tracking System]

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

> close 596767
Bug #596767 [nfs-kernel-server] nfs-kernel-server does not check the ucf 
registry for conflicting package, registrations.
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#601550: marked as done ([nfs-kernel-server] Root is always squashed when using sec=gss/krb5)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:44:32 +0200 (CEST)
with message-id <20240914074432.937bfbe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #601550,
regarding [nfs-kernel-server] Root is always squashed when using sec=gss/krb5
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.)


-- 
601550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.1.2-6lenny2
Severity: normal

--- Please enter the report below this line. ---
I have a NFSv4 server exports configured as follows:
/export   
gss/krb5(rw,fsid=0,insecure,no_root_squash,no_subtree_check,async)
/export/users 
gss/krb5(rw,nohide,insecure,no_root_squash,no_subtree_check,async)

On the other side I have clients with autofs configration like:
*   -fstype=nfs4,rw,soft,intr,bg,nosuid,nodev,sec=krb5,port=2049,proto=tcp  
nfs.mydomain.cz:/users/&

Everythink works great for regular users but when root is always squashed even 
when I set no_root_squash. I tried a configuration without kerberos and it 
worked as expected (I just removed gss/krb5 and sec=krb5 from configurations). 
Using kerberos root is always mapped to nobody:nogroup. Output from idmapd:

root@server# rpc.idmapd -c /etc/idmapd.conf -f -vvv
rpc.idmapd: libnfsidmap: using domain: localdomain

rpc.idmapd: libnfsidmap: using translation method: nsswitch

rpc.idmapd: Expiration time is 600 seconds.
rpc.idmapd: Opened /proc/net/rpc/nfs4.nametoid/channel
rpc.idmapd: Opened /proc/net/rpc/nfs4.idtoname/channel
rpc.idmapd: nfsdcb: authbuf=gss/krb5 authtype=user
rpc.idmapd:  Server: (user) id "0" -> name "root@localdomain"
rpc.idmapd: nfsdcb: authbuf=gss/krb5 authtype=group
rpc.idmapd:  Server: (group) id "0" -> name "root@localdomain"
rpc.idmapd: nfsdcb: authbuf=gss/krb5 authtype=user
rpc.idmapd:  Server: (user) id "2000" -> name "ares@localdomain"
rpc.idmapd: nfsdcb: authbuf=gss/krb5 authtype=group
rpc.idmapd:  Server: (group) id "2000" -> name "ares@localdomain"

--- System information. ---
Debian Release: 5.0.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) (ignored: 
LC_ALL set to cs_CZ.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages nfs-kernel-server depends on:
ii  libblkid1   1.41.3-1 block device id library
ii  libc6   2.7-18lenny6 GNU C Library: Shared libraries
ii  libcomerr2  1.41.3-1 common error description library
ii  libgssglue1 0.1-2mechanism-switch gssapi library
ii  libkrb531.6.dfsg.4~beta1-5lenny4 MIT Kerberos runtime libraries
ii  libnfsidmap20.20-1   An nfs idmapping library
ii  librpcsecgss3   0.18-1   allows secure rpc communication 
us
ii  libwrap07.6.q-16 Wietse Venema's TCP wrappers 
libra
ii  lsb-base3.2-20   Linux Standard Base 3.2 init 
scrip
ii  nfs-common  1:1.1.2-6lenny2  NFS support files common to client
ii  ucf 3.0016   Update Configuration File: preserv

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.






--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Bug#949577: marked as done (nfs-kernel-server: Unable to see sub-mounted filesystems with nohide set)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:41:02 +0200 (CEST)
with message-id <20240914074102.05857be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #949577,
regarding nfs-kernel-server: Unable to see sub-mounted filesystems with nohide 
set
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.)


-- 
949577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: nfs-kernel-server
Version: 1:1.3.4-2.5
Severity: normal

Dear Maintainer,

We use NFSv3 to mount /home on our lab machines. The mount is a ZFS
filesystem with snapshot visibility enabled (this makes
/home/.zfs/snapshot be visibile to users so that they can restore files
if needed). We are using standard /etc/exports, and the ZFS sharenfs
option is disabled.

Since the upgrade to Buster from Stretch, we are unable to view the
contents of snapshots under .zfs/snapshot/, but can
accurately see the list of snapshots in .zfs/snapshot. Each ZFS snapshot
is a separate file system, mounted under the snapshot name in
.zfs/snapshot. The nohide option has no effect on whether we can see them
or not.

The /etc/exports below is a snippet of the file, but represents the
base case where we are encountering this issue. I am not sure if it is a
bug in NFS, ZFS or a user issue.

Thanks
Kyle

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
151   udp  55442  mountd
151   tcp  39107  mountd
152   udp  34059  mountd
152   tcp  56283  mountd
153   udp  38252  mountd
153   tcp  46465  mountd
133   tcp   2049  nfs
134   tcp   2049  nfs
1002273   tcp   2049
133   udp   2049  nfs
1002273   udp   2049
1000211   udp  58819  nlockmgr
1000213   udp  58819  nlockmgr
1000214   udp  58819  nlockmgr
1000211   tcp  37101  nlockmgr
1000213   tcp  37101  nlockmgr
1000214   tcp  37101  nlockmgr
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
[...]
# ssh.aims.ac.za (old and new)_
/export10.1.29.6(rw,fsid=0,insecure,no_subtree_check,async)
/export/home.aims10.1.29.6(rw,nohide,insecure,no_subtree_check,async)
[...]
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_ZA:en (charmap=UTF-8)

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nfs-kernel-server depends on:
ii  keyutils  1.6-6
ii  libblkid1 2.34-0.1
ii  libc6 2.29-9
ii  libcap2   1:2.27-1
ii  libsqlite3-0  3.30.1+fossil191229-1
ii  libtirpc3 1.2.5-1
ii  libwrap0  7.6.q-30
ii  lsb-base  11.1.0
ii  netbase   6.0
ii  nfs-common1:1.3.4-2.5+b1
ii  ucf   3.0038+nmu1

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Bug#1006518: marked as done (nfs-common: mount nfsv4 hangs)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:42:09 +0200 (CEST)
with message-id <20240914074209.5f055be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1006518,
regarding nfs-common: mount nfsv4 hangs
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.)


-- 
1006518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:2.6.1-1
Severity: important

After nfs-common and libnfsidmap update to version
ii  libnfsidmap1:amd64 1:2.6.1-1 amd64  
  NFS idmapping library
ii  nfs-common 1:2.6.1-1 amd64  
  NFS support files common to client and server

mounting nfs v4 hangs, no visible output in dmesg, switching to vers=3 works 
fine.
rpcdebug shows:
Feb 26 15:00:43 vostro kernel: [ 1215.145253] nfs_create_rpc_client: cannot 
create RPC client. Error = -22  

   
Feb 26 15:00:43 vostro kernel: [ 1215.159259] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:43 vostro kernel: [ 1215.162745] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:43 vostro kernel: [ 1215.163454] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:43 vostro kernel: [ 1215.164258] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:43 vostro kernel: [ 1215.165173] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:43 vostro kernel: [ 1215.166036] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:43 vostro kernel: [ 1215.166853] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:43 vostro kernel: [ 1215.167682] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:43 vostro kernel: [ 1215.168433] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:43 vostro kernel: [ 1215.169193] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:44 vostro kernel: [ 1215.273955] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:44 vostro kernel: [ 1215.477807] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:44 vostro kernel: [ 1215.885686] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:45 vostro kernel: [ 1216.717869] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:47 vostro kernel: [ 1218.349984] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:50 vostro kernel: [ 1221.745568] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:00:57 vostro kernel: [ 1228.397803] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:01:10 vostro kernel: [ 1241.453733] nfs41_sequence_process: Error 0 
free the slot 
Feb 26 15:01:22 vostro kernel: [ 1253.340717] <-- nfs4_try_get_tree() = -4 
[error]
Feb 26 15:01:22 vostro kernel: [ 1253.364230] NFS: Got error -512 from the 
server on DESTROY_SESSION. Session has been destroyed regardless...
Feb 26 15:01:22 vostro kernel: [ 1253.364360] NFS: Got error -512 from the 
server NAS on DESTROY_CLIENTID.

did a test on clean 'testing' vm, and after upgrading to 'unstable' same issue 
occured



-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  60287  status
1000241   tcp  60425  status
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-2-amd64 (SMP w/8 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), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nfs-common depends on:
ii  adduser  3.118
ii  init-system-helpers  1.62
ii  keyutils 1.6.1-2
ii  libc62.33-7
ii  libcap2  1:2.44-1
ii  libcom-err2  

Processed: closing 648635

[Debian Bug Tracking System]

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

> close 648635
Bug #648635 [nfs-kernel-server] rpc.nfsd still utilizes tcp6/udp6 ports when 
IPv6 is disabled
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#640222: marked as done (nfs-common: init script failure during installation, leaving package half-configured)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:35:48 +0200 (CEST)
with message-id <20240914073548.215cdbe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #640222,
regarding nfs-common: init script failure during installation, leaving package 
half-configured
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.)


-- 
640222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.2.4-1
Severity: normal


For an unknown reason "/etc/init.d/nfs-common start" failed during
installation of nfs-common, leaving the package in half-configured state:

sascha.silbe@mimosa:~$ sudo aptitude install nfs-common
The following NEW packages will be installed:

  libgssglue1{a} [0.3-2] <+98.3 kB> (D: libtirpc1, D: nfs-common) (for 
nfs-common)
  libnfsidmap2{a} [0.24-1] <+123 kB> (D: nfs-common) (for nfs-common)
  libtirpc1{a} [0.2.2-5] <+242 kB> (D: nfs-common, D: rpcbind) (for nfs-common)
  nfs-common [1:1.2.4-1] <+721 kB>
  rpcbind{a} [0.2.0-6] <+172 kB> (D: nfs-common) (for nfs-common)
0 packages upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 414 kB of archives. After unpacking 1,356 kB will be used.
Do you want to continue? [Y/n/?] y
Get:1 http://ftp.de.debian.org/debian/ wheezy/main libgssglue1 armel 0.3-2 
[22.0 kB]
Get:2 http://ftp.de.debian.org/debian/ wheezy/main libtirpc1 armel 0.2.2-5 
[76.2 kB]
Get:3 http://ftp.de.debian.org/debian/ wheezy/main libnfsidmap2 armel 0.24-1 
[30.3 kB]
Get:4 http://ftp.de.debian.org/debian/ wheezy/main rpcbind armel 0.2.0-6 [41.3 
kB]
Get:5 http://ftp.de.debian.org/debian/ wheezy/main nfs-common armel 1:1.2.4-1 
[244 kB]
Fetched 414 kB in 1s (253 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Selecting previously deselected package libgssglue1.
(Reading database ... 98059 files and directories currently installed.)
Unpacking libgssglue1 (from .../libgssglue1_0.3-2_armel.deb) ...
Selecting previously deselected package libtirpc1.
Unpacking libtirpc1 (from .../libtirpc1_0.2.2-5_armel.deb) ...
Selecting previously deselected package libnfsidmap2.
Unpacking libnfsidmap2 (from .../libnfsidmap2_0.24-1_armel.deb) ...
Selecting previously deselected package rpcbind.
Unpacking rpcbind (from .../rpcbind_0.2.0-6_armel.deb) ...
Selecting previously deselected package nfs-common.
Unpacking nfs-common (from .../nfs-common_1%3a1.2.4-1_armel.deb) ...
Processing triggers for man-db ...
Setting up libgssglue1 (0.3-2) ...
Setting up libtirpc1 (0.2.2-5) ...
Setting up libnfsidmap2 (0.24-1) ...
Setting up rpcbind (0.2.0-6) ...
Starting rpcbind daemon
Setting up nfs-common (1:1.2.4-1) ...

Creating config file /etc/idmapd.conf with new version

Creating config file /etc/default/nfs-common with new version
Adding system user `statd' (UID 107) ...
Adding new user `statd' (UID 107) with group `nogroup' ...
Not creating home directory `/var/lib/nfs'.
Starting NFS common utilities: statd idmapd failed!
invoke-rc.d: initscript nfs-common, action "start" failed.
dpkg: error processing nfs-common (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
  Errors were encountered while processing:
 nfs-common
[master 294ea6f] committing changes in /etc after apt run
 Author: sascha.silbe 
 115 files changed, 525 insertions(+), 50 deletions(-)
 create mode 100644 default/nfs-common
 create mode 100644 gssapi_mech.conf
 create mode 100644 idmapd.conf
 rewrite init.d/.depend.start (69%)
 rewrite init.d/.depend.stop (60%)
 create mode 100755 init.d/nfs-common
 create mode 100755 init.d/rpcbind
 create mode 100644 insserv.conf.d/rpcbind
 create mode 100644 netconfig
 create mode 12 rc0.d/K05nfs-common
 create mode 12 rc0.d/K05rpcbind
 rename rc0.d/{K04hwclock.sh => K06hwclock.sh} (100%)
 rename rc0.d/{K05networking => K06networking} (100%)
 rename rc0.d/{K06ifupdown => K07ifupdown} (100%)
 rename rc0.d/{K07umountfs => K08umountfs} (100%)
 rename rc0.d/{K08cryptdisks => K09cryptdisks} (100%)
 rename rc0.d/{K09cryptdisks-early => K10cryptdisks-early} (100%)
 rename rc0.d/{K10umountroot => K11umountroot} (100%)
 rename rc0.d/{K11halt => K12halt} (100%)
 create mode 12 rc1.d/K05nfs-common
 create mode 12 rc1.d/K05rpcbind
 rename rc1.d/{S02bootlogs => S20bootlogs} (100%)
 rename rc1.

Processed: closing 1050840

[Debian Bug Tracking System]

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

> close 1050840
Bug #1050840 [nfs-common] nfs-common: Server no longer listens on UDP port 2049 
by default
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#883890: marked as done (nfs-common: Fully Qualified DNS Name mounts in fstab fail to be mounted)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:31:48 +0200 (CEST)
with message-id <20240914073148.b506dbe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #883890,
regarding nfs-common: Fully Qualified DNS Name mounts in fstab fail to be 
mounted
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.)


-- 
883890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.3.4-2.1
Severity: grave
Justification: renders package unusable

File systems correctly mounted after "reached target network online"

File systema rw in both cases.

Case 1

1. I deleted resolv.conf
2. Root fs rw in fstab
3. File systems mounted by IP address
4. resolve.conf built by end of boot when login possible

proc /proc   procdefaults   
0 0
/dev/mmcblk0p1   /boot   vfatdefaults,ro
0 2
#PARTUUID=62bc0a1f-02/   ext4defaults,noatime   
0 1
192.168.1.10:/nfsroot/r.32.test  /   nfs defaults,rw
0 0
192.168.1.10:/nfsroot/b827eb/c23849/var  /varnfs defaults,rw
0 0
192.168.1.10:/nfsroot/b827eb/c23849/home /home   nfs defaults,rw
0 0
#browne.danum.local:/nfsroot/b827eb/c23849/home /home   nfs defaults,rw 
   0 0
tmpfs/tmptmpfs   
nodev,nosuid,size=1%,mode=1777 0 0

Case 2

1. I deleted resolv.conf
2. Root fs rw in fstab
3. File systems mounted by server name
4. Mount failed.

proc /proc   procdefaults   
0 0
/dev/mmcblk0p1   /boot   vfatdefaults,ro
0 2
#PARTUUID=62bc0a1f-02/   ext4defaults,noatime   
0 1
192.168.1.10:/nfsroot/r.32.test  /   nfs defaults,rw
0 0
192.168.1.10:/nfsroot/b827eb/c23849/var  /varnfs defaults,rw
0 0
#192.168.1.10:/nfsroot/b827eb/c23849/home /home   nfs defaults,rw   
 0 0
browne.danum.local:/nfsroot/b827eb/c23849/home /home   nfs defaults,rw  
  0 0
tmpfs/tmptmpfs   
nodev,nosuid,size=1%,mode=1777 0 0

Case 2

1. resolv.conf not deleted.
2. Root fs rw in fstab
3. File systems mounted by server name
4. Mount failed.

proc /proc   procdefaults   
0 0
/dev/mmcblk0p1   /boot   vfatdefaults,ro
0 2
#PARTUUID=62bc0a1f-02/   ext4defaults,noatime   
0 1
192.168.1.10:/nfsroot/r.32.test  /   nfs defaults,rw
0 0
192.168.1.10:/nfsroot/b827eb/c23849/var  /varnfs defaults,rw
0 0
#192.168.1.10:/nfsroot/b827eb/c23849/home /home   nfs defaults,rw   
 0 0
browne.danum.local:/nfsroot/b827eb/c23849/home /home   nfs defaults,rw  
  0 0
tmpfs/tmptmpfs   
nodev,nosuid,size=1%,mode=1777 0 0

Conclusion: name resolution, dns lookup, is not performed at fstbab mount time.

This is supposed to work. Who's issue is this? systemd or mount?



-- Package-specific info:
-- rpcinfo --

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 9.1 (stretch)
Release:9.1
Codename:   stretch
Architecture: armv7l

Kernel: Linux 4.9.59-v7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-common depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  keyutils 1.5.9-9
ii  libc62.24-11+deb9u1
ii  libcap2  1:2.25-1
ii  libcomerr2   1.43.4-2
ii  libdevmapper1.02.1   2:1.02.137-2
ii  libevent-2.0-5   2.0.21-stable-3
ii  libgssapi-krb5-2 1.15-1+deb9u1
ii  libk5crypto3 1.15-1+deb9u1
ii  libkeyutils1 1.5.9-9
ii  libkrb5-31.15-1+deb9u1
ii  libmount12.29.2-1
ii  libnfsidmap2 0.25-5.1
ii  libtirpc10.2.5-1.2
ii  libwrap0 7.6.q-26
ii  lsb-base 9.20161125+rpi1
ii  rpcbi

Bug#590959: marked as done (idmapd only working in one direction)

[Debian Bug Tracking System]

Your message dated Sat, 14 Sep 2024 09:24:36 +0200 (CEST)
with message-id <20240914072436.03b20be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #590959,
regarding idmapd only working in one direction
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.)


-- 
590959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.1.2-6lenny2

I tried to set up nfsv4 between two lenny-installations where users have
different UIDs.

Server: User "xyz" has UID 1000
Client: User "xyz" has UID 501

/etc/exports (server) contains:

/exports  with options: rw,fsid=0,insecure,no_subtree_check,sync
/exports/home  with optione: rw,nohide,insecure,no_subtree_check,sync


/etc/default/nfs-common (server+client)
NEED_STATD=no
STATDOPTS=
NEED_IDMAPD=yes
NEED_GSSD=

/etc/idmapd.conf is identical on server+client

mount server:/home /mnt/ -t nfs4

"ls -l /mnt" translates user and group properly.
"touch /mnt/xxx" creates a file with UID 501 on the server / should be
UID 1000



--- End Message ---
--- Begin Message ---
Hi

[This reply and bug closer is sent for doing BTS maintenance for
src:nfs-utils bugs]

This bug was reported against a very old nfs-utils version without much
followups/triaging itself.

If you can reproduce it with the current version in unstable/testing or
stable at least, please reopen the bug,
https://www.debian.org/Bugs/server-control for details.

Regards,
Salvatore--- End Message ---

Processed: notfound 1072573 in 2.6.2-4, found 1072573 in 1:2.6.2-4

[Debian Bug Tracking System]

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

> notfound 1072573 2.6.2-4
Bug #1072573 [nfs-common] rpc.idmapd runs out of file descriptors
There is no source info for the package 'nfs-common' at version '2.6.2-4' with 
architecture ''
Unable to make a source version for version '2.6.2-4'
No longer marked as found in versions 2.6.2-4.
> found 1072573 1:2.6.2-4
Bug #1072573 [nfs-common] rpc.idmapd runs out of file descriptors
Marked as found in versions nfs-utils/1:2.6.2-4.
> thanks
Stopping processing here.

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

Processed: ThinkPad T14 Gen 4 kernel: hpet_acpi_add: no address or irqs in _CRS

[Debian Bug Tracking System]

Processing control commands:

> found -1 linux/6.10.9-1
Bug #1041484 [src:linux] kernel: hpet_acpi_add: no address or irqs in _CRS
Marked as found in versions linux/6.10.9-1.

-- 
1041484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcemerge 1076483 1081705

[Debian Bug Tracking System]

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

> forcemerge 1076483 1081705
Bug #1076483 [src:linux] Call Trace on rt kernel, CPU Intel 13th Gen Intel(R) 
Core(TM) i5-1340P
Bug #1076483 [src:linux] Call Trace on rt kernel, CPU Intel 13th Gen Intel(R) 
Core(TM) i5-1340P
Marked as found in versions linux/6.10.7-1 and linux/6.10.9-1.
Bug #1081705 [src:linux] Call Trace: dump_stack_lvl+0x64/0x80 RIP: 
0010:poll_idle+0x68/0xc0
Severity set to 'important' from 'minor'
Marked as found in versions linux/6.10-1~exp1 and linux/6.9.9-1.
Merged 1076483 1081705
>
End of message, stopping processing here.

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

Processed: found 1081705 6.10.9-1

[Debian Bug Tracking System]

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

> found 1081705 6.10.9-1
Bug #1081705 [src:linux] Call Trace: dump_stack_lvl+0x64/0x80 RIP: 
0010:poll_idle+0x68/0xc0
Marked as found in versions linux/6.10.9-1.
>
End of message, stopping processing here.

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

Processed: closing 867067

[Debian Bug Tracking System]

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

> close 867067
Bug #867067 [nfs-kernel-server] nfs-kernel-server: nfsdcltrack fails to init 
database
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#780944: marked as done (nfs-kernel-server exports automounted filesystems under /media only as root:root)

[Debian Bug Tracking System]

Your message dated Fri, 13 Sep 2024 23:09:10 +0200
with message-id 
and subject line Re: Bug#780944: nfs-kernel-server exports automounted 
filesystems under /media only as root:root
has caused the Debian Bug report #780944,
regarding nfs-kernel-server exports automounted filesystems under /media only 
as root:root
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.)


-- 
780944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.2.8-9
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

I am exporting /home/.. and /media, where my USB-drives are located. When I
export a directory under /home I get the correct userid and groupid mapping.
The automounted drives under /media will not mount on the nfs-client with the
correct userid or groupid. I have tried forcing it with anonuid and anongid in
exportfs and it doesn't matter everything is root:root under /media when i try
to open it on the client. I have also tried to remoutnt drives from
/media/user/.. and re-export from that directory since this seems more correct
but to no avail. I am using NFSv4 no idmapping and no kerberos so this should
be pretty stright forward but I might miss something. or its a bug.

Problem occured when I upgraded to Jessie from Wheezy on the server(the client
is a new install jessie from netinst on a virtualbox instance).

Last iteration of config files:

Server

/etc/exports
/export/media   10.0.0.0/24(rw,nohide,insecure,no_subtree_check,async,sec=sys)
/export/em  10.0.0.0/24(rw,nohide,insecure,no_subtree_check,async,sec=sys)
/export/new 10.0.0.0/24(ro,nohide,insecure,no_subtree_check,async)

/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
/dev/mapper/Melkor-root /   ext4errors=remount-ro 0   1
# /boot was on /dev/sda1 during installation
UUID=39a76d28-3c42-4f57-9e07-9bea14e41f3c /boot   ext4defaults
0   2
/dev/mapper/storage_vol1-home /home   ext4defaults0   2
/dev/mapper/Melkor-tmp /tmpext4defaults0   2
/dev/mapper/Melkor-var /varext4defaults0   2
/dev/mapper/storage_vol1-virtos /var/virtos ext4defaults0
2
/dev/mapper/Melkor-swap noneswapsw  0   0
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0
/home/executor/Azureus\040Downloads /export/new none bind 0 0
/media  /export/medianone bind 00
/media/executor /export/em   none bind 00

Client

/etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda1 during installation
UUID=cc86bad1-92b6-46f8-8601-a8a79fb4f30f /   ext4
errors=remount
-ro 0   1
# swap was on /dev/sda5 during installation
UUID=0da51868-169c-4ca5-960d-4f3f9ef6be3f noneswapsw
  0   0
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0
## NFS Mounts

#silmarilion:/media/executor   /mnt/media   nfs4_netdev,auto  0  0
#silmarilion:/export/media   /mnt/media   nfs4_netdev,sec=sys,auto  0  0
silmarilion:/export/em   /mnt/em   nfs4_netdev,sec=sys,auto  0  0
silmarilion:/export/new   /mnt/new   nfs4_netdev,auto  0  0
#media   /mnt/media  vboxsf ro,uid=1000,gid=1000 0  0


I would expect this to reslut in a mounting of /meida/em from server to client
under /mnt/em and all directories under /media/executor on the server showing
the same owner and gid as on the client and servers. Now everything is
root:root.





-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
   

Processed: notfound 1081563 in 6.10.9, found 1081563 in 6.10.9-1

[Debian Bug Tracking System]

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

> notfound 1081563 6.10.9
Bug #1081563 [src:linux] Please consider adding the new Xe Graphics driver for 
Intel GPUs
The source 'linux' and version '6.10.9' do not appear to match any binary 
packages
No longer marked as found in versions linux/6.10.9.
> found 1081563 6.10.9-1
Bug #1081563 [src:linux] Please consider adding the new Xe Graphics driver for 
Intel GPUs
Marked as found in versions linux/6.10.9-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1081546: new "GPU HANG: ecode 12:1:85dffdfb, in Renderer" regression in i915 driver since 6.10 kernel upgrade

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream moreinfo
Bug #1081546 [src:linux] new "GPU HANG: ecode 12:1:85dffdfb, in Renderer" 
regression in i915 driver since 6.10 kernel upgrade
Added tag(s) moreinfo and upstream.

-- 
1081546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

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

> merge 1081056 1081293
Bug #1081056 [src:linux] linux: thermal thermal_zone8: failed to read out 
thermal zone (-61)
Bug #1081056 [src:linux] linux: thermal thermal_zone8: failed to read out 
thermal zone (-61)
Marked as found in versions linux/6.1.106-3.
Bug #1081293 [src:linux] linux: thermal thermal_zone8: failed to read out 
thermal zone (-61)
Merged 1081056 1081293
>
End of message, stopping processing here.

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

Bug#1080492: marked as done (firmware-nonfree: [i915] With 20240709-2, the external monitors randomly blank for 2-3 seconds (regression))

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2024 21:51:14 +0200
with message-id 
and subject line Re: firmware-nonfree: [i915] With 20240709-2, the external 
monitors randomly blank for 2-3 seconds (regression)
has caused the Debian Bug report #1080492,
regarding firmware-nonfree: [i915] With 20240709-2, the external monitors 
randomly blank for 2-3 seconds (regression)
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.)


-- 
1080492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firmware-nonfree
Version: 20240709-2
Severity: important

First, some context: I have a Dell laptop with 2 external monitors
connected via a dock. With 6.8+ Linux kernels, one of the external
monitors randomly blanks for 2-3 seconds (no such issue with earlier
kernels); not always the same monitor, but in most cases, not both
at the same time. I had reported the following bugs about this issue:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072063
  https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11821

This blanking issue can occur several times per day.

After the upgrade of the binary packages of firmware-nonfree source
to 20240709-2, a new issue appeared: *both* external monitors randomly
blank for 2-3 seconds. Worse:
  * With a (non-Debian) 6.11.0-rc2+ test kernel (which I used in the
context of the other bug), this issue occurs very often: up to
several times per minute!
  * With the linux-image-6.7.12-amd64 Debian kernel, this issue also
occurs (but not often), while this kernel does not have the bug
mentioned above.

Downgrading to 20240709-1 made the issue disappear, at least with
the linux-image-6.7.12-amd64 Debian kernel (I have not tried the
6.11.0-rc2+ test kernel yet, but note that I was already using it
with 20240709-1 before September 2).

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.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

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
On Thu, 5 Sep 2024 02:24:18 +0200 Vincent Lefevre 
wrote:
[...]
> This blanking issue can occur several times per day.
> 
> After the upgrade of the binary packages of firmware-nonfree source
> to 20240709-2, a new issue appeared:
[...]
> Downgrading to 20240709-1 made the issue disappear,
[...]

No graphics firmware changed between these versions.  This is not a
firmware regression, just random variation in the previously reported
bug.

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.



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

Bug#1063660: marked as done (firmware-amd-graphics: Please backport newer firmware to Bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2024 16:48:40 +0200
with message-id <66069415-27fd-552a-d059-a0c791208...@debian.org>
and subject line Re: Bug#1063660: firmware-nonfree: Please backport newer 
firmware to Bookworm
has caused the Debian Bug report #1063660,
regarding firmware-amd-graphics: Please backport newer firmware to Bookworm
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.)


-- 
1063660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-image-amd64
Version: 6.1.76-1


update-initramfs: Generating /boot/initrd.img-6.1.0-18-amd64
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for 
module amdgpu
W: Possible missing firmware 
/lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_ta.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_toc.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_rlc.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mec.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_me.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_pfp.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for 
module amdgpu
W: Possible missing firmware 
/lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu
W: Possible missing firmware 
/lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes1.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes_2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_2_mes_2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mes_2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_mes_2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for 
module amdgpu

I: The initramfs will attempt to resume from /dev/nvme0n1p6
--- End Message ---
--- Begin Message ---

Version: 20240709-2

 firmware-nonfree (20240709-2~bpo12+1) bookworm-backports; urgency=medium
 .
   [ Dylan Aïssi ]
   * Rebuild for bookworm-backports. (Closes: #1063660)
   * Update to linux-support 6.10.6+bpo


Thanks!

Andreas--- End Message ---

Processed: Re: Bug#1081310: Wired ethernet connection disabled.

[Debian Bug Tracking System]

Processing control commands:

> found -1 5.10.218-1
Bug #1081310 [src:linux] Wired ethernet connection disabled.
Marked as found in versions linux/5.10.218-1.

-- 
1081310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1081310

[Debian Bug Tracking System]

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

> tags 1081310 - moreinfo
Bug #1081310 [src:linux] Wired ethernet connection disabled.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1081310: Wired ethernet connection disabled.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 5.10.223-1
Bug #1081310 [linux-image-5.10.0-32-amd64] Wired ethernet connection disabled.
Bug reassigned from package 'linux-image-5.10.0-32-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/5.10.223+1.
Ignoring request to alter fixed versions of bug #1081310 to the same values 
previously set
Bug #1081310 [src:linux] Wired ethernet connection disabled.
Marked as found in versions linux/5.10.223-1.
> tags -1 + moreinfo
Bug #1081310 [src:linux] Wired ethernet connection disabled.
Added tag(s) moreinfo.

-- 
1081310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: notfound 1081293 in 6.1.0-25-amd64, found 1081293 in 6.1.106-3

[Debian Bug Tracking System]

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

> notfound 1081293 6.1.0-25-amd64
Bug #1081293 [src:linux] linux: thermal thermal_zone8: failed to read out 
thermal zone (-61)
The source 'linux' and version '6.1.0-25-amd64' do not appear to match any 
binary packages
No longer marked as found in versions linux/6.1.0-25-amd64.
> found 1081293 6.1.106-3
Bug #1081293 [src:linux] linux: thermal thermal_zone8: failed to read out 
thermal zone (-61)
Marked as found in versions linux/6.1.106-3.
> thanks
Stopping processing here.

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

Processed: Re: devscripts: test-patches KeyError: 'pae'

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #1081195 [src:linux] devscripts: test-patches KeyError: 'pae'
Added tag(s) confirmed.

-- 
1081195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1081195 to src:linux

[Debian Bug Tracking System]

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

> reassign 1081195 src:linux 6.10.6-1
Bug #1081195 [devscripts] devscripts: test-patches KeyError: 'pae'
Bug reassigned from package 'devscripts' to 'src:linux'.
No longer marked as found in versions devscripts/2.23.7.
Ignoring request to alter fixed versions of bug #1081195 to the same values 
previously set
Bug #1081195 [src:linux] devscripts: test-patches KeyError: 'pae'
Marked as found in versions linux/6.10.6-1.
> thanks
Stopping processing here.

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

Bug#1081197: marked as done (linux: please Build-Depends on 'gcc' or on 'build-essential' rather than 'gcc-13')

[Debian Bug Tracking System]

Your message dated Mon, 9 Sep 2024 16:53:23 +0200
with message-id <20240909145323.6qy3gze7ajopm...@shell.thinkmo.de>
and subject line Re: Bug#1081197: linux: please Build-Depends on 'gcc' or on 
'build-essential' rather than 'gcc-13'
has caused the Debian Bug report #1081197,
regarding linux: please Build-Depends on 'gcc' or on 'build-essential' rather 
than 'gcc-13'
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.)


-- 
1081197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

src:linux currently has an explicit Build-Depends on gcc-13. This defeats the 
whole point of building against whatever 'build-essential' pulls in for the 
target Debian release, and it results in several GCC suites getting 
unnecessarily installed. It would instead be desirable for src:linux to 
Build-Depends on either the generic 'gcc' or on 'build-essential' for its 
compiler requirements.

Martin-Éric

- -- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 6.10.6-686-pae (SMP w/1 CPU thread; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmbetwAACgkQrh+Cd8S0
17ZdqA/8DC4Wz/FgWWvfeHSI6h5BNzr3UjxgeZsoOGDc2JlvcpVRAEWnIiq0QJdj
tyhJGOcevKD8btAtGjxPbzXEQOavQNB66BBW1fY/9/cky+L3MZarpYIJqRbf63SG
blU+Gfn0kNbE/EwryP+i7wRfEs9yUzECb2pyGJKccycsmqbZm4M9M1wdZk72fV3s
cWQ/Jo+s4MnEHgidLesijLZkP/EPD4iT3znONVWhGkDa6A/B/P2yDywvNajyHrRV
N4FT6mAS4HWVhegnX5yJN2/ndT9EH5QDq0zbUZLpzz2R7Z6L0RVNPHBxKgR+IruL
yNjpoM7+ggFsRTzMDW4LvpQjWaoTgQVJstnbCPpZwWwFAib0RjKIYfZzJuxw75rk
aIj7Sg1fjj3uf8Tx8NG6aeICdK1JuUY7pN3l2mSk4k3SdG9sdtYODkYC3ee5qWbc
pPC41R4uBrPpq1mWDaci+FYihaZAcK40oZHHZYwsPiSncuYIWrgjmxzi/4iaJUiv
ic7L8FHktwph79IHtosQR1KErKmiyAOKFU74/8H8DypmcIWc+gS5MziO4oiyWJmC
Bw+7I+Fuo90vSgwe35+d4f5BtXFJqVRaG5YEQNt/bcOQUDUJftDuDn0kpOxe8Y98
MYXsn3JvE9aQucbfNLHBuEIPDe6FkifLHeDDib7FPeQumMxh4qI=
=rkLN
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On Mon, Sep 09, 2024 at 03:26:08PM +0300, Martin-Éric Racine wrote:
> ma 9. syysk. 2024 klo 13.50 Bastian Blank (wa...@debian.org) kirjoitti:
> >
> > On Mon, Sep 09, 2024 at 11:51:17AM +0300, Martin-Éric Racine wrote:
> > > src:linux currently has an explicit Build-Depends on gcc-13. This defeats 
> > > the whole point of building against whatever 'build-essential' pulls in 
> > > for the target Debian release, and it results in several GCC suites 
> > > getting unnecessarily installed. It would instead be desirable for 
> > > src:linux to Build-Depends on either the generic 'gcc' or on 
> > > 'build-essential' for its compiler requirements.
> > And how will that work if src:linux uses gcc-13 to build?
> Is there any compelling reason for src:linux to hardcode the GCC
> version as an explicit dependency?

Yes, linux uses a hardcoded version of gcc to build.  This also means
that it must depend on this version.

Almost every large gcc upgrade either breaks building or running of the
kernel.  So it usually takes another round or two of gcc and/or linux
fixes to actually get something running out of it.

Bastian

-- 
If some day we are defeated, well, war has its fortunes, good and bad.
-- Commander Kor, "Errand of Mercy", stardate 3201.7--- End Message ---

Processed: closing 1070685, closing 1070685

[Debian Bug Tracking System]

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

> close 1070685 6.11~rc4-1~exp1
Bug #1070685 [src:linux] linux-image-6.1.0-21-amd64: Found Trace in the logs 
about br_netfilter and nf_conntrack
Marked as fixed in versions linux/6.11~rc4-1~exp1.
Bug #1070685 [src:linux] linux-image-6.1.0-21-amd64: Found Trace in the logs 
about br_netfilter and nf_conntrack
Marked Bug as done
> close 1070685 6.10.7-1
Bug #1070685 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-6.1.0-21-amd64: Found Trace in the logs about br_netfilter and 
nf_conntrack
Marked as fixed in versions linux/6.10.7-1.
Bug #1070685 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-6.1.0-21-amd64: Found Trace in the logs about br_netfilter and 
nf_conntrack
Bug 1070685 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#1079394: marked as done (linux-image-6.10.6-amd64: causes cifs regression, flatpak & ostree signature corruption)

[Debian Bug Tracking System]

Your message dated Mon, 9 Sep 2024 15:15:40 +0200
with message-id 
and subject line Re: Bug#1079394: linux-image-6.10.6-amd64: causes cifs 
regression, flatpak & ostree signature corruption
has caused the Debian Bug report #1079394,
regarding linux-image-6.10.6-amd64: causes cifs regression, flatpak & ostree 
signature corruption
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.)


-- 
1079394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.10.6-1
Severity: important
X-Debbugs-Cc: fores...@nom.one

Dear Maintainer,

After upgrading from kernel 6.9.12 to 6.10.4, flatpak and ostree are now
writing corrupt gpg signatures when exporting signed packages or signing
their repository metadata/summary files, when the repository is on a cifs
mount. Instead of writing signature data, null bytes are written in its
place.

No error is reported by the application or the kernel when it happens.
The problem isn't revealed until something tries to use the repository,
and finds signatures full of null bytes. Of course, this completely
breaks affected flatpak repositories.

A kernel bisect reveals this:
3ee1a1fc39819906f04d6c62c180e760cd3a689d is the first bad commit
commit 3ee1a1fc39819906f04d6c62c180e760cd3a689d
Author: David Howells 
Date:   Fri Oct 6 18:29:59 2023 +0100
cifs: Cut over to using netfslib

I was unable to determine whether the problem is fixed in kernel
6.11.0-rc4, due to even worse cifs problems in that version.

An strace of flatpak (which uses libostree) hints that the problem might
be triggered by the following sequence of events:

- create a temp file
- write signature data to the temp file
- memory map the temp file
- close the temp file
- unlink the temp file
- read the previously written signature data from the memory mapping

My investigation so far can be found in these bug reports:
https://github.com/flatpak/flatpak/issues/5911
https://github.com/ostreedev/ostree/issues/3288

I am not familiar with those projects' code, so the triggering sequence
of events is merely a hypothesis for now.

However, I can consistently reproduce the problem by passing a path
located on a cifs mount (along with a gpg key ID) to this script:


#!/bin/sh
set -e

if [ "$#" -lt 2 ] || [ "$1" = "-h" ] ; then
echo "usage: $(basename "$0")  "
exit 2
fi

repo=$1
keyid=$2
src="./foo"

echo "creating ostree repo at $repo"
ostree init --repo="$repo"

echo "creating test tree at $src"
mkdir -p "$src"
echo hi > "$src"/hello

ostree config --repo="$repo" set core.min-free-space-percent 1
ostree commit --repo="$repo" --branch=foo --gpg-sign="$keyid" "$src"

if ostree show --repo="$repo" foo; then
echo ---
echo success!
else
echo ---
ostree show --repo="$repo" --print-detached-metadata-key=ostree.gpgsigs foo
echo failure!
echo look for null bytes in the above commit signature
fi



-- Package-specific info:
** Version:
Linux version 6.10.6-amd64 (debian-kernel@lists.debian.org) 
(x86_64-linux-gnu-gcc-13 (Debian 13.3.0-5) 13.3.0, GNU ld (GNU Binutils for 
Debian) 2.43.1) #1 SMP PREEMPT_DYNAMIC Debian 6.10.6-1 (2024-08-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.10.6-amd64 
root=UUID=---- ro net.ifnames=0 quiet 
cryptdevice=UUID=----:xx 
root=/dev/mapper/xx splash

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Loaded modules:
tun
nls_utf8
cifs
cifs_arc4
nls_ucs2_utils
cifs_md4
dns_resolver
netfs
nft_masq
nft_chain_nat
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
bridge
stp
llc
nf_tables
nvme_fabrics
nfnetlink
rfcomm
essiv
authenc
crypto_null
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
qrtr
cmac
algif_hash
algif_skcipher
af_alg
zstd
bnep
zram
binfmt_misc
nls_ascii
nls_cp437
vfat
fat
mt7921e
mt7921_common
mt792x_lib
mt76_connac_lib
snd_hda_codec_realtek
mt76
snd_hda_codec_generic
snd_hda_scodec_component
snd_hda_codec_hdmi
snd_hda_intel
amd_atl
intel_rapl_msr
mac80211
intel_rapl_common
snd_intel_dspcfg
amd64_edac
snd_intel_sdw_acpi
edac_mce_amd
btusb
snd_hda_codec
btrtl
btintel
kvm_amd
btbcm
snd_hda_core
btmtk
eeepc_wmi
asus_nb_wmi
libarc4
bluetooth
asus_wmi
snd_hwdep
kvm
cfg80211
snd_pcm
battery
sparse_keymap
platform_profile
snd_timer
wmi_bmof
sp5100_tco
rapl
snd
k10

Bug#1080147: marked as done (/usr/lib/modules/6.10.6-amd64/kernel/drivers/gpu/drm/vmwgfx: Black screen on VMware guests - Command buffer error on vmwgfx)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2024 23:00:10 +
with message-id 
and subject line Bug#1079167: fixed in linux 6.10.9-1
has caused the Debian Bug report #1079167,
regarding /usr/lib/modules/6.10.6-amd64/kernel/drivers/gpu/drm/vmwgfx: Black 
screen on VMware guests - Command buffer error on vmwgfx
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.)


-- 
1079167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.10.6-1
Severity: grave
File: /usr/lib/modules/6.10.6-amd64/kernel/drivers/gpu/drm/vmwgfx
Justification: renders package unusable
X-Debbugs-Cc: c...@aptivi.anonaddy.com

I've just installed Debian Trixie Testing daily build from this page:
https://cdimage.debian.org/cdimage/daily-builds/daily/current/amd64/iso-cd/debian-testing-amd64-netinst.iso

The installer works OK, as I could install the Debian distribution but with
minimal options (without desktop). However, when I try to reboot into the
newly-installed system, I only see a black screen. I've managed to successfully
get its IP address by redirecting `ip a` into a file in the home directory and
going to rescue mode to `cat` it so I could SSH into it.

Looking into the `dmesg` output that is attached below, I can see the `Command
buffer error` message coming from the vmwgfx driver. Before the black screen,
I was able to see the kernel messages. So, I suspect that the black screen
issue came after the `Command buffer error` message, and that it's a bug in the
vmwgfx driver.

It's a clean install.

-- Package-specific info:
** Version:
Linux version 6.10.6-amd64 (debian-kernel@lists.debian.org) 
(x86_64-linux-gnu-gcc-13 (Debian 13.3.0-5) 13.3.0, GNU ld (GNU Binutils for 
Debian) 2.43.1) #1 SMP PREEMPT_DYNAMIC Debian 6.10.6-1 (2024-08-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.10.6-amd64 
root=UUID=eba572b0-3024-40c4-813b-f9ee8d1f101c ro quiet

** Tainted: W (512)
 * kernel issued warning

** Kernel log:
[2.786114] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
[2.797155] ACPI: AC: AC Adapter [ACAD] (on-line)
[2.804145] ACPI: button: Power Button [PWRF]
[2.829977] Adding 998396k swap on /dev/sda5.  Priority:-2 extents:1 
across:998396k 
[2.911644] input: PC Speaker as /devices/platform/pcspkr/input/input6
[2.918347] vmwgfx :00:0f.0: vgaarb: deactivate vga console
[2.918648] Console: switching to colour dummy device 80x25
[2.919319] vmwgfx :00:0f.0: [drm] FIFO at 0xfe00 size is 
8192 KiB
[2.919398] vmwgfx :00:0f.0: [drm] VRAM at 0xe800 size is 
131072 KiB
[2.919414] vmwgfx :00:0f.0: [drm] Running on SVGA version 2.
[2.919421] vmwgfx :00:0f.0: [drm] Capabilities: rect copy, cursor, 
cursor bypass, cursor bypass 2, 8bit emulation, alpha cursor, extended fifo, 
multimon, pitchlock, irq mask, display topology, gmr, traces, gmr2, screen 
object 2, command buffers, command buffers 2, gbobject, dx, hp cmd queue, no bb 
restriction, cap2 register, 
[2.919427] vmwgfx :00:0f.0: [drm] Capabilities2: grow otable, intra 
surface copy, dx2, gb memsize 2, screendma reg, otable ptdepth2, non ms to ms 
stretchblt, cursor mob, mshint, cb max size 4mb, dx3, frame type, trace full 
fb, extra regs, lo staging, 
[2.919704] vmwgfx :00:0f.0: [drm] DMA map mode: Caching DMA mappings.
[2.919826] vmwgfx :00:0f.0: [drm] Legacy memory limits: VRAM = 4096 
KiB, FIFO = 256 KiB, surface = 0 KiB
[2.919828] vmwgfx :00:0f.0: [drm] MOB limits: max mob size = 262144 
KiB, max mob pages = 65536
[2.919829] vmwgfx :00:0f.0: [drm] Max GMR ids is 64
[2.919830] vmwgfx :00:0f.0: [drm] Max number of GMR pages is 65536
[2.919831] vmwgfx :00:0f.0: [drm] Maximum display memory size is 262144 
KiB
[2.923906] vmwgfx :00:0f.0: [drm] Screen Target display unit initialized
[2.924545] vmwgfx :00:0f.0: [drm] Fifo max 0x0004 min 0x1000 
cap 0x077f
[2.930035] vmwgfx :00:0f.0: [drm] Using command buffers with DMA pool.
[2.930040] vmwgfx :00:0f.0: [drm] Available shader model: Legacy.
[2.953623] [drm] Initialized vmwgfx 2.20.0 20211206 for :00:0f.0 on 
minor 0
[2.969878] fbcon: vmwgfxdrmfb (fb0) is primary device
[2.970860] Console: switching to colour frame buffer device 160x50
[2.972667] vmwgfx :00:0f.0: [drm] fb0: vmwgfxdrmfb frame buffer device
[2.973380] [ cut here ]
[2.973382] Command buffer error.
[2.973396]

Bug#1079167: marked as done (linux-image-6.10.4-amd64: vmwgfx crash and black screen)

[Debian Bug Tracking System]

Your message dated Sun, 08 Sep 2024 23:00:10 +
with message-id 
and subject line Bug#1079167: fixed in linux 6.10.9-1
has caused the Debian Bug report #1079167,
regarding linux-image-6.10.4-amd64: vmwgfx crash and black screen
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.)


-- 
1079167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:linux
Version: 6.10.4-1
Severity: normal
Tags: upstream

Upgrading to kernel 6.10.4-1 when running debian inside a vmware/esx,
leads to
a  vmwgfx crash and a black screen.

Reverting back to 6.10.3-1 solves the problem.

This bug has already been reported upstream here:
https://lore.kernel.org/all/0d0330f3-2ac0-4cd5-8075-7f1cbaf72...@heusel.eu/

boot.log snippet from the vm:

2024-08-19T07:35:45.326867+02:00 debian kernel: vmwgfx :00:0f.0:
[drm] VRAM
at 0xf000 size is 131072 KiB
2024-08-19T07:35:45.326875+02:00 debian kernel: vmwgfx :00:0f.0: [drm]
Running on SVGA version 2.
2024-08-19T07:35:45.326876+02:00 debian kernel: vmwgfx :00:0f.0: [drm]
Capabilities: rect copy, cursor, cursor bypass, cursor bypass 2, 8bit
emulation, alpha cursor, extended fifo, multimon, pitchlock, irq mask,
display
topology, gmr, traces, gmr2, screen object 2, command buff
ers, command buffers 2, gbobject, dx, hp cmd queue, no bb restriction, cap2
register,
2024-08-19T07:35:45.326877+02:00 debian kernel: vmwgfx :00:0f.0: [drm]
Capabilities2: grow otable, intra surface copy, dx2, gb memsize 2, screendma
reg, otable ptdepth2, non ms to ms stretchblt, cursor mob, mshint, cb
max size
4mb, dx3, frame type, trace full fb, extra regs, lo
staging,
2024-08-19T07:35:45.326878+02:00 debian kernel: vmwgfx :00:0f.0:
[drm] DMA
map mode: Caching DMA mappings.
2024-08-19T07:35:45.326879+02:00 debian kernel: vmwgfx :00:0f.0: [drm]
Legacy memory limits: VRAM = 4096 KiB, FIFO = 256 KiB, surface = 0 KiB
2024-08-19T07:35:45.326880+02:00 debian kernel: vmwgfx :00:0f.0:
[drm] MOB
limits: max mob size = 262144 KiB, max mob pages = 65536
2024-08-19T07:35:45.326892+02:00 debian kernel: vmwgfx :00:0f.0:
[drm] Max
GMR ids is 64
2024-08-19T07:35:45.326893+02:00 debian kernel: vmwgfx :00:0f.0:
[drm] Max
number of GMR pages is 65536
2024-08-19T07:35:45.326894+02:00 debian kernel: vmwgfx :00:0f.0: [drm]
Maximum display memory size is 262144 KiB
2024-08-19T07:35:45.326895+02:00 debian kernel: vmwgfx :00:0f.0: [drm]
Screen Target display unit initialized
2024-08-19T07:35:45.326896+02:00 debian kernel: vmwgfx :00:0f.0:
[drm] Fifo
max 0x0004 min 0x1000 cap 0x077f
2024-08-19T07:35:45.326897+02:00 debian kernel: vmwgfx :00:0f.0: [drm]
Using command buffers with DMA pool.
2024-08-19T07:35:45.326906+02:00 debian kernel: vmwgfx :00:0f.0: [drm]
Available shader model: Legacy.
2024-08-19T07:35:45.326908+02:00 debian kernel: [drm] Initialized vmwgfx
2.20.0
20211206 for :00:0f.0 on minor 0
2024-08-19T07:35:45.326909+02:00 debian kernel: nvme nvme0: 15/0/0
default/read/poll queues
2024-08-19T07:35:45.326910+02:00 debian kernel: fbcon: vmwgfxdrmfb (fb0) is
primary device
2024-08-19T07:35:45.326911+02:00 debian kernel: Console: switching to colour
frame buffer device 160x50
2024-08-19T07:35:45.326911+02:00 debian kernel: vmwgfx :00:0f.0:
[drm] fb0:
vmwgfxdrmfb frame buffer device
2024-08-19T07:35:45.326912+02:00 debian kernel: [ cut here
]
2024-08-19T07:35:45.326921+02:00 debian kernel: Command buffer error.
2024-08-19T07:35:45.326922+02:00 debian kernel: WARNING: CPU: 9 PID: 442 at
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c:399
vmw_cmdbuf_ctx_process+0x24b/0x260
[vmwgfx]
2024-08-19T07:35:45.326923+02:00 debian kernel: Modules linked in: nvme
vmwgfx(+) nvme_core ata_generic ahci drm_ttm_helper t10_pi uhci_hcd
crc64_rocksoft mptspi(+) ttm xhci_pci ehci_pci libahci crc64 ata_piix
mptscsih
crc_t10dif xhci_hcd drm_kms_helper crc32_pclmul ehci_hcd libata mptbase
scsi_transport_spi crct10dif_generic crc32c_intel crct10dif_pclmul usbcore
psmouse drm e1000(+) scsi_mod crct10dif_common usb_common scsi_common
i2c_piix4
button
2024-08-19T07:35:45.326924+02:00 debian kernel: CPU: 9 PID: 442 Comm:
irq/16-vmwgfx Not tainted 6.10.4-amd64 #1 Debian 6.10.4-1
2024-08-19T07:35:45.326925+02:00 debian kernel: Hardware name: VMware, Inc.
VMware20,1/440BX Desktop Reference Platform, BIOS
VMW201.00V.21805430.B64.2305221830 05/22/2023
2024-08-19T07:35:45.326933+02:00 debian kernel: RIP:
0010:vmw_cmdbuf_ctx_process+0x24b/0x260 [vmwgfx]
2024-08-19T07:35:45.326935+02:00 debian

Bug#1071468: marked as done (linux-image-amd64: mess left when kernel installation fails (grub treats the uninstalled kernel as existing))

[Debian Bug Tracking System]

Your message dated Mon, 09 Sep 2024 00:15:09 +0200
with message-id <32b8bd198753dfa3ce664de37e79dd94ca4da66c.ca...@decadent.org.uk>
and subject line Re: linux-image-amd64: mess left when kernel installation 
fails (grub treats the uninstalled kernel as existing)
has caused the Debian Bug report #1071468,
regarding linux-image-amd64: mess left when kernel installation fails (grub 
treats the uninstalled kernel as existing)
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.)


-- 
1071468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 6.6.13-1~bpo12+1
Severity: normal
X-Debbugs-Cc: debbug.linux-am...@sideload.33mail.com

A kernel installation failed due to a corrupt deb file that could not
be unpacked. That was reported here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071467

Apparently whatever generic installation mechanism is used, it fails
to properly treat a botched delivery. That is, even though the deb
file for kernel version 6.6.13-1~bpo12+1 is only 1480 bytes and so
corrupt it cannot even be unpacked, the package was erroneously
flagged as installed, at least in part:

===8<
  $ dpkg -l | grep 6.6.13-1~bpo12+1
  iU  linux-headers-6.6.13+bpo-amd64   6.6.13-1~bpo12+1 amd64 Header files for 
Linux 6.6.13+bpo-amd64
  ii  linux-headers-6.6.13+bpo-common  6.6.13-1~bpo12+1 all   Common header 
files for Linux 6.6.13+bpo
  iU  linux-headers-amd64  6.6.13-1~bpo12+1 amd64 Header files for 
Linux amd64 configuration (meta-package)
  iF  linux-image-6.6.13+bpo-amd64 6.6.13-1~bpo12+1 amd64 Linux 6.6 for 
64-bit PCs (signed)
  iU  linux-image-amd646.6.13-1~bpo12+1 amd64 Linux for 64-bit 
PCs (meta-package)
  ii  linux-kbuild-6.6.13+bpo  6.6.13-1~bpo12+1 amd64 Kbuild 
infrastructure for Linux 6.6.13+bpo
  ii  linux-libc-dev   6.6.13-1~bpo12+1 all   Linux support 
headers for userspace development
===8<

Perhaps “iU” and “iF” are correct flags in the first column (it’s
unclear because “man dpkg” does not document these). But grub
alterations were carried out despite the failure and the default
kernel became the version that could not even be unpacked from the deb
file (6.6.13-1~bpo12+1). So it’s not just a failure of that kernel but
also a failure in the installation logic, perhaps in apt. Though I
doubt apt would influence grub, so I’m filing this in the virtual pkg
linux-image-amd64 for lack of a better place.

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-21-amd64 (SMP w/2 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), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-amd64 depends on:
ih  linux-image-6.6.13+bpo-amd64  6.6.13-1~bpo12+1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 19 May 2024 21:46:34 +0200 Manny
 wrote:
[...]
> ===8<
>   $ dpkg -l | grep 6.6.13-1~bpo12+1
>   iU  linux-headers-6.6.13+bpo-amd64   6.6.13-1~bpo12+1 amd64 Header
files for Linux 6.6.13+bpo-amd64
>   ii  linux-headers-6.6.13+bpo-common  6.6.13-1~bpo12+1 all   Common
header files for Linux 6.6.13+bpo
>   iU  linux-headers-amd64  6.6.13-1~bpo12+1 amd64 Header
files for Linux amd64 configuration (meta-package)
>   iF  linux-image-6.6.13+bpo-amd64 6.6.13-1~bpo12+1 amd64 Linux
6.6 for 64-bit PCs (signed)
>   iU  linux-image-amd64    6.6.13-1~bpo12+1 amd64 Linux
for 64-bit PCs (meta-package)
>   ii  linux-kbuild-6.6.13+bpo  6.6.13-1~bpo12+1 amd64 Kbuild
infrastructure for Linux 6.6.13+bpo
>   ii  linux-libc-dev   6.6.13-1~bpo12+1 all   Linux
support headers for userspace development
> ===8<
> 
> Perhaps “iU” and “iF” are correct flags in the first column (it’s
> unclear because “man dpkg” does not document these).

The first letter "i&qu

Bug#1076555: marked as done (linux-image-6.9.9-amd64: boot crash RIP: 0010:kmem_cache_alloc)

[Debian Bug Tracking System]

Your message dated Sat, 07 Sep 2024 18:41:44 +0200
with message-id 
and subject line Re: Bug#1076555: linux-image-6.9.9-amd64: boot crash RIP: 
0010:kmem_cache_alloc
has caused the Debian Bug report #1076555,
regarding linux-image-6.9.9-amd64: boot crash RIP: 0010:kmem_cache_alloc
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.)


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

Dear Maintainer,

I just faced this boot problem on my sid system for the first time
since I updated the Linux kernel a few days ago.

I do not know if it could be something related to some hardware failure
or a possible software bug in the linux kernel or a service.

Regards,
Patrice

-- Package-specific info:
** Version:
Linux version 6.9.9-amd64 (debian-kernel@lists.debian.org)
(x86_64-linux-gnu-gcc-13 (Debian 13.3.0-3) 13.3.0, GNU ld (GNU
Binutils for Debian) 2.42.50.20240710) #1 SMP
PREEMPT_DYNAMIC Debian 6.9.9-1 (2024-07-13)

** Command line:
initrd=\be351e757dc049ffa300ddbaf0f4856a\6.9.9-amd64\initrd.img-6.9.9-amd64
root=UUID=2b8c6592-0954-4ecd-977d-738c855f3dff ro quiet splash
systemd.machine_id=be351e757d
c049ffa300ddbaf0f4856a

** Not tainted

** Kernel log:
[   12.039117] usb 1-11: Found UVC 1.50 device Integrated_Webcam_HD (1bcf:28c4)
[   12.059706] Intel(R) Wireless WiFi driver for Linux
[   12.059850] iwlwifi :6f:00.0: enabling device ( -> 0002)
[   12.068383] iwlwifi :6f:00.0: Detected crf-id 0x3617, cnv-id
0x100530 wfpm id 0x8000
[   12.068487] iwlwifi :6f:00.0: PCI dev 2723/4080, rev=0x340, rfid=0x10a100
[   12.073697] iwlwifi :6f:00.0: TLV_FW_FSEQ_VERSION: FSEQ
Version: 89.3.35.37
[   12.074053] iwlwifi :6f:00.0: firmware: failed to load
iwl-debug-yoyo.bin (-2)
[   12.074160] iwlwifi :6f:00.0: firmware: failed to load
iwl-debug-yoyo.bin (-2)
[   12.074162] iwlwifi :6f:00.0: loaded firmware version
77.a20fb07d.0 cc-a0-77.ucode op_mode iwlmvm
[   12.080445] Bluetooth: Core ver 2.22
[   12.080462] NET: Registered PF_BLUETOOTH protocol family
[   12.080463] Bluetooth: HCI device and connection manager initialized
[   12.080466] Bluetooth: HCI socket layer initialized
[   12.080468] Bluetooth: L2CAP socket layer initialized
[   12.080470] Bluetooth: SCO socket layer initialized
[   12.113923] usb 1-11: Found UVC 1.50 device Integrated_Webcam_HD (1bcf:28c4)
[   12.131467] usbcore: registered new interface driver uvcvideo
[   12.277127] iwlwifi :6f:00.0: Detected Intel(R) Wi-Fi 6 AX200
160MHz, REV=0x340
[   12.277169] thermal thermal_zone10: failed to read out thermal zone (-61)
[   12.351469] EXT4-fs (sda): mounted filesystem
cd65fcb3-29d2-4aa9-9283-c5779d95a14f r/w with ordered data mode. Quota
mode: none.
[   12.388912] audit: type=1400 audit(1721324237.855:2):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/bin/lxc-start" pid=776 comm="apparmo
r_parser"
[   12.388933] audit: type=1400 audit(1721324237.855:3):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/bin/lxc-copy" pid=775 comm="apparmor
_parser"
[   12.389739] audit: type=1400 audit(1721324237.859:4):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="torbrowser_tor" pid=772 comm="apparmor_pa
rser"
[   12.389938] audit: type=1400 audit(1721324237.859:5):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="nvidia_modprobe" pid=769 comm="apparmor_p
arser"
[   12.389942] audit: type=1400 audit(1721324237.859:6):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="nvidia_modprobe//kmod" pid=769 comm="appa
rmor_parser"
[   12.389943] audit: type=1400 audit(1721324237.859:7):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="lsb_release" pid=767 comm="apparmor_parse
r"
[   12.390294] audit: type=1400 audit(1721324237.859:8):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/bin/man" pid=777 comm="apparmor_pars
er"
[   12.390297] audit: type=1400 audit(1721324237.859:9):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="man_filter" pid

Processed: found 1070685 in 6.10.6-1

[Debian Bug Tracking System]

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

> found 1070685 6.10.6-1
Bug #1070685 [src:linux] linux-image-6.1.0-21-amd64: Found Trace in the logs 
about br_netfilter and nf_conntrack
Marked as found in versions linux/6.10.6-1.
> thanks
Stopping processing here.

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

Processed: tagging 1070685

[Debian Bug Tracking System]

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

> tags 1070685 - moreinfo
Bug #1070685 [src:linux] linux-image-6.1.0-21-amd64: Found Trace in the logs 
about br_netfilter and nf_conntrack
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: closing 1079183

[Debian Bug Tracking System]

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

> close 1079183 6.10.7-1
Bug #1079183 [src:linux] linux-image-amd64: Bluetooth is disabled
Marked as fixed in versions linux/6.10.7-1.
Bug #1079183 [src:linux] linux-image-amd64: Bluetooth is disabled
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#1070685: linux-image-6.1.0-21-amd64: Found Trace in the logs about br_netfilter and nf_conntrack

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1070685 [src:linux] linux-image-6.1.0-21-amd64: Found Trace in the logs 
about br_netfilter and nf_conntrack
Added tag(s) moreinfo.

-- 
1070685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1080975: upgrade 6.1.106 to 6.10.6 failed

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 udev
Bug #1080975 [linux-image-amd64] upgrade 6.1.106 to 6.10.6 failed
Bug reassigned from package 'linux-image-amd64' to 'udev'.
No longer marked as found in versions linux-signed-amd64/6.10.6+1.
Ignoring request to alter fixed versions of bug #1080975 to the same values 
previously set

-- 
1080975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1080388 to udev

[Debian Bug Tracking System]

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

> reassign 1080388 udev
Bug #1080388 [src:linux] linux-image-6.10.6-amd64: Module parameters in 
/etc/modprobe.d/ are not configured
Bug reassigned from package 'src:linux' to 'udev'.
No longer marked as found in versions linux/6.10.6-1.
Ignoring request to alter fixed versions of bug #1080388 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: bug 1079686 is forwarded to https://gitlab.freedesktop.org/drm/nouveau/-/issues/384

[Debian Bug Tracking System]

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

> forwarded 1079686 https://gitlab.freedesktop.org/drm/nouveau/-/issues/384
Bug #1079686 [src:linux] nouveau: fifo: fault 01 [WRITE] at 00068000 
engine 03 [IFB] client 08 [HUB/HOST_CPU_NB]
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/drm/nouveau/-/issues/384'.
> thanks
Stopping processing here.

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

Processed: tagging 1079167

[Debian Bug Tracking System]

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

> tags 1079167 - moreinfo
Bug #1079167 [src:linux] linux-image-6.10.4-amd64: vmwgfx crash and black screen
Bug #1080147 [src:linux] 
/usr/lib/modules/6.10.6-amd64/kernel/drivers/gpu/drm/vmwgfx: Black screen on 
VMware guests - Command buffer error on vmwgfx
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1076110: Confirmed, also affects keyboard backlight

[Debian Bug Tracking System]

Processing control commands:

> notfixed 1076110 6.10.7-1
Bug #1076110 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-6.9.8-amd64: Battery care and some function keys not working on LG 
Gram with kernel 6.9.x
No longer marked as fixed in versions linux/6.10.7-1.
> fixed 1076110 6.9.11-1
Bug #1076110 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-6.9.8-amd64: Battery care and some function keys not working on LG 
Gram with kernel 6.9.x
Marked as fixed in versions linux/6.9.11-1.

-- 
1076110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 1080485, tagging 1080485

[Debian Bug Tracking System]

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

> close 1080485 6.10-1~exp1
Bug #1080485 [src:linux] linux-image-amd64: fstrim does not respect --length on 
XFS filesystems
Marked as fixed in versions linux/6.10-1~exp1.
Bug #1080485 [src:linux] linux-image-amd64: fstrim does not respect --length on 
XFS filesystems
Marked Bug as done
> tags 1080485 + upstream fixed-upstream
Bug #1080485 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-amd64: fstrim does not respect --length on XFS filesystems
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1076110: marked as done (linux-image-6.9.8-amd64: Battery care and some function keys not working on LG Gram with kernel 6.9.x)

[Debian Bug Tracking System]

Your message dated Thu, 5 Sep 2024 09:14:41 +0200
with message-id 
and subject line Re: Bug#1076110: Confirmed, also affects keyboard backlight
has caused the Debian Bug report #1076110,
regarding linux-image-6.9.8-amd64: Battery care and some function keys not 
working on LG Gram with kernel 6.9.x
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.)


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

Dear Maintainer,
I am currently running Sid on an LG Gram laptop with secure boot enabled. While 
running
a routine apt upgrade I started getting message windows during package 
installation asking
me to turn off secure boot from UEFI, or third party drivers wouldn't be 
loaded. I refused
to turn off secure boot. I believe this happened when installing the first 
kernel of the 6.9
series landed on Sid - 6.9.7 - but I'm not 100% sure. After I rebooted with 
that kernel (I
was previously on 6.8.12), battery care for my laptop stopped working. I used 
to have a value
set in KDE's systemsettings to stop charging the battery after it reached 80%, 
but this wasn't
working any more (the battery now charges to 100%), and the value on the 
systemsettings page
is set to 50% and it can't be changed. I also have TLP installed on my system 
(although usually
disabled) and upon installing the new kernel it doesn't really work with the 
following error:

+++ Battery Care
Plugin: lg-legacy
Supported features: none available
Driver usage:
* vendor (lg_laptop) = inactive (laptop not supported)

I initially debugged this issue with TLP's maintainer, and you can read the 
conversation
and the debugging steps attempted here: 
https://github.com/linrunner/TLP/issues/747
Once he suggested this may be a kernel issue I tried to reboot the laptop with 
kernel
6.8.12 and everything started working again (TLP also said that the lg_laptop 
driver was
supported and in use). Kernel 6.9.8 experiences the same issue as 6.9.7, so I 
believe something
changed and got broken in the 6.8.x -> 6.9.x jump. So far I've only talked 
about the battery
care feature being broken, but there's something else as well: the keyboard 
keys combination to
adjust screen brightness (Fn+F2 and Fn+F3) doesn't do anything any more with 
kernel 6.9, however
other key combinations, for example to adjust the volume or to turn off the 
wifi+bluetooth card,
still work.

I'm happy to help debug this issue on my hardware. In the meantime, I'll stick 
to kernel 6.8.12
so it's not an urgent matter (I don't know how many other Sid users on an LG 
Gram are out there).

Kind regards,
Iacopo


-- Package-specific info:
** Version:
Linux version 6.9.8-amd64 (debian-kernel@lists.debian.org) 
(x86_64-linux-gnu-gcc-13 (Debian 13.3.0-1) 13.3.0, GNU ld (GNU Binutils for 
Debian) 2.42.50.20240625) #1 SMP PREEMPT_DYNAMIC Debian 6.9.8-1 (2024-07-07)

** Command line:
BOOT_IMAGE=/vmlinuz-6.9.8-amd64 root=UUID=1d068a91-eadf-48a6-afd8-ad8c895f2ea0 
ro rootflags=subvol=@ quiet

** Tainted: O (4096)
 * externally-built ("out-of-tree") module was loaded

** Kernel log:
[28220.003852] PM: suspend exit
[28220.023284] ACPI Error: No handler for Region [XIN1] (9af988d1) 
[UserDefinedRegion] (20230628/evregion-126)
[28220.023304] ACPI Error: Region UserDefinedRegion (ID=143) has no handler 
(20230628/exfldio-261)
[28220.023313] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN1._TMP due to 
previous error (AE_NOT_EXIST) (20230628/psparse-529)
[28220.023934] thermal thermal_zone2: failed to read out thermal zone (-5)
[28220.030284] ACPI Error: No handler for Region [XIN1] (9af988d1) 
[UserDefinedRegion] (20230628/evregion-126)
[28220.030300] ACPI Error: Region UserDefinedRegion (ID=143) has no handler 
(20230628/exfldio-261)
[28220.030307] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to 
previous error (AE_NOT_EXIST) (20230628/psparse-529)
[28220.030618] thermal thermal_zone3: failed to read out thermal zone (-5)
[28220.567773] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[28220.567824] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[28220.567887] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90
[28220.567950] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[28819.905398] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[28819.912502] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_l

Processed: reassign 1080485 to src:linux

[Debian Bug Tracking System]

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

> reassign 1080485 src:linux 6.1.85-1
Bug #1080485 [linux-image-amd64] linux-image-amd64: fstrim does not respect 
--length on XFS filesystems
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/6.1.85+1.
Ignoring request to alter fixed versions of bug #1080485 to the same values 
previously set
Bug #1080485 [src:linux] linux-image-amd64: fstrim does not respect --length on 
XFS filesystems
Marked as found in versions linux/6.1.85-1.
> thanks
Stopping processing here.

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

Processed: reopening 1075855

[Debian Bug Tracking System]

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

> reopen 1075855
Bug #1075855 {Done: Salvatore Bonaccorso } [src:linux] 
Kernel panic caused by aacraid module prevents normal boot
Bug reopened
Ignoring request to alter fixed versions of bug #1075855 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1080438: marked as done (linux-image-6.6: Silent corruption writing files over cifs, from Raspberry Pi, while using certain compressors)

[Debian Bug Tracking System]

Your message dated Wed, 4 Sep 2024 08:31:03 +0200
with message-id 
and subject line Re: Bug#1080438: linux-image-6.6: Silent corruption writing 
files over cifs, from Raspberry Pi, while using certain compressors
has caused the Debian Bug report #1080438,
regarding linux-image-6.6: Silent corruption writing files over cifs, from 
Raspberry Pi, while using certain compressors
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.)


-- 
1080438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 1:6.6.31-1+rpt1
Severity: normal
File: linux-image-6.6
X-Debbugs-Cc: pronoiac+deb...@gmail.com

Dear Maintainer,

Short version:
I was benchmarking some compressors on Debian on a Raspberry Pi, piping to and 
from a network share on a NAS, and found that some consistently had issues 
writing to my NAS.
Specifically: lzop, pigz (parallel gzip), and pbzip2 (parallel bzip2).
This seems dependent on kernel version:
Debian 11, bullseye, kernel 6.1.21, was ok.
Debian 12, bookworm, kernel versions 6.6.20 and 6.6.31, were impacted. 

Compiling and running a mainline kernel 6.1.21 on bookworm avoided the issue. I 
don’t think Debian patches are at fault. 

There's over a year between those kernel releases. Bisecting won’t be quick, 
but it is doable. 

More details:
The Pi and NAS are directly connected by Gigabit Ethernet. Both sides are using 
self-assigned IP addresses.
The files in question are file systems, about 250 GiB.
Compression seems to work, without complaint; decompression crashes the 
process, usually within the first gig of the compressed file. It looks like the 
compressed files are corrupt.
Trying decompression during compression gets further along than it does after 
compression finishes; this might point toward something with writes and caches. 
This is a Raspberry Pi 4, with 4 GiB RAM. 
I could see "grave" severity for this, as there's potential data loss.

Previously:
* bug #1079394 looked similar, but I've already tested kernel 6.6 and seen the 
issue, so it's not the same exact bug.

-James

-- Package-specific info:
** Version:
Linux version 6.6.31+rpt-rpi-v8 (se...@raspberrypi.com) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 
1:6.6.31-1+rpt1 (2024-05-29)

** Command line:
 dma.dmachans=0x37f5 bcm2709.boardrev=0xc03112 bcm2709.serial=0x5fcff9f 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:6C:04:22 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=ttyS0,115200 
console=tty1 root=PARTUUID=7827a822-02 rootfstype=ext4 fsck.repair=yes rootwait 
quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=US

** Tainted: C (1024)
 * staging driver was loaded

** Kernel log:
[6.154450] systemd[1]: Finished systemd-sysctl.service - Apply Kernel 
Variables.
[6.192763] systemd[1]: Finished systemd-random-seed.service - Load/Save 
Random Seed.
[6.194047] systemd[1]: first-boot-complete.target - First Boot Complete was 
skipped because of an unmet condition check (ConditionFirstBoot=yes).
[6.257366] systemd[1]: Started systemd-journald.service - Journal Service.
[6.325175] systemd-journald[269]: Received client request to flush runtime 
journal.
[6.339196] systemd-journald[269]: File 
/var/log/journal/dbe1dd3f1c834c7e8fb430243fdd99ed/system.journal corrupted or 
uncleanly shut down, renaming and replacing.
[   13.720947] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   13.721222] scsi 0:0:0:1: Attached scsi generic sg1 type 13
[   13.919067] vc_sm_cma: module is from the staging directory, the quality is 
unknown, you have been warned.
[   13.953377] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[   13.953408] [vc_sm_connected_init]: start
[   13.956025] mc: Linux media interface: v0.10
[   13.956601] [vc_sm_connected_init]: installed successfully
[   13.962227] snd_bcm2835: module is from the staging directory, the quality 
is unknown, you have been warned.
[   14.093847] bcm2835_audio bcm2835_audio: card created with 8 channels
[   14.096300] videodev: Linux video capture interface: v2.00
[   14.284583] bcm2835_mmal_vchiq: module is from the staging directory, the 
quality is unknown, you have been warned.
[   14.321419] bcm2835_isp: module is from the staging directory, the quality 
is unknown, you have been warned.
[   14.390174] bcm2835-isp bcm2835-isp: Device node output[0] registered as 
/dev/video13
[   14.4

Processed: tagging 1070685

[Debian Bug Tracking System]

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

> tags 1070685 + upstream
Bug #1070685 [src:linux] linux-image-6.1.0-21-amd64: Found Trace in the logs 
about br_netfilter and nf_conntrack
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: tagging 980555

[Debian Bug Tracking System]

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

> tags 980555 - moreinfo
Bug #980555 [src:linux] Missing ec_sys module
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#1078997: marked as done (gretap tunnel with checksum enabled: some packets have zero checksum)

[Debian Bug Tracking System]

Your message dated Tue, 03 Sep 2024 03:16:14 +0200
with message-id 
and subject line Re: Bug#1078997: gretap tunnel with checksum enabled: some 
packets have zero checksum
has caused the Debian Bug report #1078997,
regarding gretap tunnel with checksum enabled: some packets have zero checksum
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.)


-- 
1078997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iproute2
Version: 6.1.0-3
 
I have 2 servers named potok1 and potok2. Each of them has many network 
interfaces:
potok1:
ip -br a
lo   UNKNOWN127.0.0.1/8 ::1/128 
ens5f0   UP 172.16.1.1/24 fe80::b696:91ff:fe94:3a74/64 
ens5f1   DOWN   172.16.2.1/24 fe80::b696:91ff:fe94:3a75/64 
ens5f2   DOWN   172.16.3.1/24 fe80::b696:91ff:fe94:3a76/64 
ens5f3   DOWN   172.16.4.1/24 
ens3f0   DOWN   172.16.5.1/24 fe80::b696:91ff:fe94:3590/64 
ens3f1   DOWN   172.16.6.1/24 fe80::b696:91ff:fe94:3591/64 
ens3f2   DOWN   172.16.7.1/24 fe80::b696:91ff:fe94:3592/64 
ens3f3   DOWN   172.16.8.1/24 fe80::b696:91ff:fe94:3593/64 
enp5s0   UP 10.10.36.62/24 
enp6s0   UP 172.16.0.1/24 fe80::6d4:c4ff:fe5b:dfc5/64 
 
potok2:
ip -br a
lo   UNKNOWN127.0.0.1/8 ::1/128 
ens5f0   UP 172.16.1.2/24 fe80::b696:91ff:fe94:36c4/64 
ens5f1   DOWN   172.16.2.2/24 fe80::b696:91ff:fe94:36c5/64 
ens5f2   DOWN   172.16.3.2/24 fe80::b696:91ff:fe94:36c6/64 
ens5f3   DOWN   172.16.4.2/24 
ens3f0   DOWN   172.16.5.2/24 fe80::b696:91ff:fe94:361c/64 
ens3f1   DOWN   172.16.6.2/24 fe80::b696:91ff:fe94:361d/64 
ens3f2   DOWN   172.16.7.2/24 fe80::b696:91ff:fe94:361e/64 
ens3f3   DOWN   172.16.8.2/24 fe80::b696:91ff:fe94:361f/64 
enp5s0   UP 10.10.36.78/24 fe80::5a05:5f0e:95f2:112d/64 
enp6s0   UP 172.16.0.2/24 fe80::6d4:c4ff:fe5b:f093/64 
 
The ens5f0 interfaces of these servers are connected via switch.
 
I configure potok1 using the following commands:
 
sudo ip link add tap12 type gretap csum local 172.16.1.1 remote 172.16.1.2
sudo ip addr add 192.168.0.1/30 dev tap12
sudo ip link set ens5f3 down
sudo ip link set tap12 up
sudo ip route add 172.16.4.0/24 via 192.168.0.2
sudo ip addr del fe80::64bf:5eff:fe2c:c18e/64 dev tap12 #Don't want IPv6 for 
tunnel interface
 
I configure potok2 using the following commands:
 
sudo ip link add tap21 type gretap csum local 172.16.1.2 remote 172.16.1.1
sudo ip addr add 192.168.0.2/30 dev tap21
sudo ip link set ens5f3 down
sudo ip link set tap21 up
sudo ip route add 172.16.4.0/24 via 192.168.0.1
sudo ip addr del fe80::3ca5:93ff:fe79:2602/64 dev tap21 #Don't want IPv6 for 
tunnel interface
 
Then I ping potok2 from potok1:
ping 172.16.4.2 -c 1
 
I expect that ICMP packets will trip through gretap tunnel there and back and 
have Checksum Present flag (see RFC 1701 Generic Routing Encapsulation) set. I 
checked this using tcpdump utility and this is as expected, but I discovered 
problem with GRE Checksum field.
 
Expected behavior: 
These tunneled ICMP packets have GRE Checksum field (see RFC 1701) populated 
with a correct value.
 
Observed behavior:
For ICMP echo request packet: as expected. For ICMP echo reply packet: GRE 
Checksum field is zero!
 
tcpdump utility on potok2 server gave me the following output:
 
sudo tcpdump -e -n -v -xx -i ens5f0
 
19:08:33.665503 b4:96:91:94:3a:74 > b4:96:91:94:36:c4, ethertype IPv4 (0x0800), 
length 140: (tos 0x0, ttl 64, id 6361, offset 0, flags [DF], proto GRE (47), 
length 126)
172.16.1.1 > 172.16.1.2: GREv0, Flags [checksum present], sum 0x940b, off 
0x0, proto TEB (0x6558), length 106
66:bf:5e:2c:c1:8e > 3e:a5:93:79:26:02, ethertype IPv4 (0x0800), length 98: 
(tos 0x0, ttl 64, id 58932, offset 0, flags [DF], proto ICMP (1), length 84)
192.168.0.1 > 172.16.4.2: ICMP echo request, id 58579, seq 1, length 64
0x:  b496 9194 36c4 b496 9194 3a74 0800 4500
0x0010:  007e 18d9 4000 402f c754 ac10 0101 ac10
0x0020:  0102 8000 6558 940b  3ea5 9379 2602
0x0030:  66bf 5e2c c18e 0800 4500 0054 e634 4000
0x0040:  4001 e3b8 c0a8 0001 ac10 0402 0800 77f8
0x0050:  e4d3 0001 01b3 ab66   2546 0a00
0x0060:    1011 1213 1415 1617 1819 1a1b
0x0070:  1c1d 1e1f 20

Processed: Re: Missing ec_sys module

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #980555 [src:linux] Missing ec_sys module
Added tag(s) patch.

-- 
980555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems