All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Micay <danielmicay@gmail.com>
To: Brad Spengler <spender@grsecurity.net>
Cc: kernel-hardening@lists.openwall.com, pageexec@freemail.hu
Subject: Re: [kernel-hardening] Stop the plagiarism
Date: Sun, 04 Jun 2017 21:44:15 -0400	[thread overview]
Message-ID: <1496627055.21652.4.camel@gmail.com> (raw)
In-Reply-To: <1496625669.21652.2.camel@gmail.com>

> migrating it to get_random_long to the write people with a 

s/write/right/

Which is why Jann's submission of a patch earlier didn't land despite it
being really clearly cut, and I really have no idea about any previous
attempts. I have no interest in researching any previous attempts to get
it fixed and guessing at why those never landed. You care who found and
fixed it first, I didn't, so I didn't look into it. That doesn't mean I
wanted credit for fixing it. I would have been happier if Jann, Kees or
Riel had submitted it instead since it's less to deal with.

It needed to be fixed before masking out one of the bytes so I made yet
another fix for it and submitted it.

When you showed up on IRC mad at me, I thought it was about the
__ro_after_init changes which referenced PaX so I couldn't understand
what you were talking about because *I didn't take this change from PaX
like those ones*. Apparently quite hard to understand.

  reply	other threads:[~2017-06-05  1:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-03 11:30 [kernel-hardening] Stop the plagiarism Brad Spengler
2017-06-03 13:53 ` Daniel Micay
2017-06-03 14:21   ` Brad Spengler
2017-06-03 15:55     ` Daniel Micay
2017-06-04  3:28       ` Brad Spengler
2017-06-04 14:15         ` Daniel Micay
2017-06-05  0:12           ` Brad Spengler
2017-06-05  1:21             ` Daniel Micay
2017-06-05  1:44               ` Daniel Micay [this message]
2017-06-04 12:49       ` Brad Spengler
2017-06-04 13:48         ` Hector Martin
2017-06-04 14:44           ` Brad Spengler
2017-06-04 16:59             ` Hector Martin
2017-06-03 15:08 ` Lionel Debroux
2017-06-03 15:16 ` Matt Brown
2017-06-03 17:32 ` Rik van Riel
2017-06-04  7:16 ` Kees Cook
2017-06-04 11:43   ` Brad Spengler
2017-06-06  0:29     ` Kees Cook
2017-06-06 13:05     ` [kernel-hardening] " Jonathan Corbet
2017-06-05 17:43   ` [kernel-hardening] " Pavel Labushev

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=1496627055.21652.4.camel@gmail.com \
    --to=danielmicay@gmail.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=pageexec@freemail.hu \
    --cc=spender@grsecurity.net \
    /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 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.