From: Christoph Hellwig <hch@lst.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, jaegeuk@kernel.org, chao@kernel.org,
ulf.hansson@linaro.org, Adrian Hunter <adrian.hunter@intel.com>,
Daeho Jeong <daehojeong@google.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mmc@vger.kernel.org
Subject: Re: security issue: data exposure when using block layer secure erase
Date: Fri, 18 Mar 2022 10:10:54 +0100 [thread overview]
Message-ID: <20220318091054.GA31758@lst.de> (raw)
In-Reply-To: <YjIm6f6pSX1CKeqb@gmail.com>
On Wed, Mar 16, 2022 at 06:05:29PM +0000, Eric Biggers wrote:
> __blkdev_issue_discard() can break up the region into multiple bios, but I don't
> see where it actually skips parts of the region. Can you explain more
> specifically where the problem is?
You're right. We used to skip misaligned parts, but that was actually
fixed two years ago.
prev parent reply other threads:[~2022-03-18 9:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 9:37 security issue: data exposure when using block layer secure erase Christoph Hellwig
2022-03-16 9:38 ` [PATCH, alternative 1] block: remove REQ_OP_SECURE_ERASE erase Christoph Hellwig
2022-03-16 9:38 ` [PATCH alternative 2] block: fix the REQ_OP_SECURE_ERASE handling to not leak erased data Christoph Hellwig
2022-03-17 9:44 ` Ulf Hansson
2022-03-18 9:11 ` Christoph Hellwig
2022-03-18 10:36 ` Ulf Hansson
2022-03-16 18:05 ` security issue: data exposure when using block layer secure erase Eric Biggers
2022-03-17 9:57 ` Joel Granados
2022-03-18 9:10 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220318091054.GA31758@lst.de \
--to=hch@lst.de \
--cc=adrian.hunter@intel.com \
--cc=axboe@kernel.dk \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.