Bug#928125: marked as done (losetup causes Dead systemd-udevd processes, blocks forever)
Your message dated Fri, 17 May 2019 19:32:12 +0000
with message-id <E1hRiaS-000Ciu-Es@fasolo.debian.org>
and subject line Bug#928125: fixed in linux 4.9.168-1+deb9u2
has caused the Debian Bug report #928125,
regarding losetup causes Dead systemd-udevd processes, blocks forever
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 owner@bugs.debian.org
immediately.)
--
928125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928125
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: losetup causes Dead systemd-udevd processes, blocks forever
- From: Brad Barnett <debian-bugs2@L8R.net>
- Date: Sun, 28 Apr 2019 12:00:07 -0400
- Message-id: <20190428120007.34e3196a@be.back.L8R.net>
Package: udev
Version: 232-25+deb9u11
After today's upgrade to debian 9.9, I attempted to create a disk image.
I have a script, it does the following:
###
dd if=/dev/zero of=/tmp/ff1.raw bs=1G seek=8 count=0
sync
sleep 1
parted /tmp/ff1.raw mklabel msdos
parted -s /tmp/ff1.raw mkpart primary linux-swap 1 100
parted -s -- /tmp/ff1.raw mkpart primary ext2 101 -1
parted -s -- /tmp/ff1.raw set 2 boot on
sleep 5
losetup -Pf /tmp/ff1.raw --show
###
The above has been run several times per month, for years.
After today's upgrade I rebooted, ran the above, and it locked on losetup.
I see this:
# ps auxwwf
root 346 0.0 0.1 45656 3420 ? Ss 11:30 0:00 /lib/systemd/systemd-udevd --daemon
root 2596 0.0 0.0 45564 2120 ? S 11:31 0:00 \_ /lib/systemd/systemd-udevd --daemon
root 2597 0.0 0.0 45564 2184 ? D 11:31 0:00 \_ /lib/systemd/systemd-udevd --daemon
root 2599 0.0 0.1 45644 3096 ? S 11:31 0:00 \_ /lib/systemd/systemd-udevd --daemon
root 2602 0.0 0.0 45564 2120 ? D 11:31 0:00 \_ /lib/systemd/systemd-udevd --daemon
root 2603 0.0 0.0 45656 1936 ? D 11:31 0:00 \_ /lib/systemd/systemd-udevd --daemon
root 2607 0.0 0.0 45656 1936 ? D 11:31 0:00 \_ /lib/systemd/systemd-udevd --daemon
root 2609 0.0 0.0 45564 2120 ? D 11:31 0:00 \_ /lib/systemd/systemd-udevd --daemon
root 2610 0.0 0.0 45656 1936 ? D 11:31 0:00 \_ /lib/systemd/systemd-udevd --daemon
root 2612 0.0 0.0 45656 1936 ? D 11:31 0:00 \_ /lib/systemd/systemd-udevd --daemon
And
root 2591 0.0 0.0 8064 780 pts/2 D 11:31 0:00 /sbin/losetup -Pf /tmp/ff1.raw --show
I also see this (last 3 'blocks' pasted):
Apr 28 11:34:17 buildvm kernel: [ 242.831744] INFO: task systemd-udevd:2612 blocked for more than 120 seconds.
Apr 28 11:34:17 buildvm kernel: [ 242.831807] Not tainted 4.9.0-9-amd64 #1 Debian 4.9.168-1
Apr 28 11:34:17 buildvm kernel: [ 242.831859] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 28 11:34:17 buildvm kernel: [ 242.831927] systemd-udevd D 0 2612 346 0x00000004
Apr 28 11:34:17 buildvm kernel: [ 242.831932] ffff8a2dbb10c400 0000000000000000 ffff8a2dbacc5240 ffff8a2dbfa18980
Apr 28 11:34:17 buildvm kernel: [ 242.831939] ffffffffaf411500 ffffaf84409e7b58 ffffffffaee15a99 1e580f2a959617cf
Apr 28 11:34:17 buildvm kernel: [ 242.831946] 00000000000402c0
ffff8a2dbfa18980 0000000000000000 ffff8a2dbacc5240
Apr 28 11:34:17 buildvm kernel: [ 242.831952] Call Trace:
Apr 28 11:34:17 buildvm kernel: [ 242.831960] [<ffffffffaee15a99>] ? __schedule+0x239/0x6f0
Apr 28 11:34:17 buildvm kernel: [ 242.831967] [<ffffffffaee15f82>] ? schedule+0x32/0x80
Apr 28 11:34:17 buildvm kernel: [ 242.831973] [<ffffffffaee1623a>] ? schedule_preempt_disabled+0xa/0x10
Apr 28 11:34:17 buildvm kernel: [ 242.831977] [<ffffffffaee17c94>] ? __mutex_lock_slowpath+0xb4/0x130
Apr 28 11:34:17 buildvm kernel: [ 242.831982] [<ffffffffaee17d2b>] ? mutex_lock+0x1b/0x30
Apr 28 11:34:17 buildvm kernel: [ 242.831988] [<ffffffffc03e11c5>] ? lo_open+0x15/0x50 [loop]
Apr 28 11:34:17 buildvm kernel: [ 242.831994] [<ffffffffaea48ce3>] ? __blkdev_get+0xd3/0x470
Apr 28 11:34:17 buildvm kernel: [ 242.832001] [<ffffffffaea492e6>] ? blkdev_get+0x126/0x330
Apr 28 11:34:17 buildvm kernel: [ 242.832008] [<ffffffffaea27e04>] ? unlock_new_inode+0x44/0x70
Apr 28 11:34:17 buildvm kernel: [ 242.832014] [<ffffffffaea47e3a>] ? bdget+0xfa/0x110
Apr 28 11:34:17 buildvm kernel: [ 242.832020] [<ffffffffaea49530>] ? blkdev_get_by_dev+0x40/0x40
Apr 28 11:34:17 buildvm kernel: [ 242.832026] [<ffffffffaea08e74>] ? do_dentry_open+0x234/0x340
Apr 28 11:34:17 buildvm kernel: [ 242.832030] [<ffffffffaea1ada7>] ? path_openat+0x777/0x15b0
Apr 28 11:34:17 buildvm kernel: [ 242.832037] [<ffffffffae9c8211>] ? page_add_file_rmap+0x11/0x110
Apr 28 11:34:17 buildvm kernel: [ 242.832042] [<ffffffffaea1cea1>] ? do_filp_open+0x91/0x100
Apr 28 11:34:17 buildvm kernel: [ 242.832047] [<ffffffffae9bb263>] ? handle_mm_fault+0xcc3/0x1350
Apr 28 11:34:17 buildvm kernel: [ 242.832052] [<ffffffffaea07b3a>] ? __check_object_size+0xfa/0x1d8
Apr 28 11:34:17 buildvm kernel: [ 242.832058] [<ffffffffaea0a3ae>] ? do_sys_open+0x12e/0x210
Apr 28 11:34:17 buildvm kernel: [ 242.832064] [<ffffffffae803b7d>] ? do_syscall_64+0x8d/0xf0
Apr 28 11:34:17 buildvm kernel: [ 242.832069] [<ffffffffaee1a84e>] ? entry_SYSCALL_64_after_swapgs+0x58/0xc6
Apr 28 11:36:18 buildvm kernel: [ 363.661408] INFO: task losetup:2591 blocked for more than 120 seconds.
Apr 28 11:36:18 buildvm kernel: [ 363.661487] Not tainted 4.9.0-9-amd64 #1 Debian 4.9.168-1
Apr 28 11:36:18 buildvm kernel: [ 363.661541] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 28 11:36:18 buildvm kernel: [ 363.661610] losetup D 0 2591 1 0x00000004
Apr 28 11:36:18 buildvm kernel: [ 363.661620] ffff8a2db7926c00 0000000000000000 ffff8a2db7956ec0 ffff8a2dbfa18980
Apr 28 11:36:18 buildvm kernel: [ 363.661628] ffffffffaf411500 ffffaf8440a7fbd8 ffffffffaee15a99 ffffffffaee1a964
Apr 28 11:36:18 buildvm kernel: [ 363.661635] 00ff8a2db7957a00 ffff8a2dbfa18980 ffff8a2dbacc5240 ffff8a2db7956ec0
Apr 28 11:36:18 buildvm kernel: [ 363.661642] Call Trace:
Apr 28 11:36:18 buildvm kernel: [ 363.661656] [<ffffffffaee15a99>] ? __schedule+0x239/0x6f0
Apr 28 11:36:18 buildvm kernel: [ 363.661663] [<ffffffffaee1a964>] ? __switch_to_asm+0x34/0x70
Apr 28 11:36:18 buildvm kernel: [ 363.661670] [<ffffffffaee15f82>] ? schedule+0x32/0x80
Apr 28 11:36:18 buildvm kernel: [ 363.661677] [<ffffffffaee1623a>] ? schedule_preempt_disabled+0xa/0x10
Apr 28 11:36:18 buildvm kernel: [ 363.661682] [<ffffffffaee17c94>] ? __mutex_lock_slowpath+0xb4/0x130
Apr 28 11:36:18 buildvm kernel: [ 363.661689] [<ffffffffaee17d2b>] ? mutex_lock+0x1b/0x30
Apr 28 11:36:18 buildvm kernel: [ 363.661697] [<ffffffffaeb15e46>] ? blkdev_reread_part+0x16/0x30
Apr 28 11:36:18 buildvm kernel: [ 363.661705] [<ffffffffc03e1803>] ? loop_reread_partitions+0x23/0x50 [loop]
Apr 28 11:36:18 buildvm kernel: [ 363.661712] [<ffffffffc03e1b3b>] ? loop_set_status+0x30b/0x3a0 [loop]
Apr 28 11:36:18 buildvm kernel: [ 363.661719] [<ffffffffc03e1e88>] ? loop_set_status64+0x48/0x70 [loop]
Apr 28 11:36:18 buildvm kernel: [ 363.661726] [<ffffffffc03e3138>] ? lo_ioctl+0xe8/0x6f0 [loop]
Apr 28 11:36:18 buildvm kernel: [ 363.661734] [<ffffffffaeb16645>] ? blkdev_ioctl+0x265/0x970
Apr 28 11:36:18 buildvm kernel: [ 363.661740] [<ffffffffae9bb37f>] ? handle_mm_fault+0xddf/0x1350
Apr 28 11:36:18 buildvm kernel: [ 363.661748] [<ffffffffaea481a9>] ? block_ioctl+0x39/0x40
Apr 28 11:36:18 buildvm kernel: [ 363.661753] [<ffffffffaea201b2>] ? do_vfs_ioctl+0xa2/0x620
Apr 28 11:36:18 buildvm kernel: [ 363.661759] [<ffffffffaea207a4>] ? SyS_ioctl+0x74/0x80
Apr 28 11:36:18 buildvm kernel: [ 363.661765] [<ffffffffae803b7d>] ? do_syscall_64+0x8d/0xf0
Apr 28 11:36:18 buildvm kernel: [ 363.661771] [<ffffffffaee1a84e>] ? entry_SYSCALL_64_after_swapgs+0x58/0xc6
Apr 28 11:36:18 buildvm kernel: [ 363.661776] INFO: task systemd-udevd:2597 blocked for more than 120 seconds.
Apr 28 11:36:18 buildvm kernel: [ 363.661841] Not tainted 4.9.0-9-amd64 #1 Debian 4.9.168-1
Apr 28 11:36:18 buildvm kernel: [ 363.661894] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 28 11:36:18 buildvm kernel: [ 363.661962] systemd-udevd D 0 2597 346 0x00000004
Apr 28 11:36:18 buildvm kernel: [ 363.661969] ffff8a2db7924400 0000000000000000 ffff8a2db79ff180 ffff8a2dbfb18980
Apr 28 11:36:18 buildvm kernel: [ 363.661976] ffff8a2dbb91cec0 ffffaf844086bd88 ffffffffaee15a99 3959c0b6fb0308ab
Apr 28 11:36:18 buildvm kernel: [ 363.661983] 00ffaf844086bd70 ffff8a2dbfb18980 ffff8a2dbb219498 ffff8a2db79ff180
Apr 28 11:36:18 buildvm kernel: [ 363.661990] Call Trace:
Apr 28 11:36:18 buildvm kernel: [ 363.661998] [<ffffffffaee15a99>] ? __schedule+0x239/0x6f0
Apr 28 11:36:18 buildvm kernel: [ 363.662006] [<ffffffffaee15f82>] ? schedule+0x32/0x80
Apr 28 11:36:18 buildvm kernel: [ 363.662013] [<ffffffffaee1623a>] ? schedule_preempt_disabled+0xa/0x10
Apr 28 11:36:18 buildvm kernel: [ 363.662017] [<ffffffffaee17c94>] ? __mutex_lock_slowpath+0xb4/0x130
Apr 28 11:36:18 buildvm kernel: [ 363.662022] [<ffffffffaee17d2b>] ? mutex_lock+0x1b/0x30
Apr 28 11:36:18 buildvm kernel: [ 363.662029] [<ffffffffc03e2ff4>] ? lo_release+0x44/0xa0 [loop]
Apr 28 11:36:18 buildvm kernel: [ 363.662036] [<ffffffffaea48b2d>] ? __blkdev_put+0x1ed/0x2d0
Apr 28 11:36:18 buildvm kernel: [ 363.662043] [<ffffffffaea491b1>] ? blkdev_close+0x21/0x30
Apr 28 11:36:18 buildvm kernel: [ 363.662048] [<ffffffffaea0dc48>] ? __fput+0xd8/0x220
Apr 28 11:36:18 buildvm kernel: [ 363.662055] [<ffffffffae898d5f>] ? task_work_run+0x7f/0xa0
Apr 28 11:36:18 buildvm kernel: [ 363.662061] [<ffffffffae803754>] ? exit_to_usermode_loop+0xa4/0xb0
Apr 28 11:36:18 buildvm kernel: [ 363.662067] [<ffffffffae803bcd>] ? do_syscall_64+0xdd/0xf0
Apr 28 11:36:18 buildvm kernel: [ 363.662073] [<ffffffffaee1a84e>] ? entry_SYSCALL_64_after_swapgs+0x58/0xc6
The above repeats for all D systemd-udev tasks, and losetup, EG:
Apr 28 11:34:17 buildvm kernel: [ 242.829350] INFO: task losetup:2591 blocked for more than 120 seconds.
Apr 28 11:34:17 buildvm kernel: [ 242.829715] INFO: task systemd-udevd:2597 blocked for more than 120 seconds.
Apr 28 11:34:17 buildvm kernel: [ 242.830018] INFO: task systemd-udevd:2602 blocked for more than 120 seconds.
Apr 28 11:34:17 buildvm kernel: [ 242.830342] INFO: task systemd-udevd:2603 blocked for more than 120 seconds.
Apr 28 11:34:17 buildvm kernel: [ 242.830679] INFO: task systemd-udevd:2607 blocked for more than 120 seconds.
Apr 28 11:34:17 buildvm kernel: [ 242.831086] INFO: task systemd-udevd:2609 blocked for more than 120 seconds.
Apr 28 11:34:17 buildvm kernel: [ 242.831413] INFO: task systemd-udevd:2610 blocked for more than 120 seconds.
Apr 28 11:34:17 buildvm kernel: [ 242.831744] INFO: task systemd-udevd:2612 blocked for more than 120 seconds.
Apr 28 11:36:18 buildvm kernel: [ 363.661408] INFO: task losetup:2591 blocked for more than 120 seconds.
Apr 28 11:36:18 buildvm kernel: [ 363.661776] INFO: task systemd-udevd:2597 blocked for more than 120 seconds.
I tried to strace this, but if I do? It works fine. Further, once I've
done an strace, further losetups work fine -- without blocking.
Not really sure what's causing this, but without strace and losetup D
forever, it's annoying to debug. Suggestions welcome.
Note that after the above INFO/hangs, the above systemd-udev and losetup
tasks sit D forever. It's been 20+ minutes, no activity in kern.log,
just dead.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.168-1+deb9u2
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 928125@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ben Hutchings <ben@decadent.org.uk> (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 ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 13 May 2019 21:59:18 +0100
Binary: linux-doc-4.9 linux-headers-4.9.0-9-common linux-headers-4.9.0-9-common-rt linux-manual-4.9 linux-source-4.9 linux-support-4.9.0-9
Source: linux
Architecture: all source
Version: 4.9.168-1+deb9u2
Distribution: stretch-security
Urgency: high
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Changed-By: Ben Hutchings <ben@decadent.org.uk>
Closes: 928125
Description:
linux-doc-4.9 - Linux kernel specific documentation for version 4.9
linux-headers-4.9.0-9-common - Common header files for Linux 4.9.0-9
linux-headers-4.9.0-9-common-rt - Common header files for Linux 4.9.0-9-rt
linux-manual-4.9 - Linux kernel API manual pages for version 4.9
linux-source-4.9 - Linux kernel source for version 4.9 with Debian patches
linux-support-4.9.0-9 - Support files for Linux 4.9
Changes:
linux (4.9.168-1+deb9u2) stretch-security; urgency=high
.
[ Salvatore Bonaccorso ]
* Revert "block/loop: Use global lock for ioctl() operation."
(Closes: #928125)
.
linux (4.9.168-1+deb9u1) stretch-security; urgency=high
.
* [x86] Update speculation mitigations:
- x86/MCE: Save microcode revision in machine check records
- x86/cpufeatures: Hide AMD-specific speculation flags
- x86/bugs: Add AMD's variant of SSB_NO
- x86/bugs: Add AMD's SPEC_CTRL MSR usage
- x86/bugs: Switch the selection of mitigation from CPU vendor to CPU
features
- x86/bugs: Fix the AMD SSBD usage of the SPEC_CTRL MSR
- x86/microcode/intel: Add a helper which gives the microcode revision
- x86/microcode/intel: Check microcode revision before updating sibling
threads
- x86/microcode: Make sure boot_cpu_data.microcode is up-to-date
- x86/microcode: Update the new microcode revision unconditionally
- x86/mm: Use WRITE_ONCE() when setting PTEs
- bitops: avoid integer overflow in GENMASK(_ULL)
- x86/speculation: Simplify the CPU bug detection logic
- locking/atomics, asm-generic: Move some macros from <linux/bitops.h> to a
new <linux/bits.h> file
- x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation
- x86/cpu: Sanitize FAM6_ATOM naming
- Documentation/l1tf: Fix small spelling typo
- x86/speculation: Apply IBPB more strictly to avoid cross-process data
leak
- x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation
- x86/speculation: Propagate information about RSB filling mitigation to
sysfs
- x86/speculation/l1tf: Drop the swap storage limit restriction when
l1tf=off
- x86/speculation: Update the TIF_SSBD comment
- x86/speculation: Clean up spectre_v2_parse_cmdline()
- x86/speculation: Remove unnecessary ret variable in cpu_show_common()
- x86/speculation: Move STIPB/IBPB string conditionals out of
cpu_show_common()
- x86/speculation: Disable STIBP when enhanced IBRS is in use
- x86/speculation: Rename SSBD update functions
- x86/speculation: Reorganize speculation control MSRs update
- x86/Kconfig: Select SCHED_SMT if SMP enabled
- sched: Add sched_smt_active()
- x86/speculation: Rework SMT state change
- x86/l1tf: Show actual SMT state
- x86/speculation: Reorder the spec_v2 code
- x86/speculation: Mark string arrays const correctly
- x86/speculataion: Mark command line parser data __initdata
- x86/speculation: Unify conditional spectre v2 print functions
- x86/speculation: Add command line control for indirect branch speculation
- x86/speculation: Prepare for per task indirect branch speculation control
- x86/process: Consolidate and simplify switch_to_xtra() code
- x86/speculation: Avoid __switch_to_xtra() calls
- x86/speculation: Prepare for conditional IBPB in switch_mm()
- x86/speculation: Split out TIF update
- x86/speculation: Prepare arch_smt_update() for PRCTL mode
- x86/speculation: Prevent stale SPEC_CTRL msr content
- x86/speculation: Add prctl() control for indirect branch speculation
- x86/speculation: Enable prctl mode for spectre_v2_user
- x86/speculation: Add seccomp Spectre v2 user space protection mode
- x86/speculation: Provide IBPB always command line options
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- Documentation: Move L1TF to separate directory
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option
- x86/speculation/mds: Add 'mitigations=' support for MDS
- x86/cpu/bugs: Use __initconst for 'const' init data
* [x86] Mitigate Microarchitectural Data Sampling (MDS) vulnerabilities
(CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091):
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/mds: Add MDSUM variant to the MDS documentation
- Documentation: Correct the possible MDS sysfs values
- x86/speculation/mds: Fix documentation typo
* [x86] msr-index: Remove dependency on <linux/bits.h>
* [rt] Update patches to apply on top of the speculation mitigation changes
* [x86] mce, tlb: Ignore ABI changes
Checksums-Sha1:
3cf9ad06772fa1e2250f95ccecf0a7107b0d0643 123228 linux_4.9.168-1+deb9u2.dsc
2f22afcec11f5491e4e8db61d6951b7b418a6315 94774584 linux_4.9.168.orig.tar.xz
1349d89187328a5102383cfe7c407f2865b042de 2732028 linux_4.9.168-1+deb9u2.debian.tar.xz
fe5d0672e36a74dd521508fc767457d428aa6cef 36957 linux_4.9.168-1+deb9u2_source.buildinfo
f3be321e50c16f8c99e8dc9579c98e9d2580d970 12499332 linux-doc-4.9_4.9.168-1+deb9u2_all.deb
e551224f199a979d90e1a7ae0cc0b389fcd76008 5740880 linux-headers-4.9.0-9-common-rt_4.9.168-1+deb9u2_all.deb
83305c5648a0daeda21e3be674ba12fbf4c3b2ed 7674072 linux-headers-4.9.0-9-common_4.9.168-1+deb9u2_all.deb
05d661dc8b328aadb6f2bdd2cf4ba6da8707dd16 3198870 linux-manual-4.9_4.9.168-1+deb9u2_all.deb
bf7a6e40877370ce9ac65e0d01e75f17b861206f 96825676 linux-source-4.9_4.9.168-1+deb9u2_all.deb
e96f76b1f005f231f2dc8bbe7910a3c080d0577c 678004 linux-support-4.9.0-9_4.9.168-1+deb9u2_all.deb
244269a9ceefac4eff43d79b392ab7efb4bf8502 41613 linux_4.9.168-1+deb9u2_all.buildinfo
Checksums-Sha256:
9ff4ff71bc5a3f087fef7e4201a8448040f84035a1298ad01a8f5d6fe5192795 123228 linux_4.9.168-1+deb9u2.dsc
8a2c04045b47472584fc8e72d8663b5c720b8ba5efba878f48ddba93bac29a7f 94774584 linux_4.9.168.orig.tar.xz
b909b4c1feb633d1d458d0fd80b96698d97d12fc790fa56a1398a951585d631a 2732028 linux_4.9.168-1+deb9u2.debian.tar.xz
e895f11c1735cd8609d81d74d25da0129b191eb9a39249b12ad5694a42e43dd4 36957 linux_4.9.168-1+deb9u2_source.buildinfo
39d4b4497dde28b68270de2758124ad4df3d061a882d0e29b72eb4254af7007f 12499332 linux-doc-4.9_4.9.168-1+deb9u2_all.deb
a40a10d1dc60d88816f2b2f88242192d02bfeacee846bf5c454ed303d028d6a8 5740880 linux-headers-4.9.0-9-common-rt_4.9.168-1+deb9u2_all.deb
f0d2dd38e1e674ab5960587adf60d2d955eec4ba755b9d03f4f9d1206368052c 7674072 linux-headers-4.9.0-9-common_4.9.168-1+deb9u2_all.deb
6b45830be32d9174a479d9850e987627067c6a6ca3366e2c3d3b6379b0f8085c 3198870 linux-manual-4.9_4.9.168-1+deb9u2_all.deb
d14c5fe9f20433bc2f947dea5d3a6ed6659213214887135ecf81604654407356 96825676 linux-source-4.9_4.9.168-1+deb9u2_all.deb
a37a8d788336c9305018a1eabc1f15f0625e670f70ebd0105668f66a8bd0d1f9 678004 linux-support-4.9.0-9_4.9.168-1+deb9u2_all.deb
d93897444ec7bd709287bc2acff6a89b31d02fbee77d3f25a816c05a316b3614 41613 linux_4.9.168-1+deb9u2_all.buildinfo
Files:
11d8ba1abf4d542429afda6d6286ba53 123228 kernel optional linux_4.9.168-1+deb9u2.dsc
efe7cbb8d928fe85597f60fca8ebb6e5 94774584 kernel optional linux_4.9.168.orig.tar.xz
717e9b64d520252d423d1445028ef3eb 2732028 kernel optional linux_4.9.168-1+deb9u2.debian.tar.xz
51b6346a6341ddddce639ee25b4e0c01 36957 kernel optional linux_4.9.168-1+deb9u2_source.buildinfo
7db9df654116a269453a56872273074e 12499332 doc optional linux-doc-4.9_4.9.168-1+deb9u2_all.deb
5759631401b852f584a6a27a8e38c5fc 5740880 kernel optional linux-headers-4.9.0-9-common-rt_4.9.168-1+deb9u2_all.deb
801b829bd43813ca60ff796160adfd23 7674072 kernel optional linux-headers-4.9.0-9-common_4.9.168-1+deb9u2_all.deb
e922a7d752d120739edfc136072ddff0 3198870 doc optional linux-manual-4.9_4.9.168-1+deb9u2_all.deb
7dffc0e4666b9a979fcec3629cb933f3 96825676 kernel optional linux-source-4.9_4.9.168-1+deb9u2_all.deb
243c25f44f29f58fb29b2e93455fd889 678004 devel optional linux-support-4.9.0-9_4.9.168-1+deb9u2_all.deb
33e1e411d9efe2880ed1d1b061f99c20 41613 kernel optional linux_4.9.168-1+deb9u2_all.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlzZ+MsACgkQ57/I7JWG
EQmWdhAAu5l6jggBPmftnbk7W/oeoJHsRz+khKDdB3uHVPgl5GfLBixknTe0/bG5
wlFnMm2F2N3rFY1oeOv9JE4YOgGRNk50blBrWkKiTGcz9+g+xIbrewpp63o+O9zW
AtZhO55V9jcMuqRBoKEZOgyI+g8jDKkzkILsVg8dH+xPl7uIWAkBXEQ5oZIe+7rH
pKedXStpEcAtuUrTsANa/VduAhyULylNWm/8v0bUCt9Qf4oiHG9IxL09YVhsXtzw
DDhdOm7/mRqnxdOfVnAErceHW+PAMaCgkQfV1O6iRu+q9plILoCzLmc+E7LfXUOo
0DjQypgQGAHFfptq+nwHydiE7w71NJIzrjOjG1ZFb5OnbiBhI5TxpjyYD484aEvQ
ZbJ+WlA+KEMOVMNU4hjJnHLJHFajs7lG183mf5Tqzs3JTqPTpkrpA3jX6+aPBIhN
qWVfWV+eBaAU2pXj032YT+Qv8RiYI6XXkcsGnoDlBLgWQQWpPQaVZXw0CfAqByKz
WUVBCfXRls5dY5R1v43ZhC4mV3J/1+e6pV/+CVWYoubGQmeFxo1UlVg71Ap38K7l
OLy+4uDsuWLGog0ZILKzk+jod1cgVB2lxaqBwuy6YRMYozpwLVJJUjYVMFCNiBSj
9FZxAyxa5m4WY+qBg10JLVd0sHPaoA2tGEm0+iOax0Da0KrzIDU=
=29tk
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: