[Bug 1823037] Re: amd_iommu possible data corruption
@MasterCATZ, please check this with the 20.04 5.4 kernel. If it's still an issue could you please file a separate kernel bug for your corruption issue? ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
seems I finally found the real issue in the bios of my Gigabyte x570 UD , when I have 4G encode option enabled I have silent data corruption ( or at least if its enabled along side with IOMMU ) I need to make another array that I can kill to keep testing with , but I can literally go into the bios enable 4G reboot then start a zfs scrub and instantly have crc errors pop up everywhere , reboot disable do a scrub and it's all good , seems to only kick in when multiple disks are in use In the past ~2012 with my Gigabyte F2A85x-UP4 AMD A10 5800k I also had data issues with IOMMU enabled ... never had issues with my intel i7 4790k build , so it could very well just be AMD IOMMU that is causing it for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
Running Ubuntu 19.10 5.4.3-050403-generic Ryzen 3900x GA x570 UD mainboard DDR 3200 , I have been getting data corruption on my 4x SSD on Sata ports ( btrfs/ext4) disks running from my LSI / Avago SAS Raid 9302-16e 12Gb/s PCIe 3.0 controller (btrfs/EXT4) and all my disks running from my HBA (zfs) I started off with PCI-e gen 4 dropped it to gen 3 as that is what my raid controller is as not using a NVMe yet all 64 gig Memory test's good and HDD's test good if tested individually anymore than 8 being accessed at a time they fail being 3 separate controllers and multiple disks I am leading towards a software issue and I remember having data issues before when I had my a10-5800k and that was solved by disabling iommu , I had no issues with this setup while running my intel 4790k -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
This bug is awaiting verification that the 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- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
** Changed in: linux (Ubuntu Cosmic) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
** Tags added: cscc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
This bug was fixed in the package linux - 5.0.0-21.22 --- linux (5.0.0-21.22) disco; urgency=medium * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when offsets are used - platform/x86: pmc_atom: Drop __initconst on dmi table - NFSv4.1 fix incorrect return value in copy_file_range - perf/core: Fix perf_event_disable_inatomic() race - genirq: Prevent use-after-free and work list corruption - usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON - usb: dwc3: Fix default lpm_nyet_threshold value - USB: serial: f81232: fix interrupt worker not stop - USB: cdc-acm: fix unthrottle races - usb-storage: Set virt_boundary_mask to avoid SG overflows - intel_th: pci: Add Comet Lake support - iio: adc: qcom-spmi-adc5: Fix of-based
[Bug 1823037] Re: amd_iommu possible data corruption
This bug was fixed in the package linux - 4.15.0-55.60 --- linux (4.15.0-55.60) bionic; urgency=medium * linux: 4.15.0-55.60 -proposed tracker (LP: #1834954) * Request backport of ceph commits into bionic (LP: #1834235) - ceph: use atomic_t for ceph_inode_info::i_shared_gen - ceph: define argument structure for handle_cap_grant - ceph: flush pending works before shutdown super - ceph: send cap releases more aggressively - ceph: single workqueue for inode related works - ceph: avoid dereferencing invalid pointer during cached readdir - ceph: quota: add initial infrastructure to support cephfs quotas - ceph: quota: support for ceph.quota.max_files - ceph: quota: don't allow cross-quota renames - ceph: fix root quota realm check - ceph: quota: support for ceph.quota.max_bytes - ceph: quota: update MDS when max_bytes is approaching - ceph: quota: add counter for snaprealms with quota - ceph: avoid iput_final() while holding mutex or in dispatch thread * QCA9377 isn't being recognized sometimes (LP: #1757218) - SAUCE: USB: Disable USB2 LPM at shutdown * hns: fix ICMP6 neighbor solicitation messages discard problem (LP: #1833140) - net: hns: fix ICMP6 neighbor solicitation messages discard problem - net: hns: fix unsigned comparison to less than zero * Fix occasional boot time crash in hns driver (LP: #1833138) - net: hns: Fix probabilistic memory overwrite when HNS driver initialized * use-after-free in hns_nic_net_xmit_hw (LP: #1833136) - net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() * hns: attempt to restart autoneg when disabled should report error (LP: #1833147) - net: hns: Restart autoneg need return failed when autoneg off * systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp) (LP: #1821625) - powerpc: sys_pkey_alloc() and sys_pkey_free() system calls - powerpc: sys_pkey_mprotect() system call * [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different (LP: #1832625) - pkey: Indicate old mkvp only if old and current mkvp are different * [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing (LP: #1832623) - s390/crypto: fix gcm-aes-s390 selftest failures * System crashes on hot adding a core with drmgr command (4.15.0-48-generic) (LP: #1833716) - powerpc/numa: improve control of topology updates - powerpc/numa: document topology_updates_enabled, disable by default * Kernel modules generated incorrectly when system is localized to a non- English language (LP: #1828084) - scripts: override locale from environment when running recordmcount.pl * [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs (LP: #1832624) - s390/zcrypt: Fix wrong dispatching for control domain CPRBs * CVE-2019-11815 - net: rds: force to destroy connection if t_sock is NULL in rds_tcp_kill_sock(). * Sound device not detected after resume from hibernate (LP: #1826868) - drm/i915: Force 2*96 MHz cdclk on glk/cnl when audio power is enabled - drm/i915: Save the old CDCLK atomic state - drm/i915: Remove redundant store of logical CDCLK state - drm/i915: Skip modeset for cdclk changes if possible * Handle overflow in proc_get_long of sysctl (LP: #1833935) - sysctl: handle overflow in proc_get_long * Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle (LP: #1808957) - Revert "UBUNTU: SAUCE: pci/nvme: prevent WDC PC SN720 NVMe from entering D3 and being disabled" - Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when suspending" - Revert "UBUNTU: SAUCE: pci: prevent Intel NVMe SSDPEKKF from entering D3" - Revert "SAUCE: nvme: add quirk to not call disable function when suspending" - Revert "SAUCE: pci: prevent sk hynix nvme from entering D3" - PCI: PM: Avoid possible suspend-to-idle issue - PCI: PM: Skip devices in D0 for suspend-to-idle - nvme-pci: Sync queues on reset - nvme: Export get and set features - nvme-pci: Use host managed power state for suspend * linux v4.15 ftbfs on a newer host kernel (e.g. hwe) (LP: #1823429) - selinux: use kernel linux/socket.h for genheaders and mdp * 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all (LP: #1830433) - x86/mm/pat: Disable preemption around __flush_tlb_all() - x86/mm: Drop usage of __flush_tlb_all() in kernel_physical_mapping_init() - x86/mm: Disable ioremap free page handling on x86-PAE - ioremap: Update pgtable free interfaces with addr - x86/mm: Add TLB purge to free pmd/pte page interfaces - x86/init: fix build with CONFIG_SWAP=n - x86/mm: provide pmdp_establish() helper - x86/mm: Use WRITE_ONCE() when setting PTEs * hinic: fix oops due to race in set_rx_mode (LP: #1832048) - hinic: fix a bug in
[Bug 1823037] Re: amd_iommu possible data corruption
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
SRU Request submitted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
** Description changed:
[Impact]
- iommu/amd: Reserve exclusion range in iova-domain
-
- BugLink: https://bugs.launchpad.net/bugs/1823037
-
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
-
- Treat exclusion ranges as reserved regions in the iommu-core
- to fix the problem.
-
- Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
- Signed-off-by: Joerg Roedel
- Reviewed-by: Gary R Hook
-
- (cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
- Signed-off-by: Jeffrey Lane
-
- iommu/amd: Set exclusion range correctly
-
- BugLink: https://bugs.launchpad.net/bugs/1823037
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
-
- Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
- Signed-off-by: Joerg Roedel
-
- (cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
- Signed-off-by: Jeffrey Lane
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range
correctly
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range
in iova-domain
fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range
correctly
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range
correctly
Note Disco only required f1cd47fe12 as the first patch was already
picked in LP: #1830934
Not necessary for Eoan as these are already upstream in 5.2-rc1
[Regression Risk]
- Low,this adds memory protection to the driver and has already been acked
upstream and tested by Dell for 24 hours with no failures noted.
+ Low,this adds memory protection to the driver and has already been applied
upstream and tested by Dell for 24 hours with no failures noted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823037
Title:
amd_iommu possible data corruption
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
** Description changed:
[Impact]
iommu/amd: Reserve exclusion range in iova-domain
BugLink: https://bugs.launchpad.net/bugs/1823037
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
Signed-off-by: Joerg Roedel
Reviewed-by: Gary R Hook
(cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
Signed-off-by: Jeffrey Lane
iommu/amd: Set exclusion range correctly
BugLink: https://bugs.launchpad.net/bugs/1823037
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
Signed-off-by: Joerg Roedel
(cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
Signed-off-by: Jeffrey Lane
-
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
ee4a87e6b7fe7e039c1f02c50c53da63e4270732
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range
in iova-domain
fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range
correctly
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range
correctly
Note Disco only required f1cd47fe12 as the first patch was already
picked in LP: #1830934
Not necessary for Eoan as these are already upstream in 5.2-rc1
[Regression Risk]
- Low,this adds memory range protection to the driver and has already been
acked upstream.
+ Low,this adds memory protection to the driver and has already been acked
upstream and tested by Dell for 24 hours with no failures noted.
** Description changed:
[Impact]
iommu/amd: Reserve exclusion range in iova-domain
BugLink: https://bugs.launchpad.net/bugs/1823037
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
Signed-off-by: Joerg Roedel
Reviewed-by: Gary R Hook
(cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
Signed-off-by: Jeffrey Lane
iommu/amd: Set exclusion range correctly
BugLink: https://bugs.launchpad.net/bugs/1823037
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
Signed-off-by: Joerg Roedel
(cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
Signed-off-by: Jeffrey Lane
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
- ee4a87e6b7fe7e039c1f02c50c53da63e4270732
+ ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range
correctly
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
[Bug 1823037] Re: amd_iommu possible data corruption
** Description changed:
[Impact]
- iommu/amd: Set exclusion range correctly
-
- BugLink: https://bugs.launchpad.net/bugs/1823037
-
- The exlcusion range limit register needs to contain the
- base-address of the last page that is part of the range, as
- bits 0-11 of this register are treated as 0xfff by the
- hardware for comparisons.
-
- So correctly set the exclusion range in the hardware to the
- last page which is _in_ the range.
-
- Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
- Signed-off-by: Joerg Roedel
-
- (cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
- Signed-off-by: Jeffrey Lane
-
iommu/amd: Reserve exclusion range in iova-domain
BugLink: https://bugs.launchpad.net/bugs/1823037
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
Signed-off-by: Joerg Roedel
Reviewed-by: Gary R Hook
(cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
Signed-off-by: Jeffrey Lane
- [Test Case]
+ iommu/amd: Set exclusion range correctly
+
+ BugLink: https://bugs.launchpad.net/bugs/1823037
+
+ The exlcusion range limit register needs to contain the
+ base-address of the last page that is part of the range, as
+ bits 0-11 of this register are treated as 0xfff by the
+ hardware for comparisons.
+
+ So correctly set the exclusion range in the hardware to the
+ last page which is _in_ the range.
+
+ Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
+ Signed-off-by: Joerg Roedel
+
+ (cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
+ Signed-off-by: Jeffrey Lane
+
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
ee4a87e6b7fe7e039c1f02c50c53da63e4270732
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range
in iova-domain
fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range
correctly
-
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range
correctly
-
- Note Disco only required f1cd47fe12 as the first patch was already picked in
LP: #1830934
+ Note Disco only required f1cd47fe12 as the first patch was already
+ picked in LP: #1830934
Not necessary for Eoan as these are already upstream in 5.2-rc1
[Regression Risk]
- Low,
- Only affects the amd_iommu driver:
- drivers/iommu/amd_iommu*
+ Low,this adds memory range protection to the driver and has already been
acked upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823037
Title:
amd_iommu possible data corruption
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
** Description changed:
[Impact]
iommu/amd: Set exclusion range correctly
-
+
BugLink: https://bugs.launchpad.net/bugs/1823037
-
+
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
-
+
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
-
+
Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
Signed-off-by: Joerg Roedel
-
+
(cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
Signed-off-by: Jeffrey Lane
+ iommu/amd: Reserve exclusion range in iova-domain
- iommu/amd: Reserve exclusion range in iova-domain
-
BugLink: https://bugs.launchpad.net/bugs/1823037
-
+
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.
-
+
Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.
-
+
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
Signed-off-by: Joerg Roedel
Reviewed-by: Gary R Hook
-
+
(cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
Signed-off-by: Jeffrey Lane
[Test Case]
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
- Bionic
+ Bionic:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
+ b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range
in iova-domain
+ ee4a87e6b7fe7e039c1f02c50c53da63e4270732
+
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
+ 0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range
in iova-domain
+ fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range
correctly
+
+
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
+ 6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range
correctly
- Note Disco only required f1cd47fe12 as the first patch was already
- picked in LP: #1830934
- Not necessary for Eoan, they're in 5.2-rc1.
+ Note Disco only required f1cd47fe12 as the first patch was already picked in
LP: #1830934
+
+ Not necessary for Eoan as these are already upstream in 5.2-rc1
[Regression Risk]
Low,
Only affects the amd_iommu driver:
drivers/iommu/amd_iommu*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823037
Title:
amd_iommu possible data corruption
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
** Description changed:
[Impact]
+ iommu/amd: Reserve exclusion range in iova-domain
If a device has an exclusion range specified in the IVRS table, this region
needs to be reserved in the iova-domain of that device. This hasn't happened
until now and can cause data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core to fix the
problem.
- This is a clean cherry pick from mainline of
8aafaaf2212192012f5bae305bb31cdf7681d777
- 3c677d206210f53a4be972211066c0f1cd47fe12
+ iommu/amd: Set exclusion range correctly
+
+ The exlcusion range limit register needs to contain the
+ base-address of the last page that is part of the range, as
+ bits 0-11 of this register are treated as 0xfff by the
+ hardware for comparisons.
+
+ So correctly set the exclusion range in the hardware to the
+ last page which is _in_ the range.
[Test Case]
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic
- https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
- Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
- Disco:
- https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
+ https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
+ Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
+ Disco:
+ https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
- I do not believe these are necessary for Eoan, 5.1 should already
- include them but it's worth verifying that as I started work on this
- prior to Eoan's cycle.
+ Note Disco only required f1cd47fe12 as the first patch was already
+ picked in LP: #1830934
+
+ Not necessary for Eoan, they're in 5.2-rc1.
[Regression Risk]
+ Low,
Only affects the amd_iommu driver:
drivers/iommu/amd_iommu*
** Description changed:
[Impact]
- iommu/amd: Reserve exclusion range in iova-domain
- If a device has an exclusion range specified in the IVRS table, this region
needs to be reserved in the iova-domain of that device. This hasn't happened
until now and can cause data corruption on data transfered with these devices.
-
- Treat exclusion ranges as reserved regions in the iommu-core to fix the
- problem.
-
iommu/amd: Set exclusion range correctly
-
+
+ BugLink: https://bugs.launchpad.net/bugs/1823037
+
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register are treated as 0xfff by the
hardware for comparisons.
-
+
So correctly set the exclusion range in the hardware to the
last page which is _in_ the range.
+
+ Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU
MMIO space')
+ Signed-off-by: Joerg Roedel
+
+ (cherry picked from commit 3c677d206210f53a4be972211066c0f1cd47fe12)
+ Signed-off-by: Jeffrey Lane
+
+
+ iommu/amd: Reserve exclusion range in iova-domain
+
+ BugLink: https://bugs.launchpad.net/bugs/1823037
+
+ If a device has an exclusion range specified in the IVRS
+ table, this region needs to be reserved in the iova-domain
+ of that device. This hasn't happened until now and can cause
+ data corruption on data transfered with these devices.
+
+ Treat exclusion ranges as reserved regions in the iommu-core
+ to fix the problem.
+
+ Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory
mapping requirements for devices')
+ Signed-off-by: Joerg Roedel
+ Reviewed-by: Gary R Hook
+
+ (cherry picked from commit 8aafaaf2212192012f5bae305bb31cdf7681d777)
+ Signed-off-by: Jeffrey Lane
[Test Case]
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range
correctly
These can be picked from my branches here:
Bionic
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic
1823037-amd_iommu-cherrypick
Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic
1823037-amd_iommu-cherrypick
Disco:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco
1823037-amd_iommu-cherrypick
Note Disco only required f1cd47fe12 as the first patch was already
picked in LP: #1830934
Not necessary for Eoan, they're in 5.2-rc1.
[Regression Risk]
- Low,
+ Low,
Only affects the amd_iommu driver:
drivers/iommu/amd_iommu*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Bug 1823037] Re: amd_iommu possible data corruption
** Description changed: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 3c677d206210f53a4be972211066c0f1cd47fe12 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly + These can be picked from my branches here: + Bionic + https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic + Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic + Disco: + https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco + + I do not believe these are necessary for Eoan, 5.1 should already + include them but it's worth verifying that as I started work on this + prior to Eoan's cycle. + [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
** Description changed: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. - - Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. - This is a clean cherry pick from mainline of - 8aafaaf2212192012f5bae305bb31cdf7681d777 + Treat exclusion ranges as reserved regions in the iommu-core to fix the + problem. + This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 + 3c677d206210f53a4be972211066c0f1cd47fe12 [Test Case] - [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain + 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly [Regression Risk] Only affects the amd_iommu driver: - drivers/iommu/amd_iommu* + drivers/iommu/amd_iommu* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
** Tags added: verification-done-bionic verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
All three test kernels have passed 24+ hour testing. ** Tags added: verification-done-bionic ** Tags removed: verification-done-bionic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
Hi Jerry, The test kernels are located here and have "1" appended to them. https://people.canonical.com/~jlane/testkernels/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
Jeff, The second patch improves the fix against the amount of memory in the system. We still need both patches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
So I'm a bit confused because I've been told that A: additional patches are necessary to solve the issue, and B: that the issue is solved without those additional patches. When you did the test, were you using the older, failing firmware levels, or have you updated to the patched firmware that is also part of this fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
Confirming that I was unable to reproduce the issue on linux- image-4.15.0-46-generic (4.15.0-46.49) from the test kernels repository with my test setup. Previously I was able to cause filesystem corruption within 1 hour of testing under a test load (verified by btrfs checksums) across all disks on 2 different 32-core systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
An additional patch has been identified that will be needed to solve this issue. https://github.com/torvalds/linux/commit/3c677d206210f53a4be972211066c0f1cd47fe12 #diff-083bf3d2f128b616e730b7f9f8fc65c4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
Test kernels are up here: https://people.canonical.com/~jlane/testkernels/ Please test each and report back ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
related branch https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco/+ref/amd-iommu-cherrypick ** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: Jeff Lane (bladernr) Status: In Progress ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jeff Lane (bladernr) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
