Reverting the patch of kernel/signal.c which was
applied to 2.6.37.6 and 2.6.38.2 solved the problem.
On Mon, Mar 28, 2011 at 11:05 AM, Klaus Dittrich <[email protected]> wrote:
> Reverting the patch of kernel/signal.c which was
> applied to 2.6.37.6 and ?2.6.38.2 solved the problem.
Indeed, I found that the same patch was to blame. Fix coming shortly.
On 03/28/2011 08:14 PM, Roland Dreier wrote:
> On Mon, Mar 28, 2011 at 11:05 AM, Klaus Dittrich <[email protected]> wrote:
>> Reverting the patch of kernel/signal.c which was
>> applied to 2.6.37.6 and 2.6.38.2 solved the problem.
>
> Indeed, I found that the same patch was to blame. Fix coming shortly.
Is there a patch for this already?
thanks,
--
js
> Is there a patch for this already?
Yes, it is 243b422af9ea in Linus's tree.
On 03/29/2011 11:07 PM, Roland Dreier wrote:
>> Is there a patch for this already?
>
> Yes, it is 243b422af9ea in Linus's tree.
Thanks. (Queued up for suse kernels.)
--
js