Bug 196587
| Summary: | BLKZEROOUT on dm-crypt container cause OOM / kernel panic | ||
|---|---|---|---|
| Product: | IO/Storage | Reporter: | Tom Yan (tom.ty89) |
| Component: | LVM2/DM | Assignee: | Alasdair G Kergon (agk) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | gmazyland |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 4.12.3 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | OOM / kernel panic screenshot | ||
Created attachment 257821 [details] OOM / kernel panic screenshot Attaching the OOM / kernel panic screenshot. Steps to reproduce: cryptsetup open /dev/sdX[Y] rand --type plain --key-file /dev/random blkdiscard -z /dev/mapper/rand Similar issue is NOT found in doing `cat /dev/zero > /dev/mapper/rand` on the same hardware and configuration. The issue has been observed on both a usb thumb drive (BOT only) and a SATA drive on a UAS adapter. For reasons I have no capacity to attach the SATA drive to an AHCI controller so I cannot confirm whether or not it occurs only to USB drives.