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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1+2a1syAdi2R7xD@FVFF77S0Q05N>
Date:   Mon, 31 Oct 2022 11:50:03 +0000
From:   Mark Rutland <mark.rutland@....com>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     Mukesh Ojha <quic_mojha@...cinc.com>, catalin.marinas@....com,
        will@...nel.org, broonie@...nel.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] arm64: entry: Fix typo

On Sat, Oct 29, 2022 at 08:35:49PM +0700, Bagas Sanjaya wrote:
> On Sat, Oct 29, 2022 at 12:37:48PM +0530, Mukesh Ojha wrote:
> >  /*
> >   * Handle IRQ/context state management when exiting a debug exception from
> >   * kernel mode. After this function returns it is not safe to call regular
> > - * kernel code, intrumentable code, or any code which may trigger an exception.
> > + * kernel code, instrumentable code, or any code which may trigger an exception.
> >   */
> >  static void noinstr arm64_exit_el1_dbg(struct pt_regs *regs)
> >  {
> 
> What about "... it is unsafe to call regular kernel, instrumentable, or
> any other code ..." instead?

I much prefer this as-is, but with the typo fixed.

Thanks,
Mark.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