On Tue, Jul 17, 2007 at 05:44:14PM -0500, Jon Loeliger wrote:
>
>
> A: They haven't been posted yet.
>
> Q: How do we know Segher has new patches?
>
>
rotfl -- rolling on the floor loeliger !
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
On Jul 18, 2007, at 7:07 AM, Segher Boessenkool wrote:
> A: They haven't been posted yet.
>
> Q: How do we know Segher has new patches?
He sent it to me to test, and I told him it worked...
>>>
>>> And I sent it to the list hours later, over a week ago.
>>
>> Can someone s
A: They haven't been posted yet.
Q: How do we know Segher has new patches?
>>>
>>> He sent it to me to test, and I told him it worked...
>>
>> And I sent it to the list hours later, over a week ago.
>
> Can someone send a ozlabs linuxppc list link or patchworks to the
> "new" pat
On Jul 17, 2007, at 10:30 PM, Segher Boessenkool wrote:
>>> A: They haven't been posted yet.
>>>
>>> Q: How do we know Segher has new patches?
>>
>> He sent it to me to test, and I told him it worked...
>
> And I sent it to the list hours later, over a week ago.
Can someone send a ozlabs linux
>> A: They haven't been posted yet.
>>
>> Q: How do we know Segher has new patches?
>
> He sent it to me to test, and I told him it worked...
And I sent it to the list hours later, over a week ago.
Segher
___
Linuxppc-dev mailing list
Linuxppc-dev@o
Jon Loeliger wrote:
> A: They haven't been posted yet.
>
> Q: How do we know Segher has new patches?
He sent it to me to test, and I told him it worked...
-Scott
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinf
A: They haven't been posted yet.
Q: How do we know Segher has new patches?
So, like, the other day Scott Wood mumbled:
> Jon Loeliger wrote:
> > But luckily, this gave me the opportunity to then realize that
> > we should give a great big...
> >
> > Amen-brother-by: Jon Loeliger <[EMAIL PR
Jon Loeliger wrote:
> But luckily, this gave me the opportunity to then realize that
> we should give a great big...
>
> Amen-brother-by: Jon Loeliger <[EMAIL PROTECTED]>
>
> to this patch from Scott.
>
> So, an official plea to Paul to apply this to his tree.
Segher has a newer patch that supe
On Mon, 2007-07-09 at 16:48, Scott Wood wrote:
> In older versions of glibc (through 2.3), the dynamic linker executes a
> small amount of code from the data segment, which is not marked as
> executable. A recent change (commit 9ba4ace39fdfe22268daca9f28c5df384ae462cf)
> stops this from working; t
Actually I see no good reason to enforce no-exec at all if we
can't do
it consistently. And if we're not going to enforce it then
there is
no point whinging about it.
>>>
>>>
>>> I have a new patch with just this behaviour, Scott is
>>> testing it on old glibc (I think
On Jul 11, 2007, at 10:32 AM, Scott Wood wrote:
> Segher Boessenkool wrote:
>>> Actually I see no good reason to enforce no-exec at all if we
>>> can't do
>>> it consistently. And if we're not going to enforce it then there is
>>> no point whinging about it.
>>
>>
>> I have a new patch with ju
Segher Boessenkool wrote:
>> Actually I see no good reason to enforce no-exec at all if we can't do
>> it consistently. And if we're not going to enforce it then there is
>> no point whinging about it.
>
>
> I have a new patch with just this behaviour, Scott is
> testing it on old glibc (I think
>> In older versions of glibc (through 2.3), the dynamic linker
>> executes a
>> small amount of code from the data segment, which is not marked as
>> executable. A recent change (commit
>> 9ba4ace39fdfe22268daca9f28c5df384ae462cf)
>> stops this from working; there should be a deprecation peri
Scott Wood writes:
> In older versions of glibc (through 2.3), the dynamic linker executes a
> small amount of code from the data segment, which is not marked as
> executable. A recent change (commit 9ba4ace39fdfe22268daca9f28c5df384ae462cf)
> stops this from working; there should be a deprecatio
14 matches
Mail list logo