t; > , "Steve Best" ,
> > linux-e...@vger.kernel.org
> > Sent: Tuesday, April 2, 2013 6:01:36 PM
> > Subject: Re: bisected! (WAS Re: s390x: kernel BUG at fs/ext4/inode.c:1591!)
> >
> > On Tue, 2 Apr 2013 00:06:24 -0400 (EDT), CAI Qian
> > wrote:
&
On Wed, 3 Apr 2013 03:14:44 -0400 (EDT), CAI Qian wrote:
>
> > > [Text Documents:disable-es_lookup_extent.patch]
> With this patch, I cannot reproduce it any more.
Ok that is second confirmation that bug caused by issue in es_cache,
This is not a fix though. So still try to investigate that.
>
> > [Text Documents:disable-es_lookup_extent.patch]
With this patch, I cannot reproduce it any more.
CAI Qian
--
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
[Text Documents:disable-es_lookup_extent.patch]
With this patch, I cannot reproduce it any more.
CAI Qian
--
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
On Wed, 3 Apr 2013 03:14:44 -0400 (EDT), CAI Qian caiq...@redhat.com wrote:
[Text Documents:disable-es_lookup_extent.patch]
With this patch, I cannot reproduce it any more.
Ok that is second confirmation that bug caused by issue in es_cache,
This is not a fix though. So still try to
,
linux-e...@vger.kernel.org, Lukas Czerner lczer...@redhat.com,
sta...@vger.kernel.org
Subject: Re: bisected! (WAS Re: s390x: kernel BUG at fs/ext4/inode.c:1591!)
- Original Message -
From: Dmitry Monakhov dmonak...@openvz.org
To: CAI Qian caiq...@redhat.com
Cc
On Tue, 2 Apr 2013 00:06:24 -0400 (EDT), CAI Qian wrote:
> Bisect indicated this is the culprit,
>
> 0e401101db49959f5783f6ee9e676124b5a183ac
> ext4: fix memory leakage in mext_check_coverage
Strange...
It changes a bug in move_extent.c (e4defrag functionality)
ASAIU you just previously stopped
On Tue, 2 Apr 2013 00:06:24 -0400 (EDT), CAI Qian caiq...@redhat.com wrote:
Bisect indicated this is the culprit,
0e401101db49959f5783f6ee9e676124b5a183ac
ext4: fix memory leakage in mext_check_coverage
Strange...
It changes a bug in move_extent.c (e4defrag functionality)
ASAIU you just
Bisect indicated this is the culprit,
0e401101db49959f5783f6ee9e676124b5a183ac
ext4: fix memory leakage in mext_check_coverage
This following with Dmitry's debug patch applied,
CAI Qian
Ý 101.408610¨ ES cache assertation failed for inode: 753 es_cached ex Ý56/5/744
81/20¨ != found ex
Bisect indicated this is the culprit,
0e401101db49959f5783f6ee9e676124b5a183ac
ext4: fix memory leakage in mext_check_coverage
This following with Dmitry's debug patch applied,
CAI Qian
Ý 101.408610¨ ES cache assertation failed for inode: 753 es_cached ex Ý56/5/744
81/20¨ != found ex
10 matches
Mail list logo
