Bug#895131: linux-perf: Add libopencsd support to perf
Package: src:linux Followup-For: Bug #895131 User: debian-sp...@lists.debian.org Usertags: sparc64 Hello! This change made src:linux BD-Uninstallable on sparc64 [1] as the package libopencsd doesn't build there [2]. Since this library is ARM-specific anyway, wouldn't it make more sense to have this build-dependency on ARM targets only? Thanks, Adrian > [1] https://buildd.debian.org/status/package.php?p=linux=sid > [2] https://buildd.debian.org/status/package.php?p=libopencsd=sid -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#850425: mpt3sas "swiotlb buffer is full" problem only under Xen
On 3/12/19 8:19 PM, Juergen Gross wrote: > On 12/03/2019 17:41, Hans van Kranenburg wrote: >> On 3/12/19 5:04 PM, Juergen Gross wrote: >>> On 11/03/2019 20:50, Hans van Kranenburg wrote: On 3/11/19 7:34 AM, Juergen Gross wrote: > > I'm not sure. Patch 3 of this series is basically already there (see > commit c6d4381220a0087ce19dbf6984d92c451bd6b364). So maybe all we need > is patch 4, which should really be easy to do? > > Hans, could you give it a try? You'd need to use a 4.20 kernel at least. > I can do the official patch posting in case you confirm it working. Ehm ok, well... This is interesting. I just built a 4.20.13 (without the patch), and I did it from the Debian kernel team repo, because then I just get all latest config options like I would get them in Debian. I rebooted the HP Z820 with it (with Xen 4.11) and I don't see any errors similar to the ones I pasted earlier. I haven't been running any domU on it yet (just installed it), but this is not what I expected. >>> >>> Well, commit c6d4381220a0087ce19dbf6984d92c451bd6b364 is part of a >>> rather large series making the dma interface cleaner and using it more >>> correctly where appropriate. Maybe your use case is covered by this >>> series already. >> >> It seems so. That's good, of course, but it also means that I cannot be >> of any use here any more to test the additional proposed change. ;] > > I don't think the change is needed any longer. > > Christoph's series was meant to fix stuff like that and it did that very > well. Clear. Then for 4.19 in Debian the workaround is documented in here. And if someone from the kernel team is reading along... Please mark as solved when >= 4.20 is uploaded to Debian unstable? Hans
Bug#923988: /boot/vmlinuz-4.19.0-2-arm64: dmidecode causes kernel panic (puma-rk3399)
On 3/12/19 9:57 PM, Ben Hutchings wrote: > On Tue, 2019-03-12 at 19:04 +0100, Christoph Müllner wrote: >> I've been able to reproduce and analyse this issue. >> >> The security error seems to be valid. > [...] > > I don't see a security issue here. The kernel does not and should not > stop root breaking the system with direct access to /dev/mem, *unless* > Secure Boot / lockdown is active - and in that case access to /dev/mem > is blocked completely. You are right. There is no security error. SError stands for system error.
Bug#923988: /boot/vmlinuz-4.19.0-2-arm64: dmidecode causes kernel panic (puma-rk3399)
On Tue, 2019-03-12 at 19:04 +0100, Christoph Müllner wrote: > I've been able to reproduce and analyse this issue. > > The security error seems to be valid. [...] I don't see a security issue here. The kernel does not and should not stop root breaking the system with direct access to /dev/mem, *unless* Secure Boot / lockdown is active - and in that case access to /dev/mem is blocked completely. Ben. -- Ben Hutchings Larkinson's Law: All laws are basically false. signature.asc Description: This is a digitally signed message part
Re: firmware-iwlwifi disable network-manager's root password requirement for every user
On Tue, 2019-03-12 at 15:13 +0100, cacquara...@gmail.com wrote: > Dear maintainers, > > this concerns : > > network-manager version 1.6.2-3+deb9u2 > network-manager-gnome version 1.4.4-1+deb9u1 > firmware-iwlwifi version 20161130-4 > gnome version 3.22.2 > Debian GNU/Linux version 9 (stretch) 64 bits > > ➤ I am writing to report this unsolicited behaviour: > > Steps: > > 1 - Fresh Debian with wired internet access > 2 - access to network settings require root password (this > is ok) That actually sounds like a bug. > 3 - install firmware-iwlwifi > 4 - access to network settings (LAN and Wi-Fi) do not > require password anymore, whatever user is logged in, even > after reboot. This is the behaviour I expect in GNOME. You would need to specifically configure it to prevent this. > 5 - uninstall firmware-iwlwifi restore root password > requirement. > > I've found no info about this behaviour in the documentation, > nor how to prevent this to happen without consent. > > ➤ I would like to know how to preserve or restore the primary > network-manager secure behaviour while having Wi-Fi functional. firmware-iwlwifi doesn't contain any code that would change the authentication configuration. Ben. -- Ben Hutchings Larkinson's Law: All laws are basically false. signature.asc Description: This is a digitally signed message part
Bug#924051: nfs-common: Krb5 NFSv4 Realmd AD nfsidmap files owned by nobody group 4294967294
I was able to find a solution to this issue that will require a patch/update to the libnfsidmap version 0.26. Please see reference to another user that experience the issue. https://lists.fedorahosted.org/archives/list/freeipa-us...@lists.fedorahosted.org/thread/SIA6J7IZRWX2FVGHKMS5F3HB7DE3MCFC/ I confirmed after custom compiling and using the newer lib's .so file that the naming convention was normal. One directory timed out when I did a chown but after fixing the file permissions to a user inside AD it seems to be working alright. Can you please patch libnfsidmap to use version 0.26 to fix this bug? Thanks! Michael Barkdoll
Bug#850425: mpt3sas "swiotlb buffer is full" problem only under Xen
On 12/03/2019 17:41, Hans van Kranenburg wrote: > On 3/12/19 5:04 PM, Juergen Gross wrote: >> On 11/03/2019 20:50, Hans van Kranenburg wrote: >>> On 3/11/19 7:34 AM, Juergen Gross wrote: I'm not sure. Patch 3 of this series is basically already there (see commit c6d4381220a0087ce19dbf6984d92c451bd6b364). So maybe all we need is patch 4, which should really be easy to do? Hans, could you give it a try? You'd need to use a 4.20 kernel at least. I can do the official patch posting in case you confirm it working. >>> >>> Ehm ok, well... This is interesting. >>> >>> I just built a 4.20.13 (without the patch), and I did it from the Debian >>> kernel team repo, because then I just get all latest config options like >>> I would get them in Debian. >>> >>> I rebooted the HP Z820 with it (with Xen 4.11) and I don't see any >>> errors similar to the ones I pasted earlier. >>> >>> I haven't been running any domU on it yet (just installed it), but this >>> is not what I expected. >> >> Well, commit c6d4381220a0087ce19dbf6984d92c451bd6b364 is part of a >> rather large series making the dma interface cleaner and using it more >> correctly where appropriate. Maybe your use case is covered by this >> series already. > > It seems so. That's good, of course, but it also means that I cannot be > of any use here any more to test the additional proposed change. ;] I don't think the change is needed any longer. Christoph's series was meant to fix stuff like that and it did that very well. Juergen
Bug#923988: /boot/vmlinuz-4.19.0-2-arm64: dmidecode causes kernel panic (puma-rk3399)
I've been able to reproduce and analyse this issue.
The security error seems to be valid.
What actually happens is, that dmidecode does the following (strace):
> openat(AT_FDCWD, "/dev/mem"
> , O_RDONLY) = 3
> fstat(3, {st_mode=S_IFCHR|0640, st_rdev=makedev(1, 1), ...}) = 0
> mmap(NULL, 65536, PROT_READ, MAP_SHARED, 3, 0xf) = 0x8777
> --- SIGBUS {si_signo=SIGBUS, si_code=BUS_OBJERR, si_addr=0x8777} ---
> +++ killed by SIGBUS +++
> Bus error
According to the dmidecode source code (dmidecode.c) this is some sort
of fallback mechanism for x86 and or x86_64. In any case that's not a valid
access on arm64.
I think this should not be done in dmidecode on non-x86 machines (maybe with
#ifdef __x86_64__ and friends).
> ...
> memory_scan:
>
> if
> (!(opt.flags & FLAG_QUIET))
> printf(
> "Scanning %s for entry point.\n"
> , opt.devmem);
> /* Fallback to memory scan (x86, x86_64) */
>
> if
> ((buf = mem_chunk(0xF, 0x1, opt.devmem)) == NULL)
> {
> ret = 1;
>
> goto
> exit_free;
> }
> ...
The reason why the fallback is executed is that the kernel does not find DMI
and reports this during bootup as:
> [0.353729] DMI not present or invalid.
This is caused by the fact that the bootloader (U-Boot) does not have
EFI support enabled and thus does not provide the DMI.
This is something we will address.
linux_4.19.28-1_multi.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Mar 2019 05:06:28 + Source: linux Binary: linux-doc-4.19 linux-headers-4.19.0-4-common linux-headers-4.19.0-4-common-rt linux-source-4.19 linux-support-4.19.0-4 lockdep Architecture: all source Version: 4.19.28-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 895131 913119 913138 921542 922182 922306 Description: linux-doc-4.19 - Linux kernel specific documentation for version 4.19 linux-headers-4.19.0-4-common - Common header files for Linux 4.19.0-4 linux-headers-4.19.0-4-common-rt - Common header files for Linux 4.19.0-4-rt linux-source-4.19 - Linux kernel source for version 4.19 with Debian patches linux-support-4.19.0-4 - Support files for Linux 4.19 lockdep- Runtime locking correctness validator Changes: linux (4.19.28-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.21 - devres: Align data[] to ARCH_KMALLOC_MINALIGN - drm/bufs: Fix Spectre v1 vulnerability - drm/vgem: Fix vgem_init to get drm device available. - [arm*] pinctrl: bcm2835: Use raw spinlock for RT compatibility - [x86] ASoC: Intel: mrfld: fix uninitialized variable access - gpiolib: Fix possible use after free on label - [armhf] drm/sun4i: Initialize registers in tcon-top driver - genirq/affinity: Spread IRQs to all available NUMA nodes - [armhf] gpu: ipu-v3: image-convert: Prevent race between run and unprepare - wil6210: fix reset flow for Talyn-mb - wil6210: fix memory leak in wil_find_tx_bcast_2 - ath10k: assign 'n_cipher_suites' for WCN3990 - ath9k: dynack: use authentication messages for 'late' ack - scsi: lpfc: Correct LCB RJT handling - scsi: mpt3sas: Call sas_remove_host before removing the target devices - scsi: lpfc: Fix LOGO/PLOGI handling when triggerd by ABTS Timeout event - [armhf] 8808/1: kexec:offline panic_smp_self_stop CPU - [mips] clk: boston: fix possible memory leak in clk_boston_setup() - dlm: Don't swamp the CPU with callbacks queued during recovery - [x86] PCI: Fix Broadcom CNB20LE unintended sign extension (redux) - [powerpc] pseries: add of_node_put() in dlpar_detach_node() - [arm*] drm/vc4: ->x_scaling[1] should never be set to VC4_SCALING_NONE - ptp: check gettime64 return code in PTP_SYS_OFFSET ioctl - [mips] Boston: Disable EG20T prefetch - iwlwifi: fw: do not set sgi bits for HE connection - fpga: altera-cvp: Fix registration for CvP incapable devices - [x86] fpga: altera-cvp: fix 'bad IO access' on x86_64 - [x86] vbox: fix link error with 'gcc -Og' - platform/chrome: don't report EC_MKBP_EVENT_SENSOR_FIFO as wakeup - i40e: prevent overlapping tx_timeout recover - scsi: hisi_sas: change the time of SAS SSP connection - usbnet: smsc95xx: fix rx packet alignment - [armhf,arm64] drm/rockchip: fix for mailbox read size - [arm*] OMAP2+: hwmod: Fix some section annotations - drm/amd/display: fix gamma not being applied correctly - drm/amd/display: calculate stream->phy_pix_clk before clock mapping - bpf: libbpf: retry map creation without the name - net/mlx5: EQ, Use the right place to store/read IRQ affinity hint - modpost: validate symbol names also in find_elf_symbol - perf tools: Add Hygon Dhyana support - [armhf] soc/tegra: Don't leak device tree node reference - media: rc: ensure close() is called on rc_unregister_device - media: video-i2c: avoid accessing released memory area when removing driver - [armhf] media: mtk-vcodec: Release device nodes in mtk_vcodec_init_enc_pm() - ptp: Fix pass zero to ERR_PTR() in ptp_clock_register - dmaengine: xilinx_dma: Remove __aligned attribute on zynqmp_dma_desc_ll - [powerpc] 32: Add .data..Lubsan_data*/.data..Lubsan_type* sections explicitly - media: adv*/tc358743/ths8200: fill in min width/height/pixelclock - ACPI: SPCR: Consider baud rate 0 as preconfigured state - f2fs: move dir data flush to write checkpoint process - f2fs: fix race between write_checkpoint and write_begin - f2fs: fix wrong return value of f2fs_acl_create - [arm64] io: Ensure calls to delay routines are ordered against prior readX() - net: aquantia: return 'err' if set MPI_DEINIT state fails - [sparc*] sunvdc: Do not spin in an infinite loop when vio_ldc_send() returns EAGAIN - nfsd4: fix crash on writing v4_end_grace before nfsd startup - drm: Clear state->acquire_ctx before leaving drm_atomic_helper_commit_duplicated_state() - [arm64] io: Ensure value passed to __iormb() is held in a 64-bit register - Thermal: do not clear passive state during system sleep - thermal: Fix locking in cooling device sysfs update
Bug#922182: marked as done (linux-image-4.19.0-2-cloud-amd64: Kernel call trace when testing NVME on Azure)
Your message dated Tue, 12 Mar 2019 18:00:11 + with message-id and subject line Bug#922182: fixed in linux 4.19.28-1 has caused the Debian Bug report #922182, regarding linux-image-4.19.0-2-cloud-amd64: Kernel call trace when testing NVME on Azure 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.) -- 922182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.16-1 Severity: normal The Azure team ran into the following call trace with the Debian 4.19 kernel while validating NVME devices on Microsoft Azure. The following call trace was observed while running fio on Standard_L64s_v2 size: [ 651.652598] rcu: INFO: rcu_sched self-detected stall on CPU [ 651.656617] rcu: 8-: (5250 ticks this GP) idle=4ce/1/0x4004 softirq=4630/4630 fqs=2527 [ 651.656617] rcu:(t=5256 jiffies g=69713 q=8089) [ 651.684600] Sending NMI from CPU 8 to CPUs 0: [ 651.694277] NMI backtrace for cpu 0 [ 651.694278] CPU: 0 PID: 10 Comm: ksoftirqd/0 Not tainted 4.19.0-0.bpo.1-cloud-amd64 #1 Debian 4.19.12-1~bpo9+1 [ 651.694279] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 05/18/2018 [ 651.694279] RIP: 0010:cpumask_next+0x16/0x20 [ 651.694281] Code: 38 22 75 97 eb d4 90 90 90 90 90 90 90 90 90 90 90 90 90 90 8d 57 01 48 89 f0 be 00 02 00 00 48 89 c7 48 63 d2 e8 2a 51 d8 ff c3 0f 1f 84 00 00 00 00 00 55 ba ff ff ff ff 53 48 89 fd 89 f3 [ 651.694282] RSP: 0018:9a6adf803ac0 EFLAGS: 0046 [ 651.694283] RAX: 0200 RBX: 0002 RCX: 0200 [ 651.694284] RDX: RSI: RDI: 9a6adf803b10 [ 651.694284] RBP: 9a6adf803b10 R08: R09: [ 651.694285] R10: 9a6adf803ad0 R11: R12: 00fd [ 651.694285] R13: 9a6adf803bc0 R14: 0046 R15: 000211c0 [ 651.694286] FS: () GS:9a6adf80() knlGS: [ 651.694286] CS: 0010 DS: ES: CR0: 80050033 [ 651.694286] CR2: 7f215b3d6220 CR3: 00307f486000 CR4: 003406b0 [ 651.694287] Call Trace: [ 651.694287] [ 651.694287] __send_ipi_mask+0x11e/0x310 [ 651.694288] __send_ipi_one+0x34/0x50 [ 651.694288] hv_send_ipi+0x10/0x30 [ 651.694288] check_preempt_curr+0x4e/0x90 [ 651.694289] ttwu_do_wakeup+0x19/0x140 [ 651.694289] try_to_wake_up+0x1ce/0x4a0 [ 651.694289] autoremove_wake_function+0x11/0x50 [ 651.694290] __wake_up_common+0x96/0x180 [ 651.694290] __wake_up_common_lock+0x7c/0xc0 [ 651.694290] aio_complete+0x17a/0x250 [ 651.694291] blkdev_bio_end_io+0x71/0x140 [ 651.694291] blk_update_request+0x91/0x2d0 [ 651.694291] blk_mq_end_request+0x1a/0xd0 [ 651.694292] nvme_irq+0x119/0x1d0 [nvme] [ 651.694293] __handle_irq_event_percpu+0x81/0x190 [ 651.694297] handle_irq_event_percpu+0x30/0x80 [ 651.694297] handle_irq_event+0x3c/0x60 [ 651.694298] handle_edge_irq+0x94/0x1f0 [ 651.694298] handle_irq+0x1f/0x30 [ 651.694298] do_IRQ+0x49/0xe0 [ 651.694299] common_interrupt+0xf/0xf We think this issue can be resolved with the following four upstream patches. I think these made it into the 4.20 kernel, but not 4.19: git cherry-pick 8ffe4e61c06a48324cfd97f1199bb9838acce2f2 git cherry-pick 76f99ae5b54d48430d1f0c5512a84da0ff9761e0 git cherry-pick b82592199032bf7c778f861b936287e37ebc9f62 git cherry-pick e8da8794a7fd9eef1ec9a07f0d4897c68581c72b -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-cloud-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-2-cloud-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133 ii kmod25-2 ii linux-base 4.5 Versions of packages linux-image-4.19.0-2-cloud-amd64 recommends: ii apparmor 2.13.2-7 ii firmware-linux-free 3.4 ii irqbalance 1.5.0-3 Versions of packages linux-image-4.19.0-2-cloud-amd64 suggests: pn debian-kernel-handbook ii grub-pc 2.02+dfsg1-10 pn linux-doc-4.19 Versions of packages
Bug#922306: marked as done (linux: btrfs corruption (compressed data + hole data))
Your message dated Tue, 12 Mar 2019 18:00:11 + with message-id and subject line Bug#922306: fixed in linux 4.19.28-1 has caused the Debian Bug report #922306, regarding linux: btrfs corruption (compressed data + hole data) 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.) -- 922306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 4.19.20-1 Severity: critical Tags: upstream patch Justification: causes serious data loss Hi. Apparently there was a longer existing data corruption bug in btrfs[0], AFAIU it happened when compression was used together with holes in data and there was *no* recognition by checksumming. Seems some movement got into this the last days and a patch[1] may have been found fixing the issue. Due to potential silent data corruptpion it makes perhaps sense to cherry pick that fix (maybe waiting for confirmation from upstream whether it's the final one) instead of waiting for it being released in some upcoming stable release? Cheers, Chris. [0] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85407.html [1] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg85492.html -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.28-1 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Mar 2019 05:06:28 + Source: linux Binary: linux-doc-4.19 linux-headers-4.19.0-4-common linux-headers-4.19.0-4-common-rt linux-source-4.19 linux-support-4.19.0-4 lockdep Architecture: all source Version: 4.19.28-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 895131 913119 913138 921542 922182 922306 Description: linux-doc-4.19 - Linux kernel specific documentation for version 4.19 linux-headers-4.19.0-4-common - Common header files for Linux 4.19.0-4 linux-headers-4.19.0-4-common-rt - Common header files for Linux 4.19.0-4-rt linux-source-4.19 - Linux kernel source for version 4.19 with Debian patches linux-support-4.19.0-4 - Support files for Linux 4.19 lockdep- Runtime locking correctness validator Changes: linux (4.19.28-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.21 - devres: Align data[] to ARCH_KMALLOC_MINALIGN - drm/bufs: Fix Spectre v1 vulnerability - drm/vgem: Fix vgem_init to get drm device available. - [arm*] pinctrl: bcm2835: Use raw spinlock for RT compatibility - [x86] ASoC: Intel: mrfld: fix uninitialized variable access - gpiolib: Fix possible use after free on label - [armhf] drm/sun4i: Initialize registers in tcon-top driver - genirq/affinity: Spread IRQs to all available NUMA nodes - [armhf] gpu: ipu-v3: image-convert: Prevent race between run and unprepare - wil6210: fix reset flow for Talyn-mb - wil6210: fix memory leak in wil_find_tx_bcast_2 - ath10k: assign 'n_cipher_suites' for WCN3990 - ath9k: dynack: use authentication messages for 'late' ack - scsi: lpfc: Correct LCB RJT handling - scsi: mpt3sas: Call sas_remove_host before removing the target devices - scsi: lpfc: Fix LOGO/PLOGI handling when triggerd by ABTS Timeout event - [armhf] 8808/1: kexec:offline panic_smp_self_stop CPU - [mips] clk: boston: fix possible memory leak in clk_boston_setup() - dlm: Don't swamp the CPU with
Bug#921542: marked as done (tc qdisc kernel crash)
Your message dated Tue, 12 Mar 2019 18:00:11 +
with message-id
and subject line Bug#921542: fixed in linux 4.19.28-1
has caused the Debian Bug report #921542,
regarding tc qdisc kernel crash
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.)
--
921542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.16-1
Severity: critical
When I'm trying to use this script:
#!/bin/bash
ifaces[0]="tun0"
ifaces[1]="ens192"
ifaceIn="ifb0"
ifaceOut="ifb1"
#echo ${#iface[@]}
#exit
tc qdisc del dev $ifaceIn root
for iface in ${ifaces[@]}; do
echo "Delete qdisc ingress on ${iface}"
tc qdisc del dev ${iface} handle : ingress
echo "Add qdisc ingress on ${iface}"
tc qdisc add dev ${iface} handle : ingress
#tc filter add dev ${iface} parent : protocol ip u32 match u32 0 0
action mirred egress redirect dev ${ifaceIn}
done
#tc qdisc add dev $ifaceIn root handle 1: prio bands 5
#tc qdisc add dev $ifaceIn parent 1:1 handle 10: sfq
#tc qdisc add dev $ifaceIn parent 1:2 handle 20: sfq
#tc qdisc add dev $ifaceIn parent 1:3 handle 30: sfq
#tc qdisc add dev $ifaceIn parent 1:4 handle 40: sfq
#tc qdisc add dev $ifaceIn parent 1:5 handle 50: sfq
### Create a root qdisc type DSmark
echo "Add qdisc root on ${ifaceIn} type DSmark"
tc qdisc add dev $ifaceIn handle 1:0 root dsmark indices 64 set_tc_index
### filter to copy the correct DS filed from the IP packet to skb->tc_index
echo "Add filter on parent 1:0 ${ifaceIn} for set the tcindex"
tc filter add dev $ifaceIn parent 1:0 protocol ip prio 1 tcindex mask 0xfc
shift 2
### Add a PRIO class with 5 bands on 1:0
echo "Add qdisc on parent 1:0 ${ifaceIn} as PRIO with 5 bands"
tc qdisc add dev $ifaceIn parent 1:0 handle 2:0 prio bands 5
### Add a qdisc on the leaf PRIO 2:1
#tc qdisc add dev $ifaceIn parent 2:1 tbf rate 1.5Mbit burst 1.5kB limit 1.6kB
echo "Add qdisc on leaf parent 2:1 ${ifaceIn} as SFQ"
tc qdisc add dev $ifaceIn parent 2:1 sfq
### Match the traffic with DSCP EF (ToS 0xb8 / DSCP 0x2e) mark
echo "Add filter on parent 2:0 ${ifaceIn} to match DSCP EF (ToS 0xb8 / DSCP
0x2e) mark and send the traffic to class 2:1"
tc filter add dev $ifaceIn parent 2:0 protocol ip prio 1 handle 0x2e tcindex
classid 2:1 pass_on
### Add a qdisck on leaf PRIO 2:2 - IPTV services
echo "Add qdisc on leaf parent 2:1 ${ifaceIn} as SFQ"
tc qdisc add dev $ifaceIn parent 2:2 sfq
### Match the traffic with DSCP AF41 (ToS 0x88 / DSCP 0x22) mark
echo "Add filter on parent 2:0 ${ifaceIn} to match DSCP AF41 (ToS 0x88 / DSCP
0x22 mark) and send the traffic to class 2:2"
tc filter add dev $ifaceIn parent 2:0 protocol ip prio 2 handle 0x22 tcindex
classid 2:2 pass_on
### Best Effort traffic move to 2:5
#BE class(2:2)
#tc qdisc add dev $ifaceIn parent 2:5 red limit 60KB min 15KB max 45KB burst 20
avpkt 1000 bandwidth 10Mbit probability 0.4
echo "Add qdisc on leaf parent 2:5 ${ifaceIn} as SFQ"
tc qdisc add dev $ifaceIn parent 2:5 sfq
echo "Add filter on parent 2:0 ${ifaceIn} to match DSCP BE (ToS 0x0 / DSCP 0x0
mark) and send the traffic to class 2:5"
tc filter add dev $ifaceIn parent 2:0 protocol ip prio 5 handle 0 tcindex mask
0 classid 2:5 pass_on
exit
And run it 2-3 times I'm getting a severe kernel crash:
Feb 6 17:15:34 Telenet-PC kernel: [ 511.608275] general protection fault:
[#1] SMP PTI
Feb 6 17:15:34 Telenet-PC kernel: [ 511.608279] CPU: 2 PID: 3889 Comm: tc Not
tainted 4.19.0-2-amd64 #1 Debian 4.19.16-1
Feb 6 17:15:34 Telenet-PC kernel: [ 511.608281] Hardware name: VMware, Inc.
VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 05/19/2017
Feb 6 17:15:34 Telenet-PC kernel: [ 511.608285] RIP:
0010:__kmalloc_node+0x195/0x2b0
Feb 6 17:15:34 Telenet-PC kernel: [ 511.608288] Code: fa 48 8b 74 24 08 e8 7a
54 7d 00 4c 8b 13 58 4d 85 d2 75 d7 e9 75 ff ff ff 41 8b 5a 20 49 8b 3a 48 8d
4a 01 4c 89 f8 4c 01 fb <48> 33 1b 49 33 9a 38 01 00 00 65 48 0f c7 0f 0f 94 c0
84 c0 0f 84
Feb 6 17:15:34 Telenet-PC kernel: [ 511.608289] RSP: 0018:b4ad4322b978
EFLAGS: 00010286
Feb 6 17:15:34 Telenet-PC kernel: [ 511.608291] RAX: d36cc438 RBX:
d36cc438 RCX: 0181
Feb 6 17:15:34 Telenet-PC kernel: [ 511.608292] RDX: 0180 RSI:
006012c0 RDI: 00025120
Feb 6 17:15:34 Telenet-PC kernel: [ 511.608294] RBP: 006012c0 R08:
984037ca5120 R09: 984037807900
Feb 6 17:15:34 Telenet-PC kernel: [ 511.608295] R10: 984037806a00 R11:
R12: 1c00
Feb 6
Bug#895131: marked as done (linux-perf: Add libopencsd support to perf)
Your message dated Tue, 12 Mar 2019 18:00:11 + with message-id and subject line Bug#895131: fixed in linux 4.19.28-1 has caused the Debian Bug report #895131, regarding linux-perf: Add libopencsd support to perf 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.) -- 895131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-perf-4.16 Version: 4.16~rc6-1~exp1 Severity: wishlist Tags: patch In kernel 4.16 perf has support for libopencsd, which decodes arm coresight trace packets. This should be enabled in debian kernels so that it 'just works' for users. perf compilation picks up libopencsd if it installed so enabling it is simply a matter of adding it to the build-dependencies so that it is available at build time. Attached is a patch that does this. However note that, whilst libopencsd is now packaged for debian it has not yet been uploaded to the archive (one build issue remains to be fixed before it can be uploaded), and clearly this build-dep can't be added until the library is actually available. So this bug is blocked on #891955 diff -Nru linux-4.16~rc6/debian/changelog linux-4.16~rc6/debian/changelog --- linux-4.16~rc6/debian/changelog 2018-03-20 13:52:03.0 + +++ linux-4.16~rc6/debian/changelog 2018-04-06 21:12:15.0 + @@ -1,3 +1,10 @@ +linux (4.16~rc6-1~exp2) experimental; urgency=medium + + * Non-maintainer upload. + * add build-dep on libopencsd for perf on arm + + -- Wookey Fri, 06 Apr 2018 22:12:15 +0100 + linux (4.16~rc6-1~exp1) experimental; urgency=medium * New upstream release candidate diff -Nru linux-4.16~rc6/debian/config.defines.dump linux-4.16~rc6/debian/config.defines.dump diff -Nru linux-4.16~rc6/debian/control linux-4.16~rc6/debian/control diff -Nru linux-4.16~rc6/debian/control.md5sum linux-4.16~rc6/debian/control.md5sum diff -Nru linux-4.16~rc6/debian/rules.gen linux-4.16~rc6/debian/rules.gen diff -Nru linux-4.16~rc6/debian/templates/control.source.in linux-4.16~rc6/debian/templates/control.source.in --- linux-4.16~rc6/debian/templates/control.source.in 2018-03-20 13:46:09.0 + +++ linux-4.16~rc6/debian/templates/control.source.in 2018-04-06 21:12:15.0 + @@ -45,6 +45,7 @@ libnuma-dev [amd64 arm64 hppa i386 mips mips64 mips64el mipsel mipsn32 mipsn32el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el powerpc powerpcspe ppc64 ppc64el sparc x32] , libperl-dev , libunwind8-dev [amd64 armel armhf arm64 i386] , + libopencsd-dev , python-dev , # used by upstream to build usbip autoconf , --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.28-1 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 895...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Mar 2019 05:06:28 + Source: linux Binary: linux-doc-4.19 linux-headers-4.19.0-4-common linux-headers-4.19.0-4-common-rt linux-source-4.19 linux-support-4.19.0-4 lockdep Architecture: all source Version: 4.19.28-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 895131 913119 913138 921542 922182 922306 Description: linux-doc-4.19 - Linux kernel specific documentation for version 4.19 linux-headers-4.19.0-4-common - Common header files for Linux 4.19.0-4 linux-headers-4.19.0-4-common-rt - Common header files for Linux 4.19.0-4-rt linux-source-4.19 - Linux kernel source for version 4.19 with Debian patches linux-support-4.19.0-4 - Support files for Linux 4.19 lockdep- Runtime locking correctness validator Changes: linux (4.19.28-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.21 - devres: Align data[] to ARCH_KMALLOC_MINALIGN - drm/bufs: Fix Spectre v1 vulnerability - drm/vgem: Fix vgem_init to get drm
Bug#850425: mpt3sas "swiotlb buffer is full" problem only under Xen
On 3/12/19 5:04 PM, Juergen Gross wrote: > On 11/03/2019 20:50, Hans van Kranenburg wrote: >> On 3/11/19 7:34 AM, Juergen Gross wrote: >>> >>> I'm not sure. Patch 3 of this series is basically already there (see >>> commit c6d4381220a0087ce19dbf6984d92c451bd6b364). So maybe all we need >>> is patch 4, which should really be easy to do? >>> >>> Hans, could you give it a try? You'd need to use a 4.20 kernel at least. >>> I can do the official patch posting in case you confirm it working. >> >> Ehm ok, well... This is interesting. >> >> I just built a 4.20.13 (without the patch), and I did it from the Debian >> kernel team repo, because then I just get all latest config options like >> I would get them in Debian. >> >> I rebooted the HP Z820 with it (with Xen 4.11) and I don't see any >> errors similar to the ones I pasted earlier. >> >> I haven't been running any domU on it yet (just installed it), but this >> is not what I expected. > > Well, commit c6d4381220a0087ce19dbf6984d92c451bd6b364 is part of a > rather large series making the dma interface cleaner and using it more > correctly where appropriate. Maybe your use case is covered by this > series already. It seems so. That's good, of course, but it also means that I cannot be of any use here any more to test the additional proposed change. ;] Except, for trying it to see if it won't introduce more regressions and explosions, if you want me to. Hans
Bug#850425: mpt3sas "swiotlb buffer is full" problem only under Xen
On 11/03/2019 20:50, Hans van Kranenburg wrote: > On 3/11/19 7:34 AM, Juergen Gross wrote: >> >> I'm not sure. Patch 3 of this series is basically already there (see >> commit c6d4381220a0087ce19dbf6984d92c451bd6b364). So maybe all we need >> is patch 4, which should really be easy to do? >> >> Hans, could you give it a try? You'd need to use a 4.20 kernel at least. >> I can do the official patch posting in case you confirm it working. > > Ehm ok, well... This is interesting. > > I just built a 4.20.13 (without the patch), and I did it from the Debian > kernel team repo, because then I just get all latest config options like > I would get them in Debian. > > I rebooted the HP Z820 with it (with Xen 4.11) and I don't see any > errors similar to the ones I pasted earlier. > > I haven't been running any domU on it yet (just installed it), but this > is not what I expected. Well, commit c6d4381220a0087ce19dbf6984d92c451bd6b364 is part of a rather large series making the dma interface cleaner and using it more correctly where appropriate. Maybe your use case is covered by this series already. Juergen
firmware-iwlwifi disable network-manager's root password requirement for every user
Dear maintainers, this concerns : network-manager version 1.6.2-3+deb9u2 network-manager-gnome version 1.4.4-1+deb9u1 firmware-iwlwifi version 20161130-4 gnome version 3.22.2 Debian GNU/Linux version 9 (stretch) 64 bits ➤ I am writing to report this unsolicited behaviour: Steps: 1 - Fresh Debian with wired internet access 2 - access to network settings require root password (this is ok) 3 - install firmware-iwlwifi 4 - access to network settings (LAN and Wi-Fi) do not require password anymore, whatever user is logged in, even after reboot. 5 - uninstall firmware-iwlwifi restore root password requirement. I've found no info about this behaviour in the documentation, nor how to prevent this to happen without consent. ➤ I would like to know how to preserve or restore the primary network-manager secure behaviour while having Wi-Fi functional. Yours faithfully Cacquarante
linux-latest_104_multi.changes is NEW
binary:linux-headers-rpi is NEW. binary:linux-image-rpi is NEW. binary:linux-image-rpi-dbg 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-latest_104_multi.changes
linux-latest_104_multi.changes uploaded successfully to localhost along with the files: linux-latest_104.dsc linux-latest_104.tar.xz linux-latest_104_source.buildinfo linux-doc_4.19+104_all.deb linux-latest_104_all.buildinfo linux-perf_4.19+104_all.deb linux-source_4.19+104_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux_4.19.28-1_multi.changes is NEW
binary:acpi-modules-4.19.0-4-686-di is NEW. binary:acpi-modules-4.19.0-4-686-pae-di is NEW. binary:acpi-modules-4.19.0-4-amd64-di is NEW. binary:affs-modules-4.19.0-4-4kc-malta-di is NEW. binary:affs-modules-4.19.0-4-5kc-malta-di is NEW. binary:affs-modules-4.19.0-4-loongson-3-di is NEW. binary:affs-modules-4.19.0-4-octeon-di is NEW. binary:ata-modules-4.19.0-4-4kc-malta-di is NEW. binary:ata-modules-4.19.0-4-5kc-malta-di is NEW. binary:ata-modules-4.19.0-4-686-di is NEW. binary:ata-modules-4.19.0-4-686-pae-di is NEW. binary:ata-modules-4.19.0-4-amd64-di is NEW. binary:ata-modules-4.19.0-4-arm64-di is NEW. binary:ata-modules-4.19.0-4-armmp-di is NEW. binary:ata-modules-4.19.0-4-loongson-3-di is NEW. binary:ata-modules-4.19.0-4-powerpc64le-di is NEW. binary:btrfs-modules-4.19.0-4-4kc-malta-di is NEW. binary:btrfs-modules-4.19.0-4-5kc-malta-di is NEW. binary:btrfs-modules-4.19.0-4-686-di is NEW. binary:btrfs-modules-4.19.0-4-686-pae-di is NEW. binary:btrfs-modules-4.19.0-4-amd64-di is NEW. binary:btrfs-modules-4.19.0-4-arm64-di is NEW. binary:btrfs-modules-4.19.0-4-armmp-di is NEW. binary:btrfs-modules-4.19.0-4-loongson-3-di is NEW. binary:btrfs-modules-4.19.0-4-marvell-di is NEW. binary:btrfs-modules-4.19.0-4-octeon-di is NEW. binary:btrfs-modules-4.19.0-4-powerpc64le-di is NEW. binary:btrfs-modules-4.19.0-4-s390x-di is NEW. binary:cdrom-core-modules-4.19.0-4-4kc-malta-di is NEW. binary:cdrom-core-modules-4.19.0-4-5kc-malta-di is NEW. binary:cdrom-core-modules-4.19.0-4-686-di is NEW. binary:cdrom-core-modules-4.19.0-4-686-pae-di is NEW. binary:cdrom-core-modules-4.19.0-4-amd64-di is NEW. binary:cdrom-core-modules-4.19.0-4-arm64-di is NEW. binary:cdrom-core-modules-4.19.0-4-armmp-di is NEW. binary:cdrom-core-modules-4.19.0-4-loongson-3-di is NEW. binary:cdrom-core-modules-4.19.0-4-marvell-di is NEW. binary:cdrom-core-modules-4.19.0-4-octeon-di is NEW. binary:cdrom-core-modules-4.19.0-4-powerpc64le-di is NEW. binary:cdrom-core-modules-4.19.0-4-s390x-di is NEW. binary:compress-modules-4.19.0-4-4kc-malta-di is NEW. binary:compress-modules-4.19.0-4-5kc-malta-di is NEW. binary:compress-modules-4.19.0-4-686-di is NEW. binary:compress-modules-4.19.0-4-686-pae-di is NEW. binary:compress-modules-4.19.0-4-amd64-di is NEW. binary:compress-modules-4.19.0-4-arm64-di is NEW. binary:compress-modules-4.19.0-4-armmp-di is NEW. binary:compress-modules-4.19.0-4-loongson-3-di is NEW. binary:compress-modules-4.19.0-4-marvell-di is NEW. binary:compress-modules-4.19.0-4-octeon-di is NEW. binary:compress-modules-4.19.0-4-powerpc64le-di is NEW. binary:compress-modules-4.19.0-4-s390x-di is NEW. binary:crc-modules-4.19.0-4-4kc-malta-di is NEW. binary:crc-modules-4.19.0-4-5kc-malta-di is NEW. binary:crc-modules-4.19.0-4-686-di is NEW. binary:crc-modules-4.19.0-4-686-pae-di is NEW. binary:crc-modules-4.19.0-4-amd64-di is NEW. binary:crc-modules-4.19.0-4-arm64-di is NEW. binary:crc-modules-4.19.0-4-armmp-di is NEW. binary:crc-modules-4.19.0-4-loongson-3-di is NEW. binary:crc-modules-4.19.0-4-marvell-di is NEW. binary:crc-modules-4.19.0-4-octeon-di is NEW. binary:crc-modules-4.19.0-4-powerpc64le-di is NEW. binary:crc-modules-4.19.0-4-s390x-di is NEW. binary:crypto-dm-modules-4.19.0-4-4kc-malta-di is NEW. binary:crypto-dm-modules-4.19.0-4-5kc-malta-di is NEW. binary:crypto-dm-modules-4.19.0-4-686-di is NEW. binary:crypto-dm-modules-4.19.0-4-686-pae-di is NEW. binary:crypto-dm-modules-4.19.0-4-amd64-di is NEW. binary:crypto-dm-modules-4.19.0-4-arm64-di is NEW. binary:crypto-dm-modules-4.19.0-4-armmp-di is NEW. binary:crypto-dm-modules-4.19.0-4-loongson-3-di is NEW. binary:crypto-dm-modules-4.19.0-4-marvell-di is NEW. binary:crypto-dm-modules-4.19.0-4-octeon-di is NEW. binary:crypto-dm-modules-4.19.0-4-powerpc64le-di is NEW. binary:crypto-dm-modules-4.19.0-4-s390x-di is NEW. binary:crypto-modules-4.19.0-4-4kc-malta-di is NEW. binary:crypto-modules-4.19.0-4-5kc-malta-di is NEW. binary:crypto-modules-4.19.0-4-686-di is NEW. binary:crypto-modules-4.19.0-4-686-pae-di is NEW. binary:crypto-modules-4.19.0-4-amd64-di is NEW. binary:crypto-modules-4.19.0-4-arm64-di is NEW. binary:crypto-modules-4.19.0-4-armmp-di is NEW. binary:crypto-modules-4.19.0-4-loongson-3-di is NEW. binary:crypto-modules-4.19.0-4-marvell-di is NEW. binary:crypto-modules-4.19.0-4-octeon-di is NEW. binary:crypto-modules-4.19.0-4-powerpc64le-di is NEW. binary:crypto-modules-4.19.0-4-s390x-di is NEW. binary:dasd-extra-modules-4.19.0-4-s390x-di is NEW. binary:dasd-modules-4.19.0-4-s390x-di is NEW. binary:efi-modules-4.19.0-4-686-di is NEW. binary:efi-modules-4.19.0-4-686-pae-di is NEW. binary:efi-modules-4.19.0-4-amd64-di is NEW. binary:efi-modules-4.19.0-4-arm64-di is NEW. binary:efi-modules-4.19.0-4-armmp-di is NEW. binary:event-modules-4.19.0-4-4kc-malta-di is NEW. binary:event-modules-4.19.0-4-5kc-malta-di is NEW. binary:event-modules-4.19.0-4-686-di is NEW. binary:event-modules-4.19.0-4-686-pae-di is NEW. binary:event-modules-4.19.0-4-amd64-di is NEW.
Processing of linux_4.19.28-1_multi.changes
linux_4.19.28-1_multi.changes uploaded successfully to localhost along with the files: linux_4.19.28-1.dsc linux_4.19.28.orig.tar.xz linux_4.19.28-1.debian.tar.xz linux_4.19.28-1_source.buildinfo linux-doc-4.19_4.19.28-1_all.deb linux-headers-4.19.0-4-common-rt_4.19.28-1_all.deb linux-headers-4.19.0-4-common_4.19.28-1_all.deb linux-source-4.19_4.19.28-1_all.deb linux-support-4.19.0-4_4.19.28-1_all.deb lockdep_4.19.28-1_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
linux_4.19.28-1_multi.changes REJECTED
linux_4.19.28-1_multi.changes: binary upload requires Binary field === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
linux-latest_104_multi.changes REJECTED
linux-latest_104_multi.changes: binary upload requires Binary field === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
Processing of linux-latest_104_multi.changes
linux-latest_104_multi.changes uploaded successfully to localhost along with the files: linux-latest_104.dsc linux-latest_104.tar.xz linux-latest_104_source.buildinfo linux-doc_4.19+104_all.deb linux-latest_104_all.buildinfo linux-perf_4.19+104_all.deb linux-source_4.19+104_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processing of linux_4.19.28-1_multi.changes
linux_4.19.28-1_multi.changes uploaded successfully to localhost along with the files: linux_4.19.28-1.dsc linux_4.19.28.orig.tar.xz linux_4.19.28-1.debian.tar.xz linux_4.19.28-1_source.buildinfo linux-doc-4.19_4.19.28-1_all.deb linux-headers-4.19.0-4-common-rt_4.19.28-1_all.deb linux-headers-4.19.0-4-common_4.19.28-1_all.deb linux-source-4.19_4.19.28-1_all.deb linux-support-4.19.0-4_4.19.28-1_all.deb lockdep_4.19.28-1_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
