Re: Call traces w/ 2.6.35.2 (not w/ 2.6.35.1 plus 2.6.35.2-rc1)

[Sedat Dilek]

On Sat, Aug 14, 2010 at 3:43 PM, Greg KH <gregkh@xxxxxxx> wrote:
> On Sat, Aug 14, 2010 at 08:36:30AM +0200, Sedat Dilek wrote:
>> Hope this helps to give an overview what has changed:
[...]
>
> I still fail to understand what you are trying to show here at all.
>
> confused,
>
> greg k-h
>

I was trying to show you that the patches in .35.2-rc1 and .35.2 are
not the same.
Normally, the rcX patches become the final ones.

Unfortunately, I was too lazy to check the names of the patches and
simply compared the files that have been modified (lines beginning
with "diff --git a/file b/file").

In the meantime, Mr./Mrs.(?) "wylda" (sorry, don't know if first or
last name) bisected the problem [1].

The confusing part for me is why "fresh" upstream patches entered a
2.6.35.y fix-series.
I can't say if only i386 is concerned, but as

mm: fix missing page table unmap for stack guard page failure case
mm: keep a guard page below a grow-down stack segment

are also upstream patches, I think the both cause problems for
.35-gitX also [2].

- Sedat -

[1] https://bugzilla.kernel.org/show_bug.cgi?id=16588
[2] https://bugzilla.kernel.org/show_bug.cgi?id=16588#c5
[3] [1] http://lkml.org/lkml/2010/8/14/54
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/