From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Caleb Sander Mateos <csander@purestorage.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Anuj Gupta <anuj20.g@samsung.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 0/3] block: zero non-PI portion of auto integrity buffer
Date: Thu, 08 Jan 2026 16:37:11 -0500 [thread overview]
Message-ID: <yq11pjzrdlg.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260108172212.1402119-1-csander@purestorage.com> (Caleb Sander Mateos's message of "Thu, 8 Jan 2026 10:22:09 -0700")
Caleb,
> For block devices capable of storing "opaque" metadata in addition to
> protection information, ensure the opaque bytes are initialized by the
> block layer's auto integrity generation. Otherwise, the contents of
> kernel memory can be leaked via the storage device. Two follow-on
> patches simplify the bio_integrity_prep() code a bit.
LGTM.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen
next prev parent reply other threads:[~2026-01-08 21:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 17:22 [PATCH v2 0/3] block: zero non-PI portion of auto integrity buffer Caleb Sander Mateos
2026-01-08 17:22 ` [PATCH v2 1/3] " Caleb Sander Mateos
2026-01-09 5:51 ` Christoph Hellwig
2026-01-08 17:22 ` [PATCH v2 2/3] block: replace gfp_t with bool in bio_integrity_prep() Caleb Sander Mateos
2026-01-08 22:28 ` Anuj gupta
2026-01-09 5:52 ` Christoph Hellwig
2026-01-08 17:22 ` [PATCH v2 3/3] block: use pi_tuple_size in bi_offload_capable() Caleb Sander Mateos
2026-01-08 22:39 ` Anuj gupta
2026-01-09 5:53 ` Christoph Hellwig
2026-01-08 21:37 ` Martin K. Petersen [this message]
2026-01-09 13:57 ` [PATCH v2 0/3] block: zero non-PI portion of auto integrity buffer Jens Axboe
2026-01-09 16:29 ` Caleb Sander Mateos
2026-01-10 17:21 ` Jens Axboe
2026-01-10 17:28 ` Jens Axboe
2026-01-10 20:05 ` Caleb Sander Mateos
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=yq11pjzrdlg.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox