Prev: [PATCH] md: fix raid6test build error
Next: [PATCH] x86/mm: remove unused DBG() macro
From: Kyle McMartin on 15 Jun 2010 04:20
On Mon, Jun 14, 2010 at 12:57:16PM -0700, Andrew Morton wrote:
> > Do you send it to stable ? I am hitting the same bug and count is high
> > on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
> >
>
> The commit didn't have a cc:stable in the changelog so no, it probably
> wasn't backported.
>
> But that commit was later reverted anyway. Hopefully when the real fix
> gets merged, it will be backported.
>

Yes, we backported it when it hit mainline, and have since pulled them
until the real fix is sorted out.

thanks, Kyle.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Bastien ROUCARIES on 15 Jun 2010 04:30
On Mon, Jun 14, 2010 at 9:57 PM, Andrew Morton
<akpm(a)linux-foundation.org> wrote:
> On Thu, 10 Jun 2010 11:06:17 +0200
> Bastien ROUCARIES <roucaries.bastien(a)gmail.com> wrote:
>
>> > > I don't see anything which would generate this warning in 2.6.33.4's
>> > > fs/fs-writeback.c:597. __RH must have mucked with it.
>> > Already fixed in mainstream by
>> > commit 7c8a3554c683f512dbcee26faedb42e4c05f12fa
>> > Author: Jens Axboe <jens.axboe(a)oracle.com>
>> > Date: __ Tue May 18 14:29:29 2010 +0200
>>
>> Do you send it to stable ? I am hitting the same bug and count is high
>> on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
>>
>
> The commit didn't have a cc:stable in the changelog so no, it probably
> wasn't backported.
>
> But that commit was later reverted anyway. �Hopefully when the real fix
> gets merged, it will be backported.

Thank Andrew. I am hitting this warning at each boot, without anything
fancy on my machine
(I am hitting it just after mounting the root partition, i suppose
reiserfs user_xattr, acl help but I was expecting that automatic
testing could catch this kind of bug)

Regards

Bastien
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Bastien ROUCARIES on 1 Jul 2010 04:00
On Tue, Jun 15, 2010 at 10:25 AM, Bastien ROUCARIES
<roucaries.bastien(a)gmail.com> wrote:
> On Mon, Jun 14, 2010 at 9:57 PM, Andrew Morton
> <akpm(a)linux-foundation.org> wrote:
>> On Thu, 10 Jun 2010 11:06:17 +0200
>> Bastien ROUCARIES <roucaries.bastien(a)gmail.com> wrote:
>>
>>> > > I don't see anything which would generate this warning in 2.6.33.4's
>>> > > fs/fs-writeback.c:597. __RH must have mucked with it.
>>> > Already fixed in mainstream by
>>> > commit 7c8a3554c683f512dbcee26faedb42e4c05f12fa
>>> > Author: Jens Axboe <jens.axboe(a)oracle.com>
>>> > Date: __ Tue May 18 14:29:29 2010 +0200
>>>
>>> Do you send it to stable ? I am hitting the same bug and count is high
>>> on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
>>>
>>
>> The commit didn't have a cc:stable in the changelog so no, it probably
>> wasn't backported.
>>
>> But that commit was later reverted anyway. �Hopefully when the real fix
>> gets merged, it will be backported.
>

Any news of this bug ?

Regard

Bastien
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Andrew Morton on 7 Jul 2010 17:00
On Thu, 1 Jul 2010 09:54:07 +0200
Bastien ROUCARIES <roucaries.bastien(a)gmail.com> wrote:

> On Tue, Jun 15, 2010 at 10:25 AM, Bastien ROUCARIES
> <roucaries.bastien(a)gmail.com> wrote:
> > On Mon, Jun 14, 2010 at 9:57 PM, Andrew Morton
> > <akpm(a)linux-foundation.org> wrote:
> >> On Thu, 10 Jun 2010 11:06:17 +0200
> >> Bastien ROUCARIES <roucaries.bastien(a)gmail.com> wrote:
> >>
> >>> > > I don't see anything which would generate this warning in 2.6.33.4's
> >>> > > fs/fs-writeback.c:597. __RH must have mucked with it.
> >>> > Already fixed in mainstream by
> >>> > commit 7c8a3554c683f512dbcee26faedb42e4c05f12fa
> >>> > Author: Jens Axboe <jens.axboe(a)oracle.com>
> >>> > Date: __ Tue May 18 14:29:29 2010 +0200
> >>>
> >>> Do you send it to stable ? I am hitting the same bug and count is high
> >>> on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
> >>>
> >>
> >> The commit didn't have a cc:stable in the changelog so no, it probably
> >> wasn't backported.
> >>
> >> But that commit was later reverted anyway. __Hopefully when the real fix
> >> gets merged, it will be backported.
> >
>
> Any news of this bug ?
>

There have been various dramas in the writeback code recently.
Christoph has been working on it.

Christoph, is this oops known about, and are those patches expected to
fix it?

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Hellwig on 7 Jul 2010 17:10
On Wed, Jul 07, 2010 at 01:51:18PM -0700, Andrew Morton wrote:
> There have been various dramas in the writeback code recently.
> Christoph has been working on it.
>
> Christoph, is this oops known about, and are those patches expected to
> fix it?

I have no idea what oops you mean. But the writeback code is very
different now compared to 2.6.33, and with the latest fixes in Jens'
tree there are no known issues left. (know to me anyway)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: [PATCH] md: fix raid6test build error
Next: [PATCH] x86/mm: remove unused DBG() macro