[UBUNTU 22.04] s390/cpum_cf: make crypto counters upward compatible

[bugproxy]

SRU Justification:

[ Impact ]

 * The CPU Measurement Facility (CPU MF) crypto counter set
   is not listed in the device sysfs tree - it's not exported
   in the sysfs directory /sys/devices/cpum_cf/events.

 * The attribute files for each CPU-MF counter defined
   in the crypto counter set is missing.

 * This is caused by the counter second version number of CPU MF
   hardware being incremented on new machines.

 * This causes a sanity check to fail,
   but the counters are supported by hardware.

 * The solution is to remove the upper limit in counter second
   version number check.

[ Fix ]

 * f10933cbd2df f10933cbd2dfddf6273698a45f76db9bafd8150f
   "s390/cpum_cf: make crypto counters upward compatible across machine types"

 * The fix was upstream accepted with kernel v6.10(-rc1).

 * Upstream commit applies cleanly on noble master-next,
   but needed to be backported to jammy master-next due to different code
   and context in kernel 5.15.

[ Test Plan ]

 * Run the following commands on a new machine generation:
   (hence only doable by IBM)
   # ls -l /sys/devices/cpum_cf/events/ | grep AES

 * If the output is empty than this patch is required.

 * With a patched kernel the output should be like:
   # ls /sys/devices/cpum_cf/events/ | grep AES
   AES_BLOCKED_CYCLES
   AES_BLOCKED_FUNCTIONS
   AES_CYCLES
   AES_FUNCTIONS

[ Where problems could occur ]

 * This affects s390x only - CPU MF is s390-specific,
   and only s390 specific code is modified.

 * And it furthermore is limited to the crypto counter set
   of CPU MF.

 * So any impact is likely limited to hardware crypto counters
   on s390x only.

 * In s390/kernel/perf_cpum_cf.c the else if case got changed from
   explicitly checking for 6 or 7 to >= 6 which seems to require
   attention for future 8 and more cases.

 * In s390/kernel/perf_cpum_cf_events.c the switch (ci.csvn) statement
   was changed to an if / else if with similar logic.
   Again attentioin for any potential future cases >= 8.

 * It does not look like currently used cases (1..5 and 6..7)
   are affected by the modification, just >7.

 * Test build of patched jammy and noble s390x kernels were build
   and are avaiable here:
   https://launchpad.net/~fheimes/+archive/ubuntu/lp2074380

[ Other Info ]

 * Since the code/fix was upstream accepted with kernel v6.10(-rc1)
   it does not affect the current development release oracular.

 * This SRU can also be seen under the umbrella of new
    hardware enablement.

 * Since it requires special hw, the verification needs to be
   done by IBM.

__________

Description: kernel: s390/cpum_cf: make crypto counters upward compatible

Symptom: The CPU Measurement facility crypto counter set is not
               listed in the device sysfs tree.

Problem: The CPU Measurement facility crypto counter set is not
               exported in the sysfs directory
               /sys/devices/cpum_cf/events.
               The attribute files for each CPU-MF counter defined
               in the crypto counter set is missing. This is caused
               by the counter second version number of the CPU
               Measurement Facility hardware being incremented on
               new machines. This causes a sanity check to fail,
               but the counters are supported by hardware.

Solution: Remove upper limit in counter second version number
               check.

Reproduction: Run command on a new machine generation:
                # ls -l /sys/devices/cpum_cf/events/ | grep AES
                #
               If the output is empty than this patch is required.
               The output should be:
                # ls /sys/devices/cpum_cf/events/ | grep AES
                AES_BLOCKED_CYCLES
                AES_BLOCKED_FUNCTIONS
                AES_CYCLES
                AES_FUNCTIONS
                #

Upstream-ID of fix: f10933cbd2dfddf6273698a45f76db9bafd8150f

[Frank Heimes (fheimes)]

The commit applies fine to the noble master-next tree (kernel 6.8),
and a test build was triggered here: https://launchpad.net/~fheimes/+archive/ubuntu/lp2074380

However, the cpumf code in jammy master-next (kernel 5.15) is quite different.
git blame tells me that probably the following commits are needed as well:
111783-1a33aee1dc24 s390/cpum_cf: remove function validate_ctr_auth() by inline code
111784-9ae9b868aeaa s390/cpum_cf: provide counter number to validate_ctr_version()
111785:46c4d945ea1f s390/cpum_cf: introduce static CPU counter facility information
but they (first of all 46c4d945ea1f) also do not apply cleanly.

