From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
pageexec@freemail.hu, Arjan van de Ven <arjan@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: vmsplice exploits, stack protector and Makefiles
Date: Thu, 14 Feb 2008 07:12:03 +0100 [thread overview]
Message-ID: <20080214061203.GA31327@elte.hu> (raw)
In-Reply-To: <20080213171614.GA12259@uranus.ravnborg.org>
* Sam Ravnborg <sam@ravnborg.org> wrote:
> > > if you're merging this, please do the independent parts really
> > > independenrly. For example, the above is a patch in its own right,
> > > and probably worth doing regardless of anything else.
> >
> > yes. I wanted to have it tested for a bit, because the lack of use
> > of the gcc flag means complete lack of testing coverage. The
> > obligatory "please add a stackprotector self-test" debug feature
> > request went to Arjan two days ago already.
>
> Do you think that the top-lvel Makefile change is OK to merge? I would
> like to merge it separatly to have maximum bisectability.
sure.
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
next prev parent reply other threads:[~2008-02-14 6:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 17:00 vmsplice exploits, stack protector and Makefiles Arjan van de Ven
2008-02-12 18:50 ` Sam Ravnborg
2008-02-12 19:08 ` Arjan van de Ven
2008-02-12 19:36 ` Sam Ravnborg
2008-02-13 13:38 ` pageexec
2008-02-13 15:29 ` Ingo Molnar
2008-02-13 16:29 ` Randy Dunlap
2008-02-13 15:48 ` pageexec
2008-02-14 12:20 ` Jan Engelhardt
2008-02-13 16:48 ` Ingo Molnar
2008-02-13 16:15 ` pageexec
2008-02-14 6:16 ` Ingo Molnar
2008-02-14 7:30 ` Ingo Molnar
2008-02-14 10:23 ` pageexec
2008-02-13 15:53 ` Linus Torvalds
2008-02-13 16:01 ` Ingo Molnar
2008-02-13 17:16 ` Sam Ravnborg
2008-02-14 6:12 ` Ingo Molnar [this message]
2008-02-14 7:43 ` Sam Ravnborg
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=20080214061203.GA31327@elte.hu \
--to=mingo@elte.hu \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pageexec@freemail.hu \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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 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.