linux-signed-i386_4.19.235+1_source.changes is NEW
Mapping buster-proposed-updates to oldstable-proposed-updates. binary:acpi-modules-4.19.0-20-686-di is NEW. binary:acpi-modules-4.19.0-20-686-pae-di is NEW. binary:ata-modules-4.19.0-20-686-di is NEW. binary:ata-modules-4.19.0-20-686-pae-di is NEW. binary:btrfs-modules-4.19.0-20-686-di is NEW. binary:btrfs-modules-4.19.0-20-686-pae-di is NEW. binary:cdrom-core-modules-4.19.0-20-686-di is NEW. binary:cdrom-core-modules-4.19.0-20-686-pae-di is NEW. binary:compress-modules-4.19.0-20-686-di is NEW. binary:compress-modules-4.19.0-20-686-pae-di is NEW. binary:crc-modules-4.19.0-20-686-di is NEW. binary:crc-modules-4.19.0-20-686-pae-di is NEW. binary:crypto-dm-modules-4.19.0-20-686-di is NEW. binary:crypto-dm-modules-4.19.0-20-686-pae-di is NEW. binary:crypto-modules-4.19.0-20-686-di is NEW. binary:crypto-modules-4.19.0-20-686-pae-di is NEW. binary:efi-modules-4.19.0-20-686-di is NEW. binary:efi-modules-4.19.0-20-686-pae-di is NEW. binary:event-modules-4.19.0-20-686-di is NEW. binary:event-modules-4.19.0-20-686-pae-di is NEW. binary:ext4-modules-4.19.0-20-686-di is NEW. binary:ext4-modules-4.19.0-20-686-pae-di is NEW. binary:fat-modules-4.19.0-20-686-di is NEW. binary:fat-modules-4.19.0-20-686-pae-di is NEW. binary:fb-modules-4.19.0-20-686-di is NEW. binary:fb-modules-4.19.0-20-686-pae-di is NEW. binary:firewire-core-modules-4.19.0-20-686-di is NEW. binary:firewire-core-modules-4.19.0-20-686-pae-di is NEW. binary:fuse-modules-4.19.0-20-686-di is NEW. binary:fuse-modules-4.19.0-20-686-pae-di is NEW. binary:i2c-modules-4.19.0-20-686-di is NEW. binary:i2c-modules-4.19.0-20-686-pae-di is NEW. binary:input-modules-4.19.0-20-686-di is NEW. binary:input-modules-4.19.0-20-686-pae-di is NEW. binary:isofs-modules-4.19.0-20-686-di is NEW. binary:isofs-modules-4.19.0-20-686-pae-di is NEW. binary:jfs-modules-4.19.0-20-686-di is NEW. binary:jfs-modules-4.19.0-20-686-pae-di is NEW. binary:kernel-image-4.19.0-20-686-di is NEW. binary:kernel-image-4.19.0-20-686-pae-di is NEW. binary:linux-image-4.19.0-20-686 is NEW. binary:linux-image-4.19.0-20-686-pae is NEW. binary:linux-image-4.19.0-20-rt-686-pae is NEW. binary:loop-modules-4.19.0-20-686-di is NEW. binary:loop-modules-4.19.0-20-686-pae-di is NEW. binary:md-modules-4.19.0-20-686-di is NEW. binary:md-modules-4.19.0-20-686-pae-di is NEW. binary:mmc-core-modules-4.19.0-20-686-di is NEW. binary:mmc-core-modules-4.19.0-20-686-pae-di is NEW. binary:mmc-modules-4.19.0-20-686-di is NEW. binary:mmc-modules-4.19.0-20-686-pae-di is NEW. binary:mouse-modules-4.19.0-20-686-di is NEW. binary:mouse-modules-4.19.0-20-686-pae-di is NEW. binary:mtd-core-modules-4.19.0-20-686-di is NEW. binary:mtd-core-modules-4.19.0-20-686-pae-di is NEW. binary:multipath-modules-4.19.0-20-686-di is NEW. binary:multipath-modules-4.19.0-20-686-pae-di is NEW. binary:nbd-modules-4.19.0-20-686-di is NEW. binary:nbd-modules-4.19.0-20-686-pae-di is NEW. binary:nic-modules-4.19.0-20-686-di is NEW. binary:nic-modules-4.19.0-20-686-pae-di is NEW. binary:nic-pcmcia-modules-4.19.0-20-686-di is NEW. binary:nic-pcmcia-modules-4.19.0-20-686-pae-di is NEW. binary:nic-shared-modules-4.19.0-20-686-di is NEW. binary:nic-shared-modules-4.19.0-20-686-pae-di is NEW. binary:nic-usb-modules-4.19.0-20-686-di is NEW. binary:nic-usb-modules-4.19.0-20-686-pae-di is NEW. binary:nic-wireless-modules-4.19.0-20-686-di is NEW. binary:nic-wireless-modules-4.19.0-20-686-pae-di is NEW. binary:pata-modules-4.19.0-20-686-di is NEW. binary:pata-modules-4.19.0-20-686-pae-di is NEW. binary:pcmcia-modules-4.19.0-20-686-di is NEW. binary:pcmcia-modules-4.19.0-20-686-pae-di is NEW. binary:pcmcia-storage-modules-4.19.0-20-686-di is NEW. binary:pcmcia-storage-modules-4.19.0-20-686-pae-di is NEW. binary:ppp-modules-4.19.0-20-686-di is NEW. binary:ppp-modules-4.19.0-20-686-pae-di is NEW. binary:sata-modules-4.19.0-20-686-di is NEW. binary:sata-modules-4.19.0-20-686-pae-di is NEW. binary:scsi-core-modules-4.19.0-20-686-di is NEW. binary:scsi-core-modules-4.19.0-20-686-pae-di is NEW. binary:scsi-modules-4.19.0-20-686-di is NEW. binary:scsi-modules-4.19.0-20-686-pae-di is NEW. binary:scsi-nic-modules-4.19.0-20-686-di is NEW. binary:scsi-nic-modules-4.19.0-20-686-pae-di is NEW. binary:serial-modules-4.19.0-20-686-di is NEW. binary:serial-modules-4.19.0-20-686-pae-di is NEW. binary:sound-modules-4.19.0-20-686-di is NEW. binary:sound-modules-4.19.0-20-686-pae-di is NEW. binary:speakup-modules-4.19.0-20-686-di is NEW. binary:speakup-modules-4.19.0-20-686-pae-di is NEW. binary:squashfs-modules-4.19.0-20-686-di is NEW. binary:squashfs-modules-4.19.0-20-686-pae-di is NEW. binary:udf-modules-4.19.0-20-686-di is NEW. binary:udf-modules-4.19.0-20-686-pae-di is NEW. binary:uinput-modules-4.19.0-20-686-di is NEW. binary:uinput-modules-4.19.0-20-686-pae-di is NEW. binary:usb-modules-4.19.0-20-686-di is NEW. binary:usb-modules-4.19.0-20-686-pae-di is NEW. binary:usb-serial-modules-4.19.0-20-686-di is NEW. binary:usb-serial-modules-4.19.0-20-686-pae-di is NEW. binary:usb-stora
Processing of linux-signed-i386_4.19.235+1_source.changes
linux-signed-i386_4.19.235+1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_4.19.235+1.dsc linux-signed-i386_4.19.235+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-latest_105+deb10u15_source.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 Mar 2022 07:54:21 +0100 Source: linux-latest Architecture: source Version: 105+deb10u15 Distribution: buster Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-latest (105+deb10u15) buster; urgency=medium . * Update to 4.19.0-20 Checksums-Sha1: ba54b93034a243e9030bf39a96a243d83faa228c 11743 linux-latest_105+deb10u15.dsc 0eca5483e8610c98917ba99f7c56cea0bd2ab291 20808 linux-latest_105+deb10u15.tar.xz 35d278d1bf830df7b2ab2113c3de0ea4cec61e9b 6309 linux-latest_105+deb10u15_source.buildinfo Checksums-Sha256: 22349bf4af1af2abb05e1fe55ba27ea882670948bd15f922d80e0f20d4226c7d 11743 linux-latest_105+deb10u15.dsc 10e7ba0e101c5f8c69c1580e4fdd888ab2a9b44b5867ca7bcf08d340a94e6d8f 20808 linux-latest_105+deb10u15.tar.xz d178463ae4c2909cb140c94dda3572d6d69db6bd2d90a6fe870b3d5a22fb282e 6309 linux-latest_105+deb10u15_source.buildinfo Files: 1ceef865ca19be6f5109c81240711f8d 11743 kernel optional linux-latest_105+deb10u15.dsc e559a0e673fc1910696aab437ad01684 20808 kernel optional linux-latest_105+deb10u15.tar.xz 211d7b9bc3acda4c37d3b9d5b8683ef5 6309 kernel optional linux-latest_105+deb10u15_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmI1f8ZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89E/SMQAJPzY62FV5KJmZZMJNpsEKOBqdsUGfU0 buITDlTm8E9vHZEanM8KBFZOOKOAO3e8ITztbk811wjkacTZPS4LRU6qGgjp5jsi xDOiGUGgQU3my3tX6/DGVNc9zX0zPeyEWcxpHBkgmstmN6RAagJjk6m5Mg2YWIfU qnWl5iHg9TDYvIpUzqUX4DOkUnbGHyFJVZWEZyunKzrYAjuuTeTszSV6GL8QY8D7 MQpncns0zMxYKLoCR+Hm9P+OcPIkblen+nPJQzJllk9xeMgHypKmXBQxZdkEOYWY 5vID9LJuxS4JPMueNdy3nAXYo61xGyewibhO7TmUWmzBNdnz0YdTZMKUTHRKe7GV QB/c+3FdhlTjMaWrHjubjJ1Y1MiO+MbgXanmN9Xuy7IIjkV9n5+YIhFTx2QzSpgl zKrhGVNlLKaCILpTgJqBVOkZ2O37zPXPsaPwU7s602OENFT5tVF26x7fbm7ghTa2 t2atquLsqnlBemtbCKCy+4hBiF9YYgKSNNvW9aE4lqcvb2Ol089aS9oKPBJ5QAFW 2E1uVdC39+yjMme8FALHLLl2IHVan9+BRNREYSC1sG13l5iSsX2eywOqtrqJ68d7 9LdY34OqTeX3zPz9ttfs7dwDOl9bdbd3IgiIL2qZEigwS6aQeKUjMu7BE50WxyKF yGddfJ3HAGT/ =DYhT -END PGP SIGNATURE- Thank you for your contribution to Debian.
linux-signed-i386_5.10.103+1~bpo10+1_source.changes is NEW
binary:acpi-modules-5.10.0-0.bpo.12-686-di is NEW. binary:acpi-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:ata-modules-5.10.0-0.bpo.12-686-di is NEW. binary:ata-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:btrfs-modules-5.10.0-0.bpo.12-686-di is NEW. binary:btrfs-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:cdrom-core-modules-5.10.0-0.bpo.12-686-di is NEW. binary:cdrom-core-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:crc-modules-5.10.0-0.bpo.12-686-di is NEW. binary:crc-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:crypto-dm-modules-5.10.0-0.bpo.12-686-di is NEW. binary:crypto-dm-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:crypto-modules-5.10.0-0.bpo.12-686-di is NEW. binary:crypto-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:efi-modules-5.10.0-0.bpo.12-686-di is NEW. binary:efi-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:event-modules-5.10.0-0.bpo.12-686-di is NEW. binary:event-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:ext4-modules-5.10.0-0.bpo.12-686-di is NEW. binary:ext4-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:f2fs-modules-5.10.0-0.bpo.12-686-di is NEW. binary:f2fs-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:fat-modules-5.10.0-0.bpo.12-686-di is NEW. binary:fat-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:fb-modules-5.10.0-0.bpo.12-686-di is NEW. binary:fb-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:firewire-core-modules-5.10.0-0.bpo.12-686-di is NEW. binary:firewire-core-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:fuse-modules-5.10.0-0.bpo.12-686-di is NEW. binary:fuse-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:i2c-modules-5.10.0-0.bpo.12-686-di is NEW. binary:i2c-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:input-modules-5.10.0-0.bpo.12-686-di is NEW. binary:input-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:isofs-modules-5.10.0-0.bpo.12-686-di is NEW. binary:isofs-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:jfs-modules-5.10.0-0.bpo.12-686-di is NEW. binary:jfs-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:kernel-image-5.10.0-0.bpo.12-686-di is NEW. binary:kernel-image-5.10.0-0.bpo.12-686-pae-di is NEW. binary:linux-image-5.10.0-0.bpo.12-686 is NEW. binary:linux-image-5.10.0-0.bpo.12-686-pae is NEW. binary:linux-image-5.10.0-0.bpo.12-rt-686-pae is NEW. binary:loop-modules-5.10.0-0.bpo.12-686-di is NEW. binary:loop-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:md-modules-5.10.0-0.bpo.12-686-di is NEW. binary:md-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:mmc-core-modules-5.10.0-0.bpo.12-686-di is NEW. binary:mmc-core-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:mmc-modules-5.10.0-0.bpo.12-686-di is NEW. binary:mmc-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:mouse-modules-5.10.0-0.bpo.12-686-di is NEW. binary:mouse-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:mtd-core-modules-5.10.0-0.bpo.12-686-di is NEW. binary:mtd-core-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:multipath-modules-5.10.0-0.bpo.12-686-di is NEW. binary:multipath-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:nbd-modules-5.10.0-0.bpo.12-686-di is NEW. binary:nbd-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:nic-modules-5.10.0-0.bpo.12-686-di is NEW. binary:nic-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:nic-pcmcia-modules-5.10.0-0.bpo.12-686-di is NEW. binary:nic-pcmcia-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:nic-shared-modules-5.10.0-0.bpo.12-686-di is NEW. binary:nic-shared-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:nic-usb-modules-5.10.0-0.bpo.12-686-di is NEW. binary:nic-usb-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:nic-wireless-modules-5.10.0-0.bpo.12-686-di is NEW. binary:nic-wireless-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:pata-modules-5.10.0-0.bpo.12-686-di is NEW. binary:pata-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:pcmcia-modules-5.10.0-0.bpo.12-686-di is NEW. binary:pcmcia-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:pcmcia-storage-modules-5.10.0-0.bpo.12-686-di is NEW. binary:pcmcia-storage-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:ppp-modules-5.10.0-0.bpo.12-686-di is NEW. binary:ppp-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:rfkill-modules-5.10.0-0.bpo.12-686-di is NEW. binary:rfkill-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:sata-modules-5.10.0-0.bpo.12-686-di is NEW. binary:sata-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:scsi-core-modules-5.10.0-0.bpo.12-686-di is NEW. binary:scsi-core-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:scsi-modules-5.10.0-0.bpo.12-686-di is NEW. binary:scsi-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:scsi-nic-modules-5.10.0-0.bpo.12-686-di is NEW. binary:scsi-nic-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:serial-modules-5.10.0-0.bpo.12-686-di is NEW. binary:serial-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:sound-modules-5.10.0-0.bpo.12-686-di is NEW. binary:sound-modules-5.10.0-0.bpo.12-686-pae-di is NEW. binary:speakup-modules-5.10.0-0.b
Processing of linux-signed-i386_5.10.103+1~bpo10+1_source.changes
linux-signed-i386_5.10.103+1~bpo10+1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_5.10.103+1~bpo10+1.dsc linux-signed-i386_5.10.103+1~bpo10+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-signed-arm64_4.19.235+1_source.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Mar 2022 20:48:39 +0100 Source: linux-signed-arm64 Architecture: source Version: 4.19.235+1 Distribution: buster-proposed-updates Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-arm64 (4.19.235+1) buster; urgency=medium . * Sign kernel from linux 4.19.235-1 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.233 - mac80211_hwsim: report NOACK frames in tx_status - mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work - [arm*] i2c: bcm2835: Avoid clock stretching timeouts - [x86] ASoC: rt5682: do not block workqueue if card is unbound - Input: clear BTN_RIGHT/MIDDLE on buttonpads - cifs: fix double free race when mount fails in cifs_get_root() - net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 - usb: gadget: don't release an existing dev->buf (CVE-2022-24958) - usb: gadget: clear related members when goto fail (CVE-2022-24958) - ata: pata_hpt37x: fix PCI clock detection - [x86] ALSA: intel_hdmi: Fix reference to PCM buffer address - ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min - xfrm: fix MTU regression - netfilter: fix use-after-free in __nf_register_net_hook() - xfrm: fix the if_id check in changelink - xfrm: enforce validity of offload input flags - netfilter: nf_queue: don't assume sk is full socket - netfilter: nf_queue: fix possible use-after-free - batman-adv: Request iflink once in batadv-on-batadv check - batman-adv: Request iflink once in batadv_get_real_netdevice - batman-adv: Don't expect inter-netns unique iflink indices - net: dcb: flush lingering app table entries for unregistered devices - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server - block: Fix fsync always failed if once failed - PCI: pciehp: Fix infinite loop in IRQ handler upon power fault - xen/netfront: destroy queues before real_num_tx_queues is zeroed - mac80211: fix forwarded mesh frames AC & queue selection - [arm64,armhf] net: stmmac: fix return value of __setup handler - net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() - efivars: Respect "block" flag in efivar_entry_set_safe() - can: gs_usb: change active_channels's type from atomic_t to u8 - [armel,armhf] 9182/1: mmu: fix returns from early_param() and __setup() functions - net: chelsio: cxgb3: check the return value of pci_find_capability() - nl80211: Handle nla_memdup failures in handle_nan_filter - Input: elan_i2c - move regulator_[en|dis]able() out of elan_[en|dis]able_power() - Input: elan_i2c - fix regulator enable count imbalance after suspend/resume - HID: add mapping for KEY_ALL_APPLICATIONS - memfd: fix F_SEAL_WRITE after shmem huge page allocated - tracing/histogram: Fix sorting on old "cpu" value - btrfs: add missing run of delayed items after unlink during log replay - net: dcb: disable softirqs in dcbnl_flush_dev() - hamradio: fix macro redefine warning https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.234 - [arm*] Provide a wrapper for SMCCC 1.1 calls - [arm64,armhf] smccc/psci: add arm_smccc_1_1_get_conduit() - [armhf] report Spectre v2 status through sysfs - [armel,armhf] early traps initialisation - [armel,armhf] use LOADADDR() to get load address of sections - [armel,armhf] Spectre-BHB workaround - [armel,armhf] include unprivileged BPF status in Spectre V2 reporting - [armel,armhf] fix build error when BPF_SYSCALL is disabled - [armel,armhf] fix co-processor register typo - [armel,armhf] Do not use NOCROSSREFS directive with ld.lld - [armhf] fix build warning in proc-v7-bugs.c - xen/xenbus: don't let xenbus_grant_ring() remove grants in error case (CVE-2022-23040, XSA-396) - xen/grant-table: add gnttab_try_end_foreign_access() (CVE-2022-23036, CVE-2022-23038, XSA-396) - xen/blkfront: don't use gnttab_query_foreign_access() for mapped status (CVE-2022-23036, XSA-396) - xen/netfront: don't use gnttab_query_foreign_access() for mapped status (CVE-2022-23037, XSA-396) - xen/scsifront: don't use gnttab_query_foreign_access() for mapped status (CVE-2022-23038, XSA-396) - xen/gntalloc: don't use gnttab_query_foreign_access() (CVE-2022-23039, XSA-396) - xen: remove gnttab_query_foreign_access() - xen/9p: use alloc/free_pages_exact() (CVE-2022-23041, XSA-396) - xen/pvcalls: use alloc/free_pages_exact() (CVE-2022-23041, XSA-396) - xen/gnttab: fix gnttab_end_foreign_access() without page specified (CVE-2022-23041, XSA-396)
Bug#711021: mount.nfs timeout for GETPORT is much too short
I'm not sure that this bug was ever fixed.
nfs-utils actually uses nfs_getport() to get the port. That passes a
timeout of {-1, 0} to libtirpc, which is invalid and should result in
using the rpcbind client's default timeout.
The TCP client interface is implemented in src/clnt_vc.c. It has a
default timeout (ct_wait field) that can be set with CLNT_CONTROL(...,
CLSET_TIMEOUT, ...), but nfs-utils doesn't seem to do that. So it
seems like there is a default timeout of 0!
Ben.
--
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein
signature.asc
Description: This is a digitally signed message part
linux-signed-amd64_4.19.235+1_source.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Mar 2022 20:48:39 +0100 Source: linux-signed-amd64 Architecture: source Version: 4.19.235+1 Distribution: buster-proposed-updates Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-amd64 (4.19.235+1) buster; urgency=medium . * Sign kernel from linux 4.19.235-1 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.233 - mac80211_hwsim: report NOACK frames in tx_status - mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work - [arm*] i2c: bcm2835: Avoid clock stretching timeouts - [x86] ASoC: rt5682: do not block workqueue if card is unbound - Input: clear BTN_RIGHT/MIDDLE on buttonpads - cifs: fix double free race when mount fails in cifs_get_root() - net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 - usb: gadget: don't release an existing dev->buf (CVE-2022-24958) - usb: gadget: clear related members when goto fail (CVE-2022-24958) - ata: pata_hpt37x: fix PCI clock detection - [x86] ALSA: intel_hdmi: Fix reference to PCM buffer address - ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min - xfrm: fix MTU regression - netfilter: fix use-after-free in __nf_register_net_hook() - xfrm: fix the if_id check in changelink - xfrm: enforce validity of offload input flags - netfilter: nf_queue: don't assume sk is full socket - netfilter: nf_queue: fix possible use-after-free - batman-adv: Request iflink once in batadv-on-batadv check - batman-adv: Request iflink once in batadv_get_real_netdevice - batman-adv: Don't expect inter-netns unique iflink indices - net: dcb: flush lingering app table entries for unregistered devices - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server - block: Fix fsync always failed if once failed - PCI: pciehp: Fix infinite loop in IRQ handler upon power fault - xen/netfront: destroy queues before real_num_tx_queues is zeroed - mac80211: fix forwarded mesh frames AC & queue selection - [arm64,armhf] net: stmmac: fix return value of __setup handler - net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() - efivars: Respect "block" flag in efivar_entry_set_safe() - can: gs_usb: change active_channels's type from atomic_t to u8 - [armel,armhf] 9182/1: mmu: fix returns from early_param() and __setup() functions - net: chelsio: cxgb3: check the return value of pci_find_capability() - nl80211: Handle nla_memdup failures in handle_nan_filter - Input: elan_i2c - move regulator_[en|dis]able() out of elan_[en|dis]able_power() - Input: elan_i2c - fix regulator enable count imbalance after suspend/resume - HID: add mapping for KEY_ALL_APPLICATIONS - memfd: fix F_SEAL_WRITE after shmem huge page allocated - tracing/histogram: Fix sorting on old "cpu" value - btrfs: add missing run of delayed items after unlink during log replay - net: dcb: disable softirqs in dcbnl_flush_dev() - hamradio: fix macro redefine warning https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.234 - [arm*] Provide a wrapper for SMCCC 1.1 calls - [arm64,armhf] smccc/psci: add arm_smccc_1_1_get_conduit() - [armhf] report Spectre v2 status through sysfs - [armel,armhf] early traps initialisation - [armel,armhf] use LOADADDR() to get load address of sections - [armel,armhf] Spectre-BHB workaround - [armel,armhf] include unprivileged BPF status in Spectre V2 reporting - [armel,armhf] fix build error when BPF_SYSCALL is disabled - [armel,armhf] fix co-processor register typo - [armel,armhf] Do not use NOCROSSREFS directive with ld.lld - [armhf] fix build warning in proc-v7-bugs.c - xen/xenbus: don't let xenbus_grant_ring() remove grants in error case (CVE-2022-23040, XSA-396) - xen/grant-table: add gnttab_try_end_foreign_access() (CVE-2022-23036, CVE-2022-23038, XSA-396) - xen/blkfront: don't use gnttab_query_foreign_access() for mapped status (CVE-2022-23036, XSA-396) - xen/netfront: don't use gnttab_query_foreign_access() for mapped status (CVE-2022-23037, XSA-396) - xen/scsifront: don't use gnttab_query_foreign_access() for mapped status (CVE-2022-23038, XSA-396) - xen/gntalloc: don't use gnttab_query_foreign_access() (CVE-2022-23039, XSA-396) - xen: remove gnttab_query_foreign_access() - xen/9p: use alloc/free_pages_exact() (CVE-2022-23041, XSA-396) - xen/pvcalls: use alloc/free_pages_exact() (CVE-2022-23041, XSA-396) - xen/gnttab: fix gnttab_end_foreign_access() without page specified (CVE-2022-23041, XSA-396)
Bug#833925: marked as done (nfs-kernel-server: no_root_squash broken on amd64)
Your message dated Sat, 19 Mar 2022 19:59:51 +0100 with message-id and subject line Re: nfs-kernel-server: all exports are read only has caused the Debian Bug report #709403, regarding nfs-kernel-server: no_root_squash broken on amd64 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.) -- 709403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: 1:1.2.8-9 Severity: normal The no_root_squash option appears to work on i386, but not on amd64. wooledg@wooledg:~$ grep '^[^#]' /etc/exports /home -no_subtree_check arc1(ro,no_root_squash,sync) arc1:~# ls /net/hosts/wooledg/home/wooledg/.bash* /net/hosts/wooledg/home/wooledg/.bash_history /net/hosts/wooledg/home/wooledg/.bash_logout /net/hosts/wooledg/home/wooledg/.bashrc arc1:~# ls /net/hosts/wooledg/home/wooledg/Maildir ls: cannot open directory /net/hosts/wooledg/home/wooledg/Maildir: Permission denied This is somewhat similar to bug #492970, but it's architecture specific and it appears to be on the server side, not the client side. I've confirmed with NFSv3 and NFSv4 mounts from other Debian systems, and with an HP-UX client. See also: https://lists.debian.org/debian-user/2016/08/msg00245.html https://lists.debian.org/debian-user/2016/08/msg00275.html I filed the bug report from "wooledg" (my desktop box) because it has an absolutely minimal configuration that still demonstrates the problem. The real problem that I care about is on a server with many other exports as well. Same problem: jessie, amd64, no_root_squash is ignored. Jessie i386 systems work fine. -- 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 55248 status 1000241 tcp 48807 status 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 55895 nlockmgr 1000213 udp 55895 nlockmgr 1000214 udp 55895 nlockmgr 1000211 tcp 38500 nlockmgr 1000213 tcp 38500 nlockmgr 1000214 tcp 38500 nlockmgr 151 udp 43131 mountd 151 tcp 49060 mountd 152 udp 47185 mountd 152 tcp 49686 mountd 153 udp 52717 mountd 153 tcp 35670 mountd -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS="--manage-gids" NEED_SVCGSSD="" RPCSVCGSSDOPTS="" -- /etc/exports -- /home -no_subtree_check arc1(ro,no_root_squash,sync) -- /proc/fs/nfs/exports -- # Version 1.1 # Path Client(Flags) # IPs -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 libblkid1 2.25.2-6 ii libc6 2.19-18+deb8u4 ii libcap2 1:2.24-8 ii libsqlite3-0 3.8.7.1-1+deb8u1 ii libtirpc1 0.2.5-1 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian13+nmu1 ii nfs-common1:1.2.8-9 ii ucf 3.0030 nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- debconf-show failed --- End Message --- --- Begin Message --- Version: 1:1.3.4-1 This was reported to be fixed in the above version. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#783212: marked as done (nfs-kernel-server: exportfs fails to set rw, ro, no_root_squash, root_squash, no_all_squash and all_squash flags in some cases)
Your message dated Sat, 19 Mar 2022 19:59:51 +0100 with message-id and subject line Re: nfs-kernel-server: all exports are read only has caused the Debian Bug report #709403, regarding nfs-kernel-server: exportfs fails to set rw, ro, no_root_squash, root_squash, no_all_squash and all_squash flags in some cases 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.) -- 709403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709403 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 Tags: fixed-upstream Control: merge -1 709403 Dear Maintainer, after upgrading from version 1:1.2.6-4 several exports on my server lost their no_root_squash flag, causing "Permission denied" errors on the corresponding clients when using root. After some testing and debugging I came to the following conclusion: Commit 11ba3b1e01b67b7d19f26fba94fabdb60878e809 (Add a default flavor to an export's e_secinfo list) breaks export option parsing by exportfs in some cases. Upstream commit 7004991526be90ec2647d28c503936dc91bc9100 (exportfs: Fix the default authentication flavour setting) fixes the bug as a side effect of dealing with another problem sharing the same root cause. The easiest workaround is to add a sec=xyz option at the beginning of all export option strings. My test configuration is as follows: -- /etc/exports -- /srv/nfs4 -fsid=0,async,no_subtree_check,insecure,all_squash 10.0.0.2 10.0.0.3(secure,rw,no_root_squash,no_all_squash) exportfs -v output from version 1:1.2.8-9: /srv/nfs4 10.0.0.2(ro,async,wdelay,insecure,root_squash,all_squash,no_subtree_check,fsid=0,sec=sys,ro,root_squash,all_squash) /srv/nfs4 10.0.0.3(ro,async,wdelay,root_squash,all_squash,no_subtree_check,fsid=0,sec=sys,ro,root_squash,all_squash) but /var/lib/nfs/etab shows /srv/nfs4 10.0.0.2(ro,async,wdelay,hide,nocrossmnt,insecure,root_squash,all_squash,no_subtree_check,secure_locks,acl,fsid=0,anonuid=65534,anongid=65534,sec=sys,ro,root_squash,all_squash) /srv/nfs4 10.0.0.3(rw,async,wdelay,hide,nocrossmnt,secure,no_root_squash,no_all_squash,no_subtree_check,secure_locks,acl,fsid=0,anonuid=65534,anongid=65534,sec=sys,ro,root_squash,all_squash) ^ ^ ^ ^ ^ ^ meaning exportfs -a|-r produces an inconsistent etab line. Consequently rw, no_root_squash and no_all_squash get dropped by exportfs -v and mountd (last save wins). This happens under following conditions: (1) A default option specification is present on the export line. (2) The export line contains an export with rw, ro, [no_]root_squash or [no_]squash_all options different from the implied or declared default options (3) The option string for this export doesn't contain a sec=xyz option preceding the options named in (2). The underlying bug is in function parseopts at ./support/nfs/exports.c:646: A default security flavor containing duplicates of the specified default values for the READONLY, ROOTSQUASH and ALLSQUASH flags is added to the default options. This default flavor is erroneously reused for all exports on the same line in spite of containing flags that can be altered by export specifications. This results in possibly incorrect options at the end of the export specifications in the etab file. The bug fix is to generate a default security flavor seperately for each export that doesn't already have one. This is in effect what upstream commit 7004991526be90ec2647d28c503936dc91bc9100 does by deferring the generation of default security flavors as long as possible. I have patched version 1:1.2.8-9 with upstream commit 7004991526be90ec2647d28c503936dc91bc9100 and it works as expected: exportfs -v output from version 1:1.2.8-9.1: /srv/nfs4 10.0.0.2(ro,async,wdelay,insecure,root_squash,all_squash,no_subtree_check,fsid=0,sec=sys,ro,root_squash,all_squash) /srv/nfs4 10.0.0.3(rw,async,wdelay,no_root_squash,no_subtree_check,fsid=0,sec=sys,rw,no_root_squash,no_all_squash) /var/lib/nfs/etab after exportfs -r (version 1:1.2.8-9.1): /srv/nfs4 10.0.0.2(ro,async,wdelay,hide,nocrossmnt,insecure,root_squash,all_squash,no_subtree_check,secure_locks,acl,fsid=0,anonuid=65534,anongid=65534,sec=sys,ro,root_squash,all_squash) /srv/nfs4 10.0.0.3(rw,async,wdelay,hide,nocrossmnt,secure,no_root_squash,no_all_squash,no_subtree_check,secure_locks,acl,fsid=0,anonuid=65534,anongid=65534,sec=sy
Bug#709403: marked as done (nfs-kernel-server: exportfs fails to set rw, ro, no_root_squash, root_squash, no_all_squash and all_squash flags in some cases)
Your message dated Sat, 19 Mar 2022 19:59:51 +0100 with message-id and subject line Re: nfs-kernel-server: all exports are read only has caused the Debian Bug report #709403, regarding nfs-kernel-server: exportfs fails to set rw, ro, no_root_squash, root_squash, no_all_squash and all_squash flags in some cases 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.) -- 709403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: 1:1.2.8-2 Severity: important Upgrade of nfs-kernel-server from 1:1.2.6-3 to 1:1.2.8-2 turned all my NFS exports to read-only. Before upgrade `sudo exportfs -v` show something like /root.nfs/r3 192.168.0.0/24(rw,root_squash,all_squash,no_subtree_check,mountpoint,anonuid=1000,anongid=1000) but after upgrade it is /root.nfs/r3 192.168.0.0/24(ro,root_squash,all_squash,no_subtree_check,mountpoint,anonuid=1000,anongid=1000) even though there were no changes to /etc/exports. I can't make any of my NFS exports writable without downgrading "nfs-kernel-server" and corresponding "nfs-common". Please advise. Thanks. Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B --- System information. --- Architecture: amd64 Kernel: Linux 3.8-2-amd64 --- End Message --- --- Begin Message --- Version: 1:1.3.4-1 This was reported to be fixed in the above version. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: retitle 679274 to init script does not start nfsd when /etc/exports is empty, tagging 679274
Processing commands for cont...@bugs.debian.org: > retitle 679274 init script does not start nfsd when /etc/exports is empty Bug #679274 [nfs-kernel-server] nfs-kernel-server: upgrading to 1:1.2.6-2 fails to start the kernel server Changed Bug title to 'init script does not start nfsd when /etc/exports is empty' from 'nfs-kernel-server: upgrading to 1:1.2.6-2 fails to start the kernel server'. > tags 679274 + wontfix Bug #679274 [nfs-kernel-server] init script does not start nfsd when /etc/exports is empty Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 679274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
linux-signed-arm64_4.19.235+1_source.changes is NEW
Mapping buster-proposed-updates to oldstable-proposed-updates. binary:ata-modules-4.19.0-20-arm64-di is NEW. binary:btrfs-modules-4.19.0-20-arm64-di is NEW. binary:cdrom-core-modules-4.19.0-20-arm64-di is NEW. binary:compress-modules-4.19.0-20-arm64-di is NEW. binary:crc-modules-4.19.0-20-arm64-di is NEW. binary:crypto-dm-modules-4.19.0-20-arm64-di is NEW. binary:crypto-modules-4.19.0-20-arm64-di is NEW. binary:efi-modules-4.19.0-20-arm64-di is NEW. binary:event-modules-4.19.0-20-arm64-di is NEW. binary:ext4-modules-4.19.0-20-arm64-di is NEW. binary:fat-modules-4.19.0-20-arm64-di is NEW. binary:fb-modules-4.19.0-20-arm64-di is NEW. binary:fuse-modules-4.19.0-20-arm64-di is NEW. binary:i2c-modules-4.19.0-20-arm64-di is NEW. binary:input-modules-4.19.0-20-arm64-di is NEW. binary:isofs-modules-4.19.0-20-arm64-di is NEW. binary:jfs-modules-4.19.0-20-arm64-di is NEW. binary:kernel-image-4.19.0-20-arm64-di is NEW. binary:leds-modules-4.19.0-20-arm64-di is NEW. binary:linux-image-4.19.0-20-arm64 is NEW. binary:linux-image-4.19.0-20-rt-arm64 is NEW. binary:loop-modules-4.19.0-20-arm64-di is NEW. binary:md-modules-4.19.0-20-arm64-di is NEW. binary:mmc-modules-4.19.0-20-arm64-di is NEW. binary:mtd-core-modules-4.19.0-20-arm64-di is NEW. binary:multipath-modules-4.19.0-20-arm64-di is NEW. binary:nbd-modules-4.19.0-20-arm64-di is NEW. binary:nic-modules-4.19.0-20-arm64-di is NEW. binary:nic-shared-modules-4.19.0-20-arm64-di is NEW. binary:nic-usb-modules-4.19.0-20-arm64-di is NEW. binary:nic-wireless-modules-4.19.0-20-arm64-di is NEW. binary:ppp-modules-4.19.0-20-arm64-di is NEW. binary:sata-modules-4.19.0-20-arm64-di is NEW. binary:scsi-core-modules-4.19.0-20-arm64-di is NEW. binary:scsi-modules-4.19.0-20-arm64-di is NEW. binary:scsi-nic-modules-4.19.0-20-arm64-di is NEW. binary:squashfs-modules-4.19.0-20-arm64-di is NEW. binary:udf-modules-4.19.0-20-arm64-di is NEW. binary:uinput-modules-4.19.0-20-arm64-di is NEW. binary:usb-modules-4.19.0-20-arm64-di is NEW. binary:usb-serial-modules-4.19.0-20-arm64-di is NEW. binary:usb-storage-modules-4.19.0-20-arm64-di is NEW. binary:xfs-modules-4.19.0-20-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
Processing of linux-signed-arm64_4.19.235+1_source.changes
linux-signed-arm64_4.19.235+1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_4.19.235+1.dsc linux-signed-arm64_4.19.235+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-signed-arm64_5.10.103+1~bpo10+1_source.changes is NEW
binary:ata-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:btrfs-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:cdrom-core-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:crc-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:crypto-dm-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:crypto-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:efi-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:event-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:ext4-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:f2fs-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:fat-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:fb-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:fuse-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:i2c-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:input-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:isofs-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:jfs-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:kernel-image-5.10.0-0.bpo.12-arm64-di is NEW. binary:leds-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:linux-image-5.10.0-0.bpo.12-arm64 is NEW. binary:linux-image-5.10.0-0.bpo.12-cloud-arm64 is NEW. binary:linux-image-5.10.0-0.bpo.12-rt-arm64 is NEW. binary:loop-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:md-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:mmc-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:mtd-core-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:multipath-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:nbd-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:nic-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:nic-shared-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:nic-usb-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:nic-wireless-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:ppp-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:sata-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:scsi-core-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:scsi-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:scsi-nic-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:squashfs-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:udf-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:uinput-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:usb-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:usb-serial-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:usb-storage-modules-5.10.0-0.bpo.12-arm64-di is NEW. binary:xfs-modules-5.10.0-0.bpo.12-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
Bug#659465: marked as done (nfs-common: need to restart nfs-common at the end of init on the NFS server)
Your message dated Sat, 19 Mar 2022 18:33:26 +0100 with message-id <5f9a545642e7b462e922ff46e9a8bad3dc71fa75.ca...@decadent.org.uk> and subject line Re: nfs-common: need to restart nfs-common at the end of init on the NFS server has caused the Debian Bug report #659465, regarding nfs-common: need to restart nfs-common at the end of init on the NFS server 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.) -- 659465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.2.5-4 Severity: important Dear Maintainer, However some people reported bugs that look like this one, I can't determine whether this is exactly the same issue. The issue is that the NFS clients fail to map user ids from NFS server, complaining about wrong domain name (localdomain instead of the true domain name). I use NFSv4 with MIT Kerberos authentication and openldap to store user information. Everything is working fine (auth, nss, nfs mounting, etc) except NFS id mapping. Domain is provided by DHCP, and setting domain in idmapd.conf as well does not solve the problem. Both client and server are Debian testing. Restarting nfs-common on the server after init actually solves the problem, and I added this to rc.local script as a workaround. So I guess that there is something wrong in the init running order. -- 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 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 33790 nlockmgr 1000213 udp 33790 nlockmgr 1000214 udp 33790 nlockmgr 1000211 tcp 49108 nlockmgr 1000213 tcp 49108 nlockmgr 1000214 tcp 49108 nlockmgr 151 udp 42771 mountd 151 tcp 55095 mountd 152 udp 56799 mountd 152 tcp 41919 mountd 153 udp 58820 mountd 153 tcp 34937 mountd 1000241 udp 58559 status 1000241 tcp 41350 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= 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: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113+nmu1 ii initscripts 2.88dsf-22 ii libc6 2.13-26 ii libcap2 1:2.22-1 ii libcomerr2 1.42-1 ii libdevmapper1.02.1 2:1.02.67-2 ii libevent-2.0-5 2.0.16-stable-1 ii libgssapi-krb5-21.10+dfsg~beta1-2 ii libgssglue1 0.3-4 ii libk5crypto31.10+dfsg~beta1-2 ii libkeyutils11.5.2-2 ii libkrb5-3 1.10+dfsg~beta1-2 ii libmount1 2.20.1-1.2 ii libnfsidmap20.25-1 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-22 ii lsb-base3.2-28.1 ii rpcbind 0.2.0-7 ii ucf 3.0025+nmu2 Versions of packages nfs-common recommends: ii python 2.7.2-10 nfs-common suggests no packages. Versions of packages nfs-kernel-server depends on: ii libblkid1 2.20.1-1.2 ii libc6 2.13-26 ii libnfsidmap2 0.25-1 ii libtirpc1 0.2.2-5 ii libwrap0 7.6.q-22 ii lsb-base 3.2-28.1 ii ucf 3.0025+nmu2 -- Configuration Files: /etc/default/nfs-common changed: NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD=yes /etc/idmapd.conf changed: [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- no debconf information --- End Message --- --- Begin Message --- Closing this due to lack of response. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Br
Processed: submitter 848306
Processing commands for cont...@bugs.debian.org: > submitter 848306 debian-kernel@lists.debian.org Bug #848306 [nfs-common] should stop distributing rpc.svcgssd Changed Bug submitter to 'debian-kernel@lists.debian.org' from 'Daniel Pocock '. > thanks Stopping processing here. Please contact me if you need assistance. -- 848306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#649052: marked as done (nfs-kernel-server: svcgssd can't open /usr/lib/libgssapi_krb5.so.2: /usr/lib/libgssapi_krb5.so.2: cannot open shared object file)
Your message dated Sat, 19 Mar 2022 18:30:22 +0100 with message-id and subject line Re: nfs-kernel-server: svcgssd can't open /usr/lib/libgssapi_krb5.so.2: /usr/lib/libgssapi_krb5.so.2: cannot open shared object file has caused the Debian Bug report #649052, regarding nfs-kernel-server: svcgssd can't open /usr/lib/libgssapi_krb5.so.2: /usr/lib/libgssapi_krb5.so.2: cannot open shared object file 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.) -- 649052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: 1:1.2.4-1~bpo60+1 Severity: important Tags: upstream When a repository of backports update the nfs-kernel-server, and then krb5-user, then the nfs-kernel-server not run with the error: = Starting NFS kernel daemon: nfsd svcgssdcan't open /usr/lib/libgssapi_krb5.so.2: /usr/lib/libgssapi_krb5.so.2: cannot open shared object file: No suchfile or directory rpc.svcgssd: Unable to obtain list of supported mechanisms. Check that gss library is properly configured. rpc.svcgssd: ERROR: Problem with gssapi library failed! = When I update the package libgssglue1, then everything becomes good: = ARCHIV ~ # dpkg --search /etc/gssapi_mech.conf libgssglue1: /etc/gssapi_mech.conf ARCHIV ~ # apt-get -t squeeze-backports install libgssglue1 Чтение списков пакетов... Готово Построение дерева зависимостей Чтение информации о состоянии... Готово Следующие пакеты устанавливались автоматически и больше не требуются: libpth20 libkadm5clnt-mit7 libgpgme11 Для их удаления используйте 'apt-get autoremove'. Пакеты, которые будут обновлены: libgssglue1 обновлено 1, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 230 пакетов не обновлено. Необходимо скачать 23,3 kБ архивов. После данной операции, объём занятого дискового пространства уменьшится на 22,5 kB. Получено:1 http://ftp.de.debian.org/debian/ wheezy/main libgssglue1 i386 0.3-3.1 [23,3 kB] Получено 23,3 kБ за 0с (33,7 kБ/c) Чтение журнала изменений... Выполнено (Чтение базы данных ... на данный момент установлено 37052 файла и каталога.) Подготовка к замене пакета libgssglue1 0.1-4 (используется файл .../libgssglue1_0.3-3.1_i386.deb) ... Распаковывается замена для пакета libgssglue1 ... Настраивается пакет libgssglue1 (0.3-3.1) ... Устанавливается новая версия файла настройки /etc/gssapi_mech.conf ... ARCHIV ~ # service nfs-kernel-server restart Stopping NFS kernel daemon: mountd svcgssd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon...exportfs: scandir /etc/exports.d: No such file or directory .. Starting NFS kernel daemon: nfsd svcgssd mountd. == perhaps it should be noted as a dependency package libgssglue1 ... -- 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 52124 status 1000241 tcp 44262 status 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 41525 nlockmgr 1000213 udp 41525 nlockmgr 1000214 udp 41525 nlockmgr 1000211 tcp 41766 nlockmgr 1000213 tcp 41766 nlockmgr 1000214 tcp 41766 nlockmgr 151 udp 52008 mountd 151 tcp 57750 mountd 152 udp 37176 mountd 152 tcp 38245 mountd 153 udp 34956 mountd 153 tcp 53819 mountd -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS=--manage-gids NEED_SVCGSSD=yes RPCSVCGSSDOPTS=yes -- /etc/exports -- /nfsgss/krb5(rw,sync,no_subtree_check) /archiv-big files(rw,sync,no_subtree_check) /archiv-small files(rw,sync,no_subtree_check) -- /proc/fs/nfs/exports -- # Version 1.1 # Path Client(Flags) # IPs -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing') Architec
Bug#644948: marked as done (nfs-common: Wrong uid/gid with latest version using NFSv4)
Your message dated Sat, 19 Mar 2022 18:29:02 +0100 with message-id <4b512fde181875e8800a4526d149362b46101e43.ca...@decadent.org.uk> and subject line Re: nfs-common: Wrong uid/gid with latest version using NFSv4 has caused the Debian Bug report #644948, regarding nfs-common: Wrong uid/gid with latest version using 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.) -- 644948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.2.5-2 Severity: important After upgrade to nfs-common 1:1.2.5-2 I noticed that uid/gid's are displayed as 'nobody' and 'nogroup' respectively. This is the case checking with both Nautilus and terminal. Downgrading to 1:1.2.4-1 from Testing fixes the problem. I am using Squeeze with nfs-kernel-server version 1:1.2.2-4 on the server side. -- 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 45260 status 1000241 tcp 50813 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD=yes NEED_GSSD= -- /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: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-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 ii initscripts 2.88dsf-13.11 ii libc6 2.13-21 ii libcap2 1:2.22-1 ii libcomerr2 1.42~WIP-2011-10-05-2 ii libdevmapper1.02.1 2:1.02.65-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 --- Closing this, as the problem appears to have been a misconfiguration rather than a bug. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#644236: marked as done (installation fails when rpcbind is disabled, although nfs-common is disabled there too)
Your message dated Sat, 19 Mar 2022 18:26:23 +0100 with message-id and subject line Re: installation fails when rpcbind is disabled, although nfs-common is disabled there too has caused the Debian Bug report #644236, regarding installation fails when rpcbind is disabled, although nfs-common is disabled there too 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.) -- 644236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.2.5-2 Severity: important Dear Maintainer, I have found a bug on upgrading nfs-common that might be nfs-common init script header or insserv related: * What led up to the situation? Upgrading nfs-common when nfs-common and (!) rpcbind is disabled in insserv. merkaba:~> LANG=C apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: kmymoney kmymoney-common tryton-client 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Setting up nfs-common (1:1.2.5-2) ... insserv: Service rpcbind has to be enabled to start service nfs-common insserv: exiting now! update-rc.d: error: insserv rejected the script header 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 E: Sub-process /usr/bin/dpkg returned an error code (1) * What exactly did you do (or not do) that was effective (or ineffective)? Explicetely disabling nfs-common again does not help: merkaba:~> insserv -r nfs-common merkaba:~> LANG=C apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: kmymoney kmymoney-common tryton-client 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Setting up nfs-common (1:1.2.5-2) ... insserv: Service rpcbind has to be enabled to start service nfs-common insserv: exiting now! update-rc.d: error: insserv rejected the script header 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 E: Sub-process /usr/bin/dpkg returned an error code (1) * What was the outcome of this action? The installation failed. * What outcome did you expect instead? It should have succeeded. This is on a laptop where I only use NFS on demand. I do not want to have it running when I do not use it. I think this is a valid usage scenario. Thus when nfs-common *and* rpcbind are disabled in insserv installation should still succeed. This might be a bug in insserv. If so please reassign. * Workaround to have apt upgrade nfs-common Temporarily enabling both nfs-common and rpcbind lets nfs-common upgrade smoothly: merkaba:~#100> insserv rpcbind merkaba:~> insserv nfs-common merkaba:~> LANG=C apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: kmymoney kmymoney-common tryton-client 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Setting up nfs-common (1:1.2.5-2) ... Stopping NFS common utilities: idmapd statd. Starting NFS common utilities: statd Not starting: portmapper is not running ... (warning). merkaba:~> insserv -r nfs-common merkaba:~> insserv -r rpcbind merkaba:~> Bug script failed due to rpcbind not running, but I do not think it matters for this bugreport. If you want to have output of it, please tell. Thanks, Martin *** End of the template - remove these lines *** -- Package-specific info: -- rpcinfo -- -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (120, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8,
Processed: tagging 644236
Processing commands for cont...@bugs.debian.org: > tags 644236 + stretch Bug #644236 [nfs-common] installation fails when rpcbind is disabled, although nfs-common is disabled there too Added tag(s) stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 644236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of linux-signed-arm64_5.10.103+1~bpo10+1_source.changes
linux-signed-arm64_5.10.103+1~bpo10+1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_5.10.103+1~bpo10+1.dsc linux-signed-arm64_5.10.103+1~bpo10+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1006346: cloud.debian.org: bullseye AMIs don't boot on Amazon EC2 Xen instances with Enhanced Networking
On Sat, Mar 19, 2022 at 10:41:39AM +0100, Salvatore Bonaccorso wrote: > > >From the upstream discussion on the linux-pci mailing list [*]: > > > > > Yes. My understanding is that the issue is because AWS is using older > > > versions of Xen. They are in the process of updating their fleet to a > > > newer version of Xen so the change introduced with Stefan's commit > > > isn't an issue any longer. > > > > > > I think the changes are scheduled to be completed in the next 10-12 > > > weeks. For now we are carrying a revert in the Fedora Kernel. > > > > > > You can follow this Fedora CoreOS issue if you'd like to know more > > > about when the change lands in their backend. We work closely with one > > > of their partner engineers and he keeps us updated. > > > https://github.com/coreos/fedora-coreos-tracker/issues/1066 > > > > Ideally we can revert the upstream commit from the stable kernels, since > > otherwise Debian users on AWS Xen instance types may be stuck using > > older, unsafe kernels. Especially if we have time to include the change > > in the upcoming bullseye and buster point releases. If the kernel > > updates for those stable updates have already been built, though, it > > might be too late to matter. By the time we publish our next kernel > > builds, the AWS Xen update may be complete. > > Wehere one can track the update status for their Xen version directly > or is following the above the only reference? It's just for reference; the deployment timeline isn't published. As far as I know, it's also subject to change in the event that unexpected issues arise or it's preempted by some high severity issue. > How frequent is this particular combination of hardware/software? We > have the change already applied for a while in bullseye, buster would > be impacted new since the last update done for security fixes The impacted instance types aren't the most common, as they're not the latest generation. So I expect that the majority of the impact is felt by people or organizations that haven't yet been able to make time to switch to newer instance types. The implication here, of course, is that many of these deployments may be production environment where stability is prioritized over migration to the new thing. We get a little bit of data about what instance types are used with Debian on AWS, but it's incomplete as it only reflects usage by AWS customers who use access Debian via the AWS Marketplace. Consider it something like popcon data; it's essentially opt-in. If the data we get from the Marketplace covering the past 3 days worth of activity is representative of the Debian usage in general, then it looks like roughly 1% of Debian users on AWS are trying to use the impacted instance types. > Are there workarounds for the affected users of this combination? I > see some options listed in > https://wiki.debian.org/Cloud/AmazonEC2Image/Bullseye People can use newer generation instance types, which are not impacted. Depending on the use case, that could be a trivial change, but it could also be disruptive. Newer instance types aren't based on Xen at all and expose a different hardware device model to the instance. Debian supports the newer instance types, but the end user workload may still need additional nontrivial qualification. > If we revert the commit it reverts a fix for a bug with Marvell NVME > devices. > > But we cannot just revert the commit for the cloud images. Understood. > If we know something about the release schedule from Amazon to update > their Xen instances (which is the way to move forward, since upstream > won't revert the commit) then we should leave the status as it is for > bullseye (and now for buster). For bullseye there is there is > CVE-2022-0847 fixes they would need to pick up. Yes, the problem will go away when the Xen fleet is updated. It sounds like we're looking at roughly a 3 month timeline, after which point the patch won't be a problem. However, until then, people who need to use Xen instances will be stuck either running an unsafe kernel or building their own. noah
Bug#637461: marked as done (nfs-common: On stations, does not mount at boot of server NFS share)
Your message dated Sat, 19 Mar 2022 17:41:43 +0100 with message-id <1de20de75275d8975d0b22f51169186ce64baa83.ca...@decadent.org.uk> and subject line Re: nfs-common: On stations, does not mount at boot of server NFS share has caused the Debian Bug report #637461, regarding nfs-common: On stations, does not mount at boot of server NFS share 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.) -- 637461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.2.2-4 Severity: important Dear Sir the server seems fine and working. Everyboots do not mount tbhe /home/freevonfs so I gotta do manually with root eaach time :( server side is fine /etc/fstab is like on client: # /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). # # proc/proc procdefaults0 0 # / was on /dev/sda1 during installation UUID=70101d91-72a6-4ce9-a482-6e508b9ef9ef / ext4 errors=remount-ro 0 1 # /home was on /dev/sda6 during installation UUID=686693f7-7878-425f-8490-8e7b784a86ef /home ext3defaults 0 2 # swap was on /dev/sda5 during installation UUID=a1f64a19-2ce8-49ed-98b9-595ff4d2cb5e noneswapsw 0 0 #/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 #/dev/sdb1 /media/usb0 autorw,user,noauto 0 0 192.168.1.2:/music /home/freevonfs nfs auto,defaults 0 0 -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (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 Versions of packages nfs-common depends on: ii adduser 3.112+nmu2 add and remove users and groups ii initscripts 2.88dsf-13.1 scripts for initializing and shutt ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libcap2 1:2.19-3 support for getting/setting POSIX. ii libcomerr2 1.41.12-4stable1 common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-21.8.3+dfsg-4squeeze1 MIT Kerberos runtime libraries - k ii libgssglue1 0.1-4mechanism-switch gssapi library ii libk5crypto31.8.3+dfsg-4squeeze1 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4squeeze1 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 netbase 4.45 Basic TCP/IP networking system ii portmap 6.0.0-2 RPC port mapper ii ucf 3.0025+nmu1 Update Configuration File: preserv nfs-common recommends no packages. nfs-common suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Closing due to lack of response. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#637874: marked as done (nfs-kernel-server: need to restart daily the server to let users mount the exports)
Your message dated Sat, 19 Mar 2022 17:41:43 +0100 with message-id <1de20de75275d8975d0b22f51169186ce64baa83.ca...@decadent.org.uk> and subject line Re: nfs-common: On stations, does not mount at boot of server NFS share has caused the Debian Bug report #637461, regarding nfs-kernel-server: need to restart daily the server to let users mount the exports 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.) -- 637461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: last one of debian stable , up to date Severity: important Hi, Since 1-2 years, the bug has not been fixed yet. Now debian testing is now stable, and bugs remains. OK. I will post you the content of my /etc//exports soon. it is however very basic and normal. The server debian is very well installed and the bug surely exists. To let stations to mount the /home, 1 - /etc/init.d/nfs-kernel-server restart must be performed frequently 2-on stations. you must create a script into rc2.d to say to mount /home via mount /home with a well prior configured /etc/fstab hank s alot love debian -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (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 --- End Message --- --- Begin Message --- Closing due to lack of response. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#625601: marked as done (mount.nfs complains about statd is not running while it is running)
Your message dated Sat, 19 Mar 2022 17:39:17 +0100 with message-id <51e496c44bb03e3fcdfd48946bc6907a80bab1b1.ca...@decadent.org.uk> and subject line Re: mount.nfs complains about statd is not running while it is running has caused the Debian Bug report #625601, regarding mount.nfs complains about statd is not running while it is running 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.) -- 625601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.2.3-2 Severity: important rpcinfo: can't contact portmapper: rpcinfo: RPC: Authentication error; why = Client credential too weak The package bug script /usr/share/bug/nfs-common/script exited with an error status (return code = 256). Do you still want to file a report? [y|N|q|?]? reporting nevertheless. I start nfs client services: shambhala:~> /etc/init.d/nfs-common stop Stopping NFS common utilities: idmapd statd. shambhala:~> /etc/init.d/rpcbind stop Stopping rpcbind daemon shambhala:~> /etc/init.d/rpcbind start Starting rpcbind daemon shambhala:~> rpcinfo -p program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper shambhala:~> /etc/init.d/nfs-common start Starting NFS common utilities: statd idmapd. shambhala:~> rpcinfo -p 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 37575 status 1000241 tcp 54562 status shambhala:~> ps aux | grep statd | grep -v grep statd13555 0.0 0.0 2268 1012 ?Ss 15:37 0:00 /sbin/rpc.statd I mount an export: shambhala:~> mount -t nfs -o vers=3 172.21.101.9:/vol/nfstest /mnt/zeit /bin/sh: Illegal option -p mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified (I reported the bashism in /usr/sbin/start-statd separately.) I have in daemon.log: shambhala:~> tail -3 /var/log/daemon.log May 4 15:37:35 localhost rpc.statd[13555]: Version 1.2.3 starting May 4 15:37:35 localhost sm-notify[13556]: Version 1.2.3 starting May 4 15:37:35 localhost sm-notify[13556]: Already notifying clients; Exiting! sm-notify does not appear to be running: shambhala:~> ps aux | egrep "(rpc|sm-notify)" | grep -v grep root 1906 0.0 0.0 0 0 ?S< 13:55 0:00 [rpciod] root 13544 0.0 0.0 2204 932 ?Ss 15:37 0:00 /sbin/rpcbind -w statd13555 0.0 0.0 2268 1012 ?Ss 15:37 0:00 /sbin/rpc.statd root 13568 0.0 0.0 2492 536 ?Ss 15:37 0:00 /usr/sbin/rpc.idmapd Thanks. -- Package-specific info: -- rpcinfo -- -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (450, 'testing'), (400, 'unstable'), (110, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38.5-tp42-snapshot-resv-size-dirty (PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.112+nmu2 add and remove users and groups ii initscripts 2.88dsf-13.5scripts for initializing and shutt ii libc62.11.2-11 Embedded GNU C Library: Shared lib ii libcap2 1:2.20-1support for getting/setting POSIX. ii libcomerr2 1.41.12-2 common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-2 1.9+dfsg-1+b1 MIT Kerberos runtime libraries - k ii libgssglue1 0.2-2 mechanism-switch gssapi library ii libk5crypto3 1.9+dfsg-1+b1 MIT Kerberos runtime libraries - C ii libkrb5-31.9+dfsg-1+b1 MIT Kerberos runtime libraries ii libnfsidmap2 0.24-1 An nfs idmapping library ii libtirpc10.2.1-1 transport-independent RPC library ii libwrap0 7.6.q-19Wietse Venema's TCP wrappers libra ii lsb-base
Bug#620299: marked as done (nfs-kernel-server: nfs stop working after some time - rpc.mountd and rpciod in D state)
Your message dated Sat, 19 Mar 2022 17:37:13 +0100 with message-id and subject line Re: nfs-kernel-server: nfs stop working after some time - rpc.mountd and rpciod in D state has caused the Debian Bug report #620299, regarding nfs-kernel-server: nfs stop working after some time - rpc.mountd and rpciod in D state 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.) -- 620299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: 1:1.2.2-4 Severity: important Tags: squeeze Hi, I've got a strange behavior with my nfs server since I use nfsv4. I'm using nfsv3 and nfsv4 with libpam-ldap, libnss-ldap, and unscd. The server, after some times (it can be few days or some weeks), stop responding, and the clients cannot mount shares anymore. Once the server has hung, the first rpciod process is in D state, as the rpc.mountd process. I can kill -9 the rpc.mountd process and restart it, but it get back in D state as soon as a mount request occurs. I'm unable to get nfs working again, unless rebooting the server. Here is my configuration. 'nas' and 'dev' are two nfs servers, mounted on each other. The problems occurs on the server 'dev'. root@dev:/# cat /etc/fstab # proc/proc procdefaults0 0 cgroup /cgroup cgroup defaults0 0 /dev/sda3/boot ext2defaults0 2 /dev/mapper/dev-swap none swapsw 0 0 /dev/mapper/dev-root / ext4errors=remount-ro 0 1 /dev/mapper/dev-home /home ext4defaults0 2 /dev/mapper/dev-tmp /tmpext4defaults0 2 /dev/mapper/dev-usr /usrext4defaults0 2 /dev/mapper/dev-var /varext4defaults0 2 /dev/mapper/dev-log /var/logext4defaults0 2 /dev/mapper/dev-dns /var/dns-devext4defaults0 2 /dev/mapper/dev-dns /dns-devext4defaults0 2 nas:/dns-nas/dns-nasnfs4_netdev,rw,soft,tcp 0 0 nas:/sav/var/savnfs4_netdev,rw,soft 0 0 root@dev:/# cat /etc/exports # nfsv3 /dns-dev192.168.151.0/24(rw,sync,subtree_check,no_root_squash) # nfsv4 /var/ 192.168.151.0/24(fsid=0,rw,sync,crossmnt,no_subtree_check) /var/dns-dev 192.168.151.0/24(rw,sync,crossmnt,no_subtree_check,no_root_squash) root@dev:/# showmount -a rpc mount dump: RPC: Timed out root@dev:/# showmount -e rpc mount dump: RPC: Timed out root@dev:/# rpcinfo -p program no_version protocole no_port 102 tcp111 portmapper 1000241 udp 47486 status 1000241 tcp 33830 status 102 udp111 portmapper 1000211 udp 49373 nlockmgr 1000213 udp 49373 nlockmgr 1000214 udp 49373 nlockmgr 1000211 tcp 36200 nlockmgr 1000213 tcp 36200 nlockmgr 1000214 tcp 36200 nlockmgr 132 tcp 2049 nfs 133 tcp 2049 nfs 134 tcp 2049 nfs 132 udp 2049 nfs 133 udp 2049 nfs 134 udp 2049 nfs 151 udp 41885 mountd 151 tcp 54023 mountd 152 udp 41885 mountd 152 tcp 54023 mountd 153 udp 41885 mountd 153 tcp 54023 mountd root@dev:/# cat /proc/fs/nfsd/exports # Version 1.1 # Path Client(Flags) # IPs root@nas:/# cat /etc/fstab # proc/proc procdefaults0 0 /dev/hda2 noneswapsw 0 0 /dev/hda1 / ext3errors=remount-ro 0 1 /dev/mapper/nas-tmp /tmpext3defaults0 2 /dev/mapper/nas-usr /usrext3defaults0 2 /dev/mapper/nas-var /varext3defaults0 2 /dev/mapper/nas-cache /var/cache ext3defaults0 2 /dev/mapper/nas-log /var/logext3defaults0 2 /dev/mapper/nas-dns /dnsext4defaults0 2 /dev/mapper/nas-dns /dns-nasext4defaults0 2 /dev/mapper/nas-dns /var/dns-nasext4defaults0 2 /dev/mapper/nas-sav /var/savext4defaults0 2 dev:/dns-dev
Bug#602642: marked as done (nfs-kernel-server: Crossmnt stopped working after upgrade from Lenny to Squeeze)
Your message dated Sat, 19 Mar 2022 17:33:00 +0100 with message-id <5bbed3a214fc8631cdf3c68e4f18d4f378b35f75.ca...@decadent.org.uk> and subject line Re: nfs-kernel-server: Crossmnt stopped working after upgrade from Lenny to Squeeze has caused the Debian Bug report #602642, regarding nfs-kernel-server: Crossmnt stopped working after upgrade from Lenny to Squeeze 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.) -- 602642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: 1:1.1.2-6lenny2 Severity: important Upgraded file server from Lenny to Squeeze. After upgrade NFS clients failed to access bind mounted subdirectories on NFS server, error message about stale NFS handle. Basic setup on "fileserver": /dev/md0 is mounted at /mnt/md0 in fstab /mnt/md0/raid is bind mounted at /data/raid in fstab /etc/exports looks like this: /data 192.168.0.0/255.255.255.0(ro,no_subtree_check,crossmnt) NFS clients mount fileserver:/data. This setup has been used for about a year. After "fileserver" was upgraded to Squeeze the clients could mount fileserver:/data but not access the raid subfolder, got an error message about stale NFS handle. Downgrading nfs-kernel-server and nfs-common to Lenny versions (1:1.1.2-6lenny2) restored functionality. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-kernel-server depends on: ii libblkid12.17.2-3.3 block device id library ii libc62.11.2-7Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-2 common error description library ii libgssglue1 0.1-4 mechanism-switch gssapi library ii libkrb53 1.8.3+dfsg-2transitional package for MIT Kerbe ii libnfsidmap2 0.23-2 An nfs idmapping library ii librpcsecgss30.19-2 allows secure rpc communication us ii libwrap0 7.6.q-19Wietse Venema's TCP wrappers libra ii lsb-base 3.2-23.1Linux Standard Base 3.2 init scrip ii nfs-common 1:1.1.2-6lenny2 NFS 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 --- Closing this due to lack of response. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#600871: marked as done (nfs-common: Very slow and unreliable performance of GUI(KDE) when /home nfs mounted)
Your message dated Sat, 19 Mar 2022 17:29:36 +0100 with message-id <603a22361d52220a985b6c9c5297a2288126bcb8.ca...@decadent.org.uk> and subject line Re: nfs-common: Very slow and unreliable performance of GUI(KDE) when /home nfs mounted has caused the Debian Bug report #600871, regarding nfs-common: Very slow and unreliable performance of GUI(KDE) when /home nfs 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.) -- 600871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600871 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.1.2-6lenny2 Severity: important -- System Information: Debian Release: Lenny APT prefers stable APT policy: (900, 'stable'), (700, 'stable'), (650, 'testing'), (500, 'proposed-updates') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-common depends on: ii adduser 3.110add and remove users and groups ii initscripts 2.86.ds1-61 Scripts for initializing and shutt ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libcomerr2 1.41.3-1 common error description library ii libevent1 1.3e-3 An asynchronous event notification 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 netbase 4.34 Basic TCP/IP networking system ii portmap 6.0-9RPC port mapper ii ucf 3.0016 Update Configuration File: preserv nfs-common recommends no packages. nfs-common suggests no packages. -- no debconf information The problem has occurred, when update was performed from BPO. nfs-common 1:1.1.2-6lenny2 -> 1:1.2.2-1~bpo50+1 As users /home mounted from centralized location with nfs, it become impossible to start GUI, particularly KDE. It is not a KDE problem, as when I fall-back to 1:1.1.2-6 everything was back to normal. I feel bad that I cannot introduce more logs as there is none generated by nfs IMHO. --- End Message --- --- Begin Message --- Closing this due to lack of response. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#562821: marked as done (nfs-common: Fails to map user id's via idmapd)
Your message dated Sat, 19 Mar 2022 17:27:00 +0100 with message-id and subject line Re: nfs-common: Fails to map user id's via idmapd has caused the Debian Bug report #562821, regarding nfs-common: Fails to map user id's via idmapd 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.) -- 562821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.2.0-4.1 Severity: important It seems this version have problem with starting statd which should only be used on a NFS server. An unexpected side effect is that this seems to break id mapping on NFSv4 also. The directories /var/lib/nfs/rpc_pipefs/nfs/clnt0 /var/lib/nfs/rpc_pipefs/nfs/clnt1 are not created. Have reverted to Version: 1:1.2.0-4.1 which is working properly. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-common depends on: ii adduser 3.112 add and remove users and groups ii initscripts 2.87dsf-8 scripts for initializing and shutt ii libc62.10.2-2GNU C Library: Shared libraries ii libcomerr2 1.41.9-1common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-2 1.7+dfsg-3 MIT Kerberos runtime libraries - k ii libgssglue1 0.1-4 mechanism-switch gssapi library ii libk5crypto3 1.7+dfsg-3 MIT Kerberos runtime libraries - C ii libkrb5-31.7+dfsg-3 MIT Kerberos runtime libraries ii libnfsidmap2 0.23-2 An nfs idmapping library ii librpcsecgss30.19-2 allows secure rpc communication us ii libwrap0 7.6.q-18Wietse Venema's TCP wrappers libra ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii netbase 4.40Basic TCP/IP networking system ii portmap 6.0.0-1 RPC port mapper ii ucf 3.0025 Update Configuration File: preserv nfs-common recommends no packages. nfs-common suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Closing this due to lack of response. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#568856: marked as done (heartbeat is unable to stop nfs-kernel-server)
Your message dated Sat, 19 Mar 2022 17:28:14 +0100 with message-id <32e049785983ef00676c6227b2643ecf04813378.ca...@decadent.org.uk> and subject line Re: heartbeat is unable to stop nfs-kernel-server has caused the Debian Bug report #568856, regarding heartbeat is unable to stop nfs-kernel-server 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.) -- 568856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: heartbeat Version: 2.1.3-6lenny4 Severity: important heartbeat is unable to stop nfs-kernel-server. The script returns 0 so heartbeat think that nfs is stopped, but when trying to unmount a shared disk (drbd) with /var/lib/nfs symlinked into heartbeat gives up and reboots the server, it fails since nfsd is still locking files in that folder. Has been discussed in 2004 here: http://lists.linbit.com/pipermail/drbd-user/2004-June/001107.html and on the HA website: http://www.linux-ha.org/DRBD/NFS (under 5.c and 5.d) Current workaround is calling a script that kills nfsd with haresources as suggested in linux-ha.org (If i start nfs-kernel-server manually, i am also able to stop it manually) ha.cf: ### # HA config autojoin none debugfile /var/log/ha-debug logfile /var/log/ha-log logfacility local0 keepalive 200ms #warntime 1 deadtime 2 #initdead 30 udpport 694 bcast drbdeth0 mcast drbdeth0 239.0.0.1 694 1 0 udp drbdeth0 auto_failback off node nfs-ha-01 node nfs-ha-02 apiauth default uid=nobody gid=haclient apiauth ipfail uid=hacluster apiauth ping gid=nogroup uid=nobody,hacluster respawn hacluster /usr/lib/heartbeat/ipfail ping x.x.x.x deadping 3 ### haresources: ### nfs-ha-01 x.x.x.x/24 drbddisk LVM::drbdtest Filesystem::/dev/drbd0::/cluster-metadata::ext3::defaults,noatime Filesystem::/dev/drbdtest/test::/mnt/test::xfs nfs-kernel-server nfs-common -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-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/bash Versions of packages heartbeat depends on: ii adduser 3.110add and remove users and groups ii gawk1:3.1.5.dfsg-4.1 GNU awk, a pattern scanning and pr ii iproute 20080725-2 networking and traffic control too ii iputils-ping3:20071127-1 Tools to test the reachability of ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co ii libc6 2.7-18lenny2 GNU C Library: Shared libraries ii libcurl37.18.2-8lenny3 Multi-protocol file transfer libra ii libglib2.0-02.16.6-3 The GLib library of C routines ii libgnutls26 2.4.2-6+lenny2 the GNU TLS library - runtime libr ii libltdl31.5.26-4+lenny1 A system independent dlopen wrappe ii libncurses5 5.7+20081213-1 shared libraries for terminal hand ii libnet1 1.1.2.1-2library for the construction and h ii libopenhpi2 2.12.0-1 OpenHPI libraries (runtime and sup ii libpam-runtime 1.0.1-5+lenny1 Runtime support for the PAM librar ii libpam0g1.0.1-5+lenny1 Pluggable Authentication Modules l ii libsnmp15 5.4.1~dfsg-12SNMP (Simple Network Management Pr ii libssl0.9.8 0.9.8g-15+lenny6 SSL shared libraries ii libuuid11.41.3-1 universally unique id library ii libwrap07.6.q-16 Wietse Venema's TCP wrappers libra ii libxml2 2.6.32.dfsg-5+lenny1 GNOME XML library ii libxml2-utils 2.6.32.dfsg-5+lenny1 XML utilities ii mawk1.3.3-11.1 a pattern scanning and text proces ii psmisc 22.6-1 Utilities that use the proc filesy ii python 2.5.2-3 An interactive high-level object-o ii python-central 0.6.8register and build utility for Pyt ii zlib1g 1:1.2.3.3.dfsg-12compression library - runtime Versions of packages heartbeat recommends: ii iptables 1.4.2-6administration tools for packet fi ii logrotate 3.7.1-5Log rotation utility ii rsyslog [system-log-daemon] 3.18.6-4 enhanced multi-threaded syslogd heartbeat suggests no packages. -- no debconf informatio
Bug#522926: marked as done (client cannot write to new files on server, only edit/delete/create)
Your message dated Sat, 19 Mar 2022 17:26:02 +0100
with message-id <2ecbfeced15a8c9b7f2c24dc722bf14339aa8936.ca...@decadent.org.uk>
and subject line Re: client cannot write to new files on server, only
edit/delete/create
has caused the Debian Bug report #522926,
regarding client cannot write to new files on server, only edit/delete/create
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.)
--
522926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.1.4-1
Severity: grave
I've had a great morning with NFS. First, the server had to be
restarted, which caused all clients (at least one was using each of
1.1.4-1 and 1.1.5-[12]) to require a restart, since all processes
just hung hard.
New mounts would also not work, even though trying to mount exported
filesystems without permission on the server yielded an "access
denied" error on the client.
After I rebooted the clients, they could mount and browse the
filesystem, and read files without problems.
They could edit files too.
However, they could not write to new files. They could create them,
but trying to write to them causes:
open("testfile", O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EINVAL (Invalid
argument)
The file is created, but it cannot be written to.
I can delete files just fine.
This happens with 1.1.4-1 through 1.1.5-2, talking to
a 1:1.1.2-6lenny1 kernel server.
The NFS infrastructure here has been working for years and also
after the lenny upgrade, and I have tried restarting the kernel
server daemon many times. The only thing that has changed between
when it was working and now was today's OpenSSL upgrade.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB, 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.110 add and remove users and groups
ii initscripts 2.86.ds1-61 Scripts for initializing and shutt
ii libc62.9-6 GNU C Library: Shared libraries
ii libcomerr2 1.41.3-1common error description library
ii libevent11.3e-3 An asynchronous event notification
ii libgssglue1 0.1-2 mechanism-switch gssapi library
ii libkrb53 1.6.dfsg.4~beta1-12 Transitional library package/krb4
ii libnfsidmap2 0.21-2 An nfs idmapping library
ii librpcsecgss30.18-1 allows secure rpc communication us
ii libwrap0 7.6.q-16Wietse Venema's TCP wrappers libra
ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip
ii netbase 4.34Basic TCP/IP networking system
ii portmap 6.0-9 RPC port mapper
ii ucf 3.0018 Update Configuration File: preserv
nfs-common recommends no packages.
nfs-common suggests no packages.
-- debconf-show failed
--
.''`. martin f. krafft Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
--- End Message ---
--- Begin Message ---
Closing this due to lack of response.
Ben.
--
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein
signature.asc
Description: This is a digitally signed message part
--- End Message ---
Bug#521878: marked as done (nfs-kernel-server: nfs4 mount with sec=krb5 not working cause bad uid mapping)
Your message dated Sat, 19 Mar 2022 17:24:42 +0100
with message-id <93ee5784bd1d011076afb131ce217f334acf2344.ca...@decadent.org.uk>
and subject line Re: nfs-kernel-server: nfs4 mount with sec=krb5 not working
cause bad uid mapping
has caused the Debian Bug report #521878,
regarding nfs-kernel-server: nfs4 mount with sec=krb5 not working cause bad uid
mapping
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.)
--
521878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.1.4-1
Severity: important
it's impossible to mount a nfs4 share with kerberos5 security on current sid
systems.
the problem looks like from here:(full log below)
Mar 30 19:26:55 gythtv rpc.svcgssd[g379]: WARNING: get_ids: failed to map name
'root/mythtv.mydomain.local@MYREALM.LOCAL' to uid/gid: Invalid argument
i have found some hints that this problem comes from libnfsidmap2 with google.
(http://linux-nfs.org/pipermail/nfsv4/2008-October/009399.html). But the sid
version seems to be really old.
i hope this will help to find the bug.
test setup:
krb5-kdc, nfs-server and client on same machine (for first testing
purpose)
MYREALM.LOCAL and mydomain.local are equal in my test setup.
/etc/krb5.conf
##>%
[libdefaults]
default_realm = MYREALM.LOCAL
# dns_lookup_realm = true
# dns_lookup_kdc = false
[realms]
MYREALM.LOCAL = {
kdc = mythtv.mydomain.local
admin_server = mythtv.mydomain.local
default_domain = mydomain.local
}
[domain_realm]
.mydomain.local = MYREALM.LOCAL
%<#
mythtv:~# klist -e -k /etc/krb5.keytab
Keytab name: FILE:/etc/krb5.keytab
KVNO Principal
--
3 nfs/mythtv.19.ros.03046@19.ros.03046.com (DES cbc mode with CRC-32)
3 root/mythtv.19.ros.03046@19.ros.03046.com (DES cbc mode with CRC-32)
/etc/exports:
/data gss/krb5p(rw,async,no_subtree_check,nohide,crossmnt)
/ gss/krb5p(fsid=0,rw,async,no_subtree_check,nohide,crossmnt)
mythtv:~# egrep -v "^#|^$" /etc/default/nfs-*
/etc/default/nfs-common:NEED_STATD=
/etc/default/nfs-common:STATDOPTS=
/etc/default/nfs-common:NEED_IDMAPD=yes
/etc/default/nfs-common:NEED_GSSD=yes
/etc/default/nfs-common:RPCGSSDOPTS="-vvv -rrr"
/etc/default/nfs-kernel-server:RPCNFSDCOUNT=8
/etc/default/nfs-kernel-server:RPCNFSDPRIORITY=0
/etc/default/nfs-kernel-server:RPCMOUNTDOPTS=--manage-gids
/etc/default/nfs-kernel-server:NEED_SVCGSSD=yes
/etc/default/nfs-kernel-server:RPCSVCGSSDOPTS="-vvv -rrr"
mythtv:~# mount -t nfs4 -o sec=krb5 mythtv:/data /mnt/
mount.nfs4: access denied by server while mounting mythtv:/data
log messages from daemon.log...
Mar 30 19:26:55 mythtv rpc.idmapd[2424]: New client: 52
Mar 30 19:26:55 mythtv rpc.idmapd[2424]: Opened
/var/lib/nfs/rpc_pipefs/nfs/clnt52/idmap
Mar 30 19:26:55 mythtv rpc.gssd[2428]: handling krb5 upcall
Mar 30 19:26:55 mythtv rpc.gssd[2428]: Full hostname for
'mythtv.mydomain.local' is 'mythtv.mydomain.local'
Mar 30 19:26:55 mythtv rpc.gssd[2428]: Full hostname for
'mythtv.mydomain.local' is 'mythtv.mydomain.local'
Mar 30 19:26:55 mythtv rpc.gssd[2428]: Success getting keytab entry for
'root/mythtv.mydomain.local@'
Mar 30 19:26:55 mythtv rpc.gssd[2428]: INFO: Credentials in CC
'FILE:/tmp/krb5cc_machine_MYREALM.LOCAL' are good until 1238469941
Mar 30 19:26:55 mythtv rpc.gssd[2428]: INFO: Credentials in CC
'FILE:/tmp/krb5cc_machine_MYREALM.LOCAL' are good until 1238469941
Mar 30 19:26:55 mythtv rpc.gssd[2428]: using
FILE:/tmp/krb5cc_machine_MYREALM.LOCAL as credentials cache for machine creds
Mar 30 19:26:55 mythtv rpc.gssd[2428]: using environment variable to select
krb5 ccache FILE:/tmp/krb5cc_machine_MYREALM.LOCAL
Mar 30 19:26:55 mythtv rpc.gssd[2428]: creating context using fsuid 0 (save_uid
0)
Mar 30 19:26:55 mythtv rpc.gssd[2428]: creating tcp client for server
mythtv.mydomain.local
Mar 30 19:26:55 mythtv rpc.gssd[2428]: creating context with server
nfs@mythtv.mydomain.local
Mar 30 19:26:55 mythtv rpc.gssd[2428]: in authgss_create_default()
Mar 30 19:26:55 mythtv rpc.gssd[2428]: in authgss_create()
Mar 30 19:26:55 mythtv rpc.gssd[2428]: authgss_create: name is 0x9691488
Mar 30 19:26:55 mythtv rpc.gssd[2428]: authgss_create: gd->name is 0x96937a8
Mar 30 19:26:55 mythtv rpc.gssd[2428]: in authgss_refresh()
Mar 30 19:26:55 myth
Processed: tagging 446238 ...
Processing commands for cont...@bugs.debian.org:
> tags 446238 + upstream
Bug #446238 {Done: Ben Hutchings } [nfs-common]
nfs-common: Locks when using nfs4 sec=krb5 and user ticket expires
Added tag(s) upstream.
> forwarded 446238
> https://lore.kernel.org/linux-nfs/08967499-6b9d-4dbb-8118-5e6e1e3ef06f@mail/
Bug #446238 {Done: Ben Hutchings } [nfs-common]
nfs-common: Locks when using nfs4 sec=krb5 and user ticket expires
Set Bug forwarded-to-address to
'https://lore.kernel.org/linux-nfs/08967499-6b9d-4dbb-8118-5e6e1e3ef06f@mail/'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
446238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#446238: marked as done (nfs-common: Locks when using nfs4 sec=krb5 and user ticket expires)
Your message dated Sat, 19 Mar 2022 17:21:17 +0100 with message-id <655212549a6125b02fa4162c5d6cc49085f2d4c5.ca...@decadent.org.uk> and subject line Re: nfs-utils updated to 1.3.4-1, please check your bug #446238 has caused the Debian Bug report #446238, regarding nfs-common: Locks when using nfs4 sec=krb5 and user ticket expires 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.) -- 446238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.0.10-6+etch.1 Severity: important The problem can be reproduced in the following conditions Automounted homes over nfs4 with sec=krb5 Start a session on the nfs client and let the user ticked (used to grant the nfs access) expire After this the user can not access is home (as should be expected) However, it also appens that, for example, any trial to start a new session of some other user will sucessfully mount the respective home but the login process will stay forever trying to read a file (.bash_profile for example). The client syslog presents messages like these Oct 11 07:44:46 directivo rpc.gssd[30786]: ERROR: GSS-API: error in gss_acquire_cred(): The referenced credentials have expired - No error Oct 11 07:44:46 directivo rpc.gssd[30786]: WARNING: Failed to create krb5 context for user with uid 726 for server essa.essa.pt Oct 11 07:44:46 directivo rpc.gssd[30786]: ERROR: GSS-API: error in gss_acquire_cred(): The referenced credentials have expired - No error Oct 11 07:44:46 directivo rpc.gssd[30786]: WARNING: Failed to create krb5 context for user with uid 726 for server essa.essa.pt Oct 11 07:44:46 directivo kernel: Error: state recovery failed on NFSv4 server 192.168.0.99 with error 13 Oct 11 07:44:46 directivo rpc.gssd[30786]: ERROR: GSS-API: error in gss_acquire_cred(): The referenced credentials have expired - No error Oct 11 07:44:46 directivo rpc.gssd[30786]: WARNING: Failed to create krb5 context for user with uid 726 for server essa.essa.pt Oct 11 07:44:46 directivo rpc.gssd[30786]: ERROR: GSS-API: error in gss_acquire_cred(): The referenced credentials have expired - No error Oct 11 07:44:46 directivo rpc.gssd[30786]: WARNING: Failed to create krb5 context for user with uid 726 for server essa.essa.pt Oct 11 07:44:46 directivo kernel: Error: state recovery failed on NFSv4 server 192.168.0.99 with error 13 where 726 is the owner of the expired ticket in the present case Refreshing the expired ticket for this user grants him access to his home again and, additionaly, unlocks access to the other user homes In a single user nfs client machine this is pretty harmless, but in a multiuser one or if it is an X or thin terminal server, as it is the case here, this is a show stopper On client autofs 4.1.4-13 libpam-krb5 2.6-1 On server nfs-kernel-server1.0.10-6+etch.1 krb5-kdc 1.4.4-7etch4 libkrb53 1.4.4-7etch4 If more details or log contents are needed please let me know Thanks in advance for any help Pedro Rodrigues -- 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-5-686 Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8) Versions of packages nfs-common depends on: ii adduser 3.102 Add and remove users and groups ii libc62.3.6.ds1-13etch2 GNU C Library: Shared libraries ii libcomer 1.39+1.40-WIP-2006.11.14+dfsg-2 common error description library ii libevent 1.1a-1 An asynchronous event notification ii libgssap 0.10-4 A mechanism-switch gssapi library ii libkrb53 1.4.4-7etch4MIT Kerberos runtime libraries ii libnfsid 0.18-0 An nfs idmapping library ii librpcse 0.14-2etch1 allows secure rpc communication us ii libwrap0 7.6.dbs-13 Wietse Venema's TCP wrappers libra ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip ii netbase 4.29Basic TCP/IP networking system ii portmap 5-26The RPC portmapper ii ucf 2.0020 Update Configuration File: preserv nfs-common recommends no packages. -- no debconf information -- _ Pedro Celestino
Processed: Re: nfs-common: Systemd does not correctly read /etc/default/nfs-common
Processing control commands: > tag -1 moreinfo Bug #913310 [nfs-common] nfs-common: Systemd does not correctly read /etc/default/nfs-common Added tag(s) moreinfo. -- 913310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 883890
Processing commands for cont...@bugs.debian.org: > tags 883890 - moreinfo Bug #883890 [nfs-common] nfs-common: Fully Qualified DNS Name mounts in fstab fail to be mounted Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 883890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883890 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913310: nfs-common: Systemd does not correctly read /etc/default/nfs-common
Control: tag -1 moreinfo On Fri, 09 Nov 2018 14:35:59 +0100 Marco Gaiarin wrote: > Package: nfs-common > Version: 1:1.3.4-2.1 > Severity: important > > Dear Maintainer, > > I'm trying to play with NFSv4 with my just-installed or just-upgraded stretch system. > > I've found that: > > a) is impossible to set daemons flags in /etc/default/nfs-common, because systemd does not read it. > > b) it is not possible to restart nfs common daemon, There is no nfs-common daemon. > because nfs-common is disabled (and this seems intended) > and nfs-client is a target, so seems can be run only at boot. > [probably this is a consequence of a)] > > For a), seems that the 'nfs-config' systemd stanza correctly build up '/run/sysconfig/nfs-utils' environment files, but > then, there's no 'EnvironmentFile=' row in 'nfs-client' and 'nfs- server' so environment varialbles are not read. They don't need it. Each daemon has its own unit that (in this version) does use EnvironmentFile. What is the actual problem you are trying to solve? Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
Bug#609344: marked as done (nfs-kernel-server: Serious problem with NFS server, not working under testing)
Your message dated Sat, 19 Mar 2022 17:16:27 +0100 with message-id <496c166e661e6a3ae429c4445bbc6a4c03c6fb1a.ca...@decadent.org.uk> and subject line Re: nfs-kernel-server: Serious problem with NFS server, not working under testing has caused the Debian Bug report #609344, regarding nfs-kernel-server: Serious problem with NFS server, not working under testing 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.) -- 609344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: 1:1.2.2-4 Severity: important Dear Sir, My clients hangs on mounting their home at boot # mount /home/ ^C Now I do this on the server NFS: /etc/init.d/nfs-kernel-server restart And I try again on the client: root@toshiba:/# mount /home/ root@toshiba:/# Here it is now. The server has something wrong in NFS exporting and shareing. Please a fix would be great because it is not yet stable. Best regards (I gonna try an upgrade, I fear the upgrade that will break my box... let's pray it works) All the best Linux rocks Y. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (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 Versions of packages nfs-kernel-server depends on: ii libblkid1 2.17.2-3.3 block device id library ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-2common error description library ii libgssapi-krb5-21.8.3+dfsg-2 MIT Kerberos runtime libraries - k ii libgssglue1 0.1-4mechanism-switch gssapi library ii libk5crypto31.8.3+dfsg-2 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-2 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.1 Linux Standard Base 3.2 init scrip ii nfs-common 1:1.2.2-4NFS 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 --- Closing this due to lack of response. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: tagging 832513
Processing commands for cont...@bugs.debian.org: > tags 832513 + upstream Bug #832513 [nfs-common] [nfs-common] nfs-idmapd.service fails unless package is installed nfs-kernel-server Bug #832514 [nfs-common] [nfs-common] nfs-idmapd.service fails unless package is installed nfs-kernel-server Added tag(s) upstream. Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 832513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832513 832514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#847557: marked as done (/usr/sbin/exportfs: exportfs cannot handle IPv6 addresses)
Your message dated Sat, 19 Mar 2022 17:12:54 +0100 with message-id and subject line Re: Bug#847557: nfs-utils updated to 1.3.4-1, please check your bug #847557 has caused the Debian Bug report #847557, regarding /usr/sbin/exportfs: exportfs cannot handle IPv6 addresses 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.) -- 847557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: 1:1.2.8-9.2 Severity: important File: /usr/sbin/exportfs Tags: ipv6 Dear Maintainer, when trying to export/unexport a path i cannot give IPv6 addresses to exportfs. # showmount -e Export list for testhost: /path/sub fe80::%eth0/10 # exportfs -u [fe80::%eth0]/10:/path/sub exportfs: Invalid exporting option: [fe80 When removing the [] i get the same error (without [) When using something like 2001:0db8:1234::/64 the same error occurs. -- 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 59414 mountd 151 tcp 55223 mountd 152 udp 44480 mountd 152 tcp 53745 mountd 153 udp 41426 mountd 153 tcp 55737 mountd 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 37459 nlockmgr 1000213 udp 37459 nlockmgr 1000214 udp 37459 nlockmgr 1000211 tcp 34145 nlockmgr 1000213 tcp 34145 nlockmgr 1000214 tcp 34145 nlockmgr -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS="--manage-gids" NEED_SVCGSSD="" RPCSVCGSSDOPTS="" -- /etc/exports -- /path/sub fe80::%eth0/10(rw,no_subtree_check,no_root_squash) -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/24 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.46 ii keyutils 1.5.9-9 ii libblkid12.29-1 ii libc62.24-7 ii libcap2 1:2.25-1 ii libsqlite3-0 3.15.2-1 ii libtirpc10.2.5-1 ii libwrap0 7.6.q-25 ii lsb-base 9.20161125 ii netbase 5.3 ii nfs-common 1:1.2.8-9.2 ii ucf 3.0036 nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1:1.3.4-1 On Thu, 15 Dec 2016 14:45:04 +0100 Bjoern Laessig wrote: > On Do, 2016-12-15 at 14:15 +0100, Daniel Pocock wrote: > > Thanks for providing a bug report for nfs-utils. > > https://bugs.debian.org/847557 > > - if you have time to test the new package, […] > > Trying the package from sid (1:1.3.4-1): > > # exportfs [2001:0db8:1234::]/64:/path/sub > # showmount -e localhost > Export list for localhost: > /path/sub 2001:0db8:1234::/64 > # exportfs -u [2001:0db8:1234::]/64:/path/sub > > > The bug is fixed in nfs-kernel-server version 1:1.3.4-1 Thank you for checking; I'm now closing the bug report. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: closing 847681
Processing commands for cont...@bugs.debian.org: > close 847681 Bug #847681 [nfs-utils] packaging repository and sid diverging? Various fixes needed. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 847681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 884284 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 884284 src:linux 4.9.65-3 Bug #884284 [nfs-kernel-server] nfs4_reclaim_open_state: Lock reclaim failed Bug reassigned from package 'nfs-kernel-server' to 'src:linux'. No longer marked as found in versions nfs-utils/1:1.3.4-2.1. Ignoring request to alter fixed versions of bug #884284 to the same values previously set Bug #884284 [src:linux] nfs4_reclaim_open_state: Lock reclaim failed Marked as found in versions linux/4.9.65-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 884284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: nfs-kernel-server: svcgssd starts anyways when "disabled" in /etc/default/nfs-kernel-server
Processing control commands: > tag -1 wontfix Bug #884871 [nfs-kernel-server] nfs-kernel-server: svcgssd starts anyways when "disabled" in /etc/default/nfs-kernel-server Added tag(s) wontfix. -- 884871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884871 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#884871: nfs-kernel-server: svcgssd starts anyways when "disabled" in /etc/default/nfs-kernel-server
Control: tag -1 wontfix On Wed, 20 Dec 2017 11:51:22 -0800 Matt Weatherford wrote: > Package: nfs-kernel-server > Version: 1:1.3.4-2.1 > Severity: important > > Dear Maintainer, > > First of all, thank you for all you do to support Debian > > > Heres my /etc/default/nfs-kernel-server config file, it clearly "disables svcgssd" : [...] These flags only affect the init scripts, not systemd. Use systemctl to disable or enable daemons under systemd. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
linux-signed-amd64_4.19.235+1_source.changes is NEW
Mapping buster-proposed-updates to oldstable-proposed-updates. binary:acpi-modules-4.19.0-20-amd64-di is NEW. binary:ata-modules-4.19.0-20-amd64-di is NEW. binary:btrfs-modules-4.19.0-20-amd64-di is NEW. binary:cdrom-core-modules-4.19.0-20-amd64-di is NEW. binary:compress-modules-4.19.0-20-amd64-di is NEW. binary:crc-modules-4.19.0-20-amd64-di is NEW. binary:crypto-dm-modules-4.19.0-20-amd64-di is NEW. binary:crypto-modules-4.19.0-20-amd64-di is NEW. binary:efi-modules-4.19.0-20-amd64-di is NEW. binary:event-modules-4.19.0-20-amd64-di is NEW. binary:ext4-modules-4.19.0-20-amd64-di is NEW. binary:fat-modules-4.19.0-20-amd64-di is NEW. binary:fb-modules-4.19.0-20-amd64-di is NEW. binary:firewire-core-modules-4.19.0-20-amd64-di is NEW. binary:fuse-modules-4.19.0-20-amd64-di is NEW. binary:i2c-modules-4.19.0-20-amd64-di is NEW. binary:input-modules-4.19.0-20-amd64-di is NEW. binary:isofs-modules-4.19.0-20-amd64-di is NEW. binary:jfs-modules-4.19.0-20-amd64-di is NEW. binary:kernel-image-4.19.0-20-amd64-di is NEW. binary:linux-image-4.19.0-20-amd64 is NEW. binary:linux-image-4.19.0-20-cloud-amd64 is NEW. binary:linux-image-4.19.0-20-rt-amd64 is NEW. binary:loop-modules-4.19.0-20-amd64-di is NEW. binary:md-modules-4.19.0-20-amd64-di is NEW. binary:mmc-core-modules-4.19.0-20-amd64-di is NEW. binary:mmc-modules-4.19.0-20-amd64-di is NEW. binary:mouse-modules-4.19.0-20-amd64-di is NEW. binary:mtd-core-modules-4.19.0-20-amd64-di is NEW. binary:multipath-modules-4.19.0-20-amd64-di is NEW. binary:nbd-modules-4.19.0-20-amd64-di is NEW. binary:nic-modules-4.19.0-20-amd64-di is NEW. binary:nic-pcmcia-modules-4.19.0-20-amd64-di is NEW. binary:nic-shared-modules-4.19.0-20-amd64-di is NEW. binary:nic-usb-modules-4.19.0-20-amd64-di is NEW. binary:nic-wireless-modules-4.19.0-20-amd64-di is NEW. binary:pata-modules-4.19.0-20-amd64-di is NEW. binary:pcmcia-modules-4.19.0-20-amd64-di is NEW. binary:pcmcia-storage-modules-4.19.0-20-amd64-di is NEW. binary:ppp-modules-4.19.0-20-amd64-di is NEW. binary:sata-modules-4.19.0-20-amd64-di is NEW. binary:scsi-core-modules-4.19.0-20-amd64-di is NEW. binary:scsi-modules-4.19.0-20-amd64-di is NEW. binary:scsi-nic-modules-4.19.0-20-amd64-di is NEW. binary:serial-modules-4.19.0-20-amd64-di is NEW. binary:sound-modules-4.19.0-20-amd64-di is NEW. binary:speakup-modules-4.19.0-20-amd64-di is NEW. binary:squashfs-modules-4.19.0-20-amd64-di is NEW. binary:udf-modules-4.19.0-20-amd64-di is NEW. binary:uinput-modules-4.19.0-20-amd64-di is NEW. binary:usb-modules-4.19.0-20-amd64-di is NEW. binary:usb-serial-modules-4.19.0-20-amd64-di is NEW. binary:usb-storage-modules-4.19.0-20-amd64-di is NEW. binary:xfs-modules-4.19.0-20-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
Processing of linux-signed-amd64_4.19.235+1_source.changes
linux-signed-amd64_4.19.235+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_4.19.235+1.dsc linux-signed-amd64_4.19.235+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-signed-amd64_5.10.103+1~bpo10+1_source.changes is NEW
binary:acpi-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:ata-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:btrfs-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:cdrom-core-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:crc-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:crypto-dm-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:crypto-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:efi-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:event-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:ext4-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:f2fs-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:fat-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:fb-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:firewire-core-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:fuse-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:i2c-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:input-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:isofs-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:jfs-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:kernel-image-5.10.0-0.bpo.12-amd64-di is NEW. binary:linux-image-5.10.0-0.bpo.12-amd64 is NEW. binary:linux-image-5.10.0-0.bpo.12-cloud-amd64 is NEW. binary:linux-image-5.10.0-0.bpo.12-rt-amd64 is NEW. binary:loop-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:md-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:mmc-core-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:mmc-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:mouse-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:mtd-core-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:multipath-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:nbd-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:nic-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:nic-pcmcia-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:nic-shared-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:nic-usb-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:nic-wireless-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:pata-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:pcmcia-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:pcmcia-storage-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:ppp-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:rfkill-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:sata-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:scsi-core-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:scsi-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:scsi-nic-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:serial-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:sound-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:speakup-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:squashfs-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:udf-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:uinput-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:usb-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:usb-serial-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:usb-storage-modules-5.10.0-0.bpo.12-amd64-di is NEW. binary:xfs-modules-5.10.0-0.bpo.12-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
Processing of linux-signed-amd64_5.10.103+1~bpo10+1_source.changes
linux-signed-amd64_5.10.103+1~bpo10+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_5.10.103+1~bpo10+1.dsc linux-signed-amd64_5.10.103+1~bpo10+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux-signed-i386_5.10.106+1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Mar 2022 16:40:47 +0100 Source: linux-signed-i386 Architecture: source Version: 5.10.106+1 Distribution: bullseye-proposed-updates Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-i386 (5.10.106+1) bullseye; urgency=medium . * Sign kernel from linux 5.10.106-1 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.104 - mac80211_hwsim: report NOACK frames in tx_status - mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work - [arm*] i2c: bcm2835: Avoid clock stretching timeouts - ASoC: rt5682: do not block workqueue if card is unbound - regulator: core: fix false positive in regulator_late_cleanup() - Input: clear BTN_RIGHT/MIDDLE on buttonpads - [arm64] KVM: arm64: vgic: Read HW interrupt pending state from the HW - tipc: fix a bit overflow in tipc_crypto_key_rcv() - cifs: fix double free race when mount fails in cifs_get_root() - net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 - usb: gadget: don't release an existing dev->buf (CVE-2022-24958) - usb: gadget: clear related members when goto fail (CVE-2022-24958) - exfat: reuse exfat_inode_info variable instead of calling EXFAT_I() - exfat: fix i_blocks for files truncated over 4 GiB - tracing: Add test for user space strings when filtering on string pointers - [armhf] serial: stm32: prevent TDR register overwrite when sending x_char - ata: pata_hpt37x: fix PCI clock detection - drm/amdgpu: check vm ready by amdgpu_vm->evicting flag - tracing: Add ustring operation to filtering string pointers - [x86] ALSA: intel_hdmi: Fix reference to PCM buffer address - ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min - [amd64] iommu/amd: Recover from event log overflow - [x86] drm/i915: s/JSP2/ICP2/ PCH - xen/netfront: destroy queues before real_num_tx_queues is zeroed - mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls - xfrm: fix MTU regression - netfilter: fix use-after-free in __nf_register_net_hook() - bpf, sockmap: Do not ignore orig_len parameter - xfrm: fix the if_id check in changelink - xfrm: enforce validity of offload input flags - e1000e: Correct NVM checksum verification flow - net: fix up skbs delta_truesize in UDP GRO frag_list - netfilter: nf_queue: don't assume sk is full socket - netfilter: nf_queue: fix possible use-after-free - netfilter: nf_queue: handle socket prefetch - batman-adv: Request iflink once in batadv-on-batadv check - batman-adv: Request iflink once in batadv_get_real_netdevice - batman-adv: Don't expect inter-netns unique iflink indices - net: ipv6: ensure we call ipv6_mc_down() at most once - net: dcb: flush lingering app table entries for unregistered devices - net/smc: fix connection leak - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server - rcu/nocb: Fix missed nocb_timer requeue - ice: Fix race conditions between virtchnl handling and VF ndo ops - ice: fix concurrent reset and removal of VFs - sched/topology: Make sched_init_numa() use a set for the deduplicating sort - sched/topology: Fix sched_domain_topology_level alloc in sched_init_numa() - mac80211: fix forwarded mesh frames AC & queue selection - net: stmmac: fix return value of __setup handler - mac80211: treat some SAE auth steps as final - iavf: Fix missing check for running netdev - net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() - ixgbe: xsk: change !netif_carrier_ok() handling in ixgbe_xmit_zc() - efivars: Respect "block" flag in efivar_entry_set_safe() - can: gs_usb: change active_channels's type from atomic_t to u8 - igc: igc_read_phy_reg_gpy: drop premature return - [armel,armhf] 9182/1: mmu: fix returns from early_param() and __setup() functions - [arm64,armhf] pinctrl: sunxi: Use unique lockdep classes for IRQs - igc: igc_write_phy_reg_gpy: drop premature return - memfd: fix F_SEAL_WRITE after shmem huge page allocated - [armhf] dts: switch timer config to common devkit8000 devicetree - [armhf] dts: Use 32KiHz oscillator on devkit8000 - [arm64] soc: fsl: guts: Revert commit 3c0d64e867ed - [arm64] soc: fsl: guts: Add a missing memory allocation failure check - [armhf] tegra: Move panels to AUX bus - net: chelsio: cxgb3: check the return value of pci_find_capability() - iavf: Refactor iavf state machine tracking - nl80211: Handle nla_memdup failures in handle_nan_filter - drm/amdgpu: fix suspend/resume hang regression - net: dcb: disable softirqs in dcbn
linux-signed-arm64_5.10.106+1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Mar 2022 16:40:47 +0100 Source: linux-signed-arm64 Architecture: source Version: 5.10.106+1 Distribution: bullseye-proposed-updates Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-arm64 (5.10.106+1) bullseye; urgency=medium . * Sign kernel from linux 5.10.106-1 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.104 - mac80211_hwsim: report NOACK frames in tx_status - mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work - [arm*] i2c: bcm2835: Avoid clock stretching timeouts - ASoC: rt5682: do not block workqueue if card is unbound - regulator: core: fix false positive in regulator_late_cleanup() - Input: clear BTN_RIGHT/MIDDLE on buttonpads - [arm64] KVM: arm64: vgic: Read HW interrupt pending state from the HW - tipc: fix a bit overflow in tipc_crypto_key_rcv() - cifs: fix double free race when mount fails in cifs_get_root() - net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 - usb: gadget: don't release an existing dev->buf (CVE-2022-24958) - usb: gadget: clear related members when goto fail (CVE-2022-24958) - exfat: reuse exfat_inode_info variable instead of calling EXFAT_I() - exfat: fix i_blocks for files truncated over 4 GiB - tracing: Add test for user space strings when filtering on string pointers - [armhf] serial: stm32: prevent TDR register overwrite when sending x_char - ata: pata_hpt37x: fix PCI clock detection - drm/amdgpu: check vm ready by amdgpu_vm->evicting flag - tracing: Add ustring operation to filtering string pointers - [x86] ALSA: intel_hdmi: Fix reference to PCM buffer address - ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min - [amd64] iommu/amd: Recover from event log overflow - [x86] drm/i915: s/JSP2/ICP2/ PCH - xen/netfront: destroy queues before real_num_tx_queues is zeroed - mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls - xfrm: fix MTU regression - netfilter: fix use-after-free in __nf_register_net_hook() - bpf, sockmap: Do not ignore orig_len parameter - xfrm: fix the if_id check in changelink - xfrm: enforce validity of offload input flags - e1000e: Correct NVM checksum verification flow - net: fix up skbs delta_truesize in UDP GRO frag_list - netfilter: nf_queue: don't assume sk is full socket - netfilter: nf_queue: fix possible use-after-free - netfilter: nf_queue: handle socket prefetch - batman-adv: Request iflink once in batadv-on-batadv check - batman-adv: Request iflink once in batadv_get_real_netdevice - batman-adv: Don't expect inter-netns unique iflink indices - net: ipv6: ensure we call ipv6_mc_down() at most once - net: dcb: flush lingering app table entries for unregistered devices - net/smc: fix connection leak - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server - rcu/nocb: Fix missed nocb_timer requeue - ice: Fix race conditions between virtchnl handling and VF ndo ops - ice: fix concurrent reset and removal of VFs - sched/topology: Make sched_init_numa() use a set for the deduplicating sort - sched/topology: Fix sched_domain_topology_level alloc in sched_init_numa() - mac80211: fix forwarded mesh frames AC & queue selection - net: stmmac: fix return value of __setup handler - mac80211: treat some SAE auth steps as final - iavf: Fix missing check for running netdev - net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() - ixgbe: xsk: change !netif_carrier_ok() handling in ixgbe_xmit_zc() - efivars: Respect "block" flag in efivar_entry_set_safe() - can: gs_usb: change active_channels's type from atomic_t to u8 - igc: igc_read_phy_reg_gpy: drop premature return - [armel,armhf] 9182/1: mmu: fix returns from early_param() and __setup() functions - [arm64,armhf] pinctrl: sunxi: Use unique lockdep classes for IRQs - igc: igc_write_phy_reg_gpy: drop premature return - memfd: fix F_SEAL_WRITE after shmem huge page allocated - [armhf] dts: switch timer config to common devkit8000 devicetree - [armhf] dts: Use 32KiHz oscillator on devkit8000 - [arm64] soc: fsl: guts: Revert commit 3c0d64e867ed - [arm64] soc: fsl: guts: Add a missing memory allocation failure check - [armhf] tegra: Move panels to AUX bus - net: chelsio: cxgb3: check the return value of pci_find_capability() - iavf: Refactor iavf state machine tracking - nl80211: Handle nla_memdup failures in handle_nan_filter - drm/amdgpu: fix suspend/resume hang regression - net: dcb: disable softirqs in dc
linux-signed-amd64_5.10.106+1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Mar 2022 16:40:47 +0100 Source: linux-signed-amd64 Architecture: source Version: 5.10.106+1 Distribution: bullseye-proposed-updates Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-amd64 (5.10.106+1) bullseye; urgency=medium . * Sign kernel from linux 5.10.106-1 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.104 - mac80211_hwsim: report NOACK frames in tx_status - mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work - [arm*] i2c: bcm2835: Avoid clock stretching timeouts - ASoC: rt5682: do not block workqueue if card is unbound - regulator: core: fix false positive in regulator_late_cleanup() - Input: clear BTN_RIGHT/MIDDLE on buttonpads - [arm64] KVM: arm64: vgic: Read HW interrupt pending state from the HW - tipc: fix a bit overflow in tipc_crypto_key_rcv() - cifs: fix double free race when mount fails in cifs_get_root() - net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 - usb: gadget: don't release an existing dev->buf (CVE-2022-24958) - usb: gadget: clear related members when goto fail (CVE-2022-24958) - exfat: reuse exfat_inode_info variable instead of calling EXFAT_I() - exfat: fix i_blocks for files truncated over 4 GiB - tracing: Add test for user space strings when filtering on string pointers - [armhf] serial: stm32: prevent TDR register overwrite when sending x_char - ata: pata_hpt37x: fix PCI clock detection - drm/amdgpu: check vm ready by amdgpu_vm->evicting flag - tracing: Add ustring operation to filtering string pointers - [x86] ALSA: intel_hdmi: Fix reference to PCM buffer address - ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min - [amd64] iommu/amd: Recover from event log overflow - [x86] drm/i915: s/JSP2/ICP2/ PCH - xen/netfront: destroy queues before real_num_tx_queues is zeroed - mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls - xfrm: fix MTU regression - netfilter: fix use-after-free in __nf_register_net_hook() - bpf, sockmap: Do not ignore orig_len parameter - xfrm: fix the if_id check in changelink - xfrm: enforce validity of offload input flags - e1000e: Correct NVM checksum verification flow - net: fix up skbs delta_truesize in UDP GRO frag_list - netfilter: nf_queue: don't assume sk is full socket - netfilter: nf_queue: fix possible use-after-free - netfilter: nf_queue: handle socket prefetch - batman-adv: Request iflink once in batadv-on-batadv check - batman-adv: Request iflink once in batadv_get_real_netdevice - batman-adv: Don't expect inter-netns unique iflink indices - net: ipv6: ensure we call ipv6_mc_down() at most once - net: dcb: flush lingering app table entries for unregistered devices - net/smc: fix connection leak - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client - net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server - rcu/nocb: Fix missed nocb_timer requeue - ice: Fix race conditions between virtchnl handling and VF ndo ops - ice: fix concurrent reset and removal of VFs - sched/topology: Make sched_init_numa() use a set for the deduplicating sort - sched/topology: Fix sched_domain_topology_level alloc in sched_init_numa() - mac80211: fix forwarded mesh frames AC & queue selection - net: stmmac: fix return value of __setup handler - mac80211: treat some SAE auth steps as final - iavf: Fix missing check for running netdev - net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() - ixgbe: xsk: change !netif_carrier_ok() handling in ixgbe_xmit_zc() - efivars: Respect "block" flag in efivar_entry_set_safe() - can: gs_usb: change active_channels's type from atomic_t to u8 - igc: igc_read_phy_reg_gpy: drop premature return - [armel,armhf] 9182/1: mmu: fix returns from early_param() and __setup() functions - [arm64,armhf] pinctrl: sunxi: Use unique lockdep classes for IRQs - igc: igc_write_phy_reg_gpy: drop premature return - memfd: fix F_SEAL_WRITE after shmem huge page allocated - [armhf] dts: switch timer config to common devkit8000 devicetree - [armhf] dts: Use 32KiHz oscillator on devkit8000 - [arm64] soc: fsl: guts: Revert commit 3c0d64e867ed - [arm64] soc: fsl: guts: Add a missing memory allocation failure check - [armhf] tegra: Move panels to AUX bus - net: chelsio: cxgb3: check the return value of pci_find_capability() - iavf: Refactor iavf state machine tracking - nl80211: Handle nla_memdup failures in handle_nan_filter - drm/amdgpu: fix suspend/resume hang regression - net: dcb: disable softirqs in dc
Bug#1006346: cloud.debian.org: bullseye AMIs don't boot on Amazon EC2 Xen instances with Enhanced Networking
Hi Noah, On Thu, Mar 17, 2022 at 09:54:30AM -0700, Noah Meyerhans wrote: > >From the upstream discussion on the linux-pci mailing list [*]: > > > Yes. My understanding is that the issue is because AWS is using older > > versions of Xen. They are in the process of updating their fleet to a > > newer version of Xen so the change introduced with Stefan's commit > > isn't an issue any longer. > > > > I think the changes are scheduled to be completed in the next 10-12 > > weeks. For now we are carrying a revert in the Fedora Kernel. > > > > You can follow this Fedora CoreOS issue if you'd like to know more > > about when the change lands in their backend. We work closely with one > > of their partner engineers and he keeps us updated. > > https://github.com/coreos/fedora-coreos-tracker/issues/1066 > > Ideally we can revert the upstream commit from the stable kernels, since > otherwise Debian users on AWS Xen instance types may be stuck using > older, unsafe kernels. Especially if we have time to include the change > in the upcoming bullseye and buster point releases. If the kernel > updates for those stable updates have already been built, though, it > might be too late to matter. By the time we publish our next kernel > builds, the AWS Xen update may be complete. Wehere one can track the update status for their Xen version directly or is following the above the only reference? How frequent is this particular combination of hardware/software? We have the change already applied for a while in bullseye, buster would be impacted new since the last update done for security fixes Are there workarounds for the affected users of this combination? I see some options listed in https://wiki.debian.org/Cloud/AmazonEC2Image/Bullseye If we revert the commit it reverts a fix for a bug with Marvell NVME devices. But we cannot just revert the commit for the cloud images. If we know something about the release schedule from Amazon to update their Xen instances (which is the way to move forward, since upstream won't revert the commit) then we should leave the status as it is for bullseye (and now for buster). For bullseye there is there is CVE-2022-0847 fixes they would need to pick up. Regards, Salvatore
linux-latest_105+deb10u15_source.changes ACCEPTED into oldstable-proposed-updates->oldstable-new
Mapping buster to oldstable. Mapping oldstable to oldstable-proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 Mar 2022 07:54:21 +0100 Source: linux-latest Architecture: source Version: 105+deb10u15 Distribution: buster Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-latest (105+deb10u15) buster; urgency=medium . * Update to 4.19.0-20 Checksums-Sha1: ba54b93034a243e9030bf39a96a243d83faa228c 11743 linux-latest_105+deb10u15.dsc 0eca5483e8610c98917ba99f7c56cea0bd2ab291 20808 linux-latest_105+deb10u15.tar.xz 35d278d1bf830df7b2ab2113c3de0ea4cec61e9b 6309 linux-latest_105+deb10u15_source.buildinfo Checksums-Sha256: 22349bf4af1af2abb05e1fe55ba27ea882670948bd15f922d80e0f20d4226c7d 11743 linux-latest_105+deb10u15.dsc 10e7ba0e101c5f8c69c1580e4fdd888ab2a9b44b5867ca7bcf08d340a94e6d8f 20808 linux-latest_105+deb10u15.tar.xz d178463ae4c2909cb140c94dda3572d6d69db6bd2d90a6fe870b3d5a22fb282e 6309 linux-latest_105+deb10u15_source.buildinfo Files: 1ceef865ca19be6f5109c81240711f8d 11743 kernel optional linux-latest_105+deb10u15.dsc e559a0e673fc1910696aab437ad01684 20808 kernel optional linux-latest_105+deb10u15.tar.xz 211d7b9bc3acda4c37d3b9d5b8683ef5 6309 kernel optional linux-latest_105+deb10u15_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmI1f8ZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89E/SMQAJPzY62FV5KJmZZMJNpsEKOBqdsUGfU0 buITDlTm8E9vHZEanM8KBFZOOKOAO3e8ITztbk811wjkacTZPS4LRU6qGgjp5jsi xDOiGUGgQU3my3tX6/DGVNc9zX0zPeyEWcxpHBkgmstmN6RAagJjk6m5Mg2YWIfU qnWl5iHg9TDYvIpUzqUX4DOkUnbGHyFJVZWEZyunKzrYAjuuTeTszSV6GL8QY8D7 MQpncns0zMxYKLoCR+Hm9P+OcPIkblen+nPJQzJllk9xeMgHypKmXBQxZdkEOYWY 5vID9LJuxS4JPMueNdy3nAXYo61xGyewibhO7TmUWmzBNdnz0YdTZMKUTHRKe7GV QB/c+3FdhlTjMaWrHjubjJ1Y1MiO+MbgXanmN9Xuy7IIjkV9n5+YIhFTx2QzSpgl zKrhGVNlLKaCILpTgJqBVOkZ2O37zPXPsaPwU7s602OENFT5tVF26x7fbm7ghTa2 t2atquLsqnlBemtbCKCy+4hBiF9YYgKSNNvW9aE4lqcvb2Ol089aS9oKPBJ5QAFW 2E1uVdC39+yjMme8FALHLLl2IHVan9+BRNREYSC1sG13l5iSsX2eywOqtrqJ68d7 9LdY34OqTeX3zPz9ttfs7dwDOl9bdbd3IgiIL2qZEigwS6aQeKUjMu7BE50WxyKF yGddfJ3HAGT/ =DYhT -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of linux-latest_105+deb10u15_source.changes
linux-latest_105+deb10u15_source.changes uploaded successfully to localhost along with the files: linux-latest_105+deb10u15.dsc linux-latest_105+deb10u15.tar.xz linux-latest_105+deb10u15_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
