Bug#1025735: Bug 1025735

[Mauro Carvalho Chehab]

From the logs, it seems that you're using this camera on an old
hardware. I remember lots of troubles related to old USB 2.0
bridges.

See, USB 2.0 spec supports two types of velocity:

- full-speed (the same as USB 1.1 speeds;
- high-speed (the one which comes with USB 2.0)

In thesis, USB 2.0 is meant to allow up to 480MBps, but this is not
what happens in practice, specially for cameras. Cameras typically
use ISOC endpoints, with works by allocating a certain number of
frames or microframes. This is limited, according to the spec, to:

- max of 90% of frames can be allocated on full speed
  (e. g. being used either ISOC or interrupt endpoints).
- max of 80% for for microframe periodic transfers
  (high speed).

When there a mix of USB 1.1 and USB2.0 at the same bus, those numbers may
drop radically, as USB 1.1 devices won't work at high-speed. So, the USB
core may fail to be able to allocate the required number of frames or
microframes as required by the device to work on its full resolution.

I bet this is the case, from your lsusb:

** USB devices:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching 
Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 047f:4315 Plantronics, Inc. Poly Blackwire 8225 
Series
Bus 001 Device 004: ID 046d:08d7 Logitech, Inc. QuickCam Communicate STX
Bus 001 Device 003: ID 13ba:0018 PCPlay Barcode PCP-BCG4209
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching 
Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


See at bus 1, where the camera is connected, you also have a barcode
reader, which is very likely an USB 1.1 device (as most input devices
are).

Ah, there are also some USB 2.0 bridges that are internally 
connected to USB 1.1, and sometimes end having similar troubles.

Worth mentioning that "USB 2.0 compatible" announcements on hardware
doesn't necessarily means that they support high-speed, as full-speed
is also part of USB 2.0 specs.

In any case, this has nothing to do with the V4L driver, but, instead,
to how the USB brigde and USB core/driver detects each device. You can
have a better view about how the USB devices are seen with `lsub -t`:

$ sudo lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 9, If 0, Class=Vendor Specific Class, 
Driver=r8152, 480M
|__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 8, If 0, Class=, Driver=, 12M
|__ Port 2: Dev 7, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 10, If 0, Class=Mass Storage, 
Driver=usb-storage, 480M
|__ Port 2: Dev 11, If 0, Class=Mass Storage, 
Driver=usb-storage, 480M
|__ Port 5: Dev 3, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
|__ Port 5: Dev 3, If 1, Class=Human Interface Device, 
Driver=usbhid, 12M
|__ Port 5: Dev 3, If 2, Class=Human Interface Device, 
Driver=usbhid, 12M
|__ Port 6: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 6: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 10: Dev 6, If 0, Class=Wireless, Driver=usbfs, 12M
|__ Port 10: Dev 6, If 1, Class=Wireless, Driver=usbfs, 12M

On the above example, the camera is at Bus 1 port 6, which is set to use
high-speed ("480M"). Other ports at the same bus have devices at 
high-speed ("12M"). Yet, this specific USB bridge handles each port
in separate, so the camera (using uvcvideo) can allocate all ISOC microframes
it needs.

Older USB bridges (found on machines similar to the one pointed on your
BZ) don't allow that: if one device at the bus is at full-speed, all
devices at the same bus have their speed reduced to full-speed, as
otherwise the full-speed devices wouldn't work.

Switching the camera connector to different USB ports may help. 

When there is the need of connecting input devices (they all are usually
full-speed only), you can also try using modern USB hubs, as some are
capable of isolating full-speed devices on a separate internal bus, talking
with the PC port in high-speed.

Bug#1025537: nfsd: Kernel Oops while serving NFS

[Olivier Mehani]

Hi Salvatore,

On Fri 09 Dec 2022 at 22:22:49 +0100, Salvatore Bonaccorso wrote:

On testing/bookworm, since booting on a 6-versioned linux-image, I have
noticed frequent hang ups of the nfs server, rendering it mostly
unusable. This is accompanied with Kernel Oops in the dmesg.
This sounds similar to previous bugs #1014793 and #1020548, both RESOLVED by
later patches.

How easy can you trigger and reproduce the issue? If you can easily
reach that situation, can you try to bisect the issue? Easiest would
be to first pin point between Debian revisions, and later further
bisect in upstream stable series.
Do you have the possibility to do that?


It seems to be fairly reliable.

I'll give that a go, starting with
* linux-image-5.19.0-2-amd64_5.19.11-1_amd64.deb
* linux-image-6.0.0-1-amd64_6.0.2-1_amd64.deb

I'm not certain how to bisect further. Which source and which kconfig 
should I use to build intermediate commits?


--
Olivier Mehani 
PGP fingerprint: 4435 CF6A 7C8D DD9B E2DE  F5F9 F012 A6E2 98C6 6655
Confidentiality cannot be guaranteed on emails sent or received unencrypted.

Processed: limit source to nfs-utils, tagging 939153

[Debian Bug Tracking System]

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

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

> tags 939153 + pending
Bug #939153 [src:nfs-utils] nfs-utils: Fix LSB init output
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1025845: linux: please enable CONFIG_KFENCE

[Christian Göttsche]

Source: linux
Version: 6.0.12-1
Tags: security

Please enable support for Kernel Electric-Fence (KFENCE), a memory
safety error detector, see
https://docs.kernel.org/dev-tools/kfence.html.

Whether to actually enable it by default (do not set
CONFIG_KFENCE_SAMPLE_INTERVAL) or disable it (set
CONFIG_KFENCE_SAMPLE_INTERVAL to 0) might be up for discussion (e.g.
enable in sid, disable before stable release?).

Processed: closing 807291

[Debian Bug Tracking System]

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

> close 807291
Bug #807291 [nfs-common] nfs-common: NFS client hangs with NFS4 mounts
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#522294: marked as done (nfs-kernel-server: Fails to start: start-stop-daemon: command not found [SRM])

[Debian Bug Tracking System]

Your message dated Sat, 10 Dec 2022 14:35:35 +0100
with message-id 
and subject line Re: Bug#522294: nfs-kernel-server: Fails to start: 
start-stop-daemon: command not found [SRM]
has caused the Debian Bug report #522294,
regarding nfs-kernel-server: Fails to start: start-stop-daemon: command not 
found [SRM]
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.)


-- 
522294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.1.2-6lenny1
Severity: serious
Justification: Policy 9.9

Hi.

In a clean lenny environment with mostly nfs-kernel-server installed, it
fails to start because of:
| start-stop-daemon: command not found

Obviously, since there's no default PATH set in the init script, that
just can't work. That's Policy 9.9:
| A program must not depend on environment variables to get reasonable
| defaults

Please set PATH to something like /sbin:/bin:/usr/sbin:/usr/bin or
whatever you see fit.

Please also fix the package in lenny (that's why I've put [SRM] in the
subject, and X-Debbugs-Cc'd debian-release@).

Thanks already.

Cheers,
-- 
Cyril Brulebois

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

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

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

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Cyril Brulebois  (2009-04-02):
> severity 522294 wishlist
> thanks
> (control@ in Bcc)
> 
> Cyril Brulebois  (02/04/2009):
> > Package: nfs-kernel-server
> > Version: 1:1.1.2-6lenny1
> > Severity: serious
> > Justification: Policy 9.9
> 
> OK, I really shot too fast. “rc” indeed does the right thing, and I
> guess unsetting some variables in a previous init script would qualify
> as being very unfair to the other scripts (particularly for $PATH).
> That's why I'm lowering the severity to a wishlist bug.

Since I'm getting pinged about this once in a while: I've been using
n-k-s on more recent systems without any issues, and whatever problems I
thought I spotted at the time are no practical problems at this time.

(Having a systemd service unit makes the init.d script moot anyway.)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature
--- End Message ---

Bug#805710: marked as done (nfs-common: NFS mounts don't work because nfs-common starts before rpcbind.service)

[Debian Bug Tracking System]

Your message dated Sat, 10 Dec 2022 14:39:00 +0100
with message-id 
and subject line Re: Bug#805710: nfs-common: NFS mounts don't work because 
nfs-common starts before rpcbind.service
has caused the Debian Bug report #805710,
regarding nfs-common: NFS mounts don't work because nfs-common starts before 
rpcbind.service
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.)


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

Dear Maintainer,
NFS mounts don't work on systemd enabled systems because nfs-common is
started before rpcbind. If nfs-common is restarted after boot, the
mounts start to work fine. In log files I see:
nfs-common[1301]: Not starting: portmapper is not running ... (warning).


-- 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
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  32768  nlockmgr
1000213   udp  32768  nlockmgr
1000214   udp  32768  nlockmgr
1000211   tcp  32768  nlockmgr
1000213   tcp  32768  nlockmgr
1000214   tcp  32768  nlockmgr
151   udp  32767  mountd
151   tcp  32767  mountd
152   udp  32767  mountd
152   tcp  32767  mountd
153   udp  32767  mountd
153   tcp  32767  mountd
1000241   udp  32765  status
1000241   tcp  32765  status
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS="--port 32765 --outgoing-port 32766"
NEED_IDMAPD=yes
NEED_GSSD=yes
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
Domain=kaspar.in
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
/media  /srv/nfs4/media nonerw,rbind
0   0
/srv/home   /srv/nfs4/home  nonerw,bind 
0   0
budha:/multimedia   /srv/multimedia nfs4
sec=krb5,soft,intr,timeo=10,retrans=10,noatime,auto,x-systemd.automount,x-systemd.device-timeout=10
 0   0
#budha:/srv/nfs4/multimedia /srv/multimedia nfs 
defaults,vers=3,soft,bg 0   3
#budha:/shared  /home/sharednfs4
sec=krb5,soft,retrans=4,noatime,auto,x-systemd.automount,x-systemd.device-timeout=10
0   0
-- /proc/mounts --
/dev/dm-3 /srv/nfs4/media ext4 rw,noatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/vg00-home /srv/nfs4/home ext4 rw,nosuid,nodev,relatime,data=ordered 
0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
budha:/multimedia /srv/multimedia nfs4 
rw,noatime,vers=4.0,rsize=262144,wsize=262144,namlen=255,soft,proto=tcp6,port=0,timeo=10,retrans=10,sec=krb5,clientaddr=fd3c:13aa:60ba:0:ae22:bff:fe2c:b7ae,local_lock=none,addr=fd3c:13aa:60ba::1
 0 0

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

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

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

Bug#775542: marked as done (NFS exports fail due to rpcbind not starting before nfs-common and nfs-kernel-server)

[Debian Bug Tracking System]

Your message dated Sat, 10 Dec 2022 14:39:00 +0100
with message-id 
and subject line Re: Bug#805710: nfs-common: NFS mounts don't work because 
nfs-common starts before rpcbind.service
has caused the Debian Bug report #805710,
regarding NFS exports fail due to rpcbind not starting before nfs-common and 
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.)


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

Tox fix this issue I only let 'S' runlevel in require-start LSB header in init
script and postinst. (I also remove 0 1 6 from require-stop as they look weird 
for
a 'S' runlevel started service).

I had to do the same in rpcbind (should I clone the bug report ?) which I use 
since portmap
breakage (thus portmap might suffer from the same issue though it is purged 
here).

Systemd issue:
kernel: [   11.812950] <31>systemd[1]: Activating default unit: default.target
kernel: [   11.812970] <31>systemd[1]: Trying to enqueue job 
graphical.target/start/replace
kernel: [   11.813695] <28>systemd[1]: Found ordering cycle on 
basic.target/start
kernel: [   11.813707] <30>systemd[1]: Walked on cycle path to 
sockets.target/start
kernel: [   11.813717] <30>systemd[1]: Walked on cycle path to dbus.socket/start
kernel: [   11.813726] <30>systemd[1]: Walked on cycle path to 
sysinit.target/start
kernel: [   11.813736] <30>systemd[1]: Walked on cycle path to 
nfs-common.service/start
kernel: [   11.813746] <30>systemd[1]: Walked on cycle path to 
basic.target/start
kernel: [   11.813756] <28>systemd[1]: Breaking ordering cycle by deleting job 
dbus.socket/start
kernel: [   11.813768] <31>systemd[1]: Deleting job dbus.service/start as 
dependency of job dbus.socket/start
kernel: [   11.813781] <31>systemd[1]: Deleting job avahi-daemon.service/start 
as dependency of job dbus.socket/start
kernel: [   11.813811] <28>systemd[1]: Found ordering cycle on 
basic.target/start
kernel: [   11.813821] <30>systemd[1]: Walked on cycle path to 
sysinit.target/start
kernel: [   11.813831] <30>systemd[1]: Walked on cycle path to 
nfs-common.service/start
kernel: [   11.813841] <30>systemd[1]: Walked on cycle path to 
basic.target/start
kernel: [   11.813850] <28>systemd[1]: Breaking ordering cycle by deleting job 
nfs-common.service/start
kernel: [   11.813896] <28>systemd[1]: Found ordering cycle on 
basic.target/start
kernel: [   11.813905] <30>systemd[1]: Walked on cycle path to 
sysinit.target/start
kernel: [   11.813914] <30>systemd[1]: Walked on cycle path to 
rpcbind.service/start
kernel: [   11.813924] <30>systemd[1]: Walked on cycle path to 
basic.target/start
kernel: [   11.813934] <28>systemd[1]: Breaking ordering cycle by deleting job 
rpcbind.service/start
kernel: [   11.814156] <31>systemd[1]: Installed new job graphical.target/start 
as 1
kernel: [   11.814167] <31>systemd[1]: Installed new job 
multi-user.target/start as 2
kernel: [   11.814178] <31>systemd[1]: Installed new job basic.target/start as 3
kernel: [   11.814188] <31>systemd[1]: Installed new job sysinit.target/start 
as 4
kernel: [   11.814198] <31>systemd[1]: Installed new job local-fs.target/start 
as 5
kernel: [   11.814208] <31>systemd[1]: Installed new job quotaon.service/start 
as 6
kernel: [   11.814219] <31>systemd[1]: Installed new job 
systemd-logger.socket/start as 7
kernel: [   11.814229] <31>systemd[1]: Installed new job 
quotacheck.service/start as 9
kernel: [   11.814239] <31>systemd[1]: Installed new job 
lib-init-rw.automount/start as 10
kernel: [   11.814250] <31>systemd[1]: Installed new job var-run.mount/start as 
11
kernel: [   11.814260] <31>systemd[1]: Installed new job 
remount-rootfs.service/start as 17


ie the biggest issue is Deleting job dbus.service which kills most desktop 
service (network-manager, gdm and so forth).
It looks like basic.target is bound to >= 2 runlevels and basic.target depends 
on 'S' runlevel (sysinit.target).
As nfs-common is also started in 2 runlevel, it also requires 'S' to be 
completed. Though it is also part of 'S' so is
required by 'S' (sysinit.target).
As I do not see a valid use for behing both in 'S' and '2' runlevel it does not 
looks like a bug in
systemd. Please reassign if otherwise.

Best regards,
Alban

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

Compatibility between kernel and modules

[Bastian Blank]

Hi

Our documented, I think, policy is, that we don't support loading new
modules into an old kernel within the same ABI.  This forces a reboot
after kernel installation.

However in a lot of cases this just worked.  You could update the kernel
package and continue loading most modules.

Now we have BTF support enabled, which trashes this compatibility
mostly, as it requires a way more strict match between kernel image and
modules.

