linux-signed-i386_6.0.12+1_source.changes is NEW

2022-12-09 Thread Debian FTP Masters
Mapping sid to unstable.
binary:acpi-modules-6.0.0-6-686-di is NEW.
binary:acpi-modules-6.0.0-6-686-pae-di is NEW.
binary:ata-modules-6.0.0-6-686-di is NEW.
binary:ata-modules-6.0.0-6-686-pae-di is NEW.
binary:btrfs-modules-6.0.0-6-686-di is NEW.
binary:btrfs-modules-6.0.0-6-686-pae-di is NEW.
binary:cdrom-core-modules-6.0.0-6-686-di is NEW.
binary:cdrom-core-modules-6.0.0-6-686-pae-di is NEW.
binary:crc-modules-6.0.0-6-686-di is NEW.
binary:crc-modules-6.0.0-6-686-pae-di is NEW.
binary:crypto-dm-modules-6.0.0-6-686-di is NEW.
binary:crypto-dm-modules-6.0.0-6-686-pae-di is NEW.
binary:crypto-modules-6.0.0-6-686-di is NEW.
binary:crypto-modules-6.0.0-6-686-pae-di is NEW.
binary:efi-modules-6.0.0-6-686-di is NEW.
binary:efi-modules-6.0.0-6-686-pae-di is NEW.
binary:event-modules-6.0.0-6-686-di is NEW.
binary:event-modules-6.0.0-6-686-pae-di is NEW.
binary:ext4-modules-6.0.0-6-686-di is NEW.
binary:ext4-modules-6.0.0-6-686-pae-di is NEW.
binary:f2fs-modules-6.0.0-6-686-di is NEW.
binary:f2fs-modules-6.0.0-6-686-pae-di is NEW.
binary:fat-modules-6.0.0-6-686-di is NEW.
binary:fat-modules-6.0.0-6-686-pae-di is NEW.
binary:fb-modules-6.0.0-6-686-di is NEW.
binary:fb-modules-6.0.0-6-686-pae-di is NEW.
binary:firewire-core-modules-6.0.0-6-686-di is NEW.
binary:firewire-core-modules-6.0.0-6-686-pae-di is NEW.
binary:fuse-modules-6.0.0-6-686-di is NEW.
binary:fuse-modules-6.0.0-6-686-pae-di is NEW.
binary:i2c-modules-6.0.0-6-686-di is NEW.
binary:i2c-modules-6.0.0-6-686-pae-di is NEW.
binary:input-modules-6.0.0-6-686-di is NEW.
binary:input-modules-6.0.0-6-686-pae-di is NEW.
binary:isofs-modules-6.0.0-6-686-di is NEW.
binary:isofs-modules-6.0.0-6-686-pae-di is NEW.
binary:jfs-modules-6.0.0-6-686-di is NEW.
binary:jfs-modules-6.0.0-6-686-pae-di is NEW.
binary:kernel-image-6.0.0-6-686-di is NEW.
binary:kernel-image-6.0.0-6-686-pae-di is NEW.
binary:linux-image-6.0.0-6-686 is NEW.
binary:linux-image-6.0.0-6-686-pae is NEW.
binary:linux-image-6.0.0-6-rt-686-pae is NEW.
binary:loop-modules-6.0.0-6-686-di is NEW.
binary:loop-modules-6.0.0-6-686-pae-di is NEW.
binary:md-modules-6.0.0-6-686-di is NEW.
binary:md-modules-6.0.0-6-686-pae-di is NEW.
binary:mmc-core-modules-6.0.0-6-686-di is NEW.
binary:mmc-core-modules-6.0.0-6-686-pae-di is NEW.
binary:mmc-modules-6.0.0-6-686-di is NEW.
binary:mmc-modules-6.0.0-6-686-pae-di is NEW.
binary:mouse-modules-6.0.0-6-686-di is NEW.
binary:mouse-modules-6.0.0-6-686-pae-di is NEW.
binary:mtd-core-modules-6.0.0-6-686-di is NEW.
binary:mtd-core-modules-6.0.0-6-686-pae-di is NEW.
binary:multipath-modules-6.0.0-6-686-di is NEW.
binary:multipath-modules-6.0.0-6-686-pae-di is NEW.
binary:nbd-modules-6.0.0-6-686-di is NEW.
binary:nbd-modules-6.0.0-6-686-pae-di is NEW.
binary:nic-modules-6.0.0-6-686-di is NEW.
binary:nic-modules-6.0.0-6-686-pae-di is NEW.
binary:nic-pcmcia-modules-6.0.0-6-686-di is NEW.
binary:nic-pcmcia-modules-6.0.0-6-686-pae-di is NEW.
binary:nic-shared-modules-6.0.0-6-686-di is NEW.
binary:nic-shared-modules-6.0.0-6-686-pae-di is NEW.
binary:nic-usb-modules-6.0.0-6-686-di is NEW.
binary:nic-usb-modules-6.0.0-6-686-pae-di is NEW.
binary:nic-wireless-modules-6.0.0-6-686-di is NEW.
binary:nic-wireless-modules-6.0.0-6-686-pae-di is NEW.
binary:pata-modules-6.0.0-6-686-di is NEW.
binary:pata-modules-6.0.0-6-686-pae-di is NEW.
binary:pcmcia-modules-6.0.0-6-686-di is NEW.
binary:pcmcia-modules-6.0.0-6-686-pae-di is NEW.
binary:pcmcia-storage-modules-6.0.0-6-686-di is NEW.
binary:pcmcia-storage-modules-6.0.0-6-686-pae-di is NEW.
binary:ppp-modules-6.0.0-6-686-di is NEW.
binary:ppp-modules-6.0.0-6-686-pae-di is NEW.
binary:rfkill-modules-6.0.0-6-686-di is NEW.
binary:rfkill-modules-6.0.0-6-686-pae-di is NEW.
binary:sata-modules-6.0.0-6-686-di is NEW.
binary:sata-modules-6.0.0-6-686-pae-di is NEW.
binary:scsi-core-modules-6.0.0-6-686-di is NEW.
binary:scsi-core-modules-6.0.0-6-686-pae-di is NEW.
binary:scsi-modules-6.0.0-6-686-di is NEW.
binary:scsi-modules-6.0.0-6-686-pae-di is NEW.
binary:scsi-nic-modules-6.0.0-6-686-di is NEW.
binary:scsi-nic-modules-6.0.0-6-686-pae-di is NEW.
binary:serial-modules-6.0.0-6-686-di is NEW.
binary:serial-modules-6.0.0-6-686-pae-di is NEW.
binary:sound-modules-6.0.0-6-686-di is NEW.
binary:sound-modules-6.0.0-6-686-pae-di is NEW.
binary:speakup-modules-6.0.0-6-686-di is NEW.
binary:speakup-modules-6.0.0-6-686-pae-di is NEW.
binary:squashfs-modules-6.0.0-6-686-di is NEW.
binary:squashfs-modules-6.0.0-6-686-pae-di is NEW.
binary:udf-modules-6.0.0-6-686-di is NEW.
binary:udf-modules-6.0.0-6-686-pae-di is NEW.
binary:uinput-modules-6.0.0-6-686-di is NEW.
binary:uinput-modules-6.0.0-6-686-pae-di is NEW.
binary:usb-modules-6.0.0-6-686-di is NEW.
binary:usb-modules-6.0.0-6-686-pae-di is NEW.
binary:usb-serial-modules-6.0.0-6-686-di is NEW.
binary:usb-serial-modules-6.0.0-6-686-pae-di is NEW.
binary:usb-storage-modules-6.0.0-6-686-di is NEW.
binary:usb-storage-modules-6.0.0-6-686-pae-di is NEW.
binary:xfs-modules-6.0.0-6-686-di is NEW.

