Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Alexander Gabert <pappy@nikita.ath.cx>
Cc: grsecurity@grsecurity.net, willy@debian.org,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] parisc-linux.org kernel
Date: Wed, 9 Apr 2003 09:47:32 -0600	[thread overview]
Message-ID: <20030409154732.GB4503@dsl2.external.hp.com> (raw)
In-Reply-To: <52352.145.253.137.30.1049874876.squirrel@nikita.ath.cx>

On Wed, Apr 09, 2003 at 09:54:36AM +0200, Alexander Gabert wrote:
> background:
> b) parisc-linux.org is then mainstreamed in 2.5 and will discontinue
> "split development"c) parisc-linux kernel _boots_ and _works_ and is _continued_ to be
> developed in _MAINSTREAM_ not in parisc-linux.org CVS
> i want that to happen anyway.  not just for grsec patches.
> it is a sad joke that parisc-linux.org kernels are good and the kernel.org
> parisc source is just a silly excuse for not having the parisc-linux.org
> sources melt in.  sorry for that.

No - you don't understand the roles of the various trees.

The CVS on parisc-linux.org will *always* be authoritative tree
for parisc-linux. It should be considered a "developement" branch
for kernel.org. This is true for nearly every architecture
except i386 (and alpha?) which are maintained by issueing
a patch against kernel.org.


> right, in this stadium i can "oversee" the necessary patches:
> 
> i strip the nonparisc, multiplatform support away with a perl script,
> fiddle with about 3-4 hunks that have to be taken out because they already
> exist in parisc source (for example latest ptrace kernel exploit), another
> 6-10 "look at it and try to intelligently put it into the slightly
> different parisc source" and the rest is "make up" like double insertions,
> typos and the like :-)

Oh cool - so it's not as bad as I thought...can you run
diffstat on the various "hunks" you've got?

> >> we're mostly
> >> merged for 2.5 and i'd rather spend my time working on that.
> 
> okay, this basically means to wait for a 2.5.* grsec patch and in the
> meantime continue hacking in the grsec patches by hand, which is just what

You hopefully won't have nearly the same problems as with 2.4.
(grsec team working on stale arch/parisc code)

...
> with the help of the PaX team, yesterday i managed to get the 199f patch
> going on my 712, with all GRKERNSEC* options enabled but just a little
> PAGEEXEC "brute disabled routine" in binfmt_elf.c that inverses the
> behaviour of chpax -p, i will get into that later today when i come home.
> http://nikita.ath.cx/users/pappy/grsec/199f/parisc-linux-2.4.20-pa32-grsecurity-1.9.9f-parisc-only.patch

very cool.

> thanks for your support and that you are dealing with this issue so
> friendly and open minded.

thanks too,
grant

  reply	other threads:[~2003-04-09 15:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 16:53 [parisc-linux] parisc-linux.org kernel Alexander Gabert
2003-04-08 16:58 ` Matthew Wilcox
2003-04-08 17:06   ` Alexander Gabert
2003-04-08 17:08     ` Matthew Wilcox
2003-04-09  5:49       ` Grant Grundler
2003-04-09  7:54         ` Alexander Gabert
2003-04-09 15:47           ` Grant Grundler [this message]
2003-04-09 17:23           ` pageexec
2003-04-09 17:40             ` Matthew Wilcox
2003-04-09 18:20               ` pageexec
2003-04-09 17:48             ` Matthew Wilcox
2003-04-10  5:50             ` Grant Grundler
2003-04-10 11:19               ` Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
2003-04-09  7:36 Berthold Gunreben
     [not found] <20030410155223.GA5254@dsl2.external.hp.com>
2003-04-11  5:40 ` Joel Soete
2003-04-11  9:41   ` Joel Soete
2003-04-11 15:58   ` Grant Grundler
2003-04-12 20:30     ` Joel Soete
2003-04-14 12:13     ` Joel Soete
2003-04-14 11:39       ` Alan Cox
2003-04-14 13:53         ` Joel Soete
2003-04-14 15:42           ` Joel Soete
2003-04-15 16:32         ` Joel Soete
2003-04-15 15:54           ` Alan Cox
2003-04-15 16:41           ` Randolph Chung
2003-04-15 16:47             ` Matthew Wilcox
2003-04-15 16:52               ` Joel Soete
2003-04-14 14:18       ` Michael Wood
2003-04-14 11:52 Joel Soete
2003-04-14 11:54 ` Matthew Wilcox
2003-04-14 12:53   ` Joel Soete
2003-04-16 10:13 Joel Soete
2003-04-16 11:06 ` Alan Cox
2003-04-16 16:44 Joel Soete
2003-04-16 16:50 ` Matthew Wilcox
2003-04-18  8:17 Joel Soete
2003-04-18 11:40 ` Joel Soete

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=20030409154732.GB4503@dsl2.external.hp.com \
    --to=grundler@parisc-linux.org \
    --cc=grsecurity@grsecurity.net \
    --cc=pappy@nikita.ath.cx \
    --cc=parisc-linux@parisc-linux.org \
    --cc=willy@debian.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