From: Greg KH <greg@kroah.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Matthew Wilcox <matthew@wil.cx>,
Linus Torvalds <torvalds@osdl.org>,
Kirill Korotaev <dev@openvz.org>,
tony.luck@intel.com, linux-ia64@vger.kernel.org,
Fernando Vazquez <fernando@oss.ntt.co.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@kernel.org, "David S. Miller" <davem@davemloft.net>,
devel@openvz.org, xemul@openvz.org
Subject: Re: [stable] [PATCH] IA64,sparc: local DoS with corrupted ELFs
Date: Thu, 7 Sep 2006 08:37:46 -0700 [thread overview]
Message-ID: <20060907153746.GA29602@kroah.com> (raw)
In-Reply-To: <1157634702.30159.89.camel@aeonflux.holtmann.net>
On Thu, Sep 07, 2006 at 03:11:42PM +0200, Marcel Holtmann wrote:
> Hi Greg,
>
> > > > Yes, but the -stable developers don't build for those arches, that's why
> > > > it was missed here.
> > >
> > > What's the easiest way to get coverage here? Sending a parisc
> > > workstation or server to someone? Giving accounts to some/all of the
> > > stable team? Finding someone who cares about parisc to join the stable
> > > team?
> >
> > How about: Someone from that arch trying out the -stable release
> > canidates to make sure it doesn't break anything on their arches /
> > favorite machine?
>
> this won't work for security hot-fixes, because you basically don't do a
> release candidate for them. We should think about this, too.
Well, short of me and Chris getting one of every arch out there (which I
don't recommend), I think we will just get by as we have been doing in
the past.
thanks,
greg k-h
next prev parent reply other threads:[~2006-09-07 15:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 12:17 [PATCH] IA64,sparc: local DoS with corrupted ELFs Kirill Korotaev
2006-09-05 11:39 ` Kyle McMartin
2006-09-05 13:08 ` Kirill Korotaev
2006-09-06 18:24 ` Linus Torvalds
2006-09-06 18:27 ` Matthew Wilcox
2006-09-06 18:45 ` [stable] " Greg KH
2006-09-06 19:12 ` Matthew Wilcox
2006-09-06 19:17 ` Christoph Lameter
2006-09-06 19:25 ` Greg KH
2006-09-06 20:27 ` Willy Tarreau
2006-09-07 13:11 ` Marcel Holtmann
2006-09-07 15:37 ` Greg KH [this message]
2006-09-08 9:11 ` Jes Sorensen
2006-09-06 19:06 ` Arjan van de Ven
2006-09-08 9:12 ` Jes Sorensen
2006-09-07 10:17 ` Kirill Korotaev
2006-09-07 15:17 ` Linus Torvalds
2006-09-07 20:07 ` Willy Tarreau
2006-09-07 23:42 ` Andrew Morton
2006-09-08 4:34 ` Willy Tarreau
2006-09-08 15:15 ` Kirill Korotaev
2006-09-08 15:35 ` Linus Torvalds
2006-09-08 15:49 ` Dave Jones
2006-09-08 16:09 ` Kirill Korotaev
2006-09-13 15:46 ` Randy.Dunlap
2006-09-06 20:20 ` Linus Torvalds
2006-09-06 21:27 ` Luck, Tony
2006-09-06 23:23 ` Fernando Luis Vázquez Cao
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=20060907153746.GA29602@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=dev@openvz.org \
--cc=devel@openvz.org \
--cc=fernando@oss.ntt.co.jp \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=matthew@wil.cx \
--cc=stable@kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@osdl.org \
--cc=xemul@openvz.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