Processing of linux-signed-i386_6.0.12+1_source.changes

2022-12-09 Thread Debian FTP Masters
linux-signed-i386_6.0.12+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-i386_6.0.12+1.dsc
  linux-signed-i386_6.0.12+1.tar.xz

Greetings,

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



linux-signed-i386_6.1~rc8+1~exp1_source.changes ACCEPTED into experimental

2022-12-09 Thread 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 08:20:09 +0100
Source: linux-signed-i386
Architecture: source
Version: 6.1~rc8+1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-i386 (6.1~rc8+1~exp1) experimental; urgency=medium
 .
   * Sign kernel from linux 6.1~rc8-1~exp1
 .
   * New upstream release candidate.
 .
   [ Bastian Blank ]
   * Generate calls into rules.real for setup targets.
   * Simplify source rules generation.
   * Generate calls into rules.real for extra.
   * Remove remaining old targets in rules.real.
 .
   [ Salvatore Bonaccorso ]
   * lockdown: Correct mentioning of mode when LOCK_DOWN_IN_EFI_SECURE_BOOT is
 enabled (Closes: #1025417)
Checksums-Sha1:
 60d893347c8952f67ac96a9a298581edfbb80c27 13864 
linux-signed-i386_6.1~rc8+1~exp1.dsc
 ee4a1d7865b870244f955d8614447d0fa4f50bfb 3851908 
linux-signed-i386_6.1~rc8+1~exp1.tar.xz
Checksums-Sha256:
 16df23efe4ad86cbda3e6c97792387ab13928aefce890b67b60641f89428e9a7 13864 
linux-signed-i386_6.1~rc8+1~exp1.dsc
 e9a08dd4e71de2bc5a18c36eea6b9e01f39d950dfac9fd04032bf2b26f873a2e 3851908 
linux-signed-i386_6.1~rc8+1~exp1.tar.xz
Files:
 a1ad75557cf505f0246e2a2ffad40f64 13864 kernel optional 
linux-signed-i386_6.1~rc8+1~exp1.dsc
 86a73d8fa28285c51ed788e47b5a3e14 3851908 kernel optional 
linux-signed-i386_6.1~rc8+1~exp1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmOT9PwACgkQi0FRiLdO
NzYfoA/+NPCqsy5AnBDMnsPk4R0We+vZGw9LBia6shx2HFAkpZqxiteU4GOUi6bU
UB/680Mxrqc5lo+7BzqGXWrfQz1odPrsn6g/kyocc7GIQu149G4Jixrx+EpxL41K
utGx6jjBpf0Tg3ve0Eo4FpJ+F2hAltC4f2uyU6AKg8qND19BgubaTpNdOfEn5JAc
e2CjK9Q66CgDRB8PeyVwRDcONsiF/5Gj5asAhIRiIBXEytnynvzQ6A8e2RCqx42C
Wv3TplKDlNMmYBirtJZM6ADxsba4tkb8xoAxVt1LcY/mZYCe5eEwZMZeKokf6zFe
YHCKHP87/YKzSu5pWXm8rCkL/b/YfeCdtGHybvxBodnQ/MpOrNVP9n52jqlozGRx
7UQlQTiL09ETTJvqAKVX4ui8vEO1aqNL1IUDNdnExE/ri6ZfPFjBEDtPbCwdpodl
9pyam+XH3kpSvF567z76rCqTO17UY7LbowqnmAim5r8Sgg6qVxvT8Wl3XDBmkxs9
JVNRgLUaAZZvciE8p5tpzbdH6bh8G6Fa3X0blt2tCvDVwHdhdPgEgSY8TroITiNy
K5x0/1mCNqAkrQ5OMEswkp6C1QA+NWDsDcc6PDWfIUWenQlREShTvaU3L7l49OWz
k4NUaoJfsqZ4W1SgRhPbwfidbO/sJMed2hqK+Kj5g1Us++LVmWI=
=3z9c
-END PGP SIGNATURE-



Processing of linux-signed-i386_6.1~rc8+1~exp1_source.changes

2022-12-09 Thread Debian FTP Masters
linux-signed-i386_6.1~rc8+1~exp1_source.changes uploaded successfully to 
localhost
along with the files:
  linux-signed-i386_6.1~rc8+1~exp1.dsc
  linux-signed-i386_6.1~rc8+1~exp1.tar.xz

Greetings,

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



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

2022-12-09 Thread 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-amd64
Architecture: source
Version: 6.0.12+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-amd64 (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 

linux-signed-amd64_6.0.12+1_source.changes is NEW

2022-12-09 Thread Debian FTP Masters
Mapping sid to unstable.
binary:acpi-modules-6.0.0-6-amd64-di is NEW.
binary:ata-modules-6.0.0-6-amd64-di is NEW.
binary:btrfs-modules-6.0.0-6-amd64-di is NEW.
binary:cdrom-core-modules-6.0.0-6-amd64-di is NEW.
binary:crc-modules-6.0.0-6-amd64-di is NEW.
binary:crypto-dm-modules-6.0.0-6-amd64-di is NEW.
binary:crypto-modules-6.0.0-6-amd64-di is NEW.
binary:efi-modules-6.0.0-6-amd64-di is NEW.
binary:event-modules-6.0.0-6-amd64-di is NEW.
binary:ext4-modules-6.0.0-6-amd64-di is NEW.
binary:f2fs-modules-6.0.0-6-amd64-di is NEW.
binary:fat-modules-6.0.0-6-amd64-di is NEW.
binary:fb-modules-6.0.0-6-amd64-di is NEW.
binary:firewire-core-modules-6.0.0-6-amd64-di is NEW.
binary:fuse-modules-6.0.0-6-amd64-di is NEW.
binary:i2c-modules-6.0.0-6-amd64-di is NEW.
binary:input-modules-6.0.0-6-amd64-di is NEW.
binary:isofs-modules-6.0.0-6-amd64-di is NEW.
binary:jfs-modules-6.0.0-6-amd64-di is NEW.
binary:kernel-image-6.0.0-6-amd64-di is NEW.
binary:linux-image-6.0.0-6-amd64 is NEW.
binary:linux-image-6.0.0-6-cloud-amd64 is NEW.
binary:linux-image-6.0.0-6-rt-amd64 is NEW.
binary:loop-modules-6.0.0-6-amd64-di is NEW.
binary:md-modules-6.0.0-6-amd64-di is NEW.
binary:mmc-core-modules-6.0.0-6-amd64-di is NEW.
binary:mmc-modules-6.0.0-6-amd64-di is NEW.
binary:mouse-modules-6.0.0-6-amd64-di is NEW.
binary:mtd-core-modules-6.0.0-6-amd64-di is NEW.
binary:multipath-modules-6.0.0-6-amd64-di is NEW.
binary:nbd-modules-6.0.0-6-amd64-di is NEW.
binary:nic-modules-6.0.0-6-amd64-di is NEW.
binary:nic-pcmcia-modules-6.0.0-6-amd64-di is NEW.
binary:nic-shared-modules-6.0.0-6-amd64-di is NEW.
binary:nic-usb-modules-6.0.0-6-amd64-di is NEW.
binary:nic-wireless-modules-6.0.0-6-amd64-di is NEW.
binary:pata-modules-6.0.0-6-amd64-di is NEW.
binary:pcmcia-modules-6.0.0-6-amd64-di is NEW.
binary:pcmcia-storage-modules-6.0.0-6-amd64-di is NEW.
binary:ppp-modules-6.0.0-6-amd64-di is NEW.
binary:rfkill-modules-6.0.0-6-amd64-di is NEW.
binary:sata-modules-6.0.0-6-amd64-di is NEW.
binary:scsi-core-modules-6.0.0-6-amd64-di is NEW.
binary:scsi-modules-6.0.0-6-amd64-di is NEW.
binary:scsi-nic-modules-6.0.0-6-amd64-di is NEW.
binary:serial-modules-6.0.0-6-amd64-di is NEW.
binary:sound-modules-6.0.0-6-amd64-di is NEW.
binary:speakup-modules-6.0.0-6-amd64-di is NEW.
binary:squashfs-modules-6.0.0-6-amd64-di is NEW.
binary:udf-modules-6.0.0-6-amd64-di is NEW.
binary:uinput-modules-6.0.0-6-amd64-di is NEW.
binary:usb-modules-6.0.0-6-amd64-di is NEW.
binary:usb-serial-modules-6.0.0-6-amd64-di is NEW.
binary:usb-storage-modules-6.0.0-6-amd64-di is NEW.
binary:xfs-modules-6.0.0-6-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_6.0.12+1_source.changes

2022-12-09 Thread Debian FTP Masters
linux-signed-amd64_6.0.12+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-amd64_6.0.12+1.dsc
  linux-signed-amd64_6.0.12+1.tar.xz

Greetings,

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



linux-signed-amd64_6.1~rc8+1~exp1_source.changes ACCEPTED into experimental

2022-12-09 Thread 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 08:20:09 +0100
Source: linux-signed-amd64
Architecture: source
Version: 6.1~rc8+1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-amd64 (6.1~rc8+1~exp1) experimental; urgency=medium
 .
   * Sign kernel from linux 6.1~rc8-1~exp1
 .
   * New upstream release candidate.
 .
   [ Bastian Blank ]
   * Generate calls into rules.real for setup targets.
   * Simplify source rules generation.
   * Generate calls into rules.real for extra.
   * Remove remaining old targets in rules.real.
 .
   [ Salvatore Bonaccorso ]
   * lockdown: Correct mentioning of mode when LOCK_DOWN_IN_EFI_SECURE_BOOT is
 enabled (Closes: #1025417)
Checksums-Sha1:
 f8a5a680f669ba21e31c5a6e1220ed46a1e4108e 8415 
linux-signed-amd64_6.1~rc8+1~exp1.dsc
 343b1669b04234da6735485a399f908e2a90fae7 2945988 
linux-signed-amd64_6.1~rc8+1~exp1.tar.xz
Checksums-Sha256:
 6146c54fbadb7546a1b8eaccd1202d52838a20f4df915036288e175bdc698c21 8415 
linux-signed-amd64_6.1~rc8+1~exp1.dsc
 9b6c3fa5012b98130644fc28318b51b7195c6609988a56a989e80f90c6358a33 2945988 
linux-signed-amd64_6.1~rc8+1~exp1.tar.xz
Files:
 d3c0aa6e2601ef8a37dd4969fe15706f 8415 kernel optional 
linux-signed-amd64_6.1~rc8+1~exp1.dsc
 79f4f163c72ccc716f302aea954072c5 2945988 kernel optional 
linux-signed-amd64_6.1~rc8+1~exp1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmOTnGsACgkQi0FRiLdO
Nza2EA/9FOYCSDF0Y0GJA9NEuvIZ0rlXg7okepiD3yMEFaG2GyOaNP0eS2N0mzka
8C3kN49m+j+X+xbsPmhWy0N5Q9Ku/yF0tAxDIjDkBBvdAs06cosZOTAU0WULm5AH
tNHpWwAhY7+0y4H6oCG3gjeLOq4V8Vq9t6NgciBT0yBFUkHroaPex02KZqWCOncr
0s9xH+F1u6yQVOQ6O9DbI9wb8CJixrC2JlT75XvZot5R11PEfNUCTaQ9OXUI7tlu
p0baRnWrDGTO8S6Pam1U7U1aIeevtbXLSS20GK5eXftdr4UCwUCuacZWNPjj2ARE
J8EBZjN5T2w3C2ZjIcXZTL0Ih5zFgANAK721wPEqspGzsmZhqQD6wvU4wSGct8+V
CXN2yQzt+qjAYujudwECaz/yWpjoFZLueqN5j4/3fHz+wGadkrOQm0Uqh8XZb643
+t1/ha9U1t5b1AgzPtsuDfHRNCxcIBhy9FWy4no1OdhWbVGx1fDEGlwmaORRKDCG
VFZkLCC9Gr8zrMgZjVBfplQdZzlfynEVPuqLU6ydl9udNf0ZTwQG4w1fiFaXD70a
OfL5kk+3z1BE3Fa+VCtgB4nKKWm0kfTexg2kcLVH5o/zuYzJqe8bTRf//abkimHO
aDuTCol08y+FHZGhIkJj9may7lyCotPgHbhw94avMV4VRVdgsQg=
=hPZP
-END PGP SIGNATURE-



Bug#1025537: nfsd: Kernel Oops while serving NFS

2022-12-09 Thread Salvatore Bonaccorso
Hi Olivier,

On Tue, Dec 06, 2022 at 10:54:31PM +1100, Olivier Mehani wrote:
> Package: src:linux
> Version: 6.0.10-1
> Severity: important
> File: nfsd
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
> 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?

Regards,
Salvatore



Processed: retitle 1017760 to linux: possible data corruption on microSD card, might be the hardware though?

2022-12-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 1017760 linux: possible data corruption on microSD card, might be the 
> hardware though?
Bug #1017760 [src:linux] linux-image-5.10.0-17-amd64: No space for directory 
leaf checksum. Please run e2fsck -D.
Changed Bug title to 'linux: possible data corruption on microSD card, might be 
the hardware though?' from 'linux-image-5.10.0-17-amd64: No space for directory 
leaf checksum. Please run e2fsck -D.'.
> thanks
Stopping processing here.

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



Processing of linux-signed-amd64_6.1~rc8+1~exp1_source.changes

2022-12-09 Thread Debian FTP Masters
linux-signed-amd64_6.1~rc8+1~exp1_source.changes uploaded successfully to 
localhost
along with the files:
  linux-signed-amd64_6.1~rc8+1~exp1.dsc
  linux-signed-amd64_6.1~rc8+1~exp1.tar.xz

Greetings,

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



linux_5.10.158-1_source.changes ACCEPTED into proposed-updates

2022-12-09 Thread 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
Architecture: source
Version: 5.10.158-1
Distribution: bullseye
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1022806 1024697
Changes:
 linux (5.10.158-1) bullseye; urgency=medium
 .
   * 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 interlacing
 - drm/nouveau: fix a use-after-free in 

Bug#989040: marked as done (linux-image-5.10.0-6-amd64: Missing CONFIG_AMD_MEM_ENCRYPT in kernel config makes SEV booting impossible)

2022-12-09 Thread Debian Bug Tracking System
Your message dated Fri, 09 Dec 2022 19:32:08 +
with message-id 
and subject line Bug#1024697: fixed in linux 5.10.158-1
has caused the Debian Bug report #1024697,
regarding linux-image-5.10.0-6-amd64: Missing CONFIG_AMD_MEM_ENCRYPT in kernel 
config makes SEV booting impossible
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.)


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

Package: src:linux
Version: 5.10.28-1
Severity: important

Dear Kernel team,

As previously reported in bug #959069 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959069) for kernel 
5.5.0-2, the config parameter CONFIG_AMD_MEM_ENCRYPT is missing and, 
hence, booting an Debian Buster image in a SEV enabled VM is impossible.


No log may be provided as GRUB2 simply returns to the menu upon trying 
to boot the kernel.


Compilation of the kernel currently present in the testing pocket with 
this option enabled allows the kernel to boot normally.


Please include this kernel parameter so Debian Buster may be booted out 
of the box in a SEV enabled VM.


Kind regards,

...Louis Bouchard

-- Package-specific info:
** Version:
Linux version 5.10.0-6-amd64 (debian-kernel@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 
2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09)


** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-6-amd64 
root=UUID=2a32edc5-aef2-4dcc-93ee-9cd605341279 ro console=tty0 
console=ttyS0,115200 earlyprintk=ttyS0,115200 scsi_mod.use_blk_mq=Y


** Not tainted

** Kernel log:
[1.157475] virtio_net virtio0 enp0s1: renamed from eth0
[1.160360] ahci :00:1f.2: version 3.0
[1.161125] ahci :00:1f.2: AHCI 0001. 32 slots 6 ports 1.5 
Gbps 0x3f impl SATA mode

[1.162382] ahci :00:1f.2: flags: 64bit ncq only
[1.164175] scsi host1: ahci
[1.164778] scsi host2: ahci
[1.165438] scsi host3: ahci
[1.166113] scsi host4: ahci
[1.166971] scsi host5: ahci
[1.167592] scsi host6: ahci
[1.168067] ata1: SATA max UDMA/133 abar m4096@0x9000 port 
0x9100 irq 31
[1.169210] ata2: SATA max UDMA/133 abar m4096@0x9000 port 
0x9180 irq 31
[1.170158] ata3: SATA max UDMA/133 abar m4096@0x9000 port 
0x9200 irq 31
[1.170983] ata4: SATA max UDMA/133 abar m4096@0x9000 port 
0x9280 irq 31
[1.171765] ata5: SATA max UDMA/133 abar m4096@0x9000 port 
0x9300 irq 31
[1.172612] ata6: SATA max UDMA/133 abar m4096@0x9000 port 
0x9380 irq 31

[1.180922] sd 0:0:0:0: Power-on or device reset occurred
[1.182051] sd 0:0:0:0: [sda] 19531250 512-byte logical blocks: (10.0 
GB/9.31 GiB)

[1.182860] sd 0:0:0:0: [sda] 4096-byte physical blocks
[1.183439] sd 0:0:0:0: [sda] Write Protect is off
[1.183945] sd 0:0:0:0: [sda] Mode Sense: 63 00 00 08
[1.183988] sd 0:0:0:0: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA

[1.185019] sd 0:0:0:0: [sda] Optimal transfer size 4194304 bytes
[1.217913]  sda: sda1 sda14 sda15
[1.219876] sd 0:0:0:0: [sda] Attached SCSI disk
[1.485700] ata2: SATA link down (SStatus 0 SControl 300)
[1.487349] ata3: SATA link down (SStatus 0 SControl 300)
[1.488903] ata5: SATA link down (SStatus 0 SControl 300)
[1.490509] ata6: SATA link down (SStatus 0 SControl 300)
[1.492179] ata4: SATA link down (SStatus 0 SControl 300)
[1.493897] ata1: SATA link down (SStatus 0 SControl 300)
[1.671112] EXT4-fs (sda1): mounted filesystem with ordered data 
mode. Opts: (null)
[1.760312] Not activating Mandatory Access Control as 
/sbin/tomoyo-init does not exist.

[1.966827] systemd[1]: Inserted module 'autofs4'
[2.018048] systemd[1]: systemd 241 running in system mode. (+PAM 
+AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN 
-PCRE2 default-hierarchy=hybrid)

[2.023560] systemd[1]: Detected virtualization kvm.
[2.024855] systemd[1]: Detected architecture x86-64.
[2.044339] systemd[1]: Set hostname to .
[2.324858] systemd[1]: Reached target Remote File Systems.
[2.327595] systemd[1]: Started Forward Password Requests to Wall 
Directory Watch.

[2.331404] systemd[1]: Reached target System Time Synchronized.
[2.334587] systemd[1]: Listening on udev Kernel Socket.
[2.337157] systemd[1]: Listening on Journal Socket (/dev/log).
[2.340047] systemd[1]: Created slice system-getty.slice.
[2.396217] 

Bug#987607: marked as done (linux-image-5.10.0-5-cloud-amd64: Configure SEV-enabled Debian 11 release)

2022-12-09 Thread Debian Bug Tracking System
Your message dated Fri, 09 Dec 2022 19:32:08 +
with message-id 
and subject line Bug#1024697: fixed in linux 5.10.158-1
has caused the Debian Bug report #1024697,
regarding linux-image-5.10.0-5-cloud-amd64: Configure SEV-enabled Debian 11 
release
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.)


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

Dear Maintainer,

This is to request Debian 11 releases with SEV support enabled.

SEV support can be configured with:

CONFIG_AMD_MEM_ENCRYPT=y

Thanks
Peter


-- System Information:
Sent from non Debian system.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10.158-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Dec 2022 18:14:20 +0100
Source: linux
Architecture: source
Version: 5.10.158-1
Distribution: bullseye
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1022806 1024697
Changes:
 linux (5.10.158-1) bullseye; urgency=medium
 .
   * 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 

Bug#983586: marked as done (linux-image-5.10.0-3-amd64: Please configure kernel with CONFIG_AMD_MEM_ENCRYPT=y)

2022-12-09 Thread Debian Bug Tracking System
Your message dated Fri, 09 Dec 2022 19:32:08 +
with message-id 
and subject line Bug#1024697: fixed in linux 5.10.158-1
has caused the Debian Bug report #1024697,
regarding linux-image-5.10.0-3-amd64: Please configure kernel with 
CONFIG_AMD_MEM_ENCRYPT=y
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Dear Maintainer,

please consider to set the Linux kernel option "CONFIG_AMD_MEM_ENCRYPT=y".

Without that option it is not possible to enable the memory encryption for AMD
Secure Memory Encryption (SME).

Thank you very much.

With kind regards
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10.158-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Dec 2022 18:14:20 +0100
Source: linux
Architecture: source
Version: 5.10.158-1
Distribution: bullseye
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1022806 1024697
Changes:
 linux (5.10.158-1) bullseye; urgency=medium
 .
   * 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: 

Bug#959069: marked as done (linux-image-5.5.0-2-amd64 won't boot in a AMD SEV Virtual Machine)

2022-12-09 Thread Debian Bug Tracking System
Your message dated Fri, 09 Dec 2022 19:32:08 +
with message-id 
and subject line Bug#1024697: fixed in linux 5.10.158-1
has caused the Debian Bug report #1024697,
regarding linux-image-5.5.0-2-amd64 won't boot in a AMD SEV Virtual Machine
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.)


-- 
1024697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: linux-image-5.5.0-2-amd64 won't boot in a AMD SEV Virtual Machine
Package: src:linux
Version: 5.5.17-1
Severity: important

The boot failure is total: not even a console log can be seen, and
seems to be due to the necessary memory encryption option not being set
in the debian kernel: 

# CONFIG_AMD_MEM_ENCRYPT is not set

In spite of the fact that the rest of the SEV encryption variables are
set:

CONFIG_KVM_AMD_SEV=y
CONFIG_USB_SEVSEG=m

So I'm reporting this on the assumption that it is supposed to work out
of the box and not setting AMD_MEM_ENCRYPT was an oversight.  Not
setting this means that all the I/O devices are sending encrypted
memory pages through to QEMU which is what's causing the hang.  With
this set, the kernel would bounce all the encrypted pages into
unencrypted pages before sending them to devices.

James
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10.158-1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Dec 2022 18:14:20 +0100
Source: linux
Architecture: source
Version: 5.10.158-1
Distribution: bullseye
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1022806 1024697
Changes:
 linux (5.10.158-1) bullseye; urgency=medium
 .
   * 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 

Bug#1024697: marked as done (linux-image-5.10.0-19-cloud-amd64: Please backport fix for Bug #989040 : Missing CONFIG_AMD_MEM_ENCRYPT in kernel)

