linux-kernel - Re: [PATCH] x86/insn-eval: Few typo fixes

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] [day] [month] [year] [list]

Date:   Sun, 21 Mar 2021 13:06:29 -0700 (PDT)
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Bhaskar Chowdhury <unixbhaskar@...il.com>
cc:     tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, x86@...nel.org,
        hpa@...or.com, jroedel@...e.de, mhiramat@...nel.org,
        gustavoars@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/insn-eval: Few typo fixes



On Mon, 22 Mar 2021, Bhaskar Chowdhury wrote:

>
> s/deterimine/determine/
> s/invalild/invalid/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>

Acked-by: Randy Dunlap <rdunlap@...radead.org>

> ---
> arch/x86/lib/insn-eval.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/lib/insn-eval.c b/arch/x86/lib/insn-eval.c
> index bb0b3fe1e0a0..fdd9226863d3 100644
> --- a/arch/x86/lib/insn-eval.c
> +++ b/arch/x86/lib/insn-eval.c
> @@ -232,7 +232,7 @@ static int resolve_default_seg(struct insn *insn, struct pt_regs *regs, int off)
>  * resolve_seg_reg() - obtain segment register index
>  * @insn:	Instruction with operands
>  * @regs:	Register values as seen when entering kernel mode
> - * @regoff:	Operand offset, in pt_regs, used to deterimine segment register
> + * @regoff:	Operand offset, in pt_regs, used to determine segment register
>  *
>  * Determine the segment register associated with the operands and, if
>  * applicable, prefixes and the instruction pointed by @insn.
> @@ -576,7 +576,7 @@ static int get_reg_offset_16(struct insn *insn, struct pt_regs *regs,
> 	 * If ModRM.mod is 0 and ModRM.rm is 110b, then we use displacement-
> 	 * only addressing. This means that no registers are involved in
> 	 * computing the effective address. Thus, ensure that the first
> -	 * register offset is invalild. The second register offset is already
> +	 * register offset is invalid. The second register offset is already
> 	 * invalid under the aforementioned conditions.
> 	 */
> 	if ((X86_MODRM_MOD(insn->modrm.value) == 0) &&
> --
> 2.31.0
>
>