Processed: Re: Bug#1082647: copy_exec: [regression] ignores trailing slash, installs file as directory name
Processing control commands: > tag -1 confirmed Bug #1082647 [initramfs-tools-core] copy_exec: [regression] ignores trailing slash, installs file as directory name Added tag(s) confirmed. > affects -1 release.debian.org Bug #1082647 [initramfs-tools-core] copy_exec: [regression] ignores trailing slash, installs file as directory name Added indication that 1082647 affects release.debian.org -- 1082647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1082001: linux-image-6.1.0-25-amd64: TOMOYO LSM rejects execveat(AT_EMPTY_PATH) inside chroot
Processing control commands: > tag -1 upstream Bug #1082001 [src:linux] linux-image-6.1.0-25-amd64: TOMOYO LSM rejects execveat(AT_EMPTY_PATH) inside chroot Added tag(s) upstream. -- 1082001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[bts-link] source package src:linux
# # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #1082081 (http://bugs.debian.org/1082081) # Bug title: Performance issues on VM (virtio) # * http://bugzilla.kernel.org/show_bug.cgi?id=219129 # * remote status changed: (?) -> NEW usertags 1082081 + status-NEW thanks
Processed: reassign 1081836 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1081836 src:linux Bug #1081836 [linux-image-6.10.9-1-arm64] linux-image-6.10.9-1-arm64: Please enable drivers for am64 hummingboard-t Warning: Unknown package 'linux-image-6.10.9-1-arm64' Bug reassigned from package 'linux-image-6.10.9-1-arm64' to 'src:linux'. No longer marked as found in versions linux-image-6.10.9-arm64. Ignoring request to alter fixed versions of bug #1081836 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1081836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
linux-signed-arm64_6.10.11+1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 22 Sep 2024 16:24:33 +0200 Source: linux-signed-arm64 Architecture: source Version: 6.10.11+1 Distribution: sid Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-arm64 (6.10.11+1) unstable; urgency=medium . * Sign kernel from linux 6.10.11-1 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.10.10 - libfs: fix get_stashed_dentry() - sch/netem: fix use after free in netem_dequeue - xfs: xfs_finobt_count_blocks() walks the wrong btree - net: ethernet: ti: am65-cpsw: Fix NULL dereference on XDP_TX - net: microchip: vcap: Fix use-after-free error in kunit test - net: ethernet: ti: am65-cpsw: fix XDP_DROP, XDP_TX and XDP_REDIRECT - ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object - [x86] KVM: x86: Acquire kvm->srcu when handling KVM_SET_VCPU_EVENTS - [x86] KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE - [x86] KVM: SVM: Don't advertise Bus Lock Detect to guest if SVM support is missing - ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices - ALSA: hda/realtek: add patch for internal mic in Lenovo V145 - ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx - ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP - ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx - [powerpc*] qspinlock: Fix deadlock in MCS queue - smb: client: fix double put of @cfile in smb2_set_path_size() - ksmbd: unset the binding mark of a reused connection - ksmbd: Unlock on in ksmbd_tcp_set_interfaces() - ata: libata: Fix memory leak for error path in ata_host_alloc() - [x86] tdx: Fix data leak in mmio_read() - [x86] perf/x86/intel: Limit the period on Haswell - [arm64,armhf] irqchip/gic-v2m: Fix refcount leak in gicv2m_of_init() - [riscv64] irqchip/sifive-plic: Probe plic driver early for Allwinner D1 platform - [x86] kaslr: Expose and use the end of the physical memory address space - rtmutex: Drop rt_mutex::wait_lock before scheduling - irqchip/riscv-aplic: Fix an IS_ERR() vs NULL bug in probe() - nvme-pci: Add sleep quirk for Samsung 990 Evo - Revert "Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE" - Bluetooth: MGMT: Ignore keys being loaded with invalid type - mmc: core: apply SD quirks earlier during probe - mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K - mmc: sdhci-of-aspeed: fix module autoloading - mmc: cqhci: Fix checking of CQHCI_HALT state - fuse: update stats for pages in dropped aux writeback list - fuse: disable the combination of passthrough and writeback cache - fuse: check aborted connection before adding requests to pending list for resending - fuse: use unsigned type for getxattr/listxattr size truncation - fuse: fix memory leak in fuse_create_open - fuse: clear PG_uptodate when using a stolen page - [x86] ASoC: Intel: Boards: Fix NULL pointer deref in BYT/CHT boards harder - [riscv64] misaligned: Restrict user access to kernel memory - [riscv64] clk: starfive: jh7110-sys: Add notifier for PLL0 clock - [arm64] clk: qcom: clk-alpha-pll: Fix the pll post div mask - [arm64] clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API - [arm64] pinctrl: qcom: x1e80100: Bypass PDC wakeup parent for now - can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open - mm: vmalloc: optimize vmap_lazy_nr arithmetic when purging each vmap_area - alloc_tag: fix allocation tag reporting when CONFIG_MODULES=n - codetag: debug: mark codetags for poisoned page as empty - maple_tree: remove rcu_read_lock() from mt_validate() - kexec_file: fix elfcorehdr digest exclusion when CONFIG_CRASH_HOTPLUG=y - mm: vmalloc: ensure vmap_block is initialised before adding to queue - mm/slub: add check for s->flags in the alloc_tagging_slab_free_hook - Revert "mm: skip CMA pages when they are not available" - spi: rockchip: Resolve unbalanced runtime PM / system PM handling - tracing/osnoise: Use a cpumask to know what threads are kthreads - tracing/timerlat: Only clear timer if a kthread exists - tracing: Avoid possible softlockup in tracing_iter_reset() - tracing/timerlat: Add interface_lock around clearing of kthread in stop_kthread() - userfaultfd: don't BUG_ON() if khugepaged yanks our page table - userfaultfd: fix checks for huge PMDs - fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF - eventfs: Use list_del_rcu() for SRCU protected list
Processed: submitter 1041484
Processing commands for cont...@bugs.debian.org: > submitter 1041484 xiao sheng wen(肖盛文) Bug #1041484 [src:linux] kernel: hpet_acpi_add: no address or irqs in _CRS Changed Bug submitter to 'xiao sheng wen(肖盛文) ' from '"Al Ma" '. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of linux-signed-arm64_6.10.11+1_source.changes
linux-signed-arm64_6.10.11+1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_6.10.11+1.dsc linux-signed-arm64_6.10.11+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-signed-arm64_6.10.11+1_source.changes is NEW
Mapping sid to unstable. binary:ata-modules-6.10.11-arm64-di is NEW. binary:btrfs-modules-6.10.11-arm64-di is NEW. binary:cdrom-core-modules-6.10.11-arm64-di is NEW. binary:crc-modules-6.10.11-arm64-di is NEW. binary:crypto-dm-modules-6.10.11-arm64-di is NEW. binary:crypto-modules-6.10.11-arm64-di is NEW. binary:efi-modules-6.10.11-arm64-di is NEW. binary:event-modules-6.10.11-arm64-di is NEW. binary:ext4-modules-6.10.11-arm64-di is NEW. binary:f2fs-modules-6.10.11-arm64-di is NEW. binary:fat-modules-6.10.11-arm64-di is NEW. binary:fb-modules-6.10.11-arm64-di is NEW. binary:i2c-modules-6.10.11-arm64-di is NEW. binary:input-modules-6.10.11-arm64-di is NEW. binary:isofs-modules-6.10.11-arm64-di is NEW. binary:jfs-modules-6.10.11-arm64-di is NEW. binary:kernel-image-6.10.11-arm64-di is NEW. binary:leds-modules-6.10.11-arm64-di is NEW. binary:linux-image-6.10.11-arm64 is NEW. binary:linux-image-6.10.11-arm64-16k is NEW. binary:linux-image-6.10.11-cloud-arm64 is NEW. binary:linux-image-6.10.11-rt-arm64 is NEW. binary:loop-modules-6.10.11-arm64-di is NEW. binary:md-modules-6.10.11-arm64-di is NEW. binary:mmc-modules-6.10.11-arm64-di is NEW. binary:multipath-modules-6.10.11-arm64-di is NEW. binary:nbd-modules-6.10.11-arm64-di is NEW. binary:nic-modules-6.10.11-arm64-di is NEW. binary:nic-shared-modules-6.10.11-arm64-di is NEW. binary:nic-usb-modules-6.10.11-arm64-di is NEW. binary:nic-wireless-modules-6.10.11-arm64-di is NEW. binary:ppp-modules-6.10.11-arm64-di is NEW. binary:sata-modules-6.10.11-arm64-di is NEW. binary:scsi-core-modules-6.10.11-arm64-di is NEW. binary:scsi-modules-6.10.11-arm64-di is NEW. binary:scsi-nic-modules-6.10.11-arm64-di is NEW. binary:sound-modules-6.10.11-arm64-di is NEW. binary:speakup-modules-6.10.11-arm64-di is NEW. binary:squashfs-modules-6.10.11-arm64-di is NEW. binary:udf-modules-6.10.11-arm64-di is NEW. binary:uinput-modules-6.10.11-arm64-di is NEW. binary:usb-modules-6.10.11-arm64-di is NEW. binary:usb-serial-modules-6.10.11-arm64-di is NEW. binary:usb-storage-modules-6.10.11-arm64-di is NEW. binary:xfs-modules-6.10.11-arm64-di is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports pgpedTPM5PIqC.pgp Description: PGP signature
linux-signed-amd64_6.10.11+1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 22 Sep 2024 16:24:33 +0200 Source: linux-signed-amd64 Architecture: source Version: 6.10.11+1 Distribution: sid Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-amd64 (6.10.11+1) unstable; urgency=medium . * Sign kernel from linux 6.10.11-1 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.10.10 - libfs: fix get_stashed_dentry() - sch/netem: fix use after free in netem_dequeue - xfs: xfs_finobt_count_blocks() walks the wrong btree - net: ethernet: ti: am65-cpsw: Fix NULL dereference on XDP_TX - net: microchip: vcap: Fix use-after-free error in kunit test - net: ethernet: ti: am65-cpsw: fix XDP_DROP, XDP_TX and XDP_REDIRECT - ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object - [x86] KVM: x86: Acquire kvm->srcu when handling KVM_SET_VCPU_EVENTS - [x86] KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE - [x86] KVM: SVM: Don't advertise Bus Lock Detect to guest if SVM support is missing - ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices - ALSA: hda/realtek: add patch for internal mic in Lenovo V145 - ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx - ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP - ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx - [powerpc*] qspinlock: Fix deadlock in MCS queue - smb: client: fix double put of @cfile in smb2_set_path_size() - ksmbd: unset the binding mark of a reused connection - ksmbd: Unlock on in ksmbd_tcp_set_interfaces() - ata: libata: Fix memory leak for error path in ata_host_alloc() - [x86] tdx: Fix data leak in mmio_read() - [x86] perf/x86/intel: Limit the period on Haswell - [arm64,armhf] irqchip/gic-v2m: Fix refcount leak in gicv2m_of_init() - [riscv64] irqchip/sifive-plic: Probe plic driver early for Allwinner D1 platform - [x86] kaslr: Expose and use the end of the physical memory address space - rtmutex: Drop rt_mutex::wait_lock before scheduling - irqchip/riscv-aplic: Fix an IS_ERR() vs NULL bug in probe() - nvme-pci: Add sleep quirk for Samsung 990 Evo - Revert "Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE" - Bluetooth: MGMT: Ignore keys being loaded with invalid type - mmc: core: apply SD quirks earlier during probe - mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K - mmc: sdhci-of-aspeed: fix module autoloading - mmc: cqhci: Fix checking of CQHCI_HALT state - fuse: update stats for pages in dropped aux writeback list - fuse: disable the combination of passthrough and writeback cache - fuse: check aborted connection before adding requests to pending list for resending - fuse: use unsigned type for getxattr/listxattr size truncation - fuse: fix memory leak in fuse_create_open - fuse: clear PG_uptodate when using a stolen page - [x86] ASoC: Intel: Boards: Fix NULL pointer deref in BYT/CHT boards harder - [riscv64] misaligned: Restrict user access to kernel memory - [riscv64] clk: starfive: jh7110-sys: Add notifier for PLL0 clock - [arm64] clk: qcom: clk-alpha-pll: Fix the pll post div mask - [arm64] clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API - [arm64] pinctrl: qcom: x1e80100: Bypass PDC wakeup parent for now - can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open - mm: vmalloc: optimize vmap_lazy_nr arithmetic when purging each vmap_area - alloc_tag: fix allocation tag reporting when CONFIG_MODULES=n - codetag: debug: mark codetags for poisoned page as empty - maple_tree: remove rcu_read_lock() from mt_validate() - kexec_file: fix elfcorehdr digest exclusion when CONFIG_CRASH_HOTPLUG=y - mm: vmalloc: ensure vmap_block is initialised before adding to queue - mm/slub: add check for s->flags in the alloc_tagging_slab_free_hook - Revert "mm: skip CMA pages when they are not available" - spi: rockchip: Resolve unbalanced runtime PM / system PM handling - tracing/osnoise: Use a cpumask to know what threads are kthreads - tracing/timerlat: Only clear timer if a kthread exists - tracing: Avoid possible softlockup in tracing_iter_reset() - tracing/timerlat: Add interface_lock around clearing of kthread in stop_kthread() - userfaultfd: don't BUG_ON() if khugepaged yanks our page table - userfaultfd: fix checks for huge PMDs - fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF - eventfs: Use list_del_rcu() for SRCU protected list
Processing of linux-signed-amd64_6.10.11+1_source.changes
linux-signed-amd64_6.10.11+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_6.10.11+1.dsc linux-signed-amd64_6.10.11+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-signed-amd64_6.10.11+1_source.changes is NEW
Mapping sid to unstable. binary:acpi-modules-6.10.11-amd64-di is NEW. binary:ata-modules-6.10.11-amd64-di is NEW. binary:btrfs-modules-6.10.11-amd64-di is NEW. binary:cdrom-core-modules-6.10.11-amd64-di is NEW. binary:crc-modules-6.10.11-amd64-di is NEW. binary:crypto-dm-modules-6.10.11-amd64-di is NEW. binary:crypto-modules-6.10.11-amd64-di is NEW. binary:drm-core-modules-6.10.11-amd64-di is NEW. binary:efi-modules-6.10.11-amd64-di is NEW. binary:event-modules-6.10.11-amd64-di is NEW. binary:ext4-modules-6.10.11-amd64-di is NEW. binary:f2fs-modules-6.10.11-amd64-di is NEW. binary:fat-modules-6.10.11-amd64-di is NEW. binary:fb-modules-6.10.11-amd64-di is NEW. binary:firewire-core-modules-6.10.11-amd64-di is NEW. binary:i2c-modules-6.10.11-amd64-di is NEW. binary:input-modules-6.10.11-amd64-di is NEW. binary:isofs-modules-6.10.11-amd64-di is NEW. binary:jfs-modules-6.10.11-amd64-di is NEW. binary:kernel-image-6.10.11-amd64-di is NEW. binary:linux-image-6.10.11-amd64 is NEW. binary:linux-image-6.10.11-cloud-amd64 is NEW. binary:linux-image-6.10.11-rt-amd64 is NEW. binary:loop-modules-6.10.11-amd64-di is NEW. binary:md-modules-6.10.11-amd64-di is NEW. binary:mmc-core-modules-6.10.11-amd64-di is NEW. binary:mmc-modules-6.10.11-amd64-di is NEW. binary:mouse-modules-6.10.11-amd64-di is NEW. binary:mtd-core-modules-6.10.11-amd64-di is NEW. binary:multipath-modules-6.10.11-amd64-di is NEW. binary:nbd-modules-6.10.11-amd64-di is NEW. binary:nic-modules-6.10.11-amd64-di is NEW. binary:nic-pcmcia-modules-6.10.11-amd64-di is NEW. binary:nic-shared-modules-6.10.11-amd64-di is NEW. binary:nic-usb-modules-6.10.11-amd64-di is NEW. binary:nic-wireless-modules-6.10.11-amd64-di is NEW. binary:pata-modules-6.10.11-amd64-di is NEW. binary:pcmcia-modules-6.10.11-amd64-di is NEW. binary:pcmcia-storage-modules-6.10.11-amd64-di is NEW. binary:ppp-modules-6.10.11-amd64-di is NEW. binary:rfkill-modules-6.10.11-amd64-di is NEW. binary:sata-modules-6.10.11-amd64-di is NEW. binary:scsi-core-modules-6.10.11-amd64-di is NEW. binary:scsi-modules-6.10.11-amd64-di is NEW. binary:scsi-nic-modules-6.10.11-amd64-di is NEW. binary:serial-modules-6.10.11-amd64-di is NEW. binary:sound-modules-6.10.11-amd64-di is NEW. binary:speakup-modules-6.10.11-amd64-di is NEW. binary:squashfs-modules-6.10.11-amd64-di is NEW. binary:udf-modules-6.10.11-amd64-di is NEW. binary:uinput-modules-6.10.11-amd64-di is NEW. binary:usb-modules-6.10.11-amd64-di is NEW. binary:usb-serial-modules-6.10.11-amd64-di is NEW. binary:usb-storage-modules-6.10.11-amd64-di is NEW. binary:xfs-modules-6.10.11-amd64-di is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports pgp3fuusKqP3w.pgp Description: PGP signature
Bug#711021: marked as done (mount.nfs timeout for GETPORT is much too short)
Your message dated Sun, 22 Sep 2024 23:12:00 +0200 with message-id and subject line Re: mount.nfs timeout for GETPORT is much too short has caused the Debian Bug report #711021, regarding mount.nfs timeout for GETPORT is much too short 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.) -- 711021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.2.6-3 Severity: important This NFS client stopped being able to mount from my NFS server at boot time, around the time I upgraded them both to wheezy. I think the problem started when only the server was upgraded and was ultimately triggered by avahi-daemon being installed. Since cups now recommends avahi-daemon, this can be considered a common configuration. I took a packet capture on both sides (which matched, so no packets are being lost) and saw that: - The client makes a GETPORT call - The client retries a few times at 1 second intervals, then (if using TCP) closes the connection - About 5 seconds after the first call from the client, the server sends a reply. (strace-ing rpcbind showed it requesting a reverse DNS lookup from avahi, which apparently has a 5 second timeout for mDNS lookups. The client should have had a proper reverse DNS entry, but didn't.) - The client sends a RST (TCP) or ICMP port unreachable error (UDP) when receiving the reply The relevant functions include nfs_pmap_getport() in support/nfs/getport.c, which even has a comment to say: * 2. This version times out quickly by default. It time-limits the * connect process as well as the actual RPC call, and even allows the * caller to specify the timeout. I don't know why it does this, though perhaps the intent was to fail-over quickly when auto-detecting whether the remote portmap/rpcbind uses TCP or UDP. But having failed to query on both protocols, the timeout ought to be increased when retrying. Ben. -- 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 46254 status 1000241 tcp 58492 status 1000211 udp 33374 nlockmgr 1000213 udp 33374 nlockmgr 1000214 udp 33374 nlockmgr 1000211 tcp 40195 nlockmgr 1000213 tcp 40195 nlockmgr 1000214 tcp 40195 nlockmgr -- /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 -- shadbolt:/home /home nfs nfsvers=3,nodev,nosuid,mountproto=tcp 0 0 shadbolt:/usr/local /usr/local nfs nfsvers=3,nodev,nosuid,mountproto=tcp 0 0 -- /proc/mounts -- rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 shadbolt:/home /home nfs rw,nosuid,nodev,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.2.1,mountvers=3,mountport=33045,mountproto=tcp,local_lock=none,addr=192.168.2.1 0 0 shadbolt:/usr/local /usr/local nfs rw,nosuid,nodev,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.2.1,mountvers=3,mountport=33045,mountproto=tcp,local_lock=none,addr=192.168.2.1 0 0 -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 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-7 ii libevent-2.0-5 2.0.19-stable-3 ii libgssglue1 0.4-2 ii libk5crypto31.10.1+dfsg-5 ii libkeyutils11.5.5-3 ii libkrb5-3 1.10.1+dfsg-5 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
Processed: bug 1041484 is forwarded to https://lore.kernel.org/lkml/bb1ee774f6b5a00a3a735389b14e8cf86d5ca187.ca...@decadent.org.uk/T/
Processing commands for cont...@bugs.debian.org: > forwarded 1041484 > https://lore.kernel.org/lkml/bb1ee774f6b5a00a3a735389b14e8cf86d5ca187.ca...@decadent.org.uk/T/ Bug #1041484 [src:linux] kernel: hpet_acpi_add: no address or irqs in _CRS Set Bug forwarded-to-address to 'https://lore.kernel.org/lkml/bb1ee774f6b5a00a3a735389b14e8cf86d5ca187.ca...@decadent.org.uk/T/'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1081826 is minor
Processing commands for cont...@bugs.debian.org: > severity 1081826 minor Bug #1081826 [linux-libc-dev] linux-libc-dev ships header files not needed for 99% of it's users Severity set to 'minor' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1081826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1081705 to Warning "scheduling while atomic" in intel_thermal driver with Linux 6.9+ and RT
Processing commands for cont...@bugs.debian.org: > retitle 1081705 Warning "scheduling while atomic" in intel_thermal driver > with Linux 6.9+ and RT Bug #1081705 [src:linux] Call Trace: dump_stack_lvl+0x64/0x80 RIP: 0010:poll_idle+0x68/0xc0 Bug #1076483 [src:linux] Call Trace on rt kernel, CPU Intel 13th Gen Intel(R) Core(TM) i5-1340P Changed Bug title to 'Warning "scheduling while atomic" in intel_thermal driver with Linux 6.9+ and RT' from 'Call Trace: dump_stack_lvl+0x64/0x80 RIP: 0010:poll_idle+0x68/0xc0'. Changed Bug title to 'Warning "scheduling while atomic" in intel_thermal driver with Linux 6.9+ and RT' from 'Call Trace on rt kernel, CPU Intel 13th Gen Intel(R) Core(TM) i5-1340P'. > 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
Processed: retitle 1076372 to Corruption of Longsys/Lexar NM790 NVMe drive with Linux 6.5+
Processing commands for cont...@bugs.debian.org: > retitle 1076372 Corruption of Longsys/Lexar NM790 NVMe drive with Linux 6.5+ Bug #1076372 [src:linux] linux-image-6.5.0-0.deb12.4-amd64: ext4 file corruption with newer kernels Changed Bug title to 'Corruption of Longsys/Lexar NM790 NVMe drive with Linux 6.5+' from 'linux-image-6.5.0-0.deb12.4-amd64: ext4 file corruption with newer kernels'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1076372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1081833: linux-image-6.1.0-25-amd64: regression on linux-image-6.1.0-25.amd64 regular cracks in HDMI sound during playback - 6.1.0-23 works.
Processing control commands: > tags -1 + moreinfo Bug #1081833 [src:linux] linux-image-6.1.0-25-amd64: regression on linux-image-6.1.0-25.amd64 regular cracks in HDMI sound during playback - 6.1.0-23 works. Added tag(s) moreinfo. -- 1081833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
linux_6.10.11-1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 22 Sep 2024 16:24:33 +0200 Source: linux Architecture: source Version: 6.10.11-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux (6.10.11-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.10.10 - libfs: fix get_stashed_dentry() - sch/netem: fix use after free in netem_dequeue - xfs: xfs_finobt_count_blocks() walks the wrong btree - net: ethernet: ti: am65-cpsw: Fix NULL dereference on XDP_TX - net: microchip: vcap: Fix use-after-free error in kunit test - net: ethernet: ti: am65-cpsw: fix XDP_DROP, XDP_TX and XDP_REDIRECT - ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object - [x86] KVM: x86: Acquire kvm->srcu when handling KVM_SET_VCPU_EVENTS - [x86] KVM: SVM: fix emulation of msr reads/writes of MSR_FS_BASE and MSR_GS_BASE - [x86] KVM: SVM: Don't advertise Bus Lock Detect to guest if SVM support is missing - ALSA: hda/conexant: Add pincfg quirk to enable top speakers on Sirius devices - ALSA: hda/realtek: add patch for internal mic in Lenovo V145 - ALSA: hda/realtek: Enable Mute Led for HP Victus 15-fb1xxx - ALSA: hda/realtek - Fix inactive headset mic jack for ASUS Vivobook 15 X1504VAP - ALSA: hda/realtek: Support mute LED on HP Laptop 14-dq2xxx - [powerpc*] qspinlock: Fix deadlock in MCS queue - smb: client: fix double put of @cfile in smb2_set_path_size() - ksmbd: unset the binding mark of a reused connection - ksmbd: Unlock on in ksmbd_tcp_set_interfaces() - ata: libata: Fix memory leak for error path in ata_host_alloc() - [x86] tdx: Fix data leak in mmio_read() - [x86] perf/x86/intel: Limit the period on Haswell - [arm64,armhf] irqchip/gic-v2m: Fix refcount leak in gicv2m_of_init() - [riscv64] irqchip/sifive-plic: Probe plic driver early for Allwinner D1 platform - [x86] kaslr: Expose and use the end of the physical memory address space - rtmutex: Drop rt_mutex::wait_lock before scheduling - irqchip/riscv-aplic: Fix an IS_ERR() vs NULL bug in probe() - nvme-pci: Add sleep quirk for Samsung 990 Evo - Revert "Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE" - Bluetooth: MGMT: Ignore keys being loaded with invalid type - mmc: core: apply SD quirks earlier during probe - mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K - mmc: sdhci-of-aspeed: fix module autoloading - mmc: cqhci: Fix checking of CQHCI_HALT state - fuse: update stats for pages in dropped aux writeback list - fuse: disable the combination of passthrough and writeback cache - fuse: check aborted connection before adding requests to pending list for resending - fuse: use unsigned type for getxattr/listxattr size truncation - fuse: fix memory leak in fuse_create_open - fuse: clear PG_uptodate when using a stolen page - [x86] ASoC: Intel: Boards: Fix NULL pointer deref in BYT/CHT boards harder - [riscv64] misaligned: Restrict user access to kernel memory - [riscv64] clk: starfive: jh7110-sys: Add notifier for PLL0 clock - [arm64] clk: qcom: clk-alpha-pll: Fix the pll post div mask - [arm64] clk: qcom: clk-alpha-pll: Fix the trion pll postdiv set rate API - [arm64] pinctrl: qcom: x1e80100: Bypass PDC wakeup parent for now - can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open - mm: vmalloc: optimize vmap_lazy_nr arithmetic when purging each vmap_area - alloc_tag: fix allocation tag reporting when CONFIG_MODULES=n - codetag: debug: mark codetags for poisoned page as empty - maple_tree: remove rcu_read_lock() from mt_validate() - kexec_file: fix elfcorehdr digest exclusion when CONFIG_CRASH_HOTPLUG=y - mm: vmalloc: ensure vmap_block is initialised before adding to queue - mm/slub: add check for s->flags in the alloc_tagging_slab_free_hook - Revert "mm: skip CMA pages when they are not available" - spi: rockchip: Resolve unbalanced runtime PM / system PM handling - tracing/osnoise: Use a cpumask to know what threads are kthreads - tracing/timerlat: Only clear timer if a kthread exists - tracing: Avoid possible softlockup in tracing_iter_reset() - tracing/timerlat: Add interface_lock around clearing of kthread in stop_kthread() - userfaultfd: don't BUG_ON() if khugepaged yanks our page table - userfaultfd: fix checks for huge PMDs - fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF - eventfs: Use list_del_rcu() for SRCU protected list variable - net: mana: Fix error handling in mana_create_txq
Processing of linux_6.10.11-1_source.changes
linux_6.10.11-1_source.changes uploaded successfully to localhost along with the files: linux_6.10.11-1.dsc linux_6.10.11.orig.tar.xz linux_6.10.11-1.debian.tar.xz linux_6.10.11-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux_6.10.11-1_source.changes is NEW
binary:acpi-modules-6.10.11-686-di is NEW. binary:acpi-modules-6.10.11-686-pae-di is NEW. binary:affs-modules-6.10.11-5kc-malta-di is NEW. binary:affs-modules-6.10.11-loongson-3-di is NEW. binary:affs-modules-6.10.11-mips64r2el-di is NEW. binary:affs-modules-6.10.11-mips64r6el-di is NEW. binary:affs-modules-6.10.11-octeon-di is NEW. binary:ata-modules-6.10.11-5kc-malta-di is NEW. binary:ata-modules-6.10.11-686-di is NEW. binary:ata-modules-6.10.11-686-pae-di is NEW. binary:ata-modules-6.10.11-armmp-di is NEW. binary:ata-modules-6.10.11-loongson-3-di is NEW. binary:ata-modules-6.10.11-mips64r2el-di is NEW. binary:ata-modules-6.10.11-mips64r6el-di is NEW. binary:ata-modules-6.10.11-octeon-di is NEW. binary:ata-modules-6.10.11-powerpc64le-di is NEW. binary:ata-modules-6.10.11-riscv64-di is NEW. binary:btrfs-modules-6.10.11-5kc-malta-di is NEW. binary:btrfs-modules-6.10.11-686-di is NEW. binary:btrfs-modules-6.10.11-686-pae-di is NEW. binary:btrfs-modules-6.10.11-armmp-di is NEW. binary:btrfs-modules-6.10.11-loongson-3-di is NEW. binary:btrfs-modules-6.10.11-mips64r2el-di is NEW. binary:btrfs-modules-6.10.11-mips64r6el-di is NEW. binary:btrfs-modules-6.10.11-octeon-di is NEW. binary:btrfs-modules-6.10.11-powerpc64le-di is NEW. binary:btrfs-modules-6.10.11-riscv64-di is NEW. binary:btrfs-modules-6.10.11-s390x-di is NEW. binary:cdrom-core-modules-6.10.11-5kc-malta-di is NEW. binary:cdrom-core-modules-6.10.11-686-di is NEW. binary:cdrom-core-modules-6.10.11-686-pae-di is NEW. binary:cdrom-core-modules-6.10.11-armmp-di is NEW. binary:cdrom-core-modules-6.10.11-loongson-3-di is NEW. binary:cdrom-core-modules-6.10.11-mips64r2el-di is NEW. binary:cdrom-core-modules-6.10.11-mips64r6el-di is NEW. binary:cdrom-core-modules-6.10.11-octeon-di is NEW. binary:cdrom-core-modules-6.10.11-powerpc64le-di is NEW. binary:cdrom-core-modules-6.10.11-riscv64-di is NEW. binary:cdrom-core-modules-6.10.11-s390x-di is NEW. binary:crc-modules-6.10.11-5kc-malta-di is NEW. binary:crc-modules-6.10.11-686-di is NEW. binary:crc-modules-6.10.11-686-pae-di is NEW. binary:crc-modules-6.10.11-armmp-di is NEW. binary:crc-modules-6.10.11-loongson-3-di is NEW. binary:crc-modules-6.10.11-mips64r2el-di is NEW. binary:crc-modules-6.10.11-mips64r6el-di is NEW. binary:crc-modules-6.10.11-octeon-di is NEW. binary:crc-modules-6.10.11-powerpc64le-di is NEW. binary:crc-modules-6.10.11-riscv64-di is NEW. binary:crc-modules-6.10.11-s390x-di is NEW. binary:crypto-dm-modules-6.10.11-5kc-malta-di is NEW. binary:crypto-dm-modules-6.10.11-686-di is NEW. binary:crypto-dm-modules-6.10.11-686-pae-di is NEW. binary:crypto-dm-modules-6.10.11-armmp-di is NEW. binary:crypto-dm-modules-6.10.11-loongson-3-di is NEW. binary:crypto-dm-modules-6.10.11-mips64r2el-di is NEW. binary:crypto-dm-modules-6.10.11-mips64r6el-di is NEW. binary:crypto-dm-modules-6.10.11-octeon-di is NEW. binary:crypto-dm-modules-6.10.11-powerpc64le-di is NEW. binary:crypto-dm-modules-6.10.11-riscv64-di is NEW. binary:crypto-dm-modules-6.10.11-s390x-di is NEW. binary:crypto-modules-6.10.11-5kc-malta-di is NEW. binary:crypto-modules-6.10.11-686-di is NEW. binary:crypto-modules-6.10.11-686-pae-di is NEW. binary:crypto-modules-6.10.11-armmp-di is NEW. binary:crypto-modules-6.10.11-loongson-3-di is NEW. binary:crypto-modules-6.10.11-mips64r2el-di is NEW. binary:crypto-modules-6.10.11-mips64r6el-di is NEW. binary:crypto-modules-6.10.11-octeon-di is NEW. binary:crypto-modules-6.10.11-powerpc64le-di is NEW. binary:crypto-modules-6.10.11-riscv64-di is NEW. binary:crypto-modules-6.10.11-s390x-di is NEW. binary:dasd-extra-modules-6.10.11-s390x-di is NEW. binary:dasd-modules-6.10.11-s390x-di is NEW. binary:drm-core-modules-6.10.11-5kc-malta-di is NEW. binary:drm-core-modules-6.10.11-686-di is NEW. binary:drm-core-modules-6.10.11-686-pae-di is NEW. binary:drm-core-modules-6.10.11-armmp-di is NEW. binary:drm-core-modules-6.10.11-loongson-3-di is NEW. binary:drm-core-modules-6.10.11-mips64r2el-di is NEW. binary:drm-core-modules-6.10.11-mips64r6el-di is NEW. binary:drm-core-modules-6.10.11-octeon-di is NEW. binary:drm-core-modules-6.10.11-powerpc64le-di is NEW. binary:drm-core-modules-6.10.11-riscv64-di is NEW. binary:efi-modules-6.10.11-686-di is NEW. binary:efi-modules-6.10.11-686-pae-di is NEW. binary:efi-modules-6.10.11-armmp-di is NEW. binary:efi-modules-6.10.11-riscv64-di is NEW. binary:event-modules-6.10.11-5kc-malta-di is NEW. binary:event-modules-6.10.11-686-di is NEW. binary:event-modules-6.10.11-686-pae-di is NEW. binary:event-modules-6.10.11-armmp-di is NEW. binary:event-modules-6.10.11-loongson-3-di is NEW. binary:event-modules-6.10.11-mips64r2el-di is NEW. binary:event-modules-6.10.11-mips64r6el-di is NEW. binary:event-modules-6.10.11-octeon-di is NEW. binary:event-modules-6.10.11-powerpc64le-di is NEW. binary:event-modules-6.10.11-riscv64-di is NEW. binary:ext4-modules-6.10.11-5kc-malta-di is NEW. binary:ext4-modules-6.10.11-686-di is NEW. binary:ext4-modules-6.10.11-686-pae-di is NEW. binary:ext4-modules
linux-signed-arm64_6.11+1~exp1_source.changes ACCEPTED into experimental
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Sep 2024 18:42:39 +0200 Source: linux-signed-arm64 Architecture: source Version: 6.11+1~exp1 Distribution: rc-buggy Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Changes: linux-signed-arm64 (6.11+1~exp1) experimental; urgency=medium . * Sign kernel from linux 6.11-1~exp1 . * 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/mmc/core: Enable PWRSEQ_EMMC - [arm64] drivers/phy/rockchip: Enable PHY_ROCKCHIP_SAMSUNG_HDPTX and PHY_ROCKCHIP_USBDP as module * [rt] Update to 6.11-rt7 * d/config: Update with the help of kconfigeditor2 . [ Aurelien Jarno ] * [riscv64] Enable INPUT_MISC (Closes: #1079501). . [ Bastian Blank ] * Revert "Make linux-libc-dev provide all cross packages". . [ Helge Deller ] * [hppa] Fix kernel build with CONFIG_DRM=y on parisc64. . [ Jair Gonzalez ] * [amd64] drivers/crypto/intel/iaa: Enable CRYPTO_DEV_IAA_CRYPTO (IAA Compression Accelerator Crypto Driver) (Closes: #1079272) . [ Dave Vasilevsky ] * [powerpc] Explicitly disable CRASH_DUMP on 32-bit (Closes: #1079755) . [ Ben Hutchings ] * [x86] ACPI: Enable ACPI_EC_DEBUGFS as module (Closes: #980555) * [i386] Stop building kernel packages * rtla: Switch to out-of-tree build: - Revert "tools/rtla: Restore option to set VERSION var to VERSION file's contents" - Fix installation from out-of-tree build * rtla: Enable verbose build * rtla: Build with dpkg's recommended compiler flags (regression in 6.9) * rtla: Fix missing debug symbols * rtla: Disable LTO * rtla: Set LD correctly for cross-build * objtool: Build with dpkg's recommended compiler flags (regression in 6.5.1-1¬exp1): - Revert "tools build: Clean CFLAGS and LDFLAGS for fixdep" - Update "fixdep: Allow overriding HOSTCC and HOSTLD" to clear the buildflags when overriding - d/rules.d/t/objtool: Put buildflags in the correct variables when recursing - d/rules: Delete blhc ignore regexp for objtool . [ Miao Wang ] * [loong64] Enable kernel support for LBT instructions. * [loong64] Enable KVM and para-virt support. * [loong64] Enable USB EHCI and OHCI host support. . [ Yunseong Kim ] * mm/damon: Enable DAMON, DAMON_VADDR, DAMON_PADDR, DAMON_SYSFS, DAMON_RECLAIM, DAMON_LRU_SORT . [ Miguel Bernal Marin ] * [x86] linux-cpupower: Add intel-speed-select command (Closes: #1036714) . [ Vincent Blut ] * drivers/net/wireless: Support some Wi-Fi 7 devices: enable ATH12K, MT7925E, MT7925U, MT7996E and RTW89_8922AE as modules (Closes: #1081114) . [ Emanuele Rocc
Processed: Re: Bug#1054345: linux-image-6.5.0-2-amd64: Segfault with USB Mass storage
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
Processing of linux-signed-arm64_6.11+1~exp1_source.changes
linux-signed-arm64_6.11+1~exp1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_6.11+1~exp1.dsc linux-signed-arm64_6.11+1~exp1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-signed-arm64_6.11+1~exp1_source.changes is NEW
Mapping rc-buggy to experimental. binary:ata-modules-6.11-arm64-di is NEW. binary:btrfs-modules-6.11-arm64-di is NEW. binary:cdrom-core-modules-6.11-arm64-di is NEW. binary:crc-modules-6.11-arm64-di is NEW. binary:crypto-dm-modules-6.11-arm64-di is NEW. binary:crypto-modules-6.11-arm64-di is NEW. binary:efi-modules-6.11-arm64-di is NEW. binary:event-modules-6.11-arm64-di is NEW. binary:ext4-modules-6.11-arm64-di is NEW. binary:f2fs-modules-6.11-arm64-di is NEW. binary:fat-modules-6.11-arm64-di is NEW. binary:fb-modules-6.11-arm64-di is NEW. binary:i2c-modules-6.11-arm64-di is NEW. binary:input-modules-6.11-arm64-di is NEW. binary:isofs-modules-6.11-arm64-di is NEW. binary:jfs-modules-6.11-arm64-di is NEW. binary:kernel-image-6.11-arm64-di is NEW. binary:leds-modules-6.11-arm64-di is NEW. binary:linux-image-6.11-arm64 is NEW. binary:linux-image-6.11-arm64-16k is NEW. binary:linux-image-6.11-cloud-arm64 is NEW. binary:linux-image-6.11-rt-arm64 is NEW. binary:loop-modules-6.11-arm64-di is NEW. binary:md-modules-6.11-arm64-di is NEW. binary:mmc-modules-6.11-arm64-di is NEW. binary:multipath-modules-6.11-arm64-di is NEW. binary:nbd-modules-6.11-arm64-di is NEW. binary:nic-modules-6.11-arm64-di is NEW. binary:nic-shared-modules-6.11-arm64-di is NEW. binary:nic-usb-modules-6.11-arm64-di is NEW. binary:nic-wireless-modules-6.11-arm64-di is NEW. binary:ppp-modules-6.11-arm64-di is NEW. binary:sata-modules-6.11-arm64-di is NEW. binary:scsi-core-modules-6.11-arm64-di is NEW. binary:scsi-modules-6.11-arm64-di is NEW. binary:scsi-nic-modules-6.11-arm64-di is NEW. binary:sound-modules-6.11-arm64-di is NEW. binary:speakup-modules-6.11-arm64-di is NEW. binary:squashfs-modules-6.11-arm64-di is NEW. binary:udf-modules-6.11-arm64-di is NEW. binary:uinput-modules-6.11-arm64-di is NEW. binary:usb-modules-6.11-arm64-di is NEW. binary:usb-serial-modules-6.11-arm64-di is NEW. binary:usb-storage-modules-6.11-arm64-di is NEW. binary:xfs-modules-6.11-arm64-di is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports pgpHrCp1oV15N.pgp Description: PGP signature
Processing of nfs-utils_2.7.1-3_sourceonly.changes
nfs-utils_2.7.1-3_sourceonly.changes uploaded successfully to localhost along with the files: nfs-utils_2.7.1-3.dsc nfs-utils_2.7.1-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1072573: marked as done (rpc.idmapd runs out of file descriptors)
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
nfs-utils_2.7.1-3_sourceonly.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -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- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmbtwWZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EwGAP/1c4+aQFcizzzWEJxkeH6c4NDvCu7ip1 B2T8Ki/NwXlgw5jD++zNysGJlBf49n+8AorVsIjEgfOPWCqJAYfhL0TV+ga6VA83 3ExI5l5gAGIHB7xgDWciEkyobwTR8fwFRyRpiUylySqYfbLyhYTR7TArJkGX9oLi XWXoNgEgKvj0oqGaR8oNrOyNnUIercH37BRSgOZw3g157mH3AqhQfzLDDEsJXnvH iYCb8XjQn0OwKt/HLqEXcy9sNNanx+82fhiptPliNMq6NYAKGaO1tiJts6nTyPUe oQMaVC95D9PuNvNJA+rLqzPcFbw9991NQcGxz6BqPpHey5JpdGywLrvLLllyS3Kg FZI3kJpeTXF71oQKrww5UGYu0fuw8alVTMLQETreOndRvcsQ9AcK/35cqSEc+7ys nomF18dwBPt3PRg8nZ8gRPRj1f5himm9Soiu187cSfYukGLqOKKEIjW/blu+XyLg sOVZnxTUWvJLHC6egAP9sbnae+Xfcp8LOVYs7NAqIOcpkVnB9VyvBM/mnT5vVABk WWzcWdYDyOinJoM60R0PsotqzFPSvGh+py1aoQsyTRUkvYqqHVOxE71Aw0ng6WNR l3TVDgoSllr+40A+LQtBSJoSJZljy/6Ffc0eYwmCLiXentp0AHXHvStVEtHKzzv7 VoqoMKkVIAYk =krNm -END PGP SIGNATURE- pgp9_eI85zJVi.pgp Description: PGP signature
Processed: severity of 857043 is wishlist
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
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
linux-signed-amd64_6.11+1~exp1_source.changes ACCEPTED into experimental
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Sep 2024 18:42:39 +0200 Source: linux-signed-amd64 Architecture: source Version: 6.11+1~exp1 Distribution: rc-buggy Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Changes: linux-signed-amd64 (6.11+1~exp1) experimental; urgency=medium . * Sign kernel from linux 6.11-1~exp1 . * 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/mmc/core: Enable PWRSEQ_EMMC - [arm64] drivers/phy/rockchip: Enable PHY_ROCKCHIP_SAMSUNG_HDPTX and PHY_ROCKCHIP_USBDP as module * [rt] Update to 6.11-rt7 * d/config: Update with the help of kconfigeditor2 . [ Aurelien Jarno ] * [riscv64] Enable INPUT_MISC (Closes: #1079501). . [ Bastian Blank ] * Revert "Make linux-libc-dev provide all cross packages". . [ Helge Deller ] * [hppa] Fix kernel build with CONFIG_DRM=y on parisc64. . [ Jair Gonzalez ] * [amd64] drivers/crypto/intel/iaa: Enable CRYPTO_DEV_IAA_CRYPTO (IAA Compression Accelerator Crypto Driver) (Closes: #1079272) . [ Dave Vasilevsky ] * [powerpc] Explicitly disable CRASH_DUMP on 32-bit (Closes: #1079755) . [ Ben Hutchings ] * [x86] ACPI: Enable ACPI_EC_DEBUGFS as module (Closes: #980555) * [i386] Stop building kernel packages * rtla: Switch to out-of-tree build: - Revert "tools/rtla: Restore option to set VERSION var to VERSION file's contents" - Fix installation from out-of-tree build * rtla: Enable verbose build * rtla: Build with dpkg's recommended compiler flags (regression in 6.9) * rtla: Fix missing debug symbols * rtla: Disable LTO * rtla: Set LD correctly for cross-build * objtool: Build with dpkg's recommended compiler flags (regression in 6.5.1-1¬exp1): - Revert "tools build: Clean CFLAGS and LDFLAGS for fixdep" - Update "fixdep: Allow overriding HOSTCC and HOSTLD" to clear the buildflags when overriding - d/rules.d/t/objtool: Put buildflags in the correct variables when recursing - d/rules: Delete blhc ignore regexp for objtool . [ Miao Wang ] * [loong64] Enable kernel support for LBT instructions. * [loong64] Enable KVM and para-virt support. * [loong64] Enable USB EHCI and OHCI host support. . [ Yunseong Kim ] * mm/damon: Enable DAMON, DAMON_VADDR, DAMON_PADDR, DAMON_SYSFS, DAMON_RECLAIM, DAMON_LRU_SORT . [ Miguel Bernal Marin ] * [x86] linux-cpupower: Add intel-speed-select command (Closes: #1036714) . [ Vincent Blut ] * drivers/net/wireless: Support some Wi-Fi 7 devices: enable ATH12K, MT7925E, MT7925U, MT7996E and RTW89_8922AE as modules (Closes: #1081114) . [ Emanuele Rocc
Processing of linux-signed-amd64_6.11+1~exp1_source.changes
linux-signed-amd64_6.11+1~exp1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_6.11+1~exp1.dsc linux-signed-amd64_6.11+1~exp1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-signed-amd64_6.11+1~exp1_source.changes is NEW
Mapping rc-buggy to experimental. binary:acpi-modules-6.11-amd64-di is NEW. binary:ata-modules-6.11-amd64-di is NEW. binary:btrfs-modules-6.11-amd64-di is NEW. binary:cdrom-core-modules-6.11-amd64-di is NEW. binary:crc-modules-6.11-amd64-di is NEW. binary:crypto-dm-modules-6.11-amd64-di is NEW. binary:crypto-modules-6.11-amd64-di is NEW. binary:drm-core-modules-6.11-amd64-di is NEW. binary:efi-modules-6.11-amd64-di is NEW. binary:event-modules-6.11-amd64-di is NEW. binary:ext4-modules-6.11-amd64-di is NEW. binary:f2fs-modules-6.11-amd64-di is NEW. binary:fat-modules-6.11-amd64-di is NEW. binary:fb-modules-6.11-amd64-di is NEW. binary:firewire-core-modules-6.11-amd64-di is NEW. binary:i2c-modules-6.11-amd64-di is NEW. binary:input-modules-6.11-amd64-di is NEW. binary:isofs-modules-6.11-amd64-di is NEW. binary:jfs-modules-6.11-amd64-di is NEW. binary:kernel-image-6.11-amd64-di is NEW. binary:linux-image-6.11-amd64 is NEW. binary:linux-image-6.11-cloud-amd64 is NEW. binary:linux-image-6.11-rt-amd64 is NEW. binary:loop-modules-6.11-amd64-di is NEW. binary:md-modules-6.11-amd64-di is NEW. binary:mmc-core-modules-6.11-amd64-di is NEW. binary:mmc-modules-6.11-amd64-di is NEW. binary:mouse-modules-6.11-amd64-di is NEW. binary:mtd-core-modules-6.11-amd64-di is NEW. binary:multipath-modules-6.11-amd64-di is NEW. binary:nbd-modules-6.11-amd64-di is NEW. binary:nic-modules-6.11-amd64-di is NEW. binary:nic-pcmcia-modules-6.11-amd64-di is NEW. binary:nic-shared-modules-6.11-amd64-di is NEW. binary:nic-usb-modules-6.11-amd64-di is NEW. binary:nic-wireless-modules-6.11-amd64-di is NEW. binary:pata-modules-6.11-amd64-di is NEW. binary:pcmcia-modules-6.11-amd64-di is NEW. binary:pcmcia-storage-modules-6.11-amd64-di is NEW. binary:ppp-modules-6.11-amd64-di is NEW. binary:rfkill-modules-6.11-amd64-di is NEW. binary:sata-modules-6.11-amd64-di is NEW. binary:scsi-core-modules-6.11-amd64-di is NEW. binary:scsi-modules-6.11-amd64-di is NEW. binary:scsi-nic-modules-6.11-amd64-di is NEW. binary:serial-modules-6.11-amd64-di is NEW. binary:sound-modules-6.11-amd64-di is NEW. binary:speakup-modules-6.11-amd64-di is NEW. binary:squashfs-modules-6.11-amd64-di is NEW. binary:udf-modules-6.11-amd64-di is NEW. binary:uinput-modules-6.11-amd64-di is NEW. binary:usb-modules-6.11-amd64-di is NEW. binary:usb-serial-modules-6.11-amd64-di is NEW. binary:usb-storage-modules-6.11-amd64-di is NEW. binary:xfs-modules-6.11-amd64-di is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports pgpwrcnbxZZP0.pgp Description: PGP signature
Bug#980555: marked as done (Missing ec_sys module)
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)
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)
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)
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)
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)
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)
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
linux_6.11-1~exp1_source.changes ACCEPTED into experimental
Thank you for your contribution to Debian. Accepted: -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/mmc/core: Enable PWRSEQ_EMMC - [arm64] drivers/phy/rockchip: Enable PHY_ROCKCHIP_SAMSUNG_HDPTX and PHY_ROCKCHIP_USBDP as module * [rt] Update to 6.11-rt7 * d/config: Update with the help of kconfigeditor2 . [ Aurelien Jarno ] * [riscv64] Enable INPUT_MISC (Closes: #1079501). . [ Bastian Blank ] * Revert "Make linux-libc-dev provide all cross packages". . [ Helge Deller ] * [hppa] Fix kernel build with CONFIG_DRM=y on parisc64. . [ Jair Gonzalez ] * [amd64] drivers/crypto/intel/iaa: Enable CRYPTO_DEV_IAA_CRYPTO (IAA Compression Accelerator Crypto Driver) (Closes: #1079272) . [ Dave Vasilevsky ] * [powerpc] Explicitly disable CRASH_DUMP on 32-bit (Closes: #1079755) . [ Ben Hutchings ] * [x86] ACPI: Enable ACPI_EC_DEBUGFS as module (Closes: #980555) * [i386] Stop building kernel packages * rtla: Switch to out-of-tree build: - Revert "tools/rtla: Restore option to set VERSION var to VERSION file's contents" - Fix installation from out-of-tree build * rtla: Enable verbose build * rtla: Build with dpkg's recommended compiler flags (regression in 6.9) * rtla: Fix missing debug symbols * rtla: Disable LTO * rtla: Set LD correctly for cross-build * objtool: Build with dpkg's recommended compiler flags (regression in 6.5.1-1¬exp1): - Revert "tools build: Clean CFLAGS and LDFLAGS for fixdep" - Update "fixdep: Allow overriding HOSTCC and HOSTLD" to clear the buildflags when overriding - d/rules.d/t/objtool: Put buildflags in the correct variables when recursing - d/rules: Delete blhc ignore regexp for objtool . [ Miao Wang ] * [loong64] Enable kernel support for LBT instructions. * [loong64] Enable KVM and para-virt support. * [loong64] Enable USB EHCI and OHCI host support. . [ Yunseong Kim ] * mm/damon: Enable DAMON, DAMON_VADDR, DAMON_PADDR, DAMON_SYSFS, DAMON_RECLAIM, DAMON_LRU_SORT . [ Miguel Bernal Marin ] * [x86] linux-cpupower: Add intel-speed-select command (Closes: #1036714) . [ Vincent Blut ] * drivers/net/wireless: Support some Wi-Fi 7 devices: enable ATH12K, MT7925E, MT7925U, MT7996E and RTW89_8922AE as modules (Closes: #1081114) . [ Emanuele Rocca ]
linux_6.11-1~exp1_source.changes is NEW
binary:affs-modules-6.11-5kc-malta-di is NEW. binary:affs-modules-6.11-loongson-3-di is NEW. binary:affs-modules-6.11-mips64r2el-di is NEW. binary:affs-modules-6.11-mips64r6el-di is NEW. binary:affs-modules-6.11-octeon-di is NEW. binary:ata-modules-6.11-5kc-malta-di is NEW. binary:ata-modules-6.11-armmp-di is NEW. binary:ata-modules-6.11-loongson-3-di is NEW. binary:ata-modules-6.11-mips64r2el-di is NEW. binary:ata-modules-6.11-mips64r6el-di is NEW. binary:ata-modules-6.11-octeon-di is NEW. binary:ata-modules-6.11-powerpc64le-di is NEW. binary:ata-modules-6.11-riscv64-di is NEW. binary:btrfs-modules-6.11-5kc-malta-di is NEW. binary:btrfs-modules-6.11-armmp-di is NEW. binary:btrfs-modules-6.11-loongson-3-di is NEW. binary:btrfs-modules-6.11-mips64r2el-di is NEW. binary:btrfs-modules-6.11-mips64r6el-di is NEW. binary:btrfs-modules-6.11-octeon-di is NEW. binary:btrfs-modules-6.11-powerpc64le-di is NEW. binary:btrfs-modules-6.11-riscv64-di is NEW. binary:btrfs-modules-6.11-s390x-di is NEW. binary:cdrom-core-modules-6.11-5kc-malta-di is NEW. binary:cdrom-core-modules-6.11-armmp-di is NEW. binary:cdrom-core-modules-6.11-loongson-3-di is NEW. binary:cdrom-core-modules-6.11-mips64r2el-di is NEW. binary:cdrom-core-modules-6.11-mips64r6el-di is NEW. binary:cdrom-core-modules-6.11-octeon-di is NEW. binary:cdrom-core-modules-6.11-powerpc64le-di is NEW. binary:cdrom-core-modules-6.11-riscv64-di is NEW. binary:cdrom-core-modules-6.11-s390x-di is NEW. binary:crc-modules-6.11-5kc-malta-di is NEW. binary:crc-modules-6.11-armmp-di is NEW. binary:crc-modules-6.11-loongson-3-di is NEW. binary:crc-modules-6.11-mips64r2el-di is NEW. binary:crc-modules-6.11-mips64r6el-di is NEW. binary:crc-modules-6.11-octeon-di is NEW. binary:crc-modules-6.11-powerpc64le-di is NEW. binary:crc-modules-6.11-riscv64-di is NEW. binary:crc-modules-6.11-s390x-di is NEW. binary:crypto-dm-modules-6.11-5kc-malta-di is NEW. binary:crypto-dm-modules-6.11-armmp-di is NEW. binary:crypto-dm-modules-6.11-loongson-3-di is NEW. binary:crypto-dm-modules-6.11-mips64r2el-di is NEW. binary:crypto-dm-modules-6.11-mips64r6el-di is NEW. binary:crypto-dm-modules-6.11-octeon-di is NEW. binary:crypto-dm-modules-6.11-powerpc64le-di is NEW. binary:crypto-dm-modules-6.11-riscv64-di is NEW. binary:crypto-dm-modules-6.11-s390x-di is NEW. binary:crypto-modules-6.11-5kc-malta-di is NEW. binary:crypto-modules-6.11-armmp-di is NEW. binary:crypto-modules-6.11-loongson-3-di is NEW. binary:crypto-modules-6.11-mips64r2el-di is NEW. binary:crypto-modules-6.11-mips64r6el-di is NEW. binary:crypto-modules-6.11-octeon-di is NEW. binary:crypto-modules-6.11-powerpc64le-di is NEW. binary:crypto-modules-6.11-riscv64-di is NEW. binary:crypto-modules-6.11-s390x-di is NEW. binary:dasd-extra-modules-6.11-s390x-di is NEW. binary:dasd-modules-6.11-s390x-di is NEW. binary:drm-core-modules-6.11-5kc-malta-di is NEW. binary:drm-core-modules-6.11-armmp-di is NEW. binary:drm-core-modules-6.11-loongson-3-di is NEW. binary:drm-core-modules-6.11-mips64r2el-di is NEW. binary:drm-core-modules-6.11-mips64r6el-di is NEW. binary:drm-core-modules-6.11-octeon-di is NEW. binary:drm-core-modules-6.11-powerpc64le-di is NEW. binary:drm-core-modules-6.11-riscv64-di is NEW. binary:efi-modules-6.11-armmp-di is NEW. binary:efi-modules-6.11-riscv64-di is NEW. binary:event-modules-6.11-5kc-malta-di is NEW. binary:event-modules-6.11-armmp-di is NEW. binary:event-modules-6.11-loongson-3-di is NEW. binary:event-modules-6.11-mips64r2el-di is NEW. binary:event-modules-6.11-mips64r6el-di is NEW. binary:event-modules-6.11-octeon-di is NEW. binary:event-modules-6.11-powerpc64le-di is NEW. binary:event-modules-6.11-riscv64-di is NEW. binary:ext4-modules-6.11-5kc-malta-di is NEW. binary:ext4-modules-6.11-armmp-di is NEW. binary:ext4-modules-6.11-loongson-3-di is NEW. binary:ext4-modules-6.11-mips64r2el-di is NEW. binary:ext4-modules-6.11-mips64r6el-di is NEW. binary:ext4-modules-6.11-octeon-di is NEW. binary:ext4-modules-6.11-powerpc64le-di is NEW. binary:ext4-modules-6.11-riscv64-di is NEW. binary:ext4-modules-6.11-s390x-di is NEW. binary:f2fs-modules-6.11-5kc-malta-di is NEW. binary:f2fs-modules-6.11-armmp-di is NEW. binary:f2fs-modules-6.11-loongson-3-di is NEW. binary:f2fs-modules-6.11-mips64r2el-di is NEW. binary:f2fs-modules-6.11-mips64r6el-di is NEW. binary:f2fs-modules-6.11-octeon-di is NEW. binary:f2fs-modules-6.11-powerpc64le-di is NEW. binary:f2fs-modules-6.11-riscv64-di is NEW. binary:f2fs-modules-6.11-s390x-di is NEW. binary:fancontrol-modules-6.11-powerpc64le-di is NEW. binary:fat-modules-6.11-5kc-malta-di is NEW. binary:fat-modules-6.11-armmp-di is NEW. binary:fat-modules-6.11-loongson-3-di is NEW. binary:fat-modules-6.11-mips64r2el-di is NEW. binary:fat-modules-6.11-mips64r6el-di is NEW. binary:fat-modules-6.11-octeon-di is NEW. binary:fat-modules-6.11-powerpc64le-di is NEW. binary:fat-modules-6.11-riscv64-di is NEW. binary:fat-modules-6.11-s390x-di is NEW. binary:fb-modules-6.11-5kc-malta-di is NEW. binary:fb-modules
Processing of linux_6.11-1~exp1_source.changes
linux_6.11-1~exp1_source.changes uploaded successfully to localhost along with the files: linux_6.11-1~exp1.dsc linux_6.11.orig.tar.xz linux_6.11-1~exp1.debian.tar.xz linux_6.11-1~exp1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed: bug 1076483 is forwarded to https://lore.kernel.org/linux-pm/20240919081121.10784-2-uklei...@debian.org
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)
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
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
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
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
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
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
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
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
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
Bug#1081751: Removed package(s) from experimental
We believe that the bug you reported is now fixed; the following package(s) have been removed from experimental: fuse-modules-6.6-686-di | 6.6.4-1~exp1 | i386 fuse-modules-6.6-686-pae-di | 6.6.4-1~exp1 | i386 linux-signed-i386 | 6.6.4+1~exp1 | source --- Reason --- ROM; no longer built from linux -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1081...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1081751 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1081751: Removed package(s) from unstable
| i386 udf-modules-6.5.0-5-686-di | 6.5.13-1 | i386 udf-modules-6.5.0-5-686-pae-di | 6.5.13-1 | i386 uinput-modules-6.5.0-5-686-di | 6.5.13-1 | i386 uinput-modules-6.5.0-5-686-pae-di | 6.5.13-1 | i386 usb-modules-6.5.0-5-686-di | 6.5.13-1 | i386 usb-modules-6.5.0-5-686-pae-di | 6.5.13-1 | i386 usb-serial-modules-6.5.0-5-686-di | 6.5.13-1 | i386 usb-serial-modules-6.5.0-5-686-pae-di | 6.5.13-1 | i386 usb-storage-modules-6.5.0-5-686-di | 6.5.13-1 | i386 usb-storage-modules-6.5.0-5-686-pae-di | 6.5.13-1 | i386 xfs-modules-6.5.0-5-686-di | 6.5.13-1 | i386 xfs-modules-6.5.0-5-686-pae-di | 6.5.13-1 | i386 --- Reason --- ROM; no longer built from linux -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1081...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1081751 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Processed: Re: Bug#1081563: Please consider adding the new Xe Graphics driver for Intel GPUs
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
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)
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 ---
Processing of nfs-utils_2.7.1-2_sourceonly.changes
nfs-utils_2.7.1-2_sourceonly.changes uploaded successfully to localhost along with the files: nfs-utils_2.7.1-2.dsc nfs-utils_2.7.1-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
nfs-utils_2.7.1-2_sourceonly.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -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- pgpHfKlpxkmJ5.pgp Description: PGP signature
Bug#904707: marked as done (fakeroot chown fails on kerberized NFSv4)
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)
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)
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
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
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
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?))
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)
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)
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)
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)
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)
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)
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
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
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
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)
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
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 ...")
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)
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)
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.)
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)
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
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)
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
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)
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)
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)
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
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)
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
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)
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)
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
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
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
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
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
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)
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
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