public inbox for kernel-hardening@lists.openwall.com
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Oscar Carter <oscar.carter@gmx.com>
Cc: kernel-hardening@lists.openwall.com
Subject: Re: Get involved in the KSPP
Date: Fri, 15 May 2020 01:27:32 -0700	[thread overview]
Message-ID: <202005150125.8EDF28F00@keescook> (raw)
In-Reply-To: <20200514172037.GA3127@ubuntu>

On Thu, May 14, 2020 at 07:20:37PM +0200, Oscar Carter wrote:
> On Mon, May 11, 2020 at 09:15:18AM -0700, Kees Cook wrote:
> > One mostly mechanical bit of work would be this:
> > https://github.com/KSPP/linux/issues/20
> > There are likely more fixes needed to build the kernel with
> > -Wcast-function-type (especially on non-x86 kernels). So that would let
> > you learn about cross-compiling, etc.
> >
> > Let us know what you think!
> 
> Great. This task seems good to me. I'm already working on it but I would like to
> know if it's correct to compile my work against the master branch of Linus tree
> or if there is some other better branch and tree.

For doing these kinds of things I tend to recommend either the last
full release from Linus (e.g. v5.6) or, if you want, the latest -rc2
(e.g. v5.7-rc2). Both are tagged, so you can based your tree on them
easily:

$ git clone ....
$ git checkout v5.7-rc2 -b devel/cast-function-type
$ *do stuff, etc*

-- 
Kees Cook

  reply	other threads:[~2020-05-15  8:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 12:20 Get involved in the KSPP Oscar Carter
2020-05-11 16:15 ` Kees Cook
2020-05-14 17:20   ` Oscar Carter
2020-05-15  8:27     ` Kees Cook [this message]
2020-05-16  7:25       ` Oscar Carter

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=202005150125.8EDF28F00@keescook \
    --to=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=oscar.carter@gmx.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