2022-12-09 Thread Debian Bug Tracking System
Your message dated Fri, 09 Dec 2022 19:32:08 +
with message-id 
and subject line Bug#1024697: fixed in linux 5.10.158-1
has caused the Debian Bug report #1024697,
regarding linux-image-5.10.0-19-cloud-amd64: Please backport fix for Bug 
#989040 : Missing CONFIG_AMD_MEM_ENCRYPT in kernel
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.)


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

Package: src:linux
Version: 5.10.149-2
Severity: important
X-Debbugs-Cc: lbouch...@scaleway.com

Dear Kernel team,

A fix for bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989040 
is included in kernel 5.13 but still not available for the stable kernel.


Could you please backport the fix for that bug into the stable 5.10 
kernel so it becomes available in a standard Debian Bullseye 
installation. Without this fix, Debian Bullseye is unbootable in

a virtual machine which uses Secure Enhanced Virtualization (SEV).

The fix is the enablement of the CONFIG_AMD_MEM_ENCRYPT configuration 
option.


Kind regards,

... Louis Bouchard


-- Package-specific info:
** Version:
Linux version 5.10.0-19-cloud-amd64 (debian-kernel@lists.debian.org) 
(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for 
Debian) 2.35.2) #1 SMP Debian 5.10.149-2 (2022-10-21)


** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-cloud-amd64 
root=UUID=25db7b8b-fbf8-47bd-b3c6-21fcf4de5f22 ro console=tty0 
console=ttyS0,115200 earlyprintk=ttyS0,115200 consoleblank=0


** Not tainted

** Kernel log:
[1.808563] systemd[1]: Created slice system-systemd\x2dgrowfs.slice.
[1.810794] systemd[1]: Created slice User and Session Slice.
[1.812361] systemd[1]: Started Dispatch Password Requests to Console 
Directory Watch.
[1.814189] systemd[1]: Started Forward Password Requests to Wall 
Directory Watch.
[1.816108] systemd[1]: Set up automount Arbitrary Executable File 
Formats File System Automount Point.

[1.818610] systemd[1]: Reached target Local Encrypted Volumes.
[1.820342] systemd[1]: Reached target Paths.
[1.821643] systemd[1]: Reached target Remote File Systems.
[1.823172] systemd[1]: Reached target Slices.
[1.824216] systemd[1]: Reached target Swap.
[1.825333] systemd[1]: Reached target System Time Set.
[1.826843] systemd[1]: Listening on Syslog Socket.
[1.827821] systemd[1]: Listening on fsck to fsckd communication Socket.
[1.829095] systemd[1]: Listening on initctl Compatibility Named Pipe.
[1.830420] systemd[1]: Listening on Journal Audit Socket.
[1.831536] systemd[1]: Listening on Journal Socket (/dev/log).
[1.832700] systemd[1]: Listening on Journal Socket.
[1.833727] systemd[1]: Listening on udev Control Socket.
[1.834743] systemd[1]: Listening on udev Kernel Socket.
[1.836088] systemd[1]: Mounting Huge Pages File System...
[1.837358] systemd[1]: Mounting POSIX Message Queue File System...
[1.838852] systemd[1]: Mounting Kernel Debug File System...
[1.840422] systemd[1]: Mounting Kernel Trace File System...
[1.841929] systemd[1]: Starting Create list of static device nodes 
for the current kernel...

[1.843833] systemd[1]: Starting Load Kernel Module configfs...
[1.845439] systemd[1]: Starting Load Kernel Module drm...
[1.846871] systemd[1]: Starting Load Kernel Module fuse...
[1.848423] systemd[1]: Started Nameserver information manager.
[1.851234] systemd[1]: Condition check resulted in Set Up Additional 
Binary Formats being skipped.
[1.852026] systemd[1]: Condition check resulted in File System Check 
on Root Device being skipped.

[1.853998] systemd[1]: Starting Journal Service...
[1.856523] systemd[1]: Starting Load Kernel Modules...
[1.858154] systemd[1]: Starting Remount Root and Kernel File Systems...
[1.859700] fuse: init (API version 7.32)
[1.859981] systemd[1]: Starting Coldplug All udev Devices...
[1.862214] systemd[1]: Mounted Huge Pages File System.
[1.863194] systemd[1]: Mounted POSIX Message Queue File System.
[1.864151] systemd[1]: Mounted Kernel Debug File System.
[1.865057] systemd[1]: Mounted Kernel Trace File System.
[1.866053] systemd[1]: Finished Create list of static device nodes 
for the current kernel.

[1.867461] systemd[1]: modprobe@configfs.service: Succeeded.
[1.868030] systemd[1]: Finished Load Kernel Module configfs.
[1.869046] systemd[1]: modprobe@drm.service: Succeeded.
[1.869620] systemd[1]: Finished Load Kernel Module drm.
[1.870609] 

Bug#1022806: marked as done (linux-image-5.10.0-19-amd64: amggpu unbootable problem persists)

2022-12-09 Thread Debian Bug Tracking System
Your message dated Fri, 09 Dec 2022 19:32:08 +
with message-id 
and subject line Bug#1022806: fixed in linux 5.10.158-1
has caused the Debian Bug report #1022806,
regarding linux-image-5.10.0-19-amd64: amggpu unbootable problem persists
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.)


-- 
1022806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.10.149-2
Severity: serious
Justification: 1022025, 1022051, 1022062, 1022070, 1022097, 1022147 marked 
serious so this marked serious too

Dear Maintainer,

Following other reports of post-grub kernel hangs on systems with
amdgpu, I waited for new release of linux-image-5.10.0-19-amd64,
which came quickly, but it did not solve the problem for me.

Symptoms are: grub loads kernel and a few seconds into the 
scrolling messages from the kernel the system hangs. The screen
is blank. The system is not accessible over the network.

I reverted to linux-image-5.10.0-18-amd64 and all is okay again.

The crash happens pretty early on: I believe X has not yet tried
to start. Both /var/log/syslog and /var/log/messages contain
no entries pertaining to the hanging boot (only messages from
where the earlier shutdown of 18 and the later start of 18).

Output from lscpu is below.

Automatically included output (e.g. kernel version) pertains
to linux-image-5.10.0-18-amd64, as I am unable to boot
linux-image-5.10.0-19-amd64.  I don't remove it in case it contains
other pertinent information.

I'm happy to test with other kernels or provide any requested
files/output.

Alexis

sugo# lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   48 bits physical, 48 bits virtual
CPU(s):  2
On-line CPU(s) list: 0,1
Thread(s) per core:  1
Core(s) per socket:  2
Socket(s):   1
NUMA node(s):1
Vendor ID:   AuthenticAMD
CPU family:  21
Model:   112
Model name:  AMD A9-9425 RADEON R5, 5 COMPUTE CORES 2C+3G
Stepping:0
Frequency boost: enabled
CPU MHz: 1396.583
CPU max MHz: 3100.
CPU min MHz: 1400.
BogoMIPS:6187.95
Virtualization:  AMD-V
L1d cache:   64 KiB
L1i cache:   128 KiB
L2 cache:2 MiB
NUMA node0 CPU(s):   0,1
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf:  Not affected
Vulnerability Mds:   Not affected
Vulnerability Meltdown:  Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:  Mitigation; untrained return thunk; SMT 
disabled
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled 
via prctl and seccomp
Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
Vulnerability Spectre v2:Mitigation; Retpolines, IBPB conditional, 
STIBP disabled, RSB filling, PBRSB-eIBRS Not affecte
 d
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort:   Not affected
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush mmx fxsr sse s
 se2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonst
 op_tsc cpuid extd_apicid aperfmperf pni 
pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe p
 opcnt aes xsave avx f16c lahf_lm cmp_legacy 
svm extapic cr8_legacy abm sse4a misalignsse 3dnow
 prefetch osvw ibs xop skinit wdt lwp fma4 tce 
nodeid_msr tbm perfctr_core perfctr_nb bpext pts
 c mwaitx cpb hw_pstate ssbd ibpb vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv s
 vm_lock nrip_save tsc_scale vmcb_clean 
flushbyasid decodeassists pausefilter pfthreshold avic 
 v_vmsave_vmload vgif overflow_recov
sugo# 



-- Package-specific info:
** Kernel log: boot messages should be attached


** Model information
sys_vendor: HP
product_name: HP Slim 

Bug#993290: please provide bridge-utils- compatible /etc/network/if-up-d/ script for ifupdown

2022-12-09 Thread Andreas Henriksson
Hello Michail Tokarev,

Late followup, but here's my personal opinion for the sake of having a
discussion which you asked for.
(JFTR I'm not maintaining this package and my opinion might have 0 value
on this topic.)

On Mon, Aug 30, 2021 at 12:23:09PM +0300, Michael Tokarev wrote:
> Source: iproute2
> Severity: normal
> 
> iproute2 package contains bridge control utility for a long time
> (maybe since the beginning). It is superior to brctl utility which
> is traditionally used to setup bridges on linux.
> 
> It is more: these days, bridges are often used with virtual machines,
> and there, iproute's bridge is *significantly* better when used
> together with vlan tagging, since bridge code in linux can deal with
> per-port vlan settings internally and hence we only require single
> bridge with everything, compared with a bridge for each vlan as with
> bridge-utils.

The iproute2 collection is generally where to look for utilities
that use modern kernel interfaces for networking, rather than old
tools using old/obsolete ioctl interfaces that exists for backwards
compatibility (and often can not represent the real running configuration).

> 
> By providing bridge functionality in the iproute package we'll eliminate
> bridge-utils dependency altogether.
> 
> And since ip utility can deal with vlans too, while at it we can absorb
> vlan package functionality too.

I think vlan package is a good example. The content of the package got
replaced by a script that simply gives existing users a migration path
*without* adding legacy burden on iproute2!

And speaking as a former iproute2 package maintainer and uploader of
vlan 2.0, the last part was equally important to me! :)

I think bridge-utils should follow the same path as vlan:
By having a new version that provides an upgrade path for existing
users without burdening others who never installed the legacy tools
with legacy migration cruft.

> 
> It is interesting that so far this hasn't been done. We switched to
> iproute-based bridging several years ago and it was a real game-change
> for us.
> 
> I have a script to set up bridges using ip utility (including per-port
> vlan settings), which looks like this in network/interfaces
> (a bit modified real example):
> 
> --- cut ---
> # this is the bridge interface:
> auto brf
> iface brf inet manual
>  bridge-vids 3 5 8 9 14
>  bridge-ports tls-eth
>  bridge-fd 5
>  bridge-maxwait 0
> 
> # this is the physical interface which is part of the bridge
> auto tls-eth
> iface tls-eth inet manual
>  # the same as for brf but tag14 is internal to the host
>  bridge-vids 3 5 8 9
> 
> # this is actual host's interface in vlan 1
> auto tls-mother
> iface tls-mother inet static
>  vlan 3@brf
>  address 192.168.177.15/26
>  gateway 192.168.177.5
> 
> # other interfaces for virtual machines etc
> --- cut ---
> 
> The "vlan" works both in bridge mode and with regular interfaces.
> 
> But I'd love to have some discussion about how the setup should look like
> before sending the actual script.

If my previous comments wheren't already spicy enough, here's a hot
take: I consider ifupdown itself to belong on the pile of legacy cruft.

> 
> Also I'm a bit unsure - if this functionality is to be merged into
> /etc/network/if-pre-up.d/iproute2, how can we disable the same
> functionality in if-pre-up.d/bridge-utils?

Additionally iproute2 is low-level tools, ifupdown uses it as an
implementation detail. Having iproute2 provide ifupdown glue just
creates a confusing circular relationship. If you want ifupdown to
use more of iproute2, then I say implement it in ifupdown!

> 
> Thanks!
> 
> /mjt
> 

Hope that my comments where not too spicy and hopefully some food for
though.

(If it wasn't already obvious: My suggestion is to tags +wontfix this
bug report on the iproute2 side.)

Regards,
Andreas Henriksson



linux_5.10.158-1_source.changes is NEW

2022-12-09 Thread Debian FTP Masters
Mapping bullseye to stable.
Mapping stable to proposed-updates.
binary:affs-modules-5.10.0-20-4kc-malta-di is NEW.
binary:affs-modules-5.10.0-20-5kc-malta-di is NEW.
binary:affs-modules-5.10.0-20-loongson-3-di is NEW.
binary:affs-modules-5.10.0-20-octeon-di is NEW.
binary:ata-modules-5.10.0-20-4kc-malta-di is NEW.
binary:ata-modules-5.10.0-20-5kc-malta-di is NEW.
binary:ata-modules-5.10.0-20-armmp-di is NEW.
binary:ata-modules-5.10.0-20-loongson-3-di is NEW.
binary:ata-modules-5.10.0-20-powerpc64le-di is NEW.
binary:btrfs-modules-5.10.0-20-4kc-malta-di is NEW.
binary:btrfs-modules-5.10.0-20-5kc-malta-di is NEW.
binary:btrfs-modules-5.10.0-20-armmp-di is NEW.
binary:btrfs-modules-5.10.0-20-loongson-3-di is NEW.
binary:btrfs-modules-5.10.0-20-marvell-di is NEW.
binary:btrfs-modules-5.10.0-20-octeon-di is NEW.
binary:btrfs-modules-5.10.0-20-powerpc64le-di is NEW.
binary:btrfs-modules-5.10.0-20-s390x-di is NEW.
binary:cdrom-core-modules-5.10.0-20-4kc-malta-di is NEW.
binary:cdrom-core-modules-5.10.0-20-5kc-malta-di is NEW.
binary:cdrom-core-modules-5.10.0-20-armmp-di is NEW.
binary:cdrom-core-modules-5.10.0-20-loongson-3-di is NEW.
binary:cdrom-core-modules-5.10.0-20-marvell-di is NEW.
binary:cdrom-core-modules-5.10.0-20-octeon-di is NEW.
binary:cdrom-core-modules-5.10.0-20-powerpc64le-di is NEW.
binary:cdrom-core-modules-5.10.0-20-s390x-di is NEW.
binary:crc-modules-5.10.0-20-4kc-malta-di is NEW.
binary:crc-modules-5.10.0-20-5kc-malta-di is NEW.
binary:crc-modules-5.10.0-20-armmp-di is NEW.
binary:crc-modules-5.10.0-20-loongson-3-di is NEW.
binary:crc-modules-5.10.0-20-marvell-di is NEW.
binary:crc-modules-5.10.0-20-octeon-di is NEW.
binary:crc-modules-5.10.0-20-powerpc64le-di is NEW.
binary:crc-modules-5.10.0-20-s390x-di is NEW.
binary:crypto-dm-modules-5.10.0-20-4kc-malta-di is NEW.
binary:crypto-dm-modules-5.10.0-20-5kc-malta-di is NEW.
binary:crypto-dm-modules-5.10.0-20-armmp-di is NEW.
binary:crypto-dm-modules-5.10.0-20-loongson-3-di is NEW.
binary:crypto-dm-modules-5.10.0-20-marvell-di is NEW.
binary:crypto-dm-modules-5.10.0-20-octeon-di is NEW.
binary:crypto-dm-modules-5.10.0-20-powerpc64le-di is NEW.
binary:crypto-dm-modules-5.10.0-20-s390x-di is NEW.
binary:crypto-modules-5.10.0-20-4kc-malta-di is NEW.
binary:crypto-modules-5.10.0-20-5kc-malta-di is NEW.
binary:crypto-modules-5.10.0-20-armmp-di is NEW.
binary:crypto-modules-5.10.0-20-loongson-3-di is NEW.
binary:crypto-modules-5.10.0-20-marvell-di is NEW.
binary:crypto-modules-5.10.0-20-octeon-di is NEW.
binary:crypto-modules-5.10.0-20-powerpc64le-di is NEW.
binary:crypto-modules-5.10.0-20-s390x-di is NEW.
binary:dasd-extra-modules-5.10.0-20-s390x-di is NEW.
binary:dasd-modules-5.10.0-20-s390x-di is NEW.
binary:efi-modules-5.10.0-20-armmp-di is NEW.
binary:event-modules-5.10.0-20-4kc-malta-di is NEW.
binary:event-modules-5.10.0-20-5kc-malta-di is NEW.
binary:event-modules-5.10.0-20-armmp-di is NEW.
binary:event-modules-5.10.0-20-loongson-3-di is NEW.
binary:event-modules-5.10.0-20-marvell-di is NEW.
binary:event-modules-5.10.0-20-octeon-di is NEW.
binary:event-modules-5.10.0-20-powerpc64le-di is NEW.
binary:ext4-modules-5.10.0-20-4kc-malta-di is NEW.
binary:ext4-modules-5.10.0-20-5kc-malta-di is NEW.
binary:ext4-modules-5.10.0-20-armmp-di is NEW.
binary:ext4-modules-5.10.0-20-loongson-3-di is NEW.
binary:ext4-modules-5.10.0-20-marvell-di is NEW.
binary:ext4-modules-5.10.0-20-octeon-di is NEW.
binary:ext4-modules-5.10.0-20-powerpc64le-di is NEW.
binary:ext4-modules-5.10.0-20-s390x-di is NEW.
binary:f2fs-modules-5.10.0-20-4kc-malta-di is NEW.
binary:f2fs-modules-5.10.0-20-5kc-malta-di is NEW.
binary:f2fs-modules-5.10.0-20-armmp-di is NEW.
binary:f2fs-modules-5.10.0-20-loongson-3-di is NEW.
binary:f2fs-modules-5.10.0-20-marvell-di is NEW.
binary:f2fs-modules-5.10.0-20-octeon-di is NEW.
binary:f2fs-modules-5.10.0-20-powerpc64le-di is NEW.
binary:f2fs-modules-5.10.0-20-s390x-di is NEW.
binary:fancontrol-modules-5.10.0-20-powerpc64le-di is NEW.
binary:fat-modules-5.10.0-20-4kc-malta-di is NEW.
binary:fat-modules-5.10.0-20-5kc-malta-di is NEW.
binary:fat-modules-5.10.0-20-armmp-di is NEW.
binary:fat-modules-5.10.0-20-loongson-3-di is NEW.
binary:fat-modules-5.10.0-20-marvell-di is NEW.
binary:fat-modules-5.10.0-20-octeon-di is NEW.
binary:fat-modules-5.10.0-20-powerpc64le-di is NEW.
binary:fat-modules-5.10.0-20-s390x-di is NEW.
binary:fb-modules-5.10.0-20-4kc-malta-di is NEW.
binary:fb-modules-5.10.0-20-5kc-malta-di is NEW.
binary:fb-modules-5.10.0-20-armmp-di is NEW.
binary:fb-modules-5.10.0-20-loongson-3-di is NEW.
binary:fb-modules-5.10.0-20-marvell-di is NEW.
binary:fb-modules-5.10.0-20-powerpc64le-di is NEW.
binary:firewire-core-modules-5.10.0-20-loongson-3-di is NEW.
binary:firewire-core-modules-5.10.0-20-powerpc64le-di is NEW.
binary:fuse-modules-5.10.0-20-4kc-malta-di is NEW.
binary:fuse-modules-5.10.0-20-5kc-malta-di is NEW.
binary:fuse-modules-5.10.0-20-armmp-di is NEW.
binary:fuse-modules-5.10.0-20-loongson-3-di is NEW.

Processing of linux_5.10.158-1_source.changes

2022-12-09 Thread Debian FTP Masters
linux_5.10.158-1_source.changes uploaded successfully to localhost
along with the files:
  linux_5.10.158-1.dsc
  linux_5.10.158.orig.tar.xz
  linux_5.10.158-1.debian.tar.xz
  linux_5.10.158-1_source.buildinfo

Greetings,

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



Bug#1014284: [kernel 5.18.5-1] [arm64 on Rock64 SBC]

2022-12-09 Thread Diederik de Haas
Control: tag -1 moreinfo

On Sunday, 3 July 2022 14:40:36 CET Jean-Marc LACROIX wrote:
> Package: linux-image-5.18.0-2-arm64
> Version:  5.18.5-1
> 
> Please find in  attached file success story  (!)   on recent boot  for
> target rock64 (pine64)  with 64 Go class10  MMC card with Debian  11.3
> Bullseye and Bookworm 5.18.5-1 kernel with following configuration ...

There is no attached file ... 

> ansible@hn-rock64-130:~$ uname -a
> Linux hn-rock64-130 5.18.0-2-arm64 #1 SMP Debian 5.18.5-1 (2022-06-16)
> aarch64 GNU/Linux
> ...
> ansible@hn-rock64-130:~$ cat
> /etc/apt/preferences.d/preferences_debian_v_11_bullseye* |grep -v "#"
> |grep -v ^$
> 
> Package: vmdb2
> Pin: release o=Debian,l=Debian,n=bullseye
> Pin-Priority: 920
> Package: *
> Pin: release o=Debian,l=Debian,n=bullseye/updates
> Pin-Priority: 500
> Package: *
> Pin: release o=Debian,l=Debian,n=bullseye-update
> Pin-Priority: 500
> Package: *
> Pin: release o=Debian,l=Debian,n=bullseye
> Pin-Priority: 500
> Package: *
> Pin: release o=Debian,l=Debian,n=bullseye-backports
> Pin-Priority: 100
> Package: *
> Pin: release o=Debian,l=Debian,n=buster
> Pin-Priority: 90
> Package: *
> Pin: release o=Debian,l=Debian,n=bookworm
> Pin-Priority: 80
> Package: *
> Pin: release o=Debian,l=Debian,n=sid
> Pin-Priority: 70
> Package: *
> Pin: release o=Debian,l=Debian,n=experimental
> Pin-Priority: 60
> Package: avahi-daemon
> Pin: release *
> Pin-Priority: -1
> Package: dbus
> Pin: release a=bullseye
> Pin-Priority: -1
> 
> Package: dhcpcd5
> Pin: release *
> Pin-Priority: -1
> Package: rtkit
> Pin: release *
> Pin-Priority: -1
> Package: systemd
> Pin: release *
> Pin-Priority: -1

This looks rather troublesome to me as you're combining oldstable/stable/
testing/unstable/experimental*, but AFAICT you're mostly running a Bullseye 
system and then using kernel 5.18.5-1 isn't the most logical choice.
If you want to try a newer kernel on a Bullseye system, using bullseye-
backports would be the most logical choice ...

*) I'm aware of how APT preferences work, so there's no need to explain that.
It's probably not relevant to this bug, but this is called a FrankenDebian:
https://wiki.debian.org/DontBreakDebian

> ... list of loaded kernel modules

> After installing kernel 5.18.0-2-arm64, the good  news is that the mmc
> device number now looks ALWAYS correct (!).  Previously, in the kernel
> (5.10.xx),   when booting   target,sometimes mmc  id   was  either
> /dev/mmcblk0 or /dev/mmcblk1 for unknown reasons (?).
> 
> Now either with a soft  reboot command (sudo reboot)  or with a forced
> shutdown (power ON/OFF), the identification is still good,i.e. /dev/mmcblk0.

Great.

> But [ref 1], there is still some stranges messages in dmesg ...

I'm guessing [ref 1] and [ref 2] were mentioned in the file which was NOT 
attached? The consequence is that I can't tell what the issue is what this bug 
is/should be about. Can you clarify?

> [7.585764] dwmmc_rockchip ff52.mmc: DW MMC controller at irq
> 40,32 bit host data width,256 deep fifo
> [7.586886] rockchip-pinctrl pinctrl: pin gpio0-2 already requested
> by vcc-host-5v-regulator; cannot claim for vcc-host1-5v-regulator
> [7.588110] rockchip-pinctrl pinctrl: pin-2 (vcc-host1-5v-regulator)
> status -22
> [7.588576] ehci-platform ff5c.usb: USB 2.0 started, EHCI 1.00
> [7.588797] rockchip-pinctrl pinctrl: could not request pin 2
> (gpio0-2) from group usb20-host-drv  on device rockchip-pinctrl
> [7.589899] usb usb1: New USB device found, idVendor=1d6b,
> idProduct=0002, bcdDevice= 5.18
> [7.590353] reg-fixed-voltage vcc-host1-5v-regulator: Error applying
> setting, reverse things back

Ideally these warnings should be resolved some time, but I'm seeing them too 
(I also have Rock64 devices), but AFAICT they're harmless.

> [7.694550] rk_gmac-dwmac ff54.ethernet: phy regulator is not
> available yet, deferred probing

The 'deferred probing' just means it will be tried again at a later point.
If ethernet would not work after it finished booting, that would be a problem, 
but I'm not aware that actually happens.

> As a result, it is not very clear for me why there is one warning
> message ([ref 2]) ?

Not having [ref 2] so I don't know which warning that is.
But as said earlier, there are several warnings (and maybe even errors) 
reported, but AFAIK they're harmless.

> Any ideas or suggestions will be appreciated (!)

If you could clearly state what issue/bug you encountered, that would help.
And while you're at it, please also try whether a more recent kernel may have 
already fixed the issue you tried to report.

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


Processed: Re: Bug#1014284: [kernel 5.18.5-1] [arm64 on Rock64 SBC]

2022-12-09 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 moreinfo
Bug #1014284 [src:linux] [kernel 5.18.5-1] [arm64 on Rock64 SBC]
Added tag(s) moreinfo.

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



linux_6.0.12-1_source.changes ACCEPTED into unstable

2022-12-09 Thread 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
Architecture: source
Version: 6.0.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux (6.0.12-1) unstable; urgency=medium
 .
   * 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_shutdown and iavf_remove
 - [armhf] dts: imx6q-prti6q: