From: Joonwon Kang <kjw1627@gmail.com> To: keescook@chromium.org Cc: re.emese@gmail.com, kernel-hardening@lists.openwall.com, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org, jinb.park7@gmail.com Subject: [PATCH 0/2] fix is_pure_ops_struct() Date: Thu, 1 Aug 2019 03:00:27 +0900 [thread overview] Message-ID: <cover.1564595346.git.kjw1627@gmail.com> (raw) Hello, This series fixes unreachable code bug and removes dead code in is_pure_ops_struct(). Thanks. Joonwon Kang (2): randstruct: fix a bug in is_pure_ops_struct() randstruct: remove dead code in is_pure_ops_struct() scripts/gcc-plugins/randomize_layout_plugin.c | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Joonwon Kang <kjw1627@gmail.com> To: keescook@chromium.org Cc: re.emese@gmail.com, kernel-hardening@lists.openwall.com, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org, jinb.park7@gmail.com Subject: [PATCH 0/2] fix is_pure_ops_struct() Date: Wed, 31 Jul 2019 18:00:27 +0000 [thread overview] Message-ID: <cover.1564595346.git.kjw1627@gmail.com> (raw) Hello, This series fixes unreachable code bug and removes dead code in is_pure_ops_struct(). Thanks. Joonwon Kang (2): randstruct: fix a bug in is_pure_ops_struct() randstruct: remove dead code in is_pure_ops_struct() scripts/gcc-plugins/randomize_layout_plugin.c | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) -- 2.17.1
next reply other threads:[~2019-07-31 18:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-31 18:00 Joonwon Kang [this message] 2019-07-31 18:00 ` [PATCH 0/2] fix is_pure_ops_struct() Joonwon Kang 2019-07-31 18:01 ` [PATCH 1/2] randstruct: fix a bug in is_pure_ops_struct() Joonwon Kang 2019-07-31 18:01 ` Joonwon Kang 2019-07-31 19:58 ` Kees Cook 2019-07-31 19:58 ` Kees Cook 2019-07-31 18:01 ` [PATCH 2/2] randstruct: remove dead code " Joonwon Kang 2019-07-31 18:01 ` Joonwon Kang 2019-07-31 19:59 ` Kees Cook 2019-07-31 19:59 ` Kees Cook 2019-08-01 13:41 ` Joonwon Kang 2019-08-01 13:41 ` 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=cover.1564595346.git.kjw1627@gmail.com \ --to=kjw1627@gmail.com \ --cc=jinb.park7@gmail.com \ --cc=keescook@chromium.org \ --cc=kernel-hardening@lists.openwall.com \ --cc=kernel-janitors@vger.kernel.org \ --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: linkBe 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.