atasmart.c | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 the read smart status command's return status
 was testing for a success/failure value that included 8
 bits that are "N/A" according to the standard, and required
 that they be zeros.  At least some drives do not fill them
 with zeros, so correct this by masking off the undefined
 bits.
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=61998
Bug-Ubuntu: https://launchpad.net/bugs/1143495

atasmart.c | 34 11 + 23 - 0 !
1 file changed, 11 insertions(+), 23 deletions(-)

 [patch 2/2] drop our own "many bad sectors" heuristic

This currently causes a lot of false positives, because in many cases our
threshold is either overly pessimistically low, or the raw value is implausibly
high. Just use the normalized values vs. threshold for now.

Bug: https://bugs.freedesktop.org/show_bug.cgi?id=25772
Bug-Ubuntu: https://launchpad.net/bugs/438136