From: Kees Cook <keescook@chromium.org>
To: Joonwon Kang <kjw1627@gmail.com>
Cc: re.emese@gmail.com, kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] randstruct: fix a bug in is_pure_ops_struct()
Date: Tue, 30 Jul 2019 10:11:19 -0700 [thread overview]
Message-ID: <201907301008.622218EE5@keescook> (raw)
In-Reply-To: <20190727155841.GA13586@host>
On Sun, Jul 28, 2019 at 12:58:41AM +0900, Joonwon Kang wrote:
> Before this, there were false negatives in the case where a struct
> contains other structs which contain only function pointers because
> of unreachable code in is_pure_ops_struct().
Ah, very true. Something like:
struct internal {
void (*callback)(void);
};
struct wrapper {
struct internal foo;
void (*other_callback)(void);
};
would have not been detected as is_pure_ops_struct()?
How did you notice this? (Are there cases of this in the kernel?)
> Signed-off-by: Joonwon Kang <kjw1627@gmail.com>
Applied; thanks!
-Kees
> ---
> scripts/gcc-plugins/randomize_layout_plugin.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/scripts/gcc-plugins/randomize_layout_plugin.c b/scripts/gcc-plugins/randomize_layout_plugin.c
> index 6d5bbd31db7f..a123282a4fcd 100644
> --- a/scripts/gcc-plugins/randomize_layout_plugin.c
> +++ b/scripts/gcc-plugins/randomize_layout_plugin.c
> @@ -443,13 +443,12 @@ static int is_pure_ops_struct(const_tree node)
> if (node == fieldtype)
> continue;
>
> - if (!is_fptr(fieldtype))
> - return 0;
> -
> - if (code != RECORD_TYPE && code != UNION_TYPE)
> - continue;
> + if (code == RECORD_TYPE || code == UNION_TYPE) {
> + if (!is_pure_ops_struct(fieldtype))
> + return 0;
> + }
>
> - if (!is_pure_ops_struct(fieldtype))
> + if (!is_fptr(fieldtype))
> return 0;
> }
>
> --
> 2.17.1
>
--
Kees Cook
next prev parent reply other threads:[~2019-07-30 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 15:58 [PATCH] randstruct: fix a bug in is_pure_ops_struct() Joonwon Kang
2019-07-30 17:11 ` Kees Cook [this message]
2019-07-31 16:25 ` Joonwon Kang
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=201907301008.622218EE5@keescook \
--to=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kjw1627@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=re.emese@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).