diff options
| author | Christoph Hellwig <hch@lst.de> | 2024-06-13 10:48:11 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-08-03 08:53:20 +0200 |
| commit | 23a19655fb56f241e592041156dfb1c6d04da644 (patch) | |
| tree | 66a75153825f32a8aee14c0da7eda77e0daada1c /scripts | |
| parent | 1cfdfb965e274c2b85357b3ce6a908a5a5957c19 (diff) | |
| download | linux-23a19655fb56f241e592041156dfb1c6d04da644.tar.gz linux-23a19655fb56f241e592041156dfb1c6d04da644.tar.bz2 linux-23a19655fb56f241e592041156dfb1c6d04da644.zip | |
block: initialize integrity buffer to zero before writing it to media
[ Upstream commit 899ee2c3829c5ac14bfc7d3c4a5846c0b709b78f ]
Metadata added by bio_integrity_prep is using plain kmalloc, which leads
to random kernel memory being written media. For PI metadata this is
limited to the app tag that isn't used by kernel generated metadata,
but for non-PI metadata the entire buffer leaks kernel memory.
Fix this by adding the __GFP_ZERO flag to allocations for writes.
Fixes: 7ba1ba12eeef ("block: Block layer data integrity support")
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Link: https://lore.kernel.org/r/20240613084839.1044015-2-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions