All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirill Korotaev <dev@sw.ru>
To: Greg KH <greg@kroah.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	Fernando Vazquez <fernando@oss.ntt.co.jp>,
	gregkh@suse.de, akpm@osdl.org, dev@openvz.org,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, stable@kernel.org,
	kamezawa.hiroyu@jp.fujitsu.com, xemul@openvz.org
Subject: Re: [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on IA64
Date: Tue, 29 Aug 2006 12:24:41 +0000	[thread overview]
Message-ID: <44F43209.6040603@sw.ru> (raw)
In-Reply-To: <20060829013137.GA27869@kroah.com>

Greg KH wrote:
> On Mon, Aug 28, 2006 at 03:11:31PM -0700, Luck, Tony wrote:
> 
>>>The commit 8833ebaa3f4325820fe3338ccf6fae04f6669254 introduced a change that broke 
>>>IA64 compilation as shown below:
>>
>>What happened to the mainline version of the patch to which this
>>is a fix (local DoS with corrupted ELFs)?  I don't see it in 2.6.18-rc5.
>>Did it get fixed some other way, or is it just queued somewhere?  Or do
>>we have a fix in -stable that isn't in mainline?
> 
> 
> I thought this was a fix for a prior -stable patch that did not affect
> mainline.  Or was this thought wrong?
both patches should be passed to Linus.
Probably it is my fault, since I thought that patches which got into -stable
automatically go into Linus tree.

Thanks,
Kirill


WARNING: multiple messages have this Message-ID (diff)
From: Kirill Korotaev <dev@sw.ru>
To: Greg KH <greg@kroah.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	Fernando Vazquez <fernando@oss.ntt.co.jp>,
	gregkh@suse.de, akpm@osdl.org, dev@openvz.org,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, stable@kernel.org,
	kamezawa.hiroyu@jp.fujitsu.com, xemul@openvz.org
Subject: Re: [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on IA64 (try #3)
Date: Tue, 29 Aug 2006 16:24:41 +0400	[thread overview]
Message-ID: <44F43209.6040603@sw.ru> (raw)
In-Reply-To: <20060829013137.GA27869@kroah.com>

Greg KH wrote:
> On Mon, Aug 28, 2006 at 03:11:31PM -0700, Luck, Tony wrote:
> 
>>>The commit 8833ebaa3f4325820fe3338ccf6fae04f6669254 introduced a change that broke 
>>>IA64 compilation as shown below:
>>
>>What happened to the mainline version of the patch to which this
>>is a fix (local DoS with corrupted ELFs)?  I don't see it in 2.6.18-rc5.
>>Did it get fixed some other way, or is it just queued somewhere?  Or do
>>we have a fix in -stable that isn't in mainline?
> 
> 
> I thought this was a fix for a prior -stable patch that did not affect
> mainline.  Or was this thought wrong?
both patches should be passed to Linus.
Probably it is my fault, since I thought that patches which got into -stable
automatically go into Linus tree.

Thanks,
Kirill


  parent reply	other threads:[~2006-08-29 12:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25  8:13 [PATCH] Linux 2.6.17.11 - fix compilation error on IA64 (try #3) Fernando Vazquez
2006-08-25  8:13 ` Fernando Vazquez
2006-08-25 22:07 ` [stable] " Greg KH
2006-08-25 22:07   ` Greg KH
2006-08-28 22:11 ` Luck, Tony
2006-08-28 22:11   ` Luck, Tony
2006-08-29  1:31   ` [stable] " Greg KH
2006-08-29  1:31     ` Greg KH
2006-08-29 12:24     ` [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on IA64 Kirill Korotaev
2006-08-29 12:24       ` [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on IA64 (try #3) Kirill Korotaev
2006-08-29 16:08       ` Greg KH
2006-08-29 16:08         ` Greg KH
2006-09-04 10:10         ` [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on 
2006-09-04 10:10           ` [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on IA64 (try #3) Fernando Luis Vázquez Cao
2006-09-04 10:30           ` [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on IA64 Kirill Korotaev
2006-09-04 10:30             ` [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on IA64 (try #3) Kirill Korotaev
2006-08-29 12:24     ` Kirill Korotaev [this message]
2006-08-29 12:24       ` Kirill Korotaev

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=44F43209.6040603@sw.ru \
    --to=dev@sw.ru \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=dev@openvz.org \
    --cc=fernando@oss.ntt.co.jp \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=tony.luck@intel.com \
    --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.