On Thu, Feb 28, 2013 at 1:53 AM, Hillf Danton wrote:
> On Thu, Feb 28, 2013 at 1:26 PM, KOSAKI Motohiro
> wrote:
>>> Insert new node after updating node in tree.
>>
>> Thanks. you are right. I could reproduce and verified.
>
> Thank you too;) pleasure to do minor work for you.
>
> btw, how about
On Thu, Feb 28, 2013 at 1:53 AM, Hillf Danton dhi...@gmail.com wrote:
On Thu, Feb 28, 2013 at 1:26 PM, KOSAKI Motohiro
kosaki.motoh...@jp.fujitsu.com wrote:
Insert new node after updating node in tree.
Thanks. you are right. I could reproduce and verified.
Thank you too;) pleasure to do
On Thu, Feb 28, 2013 at 1:26 PM, KOSAKI Motohiro
wrote:
>> Insert new node after updating node in tree.
>
> Thanks. you are right. I could reproduce and verified.
Thank you too;) pleasure to do minor work for you.
btw, how about your belly now? fully recovered?
Hillf
--
To unsubscribe from
> Insert new node after updating node in tree.
Thanks. you are right. I could reproduce and verified.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Insert new node after updating node in tree.
Thanks. you are right. I could reproduce and verified.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Feb 28, 2013 at 1:26 PM, KOSAKI Motohiro
kosaki.motoh...@jp.fujitsu.com wrote:
Insert new node after updating node in tree.
Thanks. you are right. I could reproduce and verified.
Thank you too;) pleasure to do minor work for you.
btw, how about your belly now? fully recovered?
Hillf
On Tue, Feb 26, 2013 at 9:54 AM, Sasha Levin wrote:
> On 02/25/2013 08:52 PM, KOSAKI Motohiro wrote:
>> On Mon, Feb 25, 2013 at 8:30 AM, Sasha Levin wrote:
>>> Hi all,
>>>
>>> While fuzzing with trinity inside a KVM tools guest running latest -next
>>> kernel,
>>> I've stumbled on the following
On Tue, Feb 26, 2013 at 9:54 AM, Sasha Levin sasha.le...@oracle.com wrote:
On 02/25/2013 08:52 PM, KOSAKI Motohiro wrote:
On Mon, Feb 25, 2013 at 8:30 AM, Sasha Levin sasha.le...@oracle.com wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next
kernel,
I've
On 02/25/2013 08:52 PM, KOSAKI Motohiro wrote:
> On Mon, Feb 25, 2013 at 8:30 AM, Sasha Levin wrote:
>> Hi all,
>>
>> While fuzzing with trinity inside a KVM tools guest running latest -next
>> kernel,
>> I've stumbled on the following BUG:
>>
>> [13551.830090] [ cut here
On Mon, Feb 25, 2013 at 8:30 AM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next
> kernel,
> I've stumbled on the following BUG:
>
> [13551.830090] [ cut here ]
> [13551.830090] kernel BUG at mm/mempolicy.c:2187!
>
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next kernel,
I've stumbled on the following BUG:
[13551.830090] [ cut here ]
[13551.830090] kernel BUG at mm/mempolicy.c:2187!
[13551.830090] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next kernel,
I've stumbled on the following BUG:
[13551.830090] [ cut here ]
[13551.830090] kernel BUG at mm/mempolicy.c:2187!
[13551.830090] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC
On Mon, Feb 25, 2013 at 8:30 AM, Sasha Levin sasha.le...@oracle.com wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next
kernel,
I've stumbled on the following BUG:
[13551.830090] [ cut here ]
[13551.830090] kernel BUG at
On 02/25/2013 08:52 PM, KOSAKI Motohiro wrote:
On Mon, Feb 25, 2013 at 8:30 AM, Sasha Levin sasha.le...@oracle.com wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next
kernel,
I've stumbled on the following BUG:
[13551.830090] [ cut here
14 matches
Mail list logo
