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
| ||
|
Date: Tue, 25 Oct 2022 20:45:45 +0900 From: Yonggil Song <yonggil.song@...sung.com> To: "agk@...hat.com" <agk@...hat.com>, "snitzer@...nel.org" <snitzer@...nel.org>, "dm-devel@...hat.com" <dm-devel@...hat.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: [PATCH] dm table: fix typo in comment integity -> integrity in comment for dm_table_get_integrity_disk Signed-off-by: Yonggil Song <yonggil.song@...sung.com> --- drivers/md/dm-table.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c index d8034ff0cb24..be0a9024923d 100644 --- a/drivers/md/dm-table.c +++ b/drivers/md/dm-table.c @@ -1151,7 +1151,7 @@ static struct gendisk * dm_table_get_integrity_disk(struct dm_table *t) * underlying devices have an integrity profile. But all devices may * not have matching profiles (checking all devices isn't reliable * during table load because this table may use other DM device(s) which - * must be resumed before they will have an initialized integity + * must be resumed before they will have an initialized integrity * profile). Consequently, stacked DM devices force a 2 stage integrity * profile validation: First pass during table load, final pass during * resume. -- 2.34.1
Powered by blists - more mailing lists