We need to fix that somehow.  Options are as far as I see
- remove BTF from modules,
- allow to load modules even on BTF mismatch, or
- reinforce that a user can't do that.

If we go with the last option we would have also some direct advantages.
We could stop signing modules with the secure boot key, but use a
temporary key.  This would for a system with signature checking enabled
effectively trash all possibilities to load modules for a different
kernel build.

This would do directly for use:
- A way faster build, as we don't longer require multi-10k signatures,
  but only a handfull, from the HSM.
- We might be forced by shim/UEFI to support SBAT if we load secure boot
  signed stuff.  If we just need to revoke the complete kernel, SBAT on
  the kernel itself is enough.
- We can do pre-built initramfs and unified image without two rounds in
  the signing service.
- We fix the current signatures without certificate chain, but which are
  still chained to the Debian secure boot CA.  (sign-file simply can't
  handle cert chains, while the kernel itself can check them on loading.)

What should we do?

Regards,
Bastian

-- 
It would be illogical to kill without reason.
-- Spock, "Journey to Babel", stardate 3842.4

Processed: closing 559296

[Debian Bug Tracking System]

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

> close 559296
Bug #559296 [nfs-common] nfs-common: Unable to umount
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#768006: marked as done (nfs-common: systemd fails to start nfs-common daemons before attmpting NFS mounts (NFSv3))

[Debian Bug Tracking System]

Your message dated Sat, 10 Dec 2022 14:39:00 +0100
with message-id 
and subject line Re: Bug#805710: nfs-common: NFS mounts don't work because 
nfs-common starts before rpcbind.service
has caused the Debian Bug report #805710,
regarding nfs-common: systemd fails to start nfs-common daemons before 
attmpting NFS mounts (NFSv3)
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.)


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

Dear Maintainer,

I am the administrator of a network of systems which use kerberized NFSv3 to 
mount user 
homedirs across systems. On one particular machine, we were running jessie but 
had not yet 
switched to systemd. After switching to systemd, I discovered that it failed to 
mount 
critical mounts on startup. They mounted fine manually. Investigating the 
journal 
(attached), I discovered that NFS failed to mount because statd was not 
available, but 
systemd did not start statd until after attempting to mount the NFS shares, 
which is why 
the manual mount worked fine.

The nfs-common systemd configuration should ensure that any nfs-common daemons 
are started 
before attempting to mount NFS shares, or ensure that if the mount call occurs 
first, that 
the system is able to gracefully recover by mounting them properly once the 
daemons are 
started, rather than by failing entirely.

Please note that I have sanitized the fstab and mounts files below, so as not 
to expose 
system details. To the best of my knowledge, they bear no relevance to the bug.

Attached is the relevant excerpt from the journal. Again I have sanitized the 
mount points; 
both kerberized mount points failed (sec=krb5 below).

-- 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
1000211   udp  47679  nlockmgr
1000213   udp  47679  nlockmgr
1000214   udp  47679  nlockmgr
1000211   tcp  44079  nlockmgr
1000213   tcp  44079  nlockmgr
1000214   tcp  44079  nlockmgr
1000241   udp  58446  status
1000241   tcp  37018  status
-- /etc/default/nfs-common --
NEED_STATD=yes
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=yes
RPCGSSDOPTS=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
:nfs bg,vers=3,sec=krb5,nosuid,nodev 0 0
:nfs 
bg,vers=3,sec=sys,nosuid,nolock,noatime,nodev 0 0
:nfs bg,vers=3,sec=sys,nosuid,nodev 0 0
-- /proc/mounts --
:  nfs 
rw,nosuid,nodev,noatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.97.134.115,mountvers=3,mountport=53011,mountproto=udp,local_lock=all,addr=129.97.134.115
 0 0
:  nfs 
rw,nosuid,nodev,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=krb5,mountaddr=129.97.134.115,mountvers=3,mountport=53011,mountproto=udp,local_lock=none,addr=129.97.134.115
 0 0
:  nfs 
rw,nosuid,nodev,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.97.134.72,mountvers=3,mountport=52732,mountproto=udp,local_lock=none,addr=129.97.134.72
 0 0

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

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

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

Versions of packages nfs-common recom

Processed: closing 524458

[Debian Bug Tracking System]

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

> close 524458
Bug #524458 [nfs-common] nfs-common: Can't read large files
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 574968

[Debian Bug Tracking System]

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

> close 574968
Bug #574968 [nfs-utils] nfs system isn't mounted while booting
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 301953

[Debian Bug Tracking System]

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

> close 301953
Bug #301953 [nfs-common] mount: retry option for nfs is completely broken
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 559296

[Debian Bug Tracking System]

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

> close 559296
Bug #559296 {Done: Salvatore Bonaccorso } [nfs-common] 
nfs-common: Unable to umount
Bug 559296 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: closing 754852

[Debian Bug Tracking System]

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

> close 754852
Bug #754852 [src:nfs-utils] nfs-utils: contains amd64 binaries (.o, .a, etc.)
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 532171

[Debian Bug Tracking System]

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

> close 532171
Bug #532171 [nfs-kernel-server] exportfs -r can fail to update options
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1025735: Bug 1025735

[Mauro Carvalho Chehab]

On Sat, 10 Dec 2022 12:34:53 + Mauro Carvalho Chehab  
wrote:

> On the above example, the camera is at Bus 1 port 6, which is set to use
> high-speed ("480M"). Other ports at the same bus have devices at 
> high-speed ("12M").

I actually meant to say:

On the above example, the camera is at Bus 1 port 6, which is set to use
high-speed ("480M"). Other ports at the same bus have devices at 
full-speed ("12M").

Processed: forcibly merging 756171 756170

[Debian Bug Tracking System]

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

> forcemerge 756171 756170
Bug #756171 [nfs-kernel-server] nfs-kernel-server: nfs timeo option incorrectly 
documented to be in tenths of a second
Bug #756170 [nfs-kernel-server] nfs-kernel-server: nfs man page lists incorrect 
info for timeo option
Merged 756170 756171
> thanks
Stopping processing here.

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

Processed: closing 756170

[Debian Bug Tracking System]

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

> close 756170
Bug #756170 [nfs-kernel-server] nfs-kernel-server: nfs man page lists incorrect 
info for timeo option
Bug #756171 [nfs-kernel-server] nfs-kernel-server: nfs timeo option incorrectly 
documented to be in tenths of a second
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 716223

[Debian Bug Tracking System]

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

> close 716223
Bug #716223 [nfs-common] [Mayhem] Bug report on nfs-common: nfsidmap crashes 
with exit status 139
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 613828

[Debian Bug Tracking System]

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

> close 613828
Bug #613828 [nfs-kernel-server] nfs-kernel-server: export list shows only one 
host
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 722092

[Debian Bug Tracking System]

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

> retitle 722092 start-statd manpage missing
Bug #722092 [nfs-common] nfs-common: missing seven manpages
Changed Bug title to 'start-statd manpage missing' from 'nfs-common: missing 
seven manpages'.
> severity 722092 minor
Bug #722092 [nfs-common] start-statd manpage missing
Severity set to 'minor' from 'normal'
> close 722092
Bug #722092 [nfs-common] start-statd manpage missing
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 610953

[Debian Bug Tracking System]

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

> close 610953
Bug #610953 [nfs-common] nfs-common: Upgrade from Lenny to Squeeze prevents 
mounting previously set up nfs exports
Bug #609487 [nfs-common] NFS/NIS GID/UID resolution fails after upgrade
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Processing of linux-signed-amd64_5.10.158+1_source.changes

[Debian FTP Masters]

linux-signed-amd64_5.10.158+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-amd64_5.10.158+1.dsc
  linux-signed-amd64_5.10.158+1.tar.xz

Greetings,

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

linux-signed-amd64_5.10.158+1_source.changes is NEW

[Debian FTP Masters]

Mapping bullseye-proposed-updates to proposed-updates.
binary:acpi-modules-5.10.0-20-amd64-di is NEW.
binary:ata-modules-5.10.0-20-amd64-di is NEW.
binary:btrfs-modules-5.10.0-20-amd64-di is NEW.
binary:cdrom-core-modules-5.10.0-20-amd64-di is NEW.
binary:crc-modules-5.10.0-20-amd64-di is NEW.
binary:crypto-dm-modules-5.10.0-20-amd64-di is NEW.
binary:crypto-modules-5.10.0-20-amd64-di is NEW.
binary:efi-modules-5.10.0-20-amd64-di is NEW.
binary:event-modules-5.10.0-20-amd64-di is NEW.
binary:ext4-modules-5.10.0-20-amd64-di is NEW.
binary:f2fs-modules-5.10.0-20-amd64-di is NEW.
binary:fat-modules-5.10.0-20-amd64-di is NEW.
binary:fb-modules-5.10.0-20-amd64-di is NEW.
binary:firewire-core-modules-5.10.0-20-amd64-di is NEW.
binary:fuse-modules-5.10.0-20-amd64-di is NEW.
binary:i2c-modules-5.10.0-20-amd64-di is NEW.
binary:input-modules-5.10.0-20-amd64-di is NEW.
binary:isofs-modules-5.10.0-20-amd64-di is NEW.
binary:jfs-modules-5.10.0-20-amd64-di is NEW.
binary:kernel-image-5.10.0-20-amd64-di is NEW.
binary:linux-image-5.10.0-20-amd64 is NEW.
binary:linux-image-5.10.0-20-cloud-amd64 is NEW.
binary:linux-image-5.10.0-20-rt-amd64 is NEW.
binary:loop-modules-5.10.0-20-amd64-di is NEW.
binary:md-modules-5.10.0-20-amd64-di is NEW.
binary:mmc-core-modules-5.10.0-20-amd64-di is NEW.
binary:mmc-modules-5.10.0-20-amd64-di is NEW.
binary:mouse-modules-5.10.0-20-amd64-di is NEW.
binary:mtd-core-modules-5.10.0-20-amd64-di is NEW.
binary:multipath-modules-5.10.0-20-amd64-di is NEW.
binary:nbd-modules-5.10.0-20-amd64-di is NEW.
binary:nic-modules-5.10.0-20-amd64-di is NEW.
binary:nic-pcmcia-modules-5.10.0-20-amd64-di is NEW.
binary:nic-shared-modules-5.10.0-20-amd64-di is NEW.
binary:nic-usb-modules-5.10.0-20-amd64-di is NEW.
binary:nic-wireless-modules-5.10.0-20-amd64-di is NEW.
binary:pata-modules-5.10.0-20-amd64-di is NEW.
binary:pcmcia-modules-5.10.0-20-amd64-di is NEW.
binary:pcmcia-storage-modules-5.10.0-20-amd64-di is NEW.
binary:ppp-modules-5.10.0-20-amd64-di is NEW.
binary:rfkill-modules-5.10.0-20-amd64-di is NEW.
binary:sata-modules-5.10.0-20-amd64-di is NEW.
binary:scsi-core-modules-5.10.0-20-amd64-di is NEW.
binary:scsi-modules-5.10.0-20-amd64-di is NEW.
binary:scsi-nic-modules-5.10.0-20-amd64-di is NEW.
binary:serial-modules-5.10.0-20-amd64-di is NEW.
binary:sound-modules-5.10.0-20-amd64-di is NEW.
binary:speakup-modules-5.10.0-20-amd64-di is NEW.
binary:squashfs-modules-5.10.0-20-amd64-di is NEW.
binary:udf-modules-5.10.0-20-amd64-di is NEW.
binary:uinput-modules-5.10.0-20-amd64-di is NEW.
binary:usb-modules-5.10.0-20-amd64-di is NEW.
binary:usb-serial-modules-5.10.0-20-amd64-di is NEW.
binary:usb-storage-modules-5.10.0-20-amd64-di is NEW.
binary:xfs-modules-5.10.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-arm64_5.10.158+1_source.changes

[Debian FTP Masters]

linux-signed-arm64_5.10.158+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-arm64_5.10.158+1.dsc
  linux-signed-arm64_5.10.158+1.tar.xz

Greetings,

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

linux-signed-arm64_5.10.158+1_source.changes is NEW

[Debian FTP Masters]

Mapping bullseye-proposed-updates to proposed-updates.
binary:ata-modules-5.10.0-20-arm64-di is NEW.
binary:btrfs-modules-5.10.0-20-arm64-di is NEW.
binary:cdrom-core-modules-5.10.0-20-arm64-di is NEW.
binary:crc-modules-5.10.0-20-arm64-di is NEW.
binary:crypto-dm-modules-5.10.0-20-arm64-di is NEW.
binary:crypto-modules-5.10.0-20-arm64-di is NEW.
binary:efi-modules-5.10.0-20-arm64-di is NEW.
binary:event-modules-5.10.0-20-arm64-di is NEW.
binary:ext4-modules-5.10.0-20-arm64-di is NEW.
binary:f2fs-modules-5.10.0-20-arm64-di is NEW.
binary:fat-modules-5.10.0-20-arm64-di is NEW.
binary:fb-modules-5.10.0-20-arm64-di is NEW.
binary:fuse-modules-5.10.0-20-arm64-di is NEW.
binary:i2c-modules-5.10.0-20-arm64-di is NEW.
binary:input-modules-5.10.0-20-arm64-di is NEW.
binary:isofs-modules-5.10.0-20-arm64-di is NEW.
binary:jfs-modules-5.10.0-20-arm64-di is NEW.
binary:kernel-image-5.10.0-20-arm64-di is NEW.
binary:leds-modules-5.10.0-20-arm64-di is NEW.
binary:linux-image-5.10.0-20-arm64 is NEW.
binary:linux-image-5.10.0-20-cloud-arm64 is NEW.
binary:linux-image-5.10.0-20-rt-arm64 is NEW.
binary:loop-modules-5.10.0-20-arm64-di is NEW.
binary:md-modules-5.10.0-20-arm64-di is NEW.
binary:mmc-modules-5.10.0-20-arm64-di is NEW.
binary:mtd-core-modules-5.10.0-20-arm64-di is NEW.
binary:multipath-modules-5.10.0-20-arm64-di is NEW.
binary:nbd-modules-5.10.0-20-arm64-di is NEW.
binary:nic-modules-5.10.0-20-arm64-di is NEW.
binary:nic-shared-modules-5.10.0-20-arm64-di is NEW.
binary:nic-usb-modules-5.10.0-20-arm64-di is NEW.
binary:nic-wireless-modules-5.10.0-20-arm64-di is NEW.
binary:ppp-modules-5.10.0-20-arm64-di is NEW.
binary:sata-modules-5.10.0-20-arm64-di is NEW.
binary:scsi-core-modules-5.10.0-20-arm64-di is NEW.
binary:scsi-modules-5.10.0-20-arm64-di is NEW.
binary:scsi-nic-modules-5.10.0-20-arm64-di is NEW.
binary:squashfs-modules-5.10.0-20-arm64-di is NEW.
binary:udf-modules-5.10.0-20-arm64-di is NEW.
binary:uinput-modules-5.10.0-20-arm64-di is NEW.
binary:usb-modules-5.10.0-20-arm64-di is NEW.
binary:usb-serial-modules-5.10.0-20-arm64-di is NEW.
binary:usb-storage-modules-5.10.0-20-arm64-di is NEW.
binary:xfs-modules-5.10.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

Bug#765472: marked as done (nfs-common: idmapd doesn't map groups with names including (german) umlauts on nfs mounted volumes)

[Debian Bug Tracking System]

Your message dated Sat, 10 Dec 2022 20:00:49 +0100
with message-id 
and subject line Re: Bug#765472: nfs-common: idmapd doesn't map groups with 
names including (german) umlauts on nfs mounted volumes
has caused the Debian Bug report #765472,
regarding nfs-common: idmapd doesn't map groups with names including (german) 
umlauts on nfs mounted volumes
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.)


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

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
situation:
nfs server (wheezy) with winbind and MS Active Directory integration.
nfs client (wheezy) with samba, winbind and MS Active Directory integration.

the nfs server is exporting a directory via nfs and group ownership set to some 
AD groups.
AD is installed in german, thus using umlauts in some default groups, e.g. 
"domänen-benutzer".

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
chgrp some files/directories to such a group (tested with two groups containing 
umlauts) on the nfs server side.

   * What was the outcome of this action?
stat on the directories on the nfs server shows GID and group name correctly.
stat (or ls -l) on the client side sees GID 4294967294 (nogroup).

switching groups on the server side from a working group to one with umlauts 
however doesn't ever change the GID on the client side, not even to nogroup.

   * What outcome did you expect instead?
a correct mapping from the server side to the nfs client.



-- 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  60854  status
1000241   tcp  38982  status
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=yes
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 7
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = netto.lan
Local-Realms = netto.lan
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
[Translation]
Method = nsswitch
-- /etc/fstab --
01nfs-01v.netto.lan:uportal/www   /mnt/nfs/uportal/www  nfs4 
proto=tcp,sec=sys  0   0
-- /proc/mounts --
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
01nfs-01v.netto.lan://uportal/www /mnt/nfs/uportal/www nfs4 
rw,relatime,vers=4,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.161.220.249,minorversion=0,local_lock=none,addr=10.161.220.250
 0 0

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

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

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

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

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

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

On Wed, Oct 15, 2014 at 01:56:37PM +0200, Norbert F wrote:
> Package: nfs-common
> Version: 1:1.2.6-4
> Severity: normal
> Tags: l10n
> 
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> situation:
> nfs server (wheezy) with winbind and MS Active Directory integration.
> nfs client (wheezy) with samba, winbind and MS Active Directory integration.
> 
> the nfs server is exporting a directory via nfs and group ownership set to 
> some AD groups.
> AD is installed i

Bug#818269: marked as done (nfs-common: Failed to get info from "systemctl is-enabled nfs-common")

[Debian Bug Tracking System]

Your message dated Sat, 10 Dec 2022 20:11:52 +0100
with message-id 
and subject line Re: Bug#818269: nfs-common: Failed to get info from "systemctl 
is-enabled nfs-common"
has caused the Debian Bug report #818269,
regarding nfs-common: Failed to get info from "systemctl is-enabled nfs-common"
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.)


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

Dear Maintainer,

I am using clean Debian Jessie + LXDE install. After installing nfs-common
package, when I typing "systemctl is-enabled nfs-common.service" (from user or
from root), I get

ecko@debian:~$ systemctl is-enabled nfs-common.service
Failed to get unit file state for nfs-common.service: No such file or directory
ecko@debian:~$

With other services, i.e. ssh, it's all right.

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

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

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



-- 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  35634  status
1000241   tcp  33540  status
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /run/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --

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

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

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

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

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

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

On Tue, Mar 15, 2016 at 01:03:27PM +0300, Reverend Homer wrote:
> Package: nfs-common
> Version: 1:1.2.8-9
> Severity: normal
> 
> Dear Maintainer,
> 
> I am using clean Debian Jessie + LXDE install. After installing nfs-common
> package, when I typing "systemctl is-enabled nfs-common.service" (from user or
> from root), I get
> 
> ecko@debian:~$ systemctl is-enabled nfs-common.service
> Failed to get unit file state for nfs-common.service: No such file or 
> directory
> ecko@debian:~$
> 
> With other services, i.e. ssh, it's all right.

I'm closing this old bugreport. In case it would be still reproducible
with a recent installation and version, then please do report back. In
sense ob BTS housekeepin I'm closing the report.

Regards,
Salvatore--- End Message ---

linux-signed-i386_6.0.12+1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Dec 2022 06:54:57 +0100
Source: linux-signed-i386
Architecture: source
Version: 6.0.12+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-i386 (6.0.12+1) unstable; urgency=medium
 .
   * Sign kernel from linux 6.0.12-1
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.0.11
 - [arm*] binder: validate alloc->mm in ->mmap() handler
 - ceph: Use kcalloc for allocating multiple elements
 - ceph: fix NULL pointer dereference for req->r_session
 - wifi: mac80211: fix memory free error when registering wiphy fail
 - wifi: cfg80211: Fix bitrates overflow issue
 - wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support
 - [riscv64] dts: sifive unleashed: Add PWM controlled LEDs
 - audit: fix undefined behavior in bit shift for AUDIT_BIT
 - wifi: airo: do not assign -1 to unsigned char
 - wifi: mac80211: Fix ack frame idr leak when mesh has no route
 - wifi: ath11k: Fix QCN9074 firmware boot on x86
 - [s390x] zcrypt: fix warning about field-spanning write
 - [armhf] spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for
   every run
 - Revert "net: macsec: report real_dev features when HW offloading is
   enabled"
 - [x86] ACPI: video: Add backlight=native DMI quirk for Dell G15 5515
 - [x86] platform/x86: ideapad-laptop: Disable touchpad_switch
 - [x86] platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2
   2-in-1
 - [x86] platform/x86/intel/pmt: Sapphire Rapids PMT errata fix
 - [x86] platform/x86/intel/hid: Add some ACPI device IDs
 - [powerpc*] scsi: ibmvfc: Avoid path failures during live migration
 - scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC
 - drm: panel-orientation-quirks: Add quirk for Nanote UMPC-01
 - drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017)
 - block, bfq: fix null pointer dereference in bfq_bio_bfqg()
 - [s390x] always build relocatable kernel
 - [arm64] syscall: Include asm/ptrace.h in syscall_wrapper header.
 - nvme: quiet user passthrough command errors
 - nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked
 - net: wwan: iosm: fix kernel test robot reported errors
 - drm/amd/display: Zeromem mypipe heap struct before using it
 - drm/amd/display: Fix FCLK deviation and tool compile issues
 - drm/amd/display: Fix gpio port mapping issue
 - Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10
   properly""
 - drm/amdgpu: Drop eviction lock when allocating PT BO
 - drm/amd/display: only fill dirty rectangles when PSR is enabled
 - ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue
 - [riscv64] vdso: Do not add missing symbols to version section in linker
   script
 - [mips*] pic32: treat port as signed integer
 - io_uring/poll: lockdep annote io_poll_req_insert_locked
 - xfrm: fix "disable_policy" on ipv4 early demux
 - [arm64] dts: rockchip: fix quartz64-a bluetooth configuration
 - xfrm: replay: Fix ESN wrap around for GSO
 - af_key: Fix send_acquire race with pfkey_register
 - [arm64,armhf] ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove
 - ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()
 - [x86] hyperv: Restore VP assist page after cpu offlining/onlining
 - scsi: storvsc: Fix handling of srb_status and capacity change events
 - [amd64,arm64] PCI: hv: Only reuse existing IRTE allocation for Multi-MSI
 - [arm64] dts: rockchip: Fix Pine64 Quartz4-B PMIC interrupt
 - [x86] ASoC: max98373: Add checks for devm_kcalloc
 - regulator: core: fix kobject release warning and memory leak in
   regulator_register()
 - regulator: core: fix UAF in destroy_regulator()
 - [arm64,armhf] bus: sunxi-rsb: Remove the shutdown callback
 - [arm64,armhf] bus: sunxi-rsb: Support atomic transfers
 - [arm64] tee: optee: fix possible memory leak in optee_register_device()
 - net: liquidio: simplify if expression
 - ipvlan: hold lower dev to avoid possible use-after-free
 - rxrpc: Fix race between conn bundle lookup and bundle removal
   [ZDI-CAN-15975]
 - nfc/nci: fix race with opening and closing
 - [i386] net: pch_gbe: fix potential memleak in pch_gbe_tx_queue()
 - 9p/fd: fix issue of list_del corruption in p9_fd_cancel()
 - netfilter: conntrack: Fix data-races around ct mark
 - netfilter: nf_tables: do not set up extensions for end interval
 - iavf: Fix a crash during reset task
 - iavf: Do not restart Tx queues after reset task failure
 - iavf: remove INITIAL_MAC_SET to allow gARP to work properly
 - iavf: Fix race condition between iavf_s

