summaryrefslogtreecommitdiffstats
path: root/fs/jfs
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2016-12-13 19:53:37 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2016-12-13 19:53:37 -0800
commitcdb98c2698b4af287925abcba4d77d92af82a0c3 (patch)
treec8a7a0a4897521bcfb55b16b8146fafdcf5a99c3 /fs/jfs
parentf4000cd99750065d5177555c0a805c97174d1b9f (diff)
downloadop-kernel-dev-cdb98c2698b4af287925abcba4d77d92af82a0c3.zip
op-kernel-dev-cdb98c2698b4af287925abcba4d77d92af82a0c3.tar.gz
Revert "nvme: add support for the Write Zeroes command"
This reverts commit 6d31e3ba232ea22458b2f36b6d3f2f9f11bf3fa4. This causes bootup problems for me both on my laptop and my desktop. What they have in common is that they have NVMe disks with dm-crypt, but it's not the same controller, so it's not controller-specific. Jens does not see it on his machine (also NVMe), so it's presumably something that triggers just on bootup. Possibly related to dm-crypt and the fact that I mark my luks volume with "allow-discards" in /etc/crypttab. It's 100% repeatable for me, which made it fairly straightforward to bisect the problem to this commit. Small mercies. So we don't know what the reason is yet, but the revert is needed to get things going again. Acked-by: Jens Axboe <axboe@fb.com> Cc: Chaitanya Kulkarni <chaitanya.kulkarni@hgst.com> Cc: Christoph Hellwig <hch@lst.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/jfs')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud