Kernel-hardening archive on lore.kernel.org
 help / color / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Kassad <aashad940@gmail.com>, kernel-hardening@lists.openwall.com
Subject: Re: Contributing to KSPP newbie
Date: Sat, 30 Nov 2019 08:54:07 -0800
Message-ID: <201911300853.4F17BA5C@keescook> (raw)
In-Reply-To: <201911300846.E8606B5B2@keescook>

On Sat, Nov 30, 2019 at 08:48:23AM -0800, Kees Cook wrote:
> On Fri, Nov 29, 2019 at 11:29:13AM +0000, Mark Rutland wrote:
> > On Thu, Nov 28, 2019 at 11:39:11PM -0500, Kassad wrote:
> > > Hey Kees,
> > > 
> > > I'm 3rd university student interested in learning more about the linux kernel.
> > > I'm came across this subsystem, since it aligns with my interest in security.
> > > Do you think as a newbie this task https://github.com/KSPP/linux/issues/11 will
> > > be a good starting point?
> > 
> > I think this specific task (Disable arm32 kuser helpers) has already
> > been done, and the ticket is stale.
> 
> Oh, thank you! I entirely missed both of these commits. I've added
> notes to the bug and closed it.
> 
> > 
> > On arm CONFIG_KUSER_HELPERS can be disabled on kernels that don't need
> > to run on HW prior to ARMv6. See commit:
> > 
> >   f6f91b0d9fd971c6 ("ARM: allow kuser helpers to be removed from the vector page")
> > 
> > On arm64, CONFIG_KUSER_HELPERS can be disabled on any kernel. See
> > commit:
> > 
> >   1b3cf2c2a3f42b ("arm64: compat: Add KUSER_HELPERS config option")
> 
> (Typo: a1b3cf2c2a3f42b)

Typo typo: af1b3cf2c2a3f42bbb680812ff1bbd715ac8af69

> 
> -Kees
> 
> > 
> > Thanks,
> > Mark.
> 
> -- 
> Kees Cook

-- 
Kees Cook

  reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29  4:39 Kassad
2019-11-29 11:29 ` Mark Rutland
2019-11-29 17:32   ` Kassad
2019-11-30 17:11     ` Kees Cook
2019-11-30 16:48   ` Kees Cook
2019-11-30 16:54     ` Kees Cook [this message]
2019-12-02 10:47     ` Mark Rutland

Reply instructions:

You may reply publically 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=201911300853.4F17BA5C@keescook \
    --to=keescook@chromium.org \
    --cc=aashad940@gmail.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=mark.rutland@arm.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

Kernel-hardening archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernel-hardening/0 kernel-hardening/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernel-hardening kernel-hardening/ https://lore.kernel.org/kernel-hardening \
		kernel-hardening@lists.openwall.com
	public-inbox-index kernel-hardening

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.openwall.lists.kernel-hardening


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git