Bug#1017869: nfs-utils: nfs-common and nfs-kernel-server initscripts are /bin/bash and shellcheck-dirty

[Salvatore Bonaccorso]

Hi,

On Sun, Aug 21, 2022 at 10:12:42PM +0200, наб wrote:
> Source: nfs-utils
> Version: 1:1.3.4-6
> Severity: minor
> Tags: patch
> 
> Dear Maintainer,
> 
> See subject; also, neither of them use any bash extensions.
> 
> Please consider the patch, below, based on current Salsa HEAD;
> this may also close #762939.

For changing to #!/bin/sh, as Ben explained in #762939:

This is true, but it sources /etc/default/nfs-common which could
contain bashisms.  I don't think this is worth the risk.

The same holds here for changing the scripts to #!/bin/sh.

Regards,
Salvatore

Processed: closing 885958

[Debian Bug Tracking System]

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

> close 885958
Bug #885958 [firmware-iwlwifi] hostapd: iwlwifi 5GHz hw_mode=a causes microcode 
fault
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 847204

[Debian Bug Tracking System]

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

> close 847204 1:2.5.4-1~exp5
Bug #847204 [nfs-kernel-server] nfs-kernel-server: `systemctl status` 
incorrectly reports server "active" even if not started
Marked as fixed in versions nfs-utils/1:2.5.4-1~exp5.
Bug #847204 [nfs-kernel-server] nfs-kernel-server: `systemctl status` 
incorrectly reports server "active" even if not started
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1025537: nfsd: Kernel Oops while serving NFS

[Salvatore Bonaccorso]

Hi Olivier,

On Sun, Dec 11, 2022 at 12:01:31AM +1100, Olivier Mehani wrote:
> Hi Salvatore,
> 
> On Fri 09 Dec 2022 at 22:22:49 +0100, Salvatore Bonaccorso wrote:
> > > On testing/bookworm, since booting on a 6-versioned linux-image, I have
> > > noticed frequent hang ups of the nfs server, rendering it mostly
> > > unusable. This is accompanied with Kernel Oops in the dmesg.
> > > This sounds similar to previous bugs #1014793 and #1020548, both RESOLVED 
> > > by
> > > later patches.
> > How easy can you trigger and reproduce the issue? If you can easily
> > reach that situation, can you try to bisect the issue? Easiest would
> > be to first pin point between Debian revisions, and later further
> > bisect in upstream stable series.
> > Do you have the possibility to do that?
> 
> It seems to be fairly reliable.
> 
> I'll give that a go, starting with
> * linux-image-5.19.0-2-amd64_5.19.11-1_amd64.deb
> * linux-image-6.0.0-1-amd64_6.0.2-1_amd64.deb

Great, thanks.

> I'm not certain how to bisect further. Which source and which kconfig should
> I use to build intermediate commits?

Does the following reference helps you further?
https://wiki.debian.org/DebianKernel/GitBisect

Thanks for taking time for pinpointing your issue.

Regards,
Salvatore

Processing of linux-signed-i386_5.10.158+1_source.changes

[Debian FTP Masters]

linux-signed-i386_5.10.158+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-i386_5.10.158+1.dsc
  linux-signed-i386_5.10.158+1.tar.xz

Greetings,

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

linux-signed-i386_5.10.158+1_source.changes is NEW

[Debian FTP Masters]

Mapping bullseye-proposed-updates to proposed-updates.
binary:acpi-modules-5.10.0-20-686-di is NEW.
binary:acpi-modules-5.10.0-20-686-pae-di is NEW.
binary:ata-modules-5.10.0-20-686-di is NEW.
binary:ata-modules-5.10.0-20-686-pae-di is NEW.
binary:btrfs-modules-5.10.0-20-686-di is NEW.
binary:btrfs-modules-5.10.0-20-686-pae-di is NEW.
binary:cdrom-core-modules-5.10.0-20-686-di is NEW.
binary:cdrom-core-modules-5.10.0-20-686-pae-di is NEW.
binary:crc-modules-5.10.0-20-686-di is NEW.
binary:crc-modules-5.10.0-20-686-pae-di is NEW.
binary:crypto-dm-modules-5.10.0-20-686-di is NEW.
binary:crypto-dm-modules-5.10.0-20-686-pae-di is NEW.
binary:crypto-modules-5.10.0-20-686-di is NEW.
binary:crypto-modules-5.10.0-20-686-pae-di is NEW.
binary:efi-modules-5.10.0-20-686-di is NEW.
binary:efi-modules-5.10.0-20-686-pae-di is NEW.
binary:event-modules-5.10.0-20-686-di is NEW.
binary:event-modules-5.10.0-20-686-pae-di is NEW.
binary:ext4-modules-5.10.0-20-686-di is NEW.
binary:ext4-modules-5.10.0-20-686-pae-di is NEW.
binary:f2fs-modules-5.10.0-20-686-di is NEW.
binary:f2fs-modules-5.10.0-20-686-pae-di is NEW.
binary:fat-modules-5.10.0-20-686-di is NEW.
binary:fat-modules-5.10.0-20-686-pae-di is NEW.
binary:fb-modules-5.10.0-20-686-di is NEW.
binary:fb-modules-5.10.0-20-686-pae-di is NEW.
binary:firewire-core-modules-5.10.0-20-686-di is NEW.
binary:firewire-core-modules-5.10.0-20-686-pae-di is NEW.
binary:fuse-modules-5.10.0-20-686-di is NEW.
binary:fuse-modules-5.10.0-20-686-pae-di is NEW.
binary:i2c-modules-5.10.0-20-686-di is NEW.
binary:i2c-modules-5.10.0-20-686-pae-di is NEW.
binary:input-modules-5.10.0-20-686-di is NEW.
binary:input-modules-5.10.0-20-686-pae-di is NEW.
binary:isofs-modules-5.10.0-20-686-di is NEW.
binary:isofs-modules-5.10.0-20-686-pae-di is NEW.
binary:jfs-modules-5.10.0-20-686-di is NEW.
binary:jfs-modules-5.10.0-20-686-pae-di is NEW.
binary:kernel-image-5.10.0-20-686-di is NEW.
binary:kernel-image-5.10.0-20-686-pae-di is NEW.
binary:linux-image-5.10.0-20-686 is NEW.
binary:linux-image-5.10.0-20-686-pae is NEW.
binary:linux-image-5.10.0-20-rt-686-pae is NEW.
binary:loop-modules-5.10.0-20-686-di is NEW.
binary:loop-modules-5.10.0-20-686-pae-di is NEW.
binary:md-modules-5.10.0-20-686-di is NEW.
binary:md-modules-5.10.0-20-686-pae-di is NEW.
binary:mmc-core-modules-5.10.0-20-686-di is NEW.
binary:mmc-core-modules-5.10.0-20-686-pae-di is NEW.
binary:mmc-modules-5.10.0-20-686-di is NEW.
binary:mmc-modules-5.10.0-20-686-pae-di is NEW.
binary:mouse-modules-5.10.0-20-686-di is NEW.
binary:mouse-modules-5.10.0-20-686-pae-di is NEW.
binary:mtd-core-modules-5.10.0-20-686-di is NEW.
binary:mtd-core-modules-5.10.0-20-686-pae-di is NEW.
binary:multipath-modules-5.10.0-20-686-di is NEW.
binary:multipath-modules-5.10.0-20-686-pae-di is NEW.
binary:nbd-modules-5.10.0-20-686-di is NEW.
binary:nbd-modules-5.10.0-20-686-pae-di is NEW.
binary:nic-modules-5.10.0-20-686-di is NEW.
binary:nic-modules-5.10.0-20-686-pae-di is NEW.
binary:nic-pcmcia-modules-5.10.0-20-686-di is NEW.
binary:nic-pcmcia-modules-5.10.0-20-686-pae-di is NEW.
binary:nic-shared-modules-5.10.0-20-686-di is NEW.
binary:nic-shared-modules-5.10.0-20-686-pae-di is NEW.
binary:nic-usb-modules-5.10.0-20-686-di is NEW.
binary:nic-usb-modules-5.10.0-20-686-pae-di is NEW.
binary:nic-wireless-modules-5.10.0-20-686-di is NEW.
binary:nic-wireless-modules-5.10.0-20-686-pae-di is NEW.
binary:pata-modules-5.10.0-20-686-di is NEW.
binary:pata-modules-5.10.0-20-686-pae-di is NEW.
binary:pcmcia-modules-5.10.0-20-686-di is NEW.
binary:pcmcia-modules-5.10.0-20-686-pae-di is NEW.
binary:pcmcia-storage-modules-5.10.0-20-686-di is NEW.
binary:pcmcia-storage-modules-5.10.0-20-686-pae-di is NEW.
binary:ppp-modules-5.10.0-20-686-di is NEW.
binary:ppp-modules-5.10.0-20-686-pae-di is NEW.
binary:rfkill-modules-5.10.0-20-686-di is NEW.
binary:rfkill-modules-5.10.0-20-686-pae-di is NEW.
binary:sata-modules-5.10.0-20-686-di is NEW.
binary:sata-modules-5.10.0-20-686-pae-di is NEW.
binary:scsi-core-modules-5.10.0-20-686-di is NEW.
binary:scsi-core-modules-5.10.0-20-686-pae-di is NEW.
binary:scsi-modules-5.10.0-20-686-di is NEW.
binary:scsi-modules-5.10.0-20-686-pae-di is NEW.
binary:scsi-nic-modules-5.10.0-20-686-di is NEW.
binary:scsi-nic-modules-5.10.0-20-686-pae-di is NEW.
binary:serial-modules-5.10.0-20-686-di is NEW.
binary:serial-modules-5.10.0-20-686-pae-di is NEW.
binary:sound-modules-5.10.0-20-686-di is NEW.
binary:sound-modules-5.10.0-20-686-pae-di is NEW.
binary:speakup-modules-5.10.0-20-686-di is NEW.
binary:speakup-modules-5.10.0-20-686-pae-di is NEW.
binary:squashfs-modules-5.10.0-20-686-di is NEW.
binary:squashfs-modules-5.10.0-20-686-pae-di is NEW.
binary:udf-modules-5.10.0-20-686-di is NEW.
binary:udf-modules-5.10.0-20-686-pae-di is NEW.
binary:uinput-modules-5.10.0-20-686-di is NEW.
binary:uinput-modules-5.10.0-20-686-pae-di is NEW.
binary:usb-modules-5.10.0-20-686-di is NEW.
binary:usb-modules-5.10.0-20-686-pae-di is NEW.
binary:usb-serial-modules-5.10.0-20-686-

linux-signed-arm64_5.10.158+1_source.changes ACCEPTED into proposed-updates

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Dec 2022 18:14:20 +0100
Source: linux-signed-arm64
Architecture: source
Version: 5.10.158+1
Distribution: bullseye-proposed-updates
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-arm64 (5.10.158+1) bullseye; urgency=medium
 .
   * Sign kernel from linux 5.10.158-1
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.150
 - ALSA: oss: Fix potential deadlock at unregistration
 - ALSA: rawmidi: Drop register_mutex in snd_rawmidi_free()
 - ALSA: usb-audio: Fix potential memory leaks
 - ALSA: usb-audio: Fix NULL dererence at error path
 - ALSA: hda/realtek: remove ALC289_FIXUP_DUAL_SPK for Dell 5530
 - ALSA: hda/realtek: Correct pin configs for ASUS G533Z
 - ALSA: hda/realtek: Add quirk for ASUS GV601R laptop
 - ALSA: hda/realtek: Add Intel Reference SSID to support headset keys
 - cifs: destage dirty pages before re-reading them for cache=none
 - cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message
 - iio: dac: ad5593r: Fix i2c read protocol requirements
 - iio: ltc2497: Fix reading conversion results
 - iio: adc: ad7923: fix channel readings for some variants
 - iio: pressure: dps310: Refactor startup procedure
 - iio: pressure: dps310: Reset chip after timeout
 - usb: add quirks for Lenovo OneLink+ Dock
 - can: kvaser_usb: Fix use of uninitialized completion
 - can: kvaser_usb_leaf: Fix overread with an invalid command
 - can: kvaser_usb_leaf: Fix TX queue out of sync after restart
 - can: kvaser_usb_leaf: Fix CAN state after restart
 - fs: dlm: fix race between test_bit() and queue_work()
 - fs: dlm: handle -EBUSY first in lock arg validation
 - HID: multitouch: Add memory barriers
 - quota: Check next/prev free block number after reading from quota file
 - [arm64,armhf] platform/chrome: cros_ec_proto: Update version on
   GET_NEXT_EVENT failure
 - [arm64] regulator: qcom_rpm: Fix circular deferral regression
 - nvme-pci: set min_align_mask before calculating max_hw_sectors
 - drm/virtio: Check whether transferred 2D BO is shmem
 - drm/udl: Restore display mode on resume
 - block: fix inflight statistics of part0
 - mm/mmap: undo ->mmap() when arch_validate_flags() fails
 - PCI: Sanitise firmware BAR assignments behind a PCI-PCI bridge
 - [x86] powercap: intel_rapl: Use standard Energy Unit for SPR Dram RAPL
   domain
 - scsi: qedf: Populate sysfs attributes for vport
 - fbdev: smscufx: Fix use-after-free in ufx_ops_open() (CVE-2022-41849)
 - btrfs: fix race between quota enable and quota rescan ioctl
 - f2fs: increase the limit for reserve_root
 - f2fs: fix to do sanity check on destination blkaddr during recovery
 - f2fs: fix to do sanity check on summary info
 - jbd2: wake up journal waiters in FIFO order, not LIFO
 - jbd2: fix potential buffer head reference count leak
 - jbd2: fix potential use-after-free in jbd2_fc_wait_bufs
 - jbd2: add miss release buffer head in fc_do_one_pass()
 - ext4: avoid crash when inline data creation follows DIO write
 - ext4: fix null-ptr-deref in ext4_write_info
 - ext4: make ext4_lazyinit_thread freezable
 - ext4: don't increase iversion counter for ea_inodes
 - ext4: ext4_read_bh_lock() should submit IO if the buffer isn't uptodate
 - ext4: place buffer head allocation before handle start
 - ext4: fix miss release buffer head in ext4_fc_write_inode
 - ext4: fix potential memory leak in ext4_fc_record_modified_inode()
 - ext4: fix potential memory leak in ext4_fc_record_regions()
 - ext4: update 'state->fc_regions_size' after successful memory allocation
 - [amd64] livepatch: fix race between fork and KLP transition
 - ftrace: Properly unset FTRACE_HASH_FL_MOD
 - ring-buffer: Allow splice to read previous partially read pages
 - ring-buffer: Have the shortest_full queue be the shortest not longest
 - ring-buffer: Check pending waiters when doing wake ups as well
 - ring-buffer: Add ring_buffer_wake_waiters()
 - ring-buffer: Fix race between reset page and reading page
 - tracing: Disable interrupt or preemption before acquiring arch_spinlock_t
 - [x86] thunderbolt: Explicitly enable lane adapter hotplug events at
   startup
 - efi: libstub: drop pointless get_memory_map() call
 - [arm64,armhf] media: cedrus: Set the platform driver data earlier
 - [x86] KVM: x86/emulator: Fix handing of POP SS to correctly set
   interruptibility
 - [x86] KVM: nVMX: Unconditionally purge queued/injected events on nested
   "exit"
 - [x86] KVM: VMX: Drop bits 31:16 when shoving exception error code into
   VMCS
 - drm/nouveau/kms/nv140-: Disable interlacin

linux-signed-amd64_5.10.158+1_source.changes ACCEPTED into proposed-updates

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Dec 2022 18:14:20 +0100
Source: linux-signed-amd64
Architecture: source
Version: 5.10.158+1
Distribution: bullseye-proposed-updates
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-amd64 (5.10.158+1) bullseye; urgency=medium
 .
   * Sign kernel from linux 5.10.158-1
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.150
 - ALSA: oss: Fix potential deadlock at unregistration
 - ALSA: rawmidi: Drop register_mutex in snd_rawmidi_free()
 - ALSA: usb-audio: Fix potential memory leaks
 - ALSA: usb-audio: Fix NULL dererence at error path
 - ALSA: hda/realtek: remove ALC289_FIXUP_DUAL_SPK for Dell 5530
 - ALSA: hda/realtek: Correct pin configs for ASUS G533Z
 - ALSA: hda/realtek: Add quirk for ASUS GV601R laptop
 - ALSA: hda/realtek: Add Intel Reference SSID to support headset keys
 - cifs: destage dirty pages before re-reading them for cache=none
 - cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message
 - iio: dac: ad5593r: Fix i2c read protocol requirements
 - iio: ltc2497: Fix reading conversion results
 - iio: adc: ad7923: fix channel readings for some variants
 - iio: pressure: dps310: Refactor startup procedure
 - iio: pressure: dps310: Reset chip after timeout
 - usb: add quirks for Lenovo OneLink+ Dock
 - can: kvaser_usb: Fix use of uninitialized completion
 - can: kvaser_usb_leaf: Fix overread with an invalid command
 - can: kvaser_usb_leaf: Fix TX queue out of sync after restart
 - can: kvaser_usb_leaf: Fix CAN state after restart
 - fs: dlm: fix race between test_bit() and queue_work()
 - fs: dlm: handle -EBUSY first in lock arg validation
 - HID: multitouch: Add memory barriers
 - quota: Check next/prev free block number after reading from quota file
 - [arm64,armhf] platform/chrome: cros_ec_proto: Update version on
   GET_NEXT_EVENT failure
 - [arm64] regulator: qcom_rpm: Fix circular deferral regression
 - nvme-pci: set min_align_mask before calculating max_hw_sectors
 - drm/virtio: Check whether transferred 2D BO is shmem
 - drm/udl: Restore display mode on resume
 - block: fix inflight statistics of part0
 - mm/mmap: undo ->mmap() when arch_validate_flags() fails
 - PCI: Sanitise firmware BAR assignments behind a PCI-PCI bridge
 - [x86] powercap: intel_rapl: Use standard Energy Unit for SPR Dram RAPL
   domain
 - scsi: qedf: Populate sysfs attributes for vport
 - fbdev: smscufx: Fix use-after-free in ufx_ops_open() (CVE-2022-41849)
 - btrfs: fix race between quota enable and quota rescan ioctl
 - f2fs: increase the limit for reserve_root
 - f2fs: fix to do sanity check on destination blkaddr during recovery
 - f2fs: fix to do sanity check on summary info
 - jbd2: wake up journal waiters in FIFO order, not LIFO
 - jbd2: fix potential buffer head reference count leak
 - jbd2: fix potential use-after-free in jbd2_fc_wait_bufs
 - jbd2: add miss release buffer head in fc_do_one_pass()
 - ext4: avoid crash when inline data creation follows DIO write
 - ext4: fix null-ptr-deref in ext4_write_info
 - ext4: make ext4_lazyinit_thread freezable
 - ext4: don't increase iversion counter for ea_inodes
 - ext4: ext4_read_bh_lock() should submit IO if the buffer isn't uptodate
 - ext4: place buffer head allocation before handle start
 - ext4: fix miss release buffer head in ext4_fc_write_inode
 - ext4: fix potential memory leak in ext4_fc_record_modified_inode()
 - ext4: fix potential memory leak in ext4_fc_record_regions()
 - ext4: update 'state->fc_regions_size' after successful memory allocation
 - [amd64] livepatch: fix race between fork and KLP transition
 - ftrace: Properly unset FTRACE_HASH_FL_MOD
 - ring-buffer: Allow splice to read previous partially read pages
 - ring-buffer: Have the shortest_full queue be the shortest not longest
 - ring-buffer: Check pending waiters when doing wake ups as well
 - ring-buffer: Add ring_buffer_wake_waiters()
 - ring-buffer: Fix race between reset page and reading page
 - tracing: Disable interrupt or preemption before acquiring arch_spinlock_t
 - [x86] thunderbolt: Explicitly enable lane adapter hotplug events at
   startup
 - efi: libstub: drop pointless get_memory_map() call
 - [arm64,armhf] media: cedrus: Set the platform driver data earlier
 - [x86] KVM: x86/emulator: Fix handing of POP SS to correctly set
   interruptibility
 - [x86] KVM: nVMX: Unconditionally purge queued/injected events on nested
   "exit"
 - [x86] KVM: VMX: Drop bits 31:16 when shoving exception error code into
   VMCS
 - drm/nouveau/kms/nv140-: Disable interlacin

Bug#1017977: Fails to load intel/ibt-20-1-3.sfi

[Olaf Meeuwissen]

Olaf Meeuwissen  writes:

> Upgrading the firmware-iwlwifi package last week (2022-11-27) from
> 20221012-1 to 20221109-2 fixed the issue for linux-image-6.0.0-4-amd64
> 6.0.8-1.  The changelog for 20221109-1 mentioned
>
>   * iwlwifi: update firmware files for Intel Bluetooth AX2*
>   * iwlwifi: Add Intel Wireless AX211 Bluethooth firmware and
> configuration (Closes: #1023245)
>
> which may be related to fixing it for my
>
>   Intel Corporation Wi-Fi 6 AX200 (rev 1a)
>
> However, upgrading today (2022-12-04) to linux-image-6.0.0-5-amd64
> 6.0.10-1 reintroduced it.
>
> Cold booting into 6.0.0-4 I have a working Bluetooth-only keyboard.
> Rebooting from that into 6.0.0-5 my keyboard remains functional.
> Cold booting into 6.0.0-5 my Bluetooth-only keyboard is unresponsive.
>
> For both 6.0.0-5 boot scenarios, dmesg --level=err includes
>
>   bluetooth hci0: firmware: failed to load intel/ibt-20-1-3.sfi (-2)
>
> Twice, actually, about 10 microseconds apart.
>
> For 6.0.0-4 there is no such error message.

FYI, the situation is unchanged after upgrading

  - firmware-iwlwifi  from 20221109-2 to 20221109-4
  - linux-image-6.0.0-5-amd64 from  6.0.10-1  to  6.0.10-2
  - linux-image-amd64 from  6.0.10-1  to  6.0.10-2

Hope this helps,
--
Olaf Meeuwissen