linux-kernel - Re: [PATCH 2/2] KVM: x86: Fix a typo about the usage of kvcalloc()

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <26cda02a-af8d-5976-9d3a-a595c0ed2fb6@huawei.com>
Date:   Thu, 3 Nov 2022 12:18:24 +0800
From:   "liaochang (A)" <liaochang1@...wei.com>
To:     Bagas Sanjaya <bagasdotme@...il.com>
CC:     <seanjc@...gle.com>, <pbonzini@...hat.com>, <tglx@...utronix.de>,
        <mingo@...hat.com>, <bp@...en8.de>, <dave.hansen@...ux.intel.com>,
        <hpa@...or.com>, <x86@...nel.org>, <kvm@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] KVM: x86: Fix a typo about the usage of kvcalloc()



在 2022/11/3 10:37, Bagas Sanjaya 写道:
> This isn't typofix as suggested from the patch subject, right?

Well, since kvcalloc uses the product of 1st and 2nd argument to do allocation,
hence current code supposes to work well, but the usage is obviously no sense,
that is why i name it a 'typo' and make it correct ;)

-- 
BR,
Liao, Chang