[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166870943118.1584889.8464452752977836109.b4-ty@oracle.com>
Date: Thu, 17 Nov 2022 13:29:34 -0500
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Nathan Chancellor <nathan@...nel.org>,
James Smart <james.smart@...adcom.com>,
Ram Vegesna <ram.vegesna@...adcom.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>
Cc: "Martin K . Petersen" <martin.petersen@...cle.com>,
Tom Rix <trix@...hat.com>, linux-kernel@...r.kernel.org,
target-devel@...r.kernel.org,
Sami Tolvanen <samitolvanen@...gle.com>,
patches@...ts.linux.dev, linux-scsi@...r.kernel.org,
Nick Desaulniers <ndesaulniers@...gle.com>,
Kees Cook <keescook@...omium.org>, llvm@...ts.linux.dev
Subject: Re: [PATCH] scsi: elx: libefc: Fix second parameter type in state callbacks
On Wed, 2 Nov 2022 09:19:06 -0700, Nathan Chancellor wrote:
> With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),
> indirect call targets are validated against the expected function
> pointer prototype to make sure the call target is valid to help mitigate
> ROP attacks. If they are not identical, there is a failure at run time,
> which manifests as either a kernel panic or thread getting killed. A
> proposed warning in clang aims to catch these at compile time, which
> reveals:
>
> [...]
Applied to 6.2/scsi-queue, thanks!
[1/1] scsi: elx: libefc: Fix second parameter type in state callbacks
https://git.kernel.org/mkp/scsi/c/3d75e766b58a
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists