All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: 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: Wed, 06 Sep 2006 18:45:09 +0000	[thread overview]
Message-ID: <20060906184509.GA15942@kroah.com> (raw)
In-Reply-To: <20060906182733.GJ2558@parisc-linux.org>

On Wed, Sep 06, 2006 at 12:27:33PM -0600, Matthew Wilcox wrote:
> On Wed, Sep 06, 2006 at 11:24:05AM -0700, Linus Torvalds wrote:
> > If MIPS and parisc don't matter for the stable tree (very possible - there 
> > are no big commercial distributions for them), then dammit, neither should 
> > ia64 and sparc (there are no big commercial distros for them either). 
> 
> Erm, RHEL and SLES both support ia64.

Yes, but the -stable developers don't build for those arches, that's why
it was missed here.

So, what's the proper patch for the next -stable release to fix this
problem?  I see a bunch of different ones floating around...

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: 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: Wed, 6 Sep 2006 11:45:09 -0700	[thread overview]
Message-ID: <20060906184509.GA15942@kroah.com> (raw)
In-Reply-To: <20060906182733.GJ2558@parisc-linux.org>

On Wed, Sep 06, 2006 at 12:27:33PM -0600, Matthew Wilcox wrote:
> On Wed, Sep 06, 2006 at 11:24:05AM -0700, Linus Torvalds wrote:
> > If MIPS and parisc don't matter for the stable tree (very possible - there 
> > are no big commercial distributions for them), then dammit, neither should 
> > ia64 and sparc (there are no big commercial distros for them either). 
> 
> Erm, RHEL and SLES both support ia64.

Yes, but the -stable developers don't build for those arches, that's why
it was missed here.

So, what's the proper patch for the next -stable release to fix this
problem?  I see a bunch of different ones floating around...

thanks,

greg k-h

  reply	other threads:[~2006-09-06 18:45 UTC|newest]

Thread overview: 56+ 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-04 12:17 ` Kirill Korotaev
2006-09-05 11:39 ` Kyle McMartin
2006-09-05 11:39   ` Kyle McMartin
2006-09-05 13:08   ` Kirill Korotaev
2006-09-05 13:08     ` Kirill Korotaev
2006-09-06 18:24 ` Linus Torvalds
2006-09-06 18:24   ` Linus Torvalds
2006-09-06 18:27   ` Matthew Wilcox
2006-09-06 18:27     ` Matthew Wilcox
2006-09-06 18:45     ` Greg KH [this message]
2006-09-06 18:45       ` [stable] " Greg KH
2006-09-06 19:12       ` Matthew Wilcox
2006-09-06 19:12         ` Matthew Wilcox
2006-09-06 19:17         ` Christoph Lameter
2006-09-06 19:17           ` Christoph Lameter
2006-09-06 19:25         ` Greg KH
2006-09-06 19:25           ` Greg KH
2006-09-06 20:27           ` Willy Tarreau
2006-09-06 20:27             ` Willy Tarreau
2006-09-07 11:17           ` Marcel Holtmann
2006-09-07 13:11             ` Marcel Holtmann
2006-09-07 15:37             ` Greg KH
2006-09-07 15:37               ` Greg KH
2006-09-08  9:11           ` Jes Sorensen
2006-09-08  9:11             ` Jes Sorensen
2006-09-06 19:06     ` Arjan van de Ven
2006-09-06 19:06       ` Arjan van de Ven
2006-09-08  9:12       ` Jes Sorensen
2006-09-08  9:12         ` Jes Sorensen
2006-09-07 10:17   ` Kirill Korotaev
2006-09-07 10:17     ` Kirill Korotaev
2006-09-07 15:17     ` Linus Torvalds
2006-09-07 15:17       ` Linus Torvalds
2006-09-07 20:07       ` Willy Tarreau
2006-09-07 20:07         ` Willy Tarreau
2006-09-07 23:42         ` Andrew Morton
2006-09-07 23:42           ` Andrew Morton
2006-09-08  4:34           ` Willy Tarreau
2006-09-08  4:34             ` Willy Tarreau
2006-09-08 15:15       ` Kirill Korotaev
2006-09-08 15:15         ` Kirill Korotaev
2006-09-08 15:35         ` Linus Torvalds
2006-09-08 15:35           ` Linus Torvalds
2006-09-08 15:49           ` Dave Jones
2006-09-08 15:49             ` Dave Jones
2006-09-08 16:09           ` Kirill Korotaev
2006-09-08 16:09             ` Kirill Korotaev
2006-09-13 15:46             ` Randy.Dunlap
2006-09-13 15:46               ` Randy.Dunlap
2006-09-06 20:20 ` Linus Torvalds
2006-09-06 20:20   ` Linus Torvalds
2006-09-06 21:27   ` Luck, Tony
2006-09-06 21:27     ` Luck, Tony
2006-09-06 23:23   ` 
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=20060906184509.GA15942@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=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 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.