mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Gabor MICSKO <gmicsko@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Grsecurity is about to be discontinued, unless...
Date: Sat, 3 Jan 2009 12:16:50 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0901031210260.3179@localhost.localdomain> (raw)
In-Reply-To: <1231013176.6497.20.camel@localhost.localdomain>



On Sat, 3 Jan 2009, Gabor MICSKO wrote:
> 
> In short, I would like to know what is your answer to this request. And
> in the case if you see no chance for the integration, I would like to
> know what is the reason behind this decision.

Quite frankly, historically the patches have been a mis-match of

 - some sane stuff

 - lots of totally insane and very annoying and invasive code.

an example of the second class is the totally idiotic "emulate NX bit - 
badly - with code segment limits" kind of patches. These kinds of patches 
only add unmaintainable crap that isn't even relevant in the long run, and 
thus any sane maintainer (me) should refuse to take them.

The apparent inability (and perhaps more importantly - total 
unwillingless) from the PaX team to be able to see what makes sense in a 
long-term general kernel and what does not, and split things up and try to 
push the sensible things up (and know which things are too ugly or too 
specialized to make sense), caused many PaX features to never be merged.

Much of it did get merged over the years (mostly because some people spent 
the time to separate things out), but no, we're not going to suddenly 
start merging code like that just because the project is in trouble. None 
of the basic issues have been solved.

			Linus

  reply	other threads:[~2009-01-03 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 20:06 Gabor MICSKO
2009-01-03 20:16 ` Linus Torvalds [this message]
2009-01-04  4:51   ` Valdis.Kletnieks
2009-01-04  0:28 ` Jiri Kosina

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=alpine.LFD.2.00.0901031210260.3179@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=gmicsko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®