From: Greg KH <greg@kroah.com>
To: Joao Moreira <jmoreira@suse.de>
Cc: kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org, danielmicay@gmail.com,
keescook@chromium.org
Subject: Re: [PATCH] vgacon: fix function prototypes
Date: Wed, 14 Mar 2018 18:03:41 +0100 [thread overview]
Message-ID: <20180314170341.GA15364@kroah.com> (raw)
In-Reply-To: <20180310064059.12720-1-jmoreira@suse.de>
On Sat, Mar 10, 2018 at 03:40:59AM -0300, Joao Moreira wrote:
> It is possible to indirectly invoke functions with prototypes that do not
> match those of the respectively used function pointers by using void types.
> Despite widely used as a feature for relaxing function invocation, this
> should be avoided when possible as it may prevent the use of heuristics
> such as prototype matching-based Control-Flow Integrity, which can be used
> to prevent ROP-based attacks.
>
> Given the above, the current efforts to improve the Linux security, and the
> upcoming kernel support to compilers with CFI features, fix prototypes in
> vgacon console driver.
>
> Another similar fix can be seen in [1].
>
> [1] https://android-review.googlesource.com/c/kernel/common/+/602010
>
> Signed-off-by: João Moreira <jmoreira@suse.de>
> Acked-by: Kees Cook <keescook@chromium.org>
> Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> ---
> drivers/video/console/vgacon.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
This fails the build :(
drivers/video/console/vgacon.c:1432:15: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.con_putcs = vgacon_putcs,
^~~~~~~~~~~~
What tree should this go to? It doesn't apply at all to my tty tree,
which is where I thought it should go, so I tried a different one and
got this mess :(
confused,
greg k-h
prev parent reply other threads:[~2018-03-14 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 6:40 [PATCH] vgacon: fix function prototypes Joao Moreira
2018-03-10 15:27 ` Kees Cook
2018-03-12 14:06 ` Bartlomiej Zolnierkiewicz
2018-03-14 17:03 ` Greg KH [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=20180314170341.GA15364@kroah.com \
--to=greg@kroah.com \
--cc=danielmicay@gmail.com \
--cc=jmoreira@suse.de \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox