https://github.com/torvalds/linux
Revision 653e4d10903b092be79c804ea0570691a2e4bebb authored by catShit on 06 January 2018, 08:15:00 UTC, committed by GitHub on 06 January 2018, 08:15:00 UTC
typically TRIM cost shorter time than ERASE, so we expect max_trim as max_discard. But when ERASE timeout is too long, it did happened actually rather than theoretically.  A type of Toshiba eMMC's ERASE_TIMEOUT_MULT is too long and controller's max_busy_timeout is relatively small, then max_discard could be 0, even max_trim is available, but max_trim < max_disable can't be true, so we get a result of 0 instead of max_trim.
1 parent 89876f2
Raw File
Tip revision: 653e4d10903b092be79c804ea0570691a2e4bebb authored by catShit on 06 January 2018, 08:15:00 UTC
fix a bug refer to max_discard is 0
Tip revision: 653e4d1
.get_maintainer.ignore
Christoph Hellwig <hch@lst.de>
back to top