Bug 196587 - BLKZEROOUT on dm-crypt container cause OOM / kernel panic
Summary: BLKZEROOUT on dm-crypt container cause OOM / kernel panic
Status: NEW
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: LVM2/DM (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Alasdair G Kergon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-04 19:53 UTC by Tom Yan
Modified: 2017-08-05 10:10 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.12.3
Subsystem:
Regression: No
Bisected commit-id:

Attachments
OOM / kernel panic screenshot (4.07 MB, image/jpeg)
2017-08-04 19:53 UTC, Tom Yan 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Tom Yan 2017-08-04 19:53:14 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.