[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq1r0yejgcv.fsf@ca-mkp.ca.oracle.com>
Date: Mon, 07 Nov 2022 22:05:36 -0500
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Nathan Chancellor <nathan@...nel.org>
Cc: James Smart <james.smart@...adcom.com>,
Ram Vegesna <ram.vegesna@...adcom.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
linux-scsi@...r.kernel.org, target-devel@...r.kernel.org,
Nick Desaulniers <ndesaulniers@...gle.com>,
Tom Rix <trix@...hat.com>, Kees Cook <keescook@...omium.org>,
Sami Tolvanen <samitolvanen@...gle.com>, llvm@...ts.linux.dev,
linux-kernel@...r.kernel.org, patches@...ts.linux.dev
Subject: Re: [PATCH] scsi: elx: libefc: Fix second parameter type in state
callbacks
Nathan,
> 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-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists