From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Nathan Chancellor <nathan@kernel.org>,
James Smart <james.smart@broadcom.com>,
Ram Vegesna <ram.vegesna@broadcom.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Tom Rix <trix@redhat.com>,
linux-kernel@vger.kernel.org, target-devel@vger.kernel.org,
Sami Tolvanen <samitolvanen@google.com>,
patches@lists.linux.dev, linux-scsi@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>,
Kees Cook <keescook@chromium.org>,
llvm@lists.linux.dev
Subject: Re: [PATCH] scsi: elx: libefc: Fix second parameter type in state callbacks
Date: Thu, 17 Nov 2022 13:29:34 -0500 [thread overview]
Message-ID: <166870943118.1584889.8464452752977836109.b4-ty@oracle.com> (raw)
In-Reply-To: <20221102161906.2781508-1-nathan@kernel.org>
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
prev parent reply other threads:[~2022-11-17 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 16:19 [PATCH] scsi: elx: libefc: Fix second parameter type in state callbacks Nathan Chancellor
2022-11-02 19:08 ` Kees Cook
2022-11-03 11:32 ` Ram Kishore Vegesna
2022-11-08 3:05 ` Martin K. Petersen
2022-11-17 18:29 ` Martin K. Petersen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=166870943118.1584889.8464452752977836109.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=patches@lists.linux.dev \
--cc=ram.vegesna@broadcom.com \
--cc=samitolvanen@google.com \
--cc=target-devel@vger.kernel.org \
--cc=trix@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.