From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BFEB2ECDE43 for ; Fri, 19 Oct 2018 11:49:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6E92B205F4 for ; Fri, 19 Oct 2018 11:49:48 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6E92B205F4 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=altlinux.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727455AbeJSTza (ORCPT ); Fri, 19 Oct 2018 15:55:30 -0400 Received: from vmicros1.altlinux.org ([194.107.17.57]:37754 "EHLO vmicros1.altlinux.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727039AbeJSTza (ORCPT ); Fri, 19 Oct 2018 15:55:30 -0400 Received: from imap.altlinux.org (imap.altlinux.org [194.107.17.38]) by vmicros1.altlinux.org (Postfix) with ESMTP id 78CA072CC59; Fri, 19 Oct 2018 14:49:44 +0300 (MSK) Received: from sole.flsd.net (sole.flsd.net [185.75.180.6]) by imap.altlinux.org (Postfix) with ESMTPSA id 643744A4A16; Fri, 19 Oct 2018 14:49:44 +0300 (MSK) Date: Fri, 19 Oct 2018 14:49:44 +0300 From: Vitaly Chikunov To: Christoph Hellwig Cc: Alasdair Kergon , Mike Snitzer , dm-devel@redhat.com, Jonathan Corbet , Shaohua Li , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org Subject: Re: [dm-devel] [PATCH] dm: add secdel target Message-ID: <20181019114944.syemvziebwfuruof@sole.flsd.net> References: <20181014112439.8119-1-vt@altlinux.org> <20181019061945.GA7403@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20181019061945.GA7403@infradead.org> User-Agent: NeoMutt/20171215-106-ac61c7 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 18, 2018 at 11:19:45PM -0700, Christoph Hellwig wrote: > Just as a note: the name is a complete misowner, a couple overwrite > are not in any way secure deletion. So naming it this way and exposing > this as erase is a problem that is going to get back to bite us. In what way it's not secure deletion? It's secure deletion by overwriting discarded data instead of leaving it as is. Thus it's secure deletion in some way. Level of security and applicability (disks choice) is to be determined by the end user. Because nobody could guarantee absolute security. Some three letter agencies require just one pass of overwrite, some say that more than one pass does not increase security. Some hardware disks advertising secure deletion may do not much more than this target. Thus 'secure erase' is applicable in that way too. > If you really want this anyway at least give it a different way, and > do a one-time warning when th first erase comes in that it is not in > any meaninful way secure. dm-erase or dm-wipe? dm-discerase? But still provide REQ_OP_SECURE_ERASE support?