Would you please let us know a minimal set of patches (based on your insights of the code) that let us apply f10933cbd2df to the jammy master-next tree (git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy --branch master-next --single-branch)
or alternatively a backport of f10933cbd2df to this tree?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2024-08-01 04:53 EDT-------
After a fews tries to fix up the prereq patches, I decided to do a backport
of the patch in question. I have used:

$ git branch
master
* master-next
master-prep
z17-toleration
$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
[branch "master-prep"]
remote = origin
merge = refs/heads/master-prep
[branch "master-next"]
remote = origin
merge = refs/heads/master-next
$

I hope this was the right code base.

[bugproxy (bugproxy)]

------- Comment (attachment only) From <email address hidden> 2024-08-01 04:49 EDT-------

[Frank Heimes (fheimes)]

Hello Thomas, thank you!
Was also my impression that a backport is probably best.
And the backport applies cleanly on jammy master-next (so yes, that is what we have to use for the next and upcoming kernel of an Ubuntu release).

Proceeding now with the kernel SRU ...

[Frank Heimes (fheimes)]

Test builds were done here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2074380

Submissions to the kernel teams mailing list was done:
https://lists.ubuntu.com/archives/kernel-team/2024-August/thread.html#152551

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux/6.8.0-48.48 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux' to 'verification-done-noble-linux'. If the problem still exists, change the tag 'verification-needed-noble-linux' to 'verification-failed-noble-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Frank Heimes (fheimes)]

I was able to successfully validate this on kernel 6.8.0-48:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
$ uname -a
Linux s1lp15 6.8.0-48-generic #48-Ubuntu SMP Fri Sep 27 13:02:00 UTC 2024 s390x s390x s390x GNU/Linux
$ ls -l /sys/devices/cpum_cf/events/ | grep AES
-r--r--r-- 1 root root 4096 Oct 2 06:22 AES_BLOCKED_CYCLES
-r--r--r-- 1 root root 4096 Oct 2 06:22 AES_BLOCKED_FUNCTIONS
-r--r--r-- 1 root root 4096 Oct 2 06:22 AES_CYCLES
-r--r--r-- 1 root root 4096 Oct 2 06:22 AES_FUNCTIONS

(hence adjusting tags accordingly)

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux/5.15.0-125.135 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy-linux' to 'verification-failed-jammy-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-aws-6.8/6.8.0-1018.19~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.8' to 'verification-failed-jammy-linux-aws-6.8'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-oracle-6.8/6.8.0-1015.15~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2024-10-16 06:27 EDT-------
I have installed the proposed kernel jammy-proposed on a new machine and can
confirm that the patch is included in the build.
The crypto counters are displayed

root@b83lp65:~# uname -a
Linux b83lp65.lnxne.boe 5.15.0-125-generic #135-Ubuntu SMP Fri Sep 27 13:52:10 UTC 2024 s390x s390x s390x GNU/Linux
root@b83lp65:~# ls -l /sys/devices/cpum_cf/events/
total 0
-r--r--r-- 1 root root 4096 Oct 16 10:13 AES_BLOCKED_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:13 AES_BLOCKED_FUNCTIONS
-r--r--r-- 1 root root 4096 Oct 16 10:13 AES_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:12 AES_FUNCTIONS
-r--r--r-- 1 root root 4096 Oct 16 10:13 CPU_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:13 DEA_BLOCKED_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:13 DEA_BLOCKED_FUNCTIONS
-r--r--r-- 1 root root 4096 Oct 16 10:13 DEA_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:12 DEA_FUNCTIONS
-r--r--r-- 1 root root 4096 Oct 16 10:13 ECC_BLOCKED_CYCLES_COUNT
-r--r--r-- 1 root root 4096 Oct 16 10:13 ECC_BLOCKED_FUNCTION_COUNT
-r--r--r-- 1 root root 4096 Oct 16 10:13 ECC_CYCLES_COUNT
-r--r--r-- 1 root root 4096 Oct 16 10:12 ECC_FUNCTION_COUNT
-r--r--r-- 1 root root 4096 Oct 16 10:13 INSTRUCTIONS
-r--r--r-- 1 root root 4096 Oct 16 10:13 L1D_DIR_WRITES
-r--r--r-- 1 root root 4096 Oct 16 10:13 L1D_PENALTY_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:13 L1I_DIR_WRITES
-r--r--r-- 1 root root 4096 Oct 16 10:13 L1I_PENALTY_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:13 PRNG_BLOCKED_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:13 PRNG_BLOCKED_FUNCTIONS
-r--r--r-- 1 root root 4096 Oct 16 10:13 PRNG_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:12 PRNG_FUNCTIONS
-r--r--r-- 1 root root 4096 Oct 16 10:13 PROBLEM_STATE_CPU_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:13 PROBLEM_STATE_INSTRUCTIONS
-r--r--r-- 1 root root 4096 Oct 16 10:13 SHA_BLOCKED_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:13 SHA_BLOCKED_FUNCTIONS
-r--r--r-- 1 root root 4096 Oct 16 10:13 SHA_CYCLES
-r--r--r-- 1 root root 4096 Oct 16 10:12 SHA_FUNCTIONS
root@b83lp65:~#

Verfication ok

[Frank Heimes (fheimes)]

Thanks for the verification, Thomas!
(I'm adjusting the tags accordingly)

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-xilinx' to 'verification-done-noble-linux-xilinx'. If the problem still exists, change the tag 'verification-needed-noble-linux-xilinx' to 'verification-failed-noble-linux-xilinx'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 6.8.0-48.48

---------------
linux (6.8.0-48.48) noble; urgency=medium

  * noble/linux: 6.8.0-48.48 -proposed tracker (LP: #2082437)

  * [SRU][Noble] Bad EPP defaults cause performance regressions on select Intel
    CPUs (LP: #2077470)
    - x86/cpu/vfm: Update arch/x86/include/asm/intel-family.h
    - cpufreq: intel_pstate: Allow model specific EPPs
    - cpufreq: intel_pstate: Update default EPPs for Meteor Lake
    - cpufreq: intel_pstate: Switch to new Intel CPU model defines
    - cpufreq: intel_pstate: Update Meteor Lake EPPs
    - cpufreq: intel_pstate: Use Meteor Lake EPPs for Arrow Lake
    - cpufreq: intel_pstate: Update Balance performance EPP for Emerald Rapids

  * power: Enable intel_rapl driver (LP: #2078834)
    - powercap: intel_rapl: Add support for ArrowLake-H platform

  * x86/vmware: Add TDX hypercall support (LP: #2077729)
    - x86/vmware: Introduce VMware hypercall API
    - x86/vmware: Add TDX hypercall support

  * Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0
    (LP: #2076866)
    - mm/mempolicy: use numa_node_id() instead of cpu_to_node()
    - mm/numa_balancing: allow migrate on protnone reference with
      MPOL_PREFERRED_MANY policy
    - mm: convert folio_estimated_sharers() to folio_likely_mapped_shared()
    - mm: factor out the numa mapping rebuilding into a new helper
    - mm: support multi-size THP numa balancing
    - mm/migrate: make migrate_misplaced_folio() return 0 on success
    - mm/migrate: move NUMA hinting fault folio isolation + checks under PTL
    - mm: fix possible OOB in numa_rebuild_large_mapping()

  * Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix
    L2 Guest hang during LTP Test (LP: #2076147)
    - mm: hold PTL from the first PTE while reclaiming a large folio

  * KOP L2 guest fails to boot with 1 core - SMT8 topology (LP: #2070329)
    - KVM: PPC: Book3S HV nestedv2: Add DPDES support in helper library for Guest
      state buffer
    - KVM: PPC: Book3S HV nestedv2: Fix doorbell emulation

  * L2 Guest migration: continuously dumping while running NFS guest migration
    (LP: #2076406)
    - KVM: PPC: Book3S HV: Fix the set_one_reg for MMCR3
    - KVM: PPC: Book3S HV: Fix the get_one_reg of SDAR
    - KVM: PPC: Book3S HV: Add one-reg interface for DEXCR register
    - KVM: PPC: Book3S HV nestedv2: Keep nested guest DEXCR in sync
    - KVM: PPC: Book3S HV: Add one-reg interface for HASHKEYR register
    - KVM: PPC: Book3S HV nestedv2: Keep nested guest HASHKEYR in sync
    - KVM: PPC: Book3S HV: Add one-reg interface for HASHPKEYR register
    - KVM: PPC: Book3S HV nestedv2: Keep nested guest HASHPKEYR in sync

  * perf build disables tracepoint support (LP: #2076190)
    - [Packaging] perf: reenable libtraceevent

  * Please backport the more restrictive XSAVES deactivation for Zen1/2 arch
    (LP: #2077321)
    - x86/CPU/AMD: Improve the erratum 1386 workaround

  * Fix alsa scarlett2 driver in 6.8 (LP: #2076402)
    - ALSA: scarlett2: Move initialisation code lower in the source
    - ALSA: scarlett2: Implement handling of the ACK notification

  * rtw89: reset IDMEM mode to preven...

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 5.15.0-125.135

---------------
linux (5.15.0-125.135) jammy; urgency=medium

  * jammy/linux: 5.15.0-125.135 -proposed tracker (LP: #2083001)

  * CVE-2024-26800
    - tls: rx: coalesce exit paths in tls_decrypt_sg()
    - tls: separate no-async decryption request handling from async
    - tls: fix use-after-free on failed backlog decryption

  * Please backport the more restrictive XSAVES deactivation for Zen1/2 arch
    (LP: #2077321)
    - x86/CPU/AMD: Improve the erratum 1386 workaround

  * Jammy update: v5.15.167 upstream stable release (LP: #2081279)
    - drm: panel-orientation-quirks: Add quirk for OrangePi Neo
    - ALSA: hda/generic: Add a helper to mute speakers at suspend/shutdown
    - ALSA: hda/conexant: Mute speakers at suspend / shutdown
    - i2c: Fix conditional for substituting empty ACPI functions
    - dma-debug: avoid deadlock between dma debug vs printk and netconsole
    - net: usb: qmi_wwan: add MeiG Smart SRM825L
    - drm/amdgpu: Fix uninitialized variable warning in amdgpu_afmt_acr
    - drm/amd/display: Assign linear_pitch_alignment even for VM
    - drm/amdgpu: fix overflowed array index read warning
    - drm/amdgpu/pm: Check the return value of smum_send_msg_to_smc
    - drm/amd/pm: fix uninitialized variable warning for smu8_hwmgr
    - drm/amd/pm: fix warning using uninitialized value of max_vid_step
    - drm/amd/pm: fix the Out-of-bounds read warning
    - drm/amdgpu: fix uninitialized scalar variable warning
    - drm/amd/pm: fix uninitialized variable warnings for vega10_hwmgr
    - drm/amdgpu: avoid reading vf2pf info size from FB
    - drm/amd/display: Check gpio_id before used as array index
    - drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6
    - drm/amd/display: Add array index check for hdcp ddc access
    - drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]
    - drm/amd/display: Check msg_id before processing transcation
    - drm/amd/display: Fix Coverity INTEGER_OVERFLOW within
      dal_gpio_service_create
    - drm/amd/amdgpu: Check tbo resource pointer
    - drm/amdgpu/pm: Fix uninitialized variable warning for smu10
    - drm/amdgpu/pm: Fix uninitialized variable agc_btc_response
    - drm/amdgpu: Fix out-of-bounds write warning
    - drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number
    - drm/amdgpu: fix ucode out-of-bounds read warning
    - drm/amdgpu: fix mc_data out-of-bounds read warning
    - drm/amdkfd: Reconcile the definition and use of oem_id in struct
      kfd_topology_device
    - apparmor: fix possible NULL pointer dereference
    - drm/amdgpu/pm: Check input value for CUSTOM profile mode setting on legacy
      SOCs
    - drm/amdgpu: fix the waring dereferencing hive
    - drm/amd/pm: check specific index for aldebaran
    - drm/amdgpu: the warning dereferencing obj for nbio_v7_4
    - drm/amd/pm: check negtive return for table entries
    - drm/amdgpu: update type of buf size to u32 for eeprom functions
    - wifi: iwlwifi: remove fw_running op
    - cpufreq: scmi: Avoid overflow of target_freq in fast switch
    - PCI: al: Check IORESOURCE_BUS existence during probe
  ...

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-gkeop/6.8.0-1002.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-gkeop' to 'verification-done-noble-linux-gkeop'. If the problem still exists, change the tag 'verification-needed-noble-linux-gkeop' to 'verification-failed-noble-linux-gkeop'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-gcp-tcpx/6.8.0-1002.3 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-gcp-tcpx' to 'verification-done-jammy-linux-gcp-tcpx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-gcp-tcpx' to 'verification-failed-jammy-linux-gcp-tcpx'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-mtk/5.15.0-1036.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-linux-mtk'. If the problem still exists, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-nvidia-tegra-igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-nvidia-tegra-5.15/5.15.0-1032.32~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-tegra-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!