linux-kernel - Re: TRIM/UNMAP/DISCARD via ATA Passthrough

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHmME9rJVUWwwzV6GCs_jESgBPe7XPOsehVZ0kgV0a71R9jjYg@mail.gmail.com>
Date:   Sat, 17 Sep 2016 03:24:12 +0200
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     "Austin S. Hemmelgarn" <ahferroin7@...il.com>
Cc:     James Bottomley <James.Bottomley@...senpartnership.com>,
        Hannes Reinecke <hare@...e.de>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        linux-scsi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: TRIM/UNMAP/DISCARD via ATA Passthrough

On Fri, Sep 16, 2016 at 7:06 PM, Austin S. Hemmelgarn
<ahferroin7@...il.com> wrote:
> 1. UAS (not some other SCSI transport) without UNMAP support.
> 2. Supports ATA_12 or ATA_16 pass through.
> 3. ATA DEVICE IDENTIFY via SAT indicates that the device supports
> DISCARD/TRIM.
> Then we'd be matching behavior on Windows, and should probably be relatively
> safe.

This very clearly seems like a sensible plan. It's nice to learn that
someone with a USB sniffer (and not just a désassembler :P) confirms
this is what Windows is doing. I see no reason for Linux not to do the
same. Are there any remaining objections to this plan?