2004-11-16 18:53:33

by Mathieu

[permalink] [raw]
Subject: 2.6.10-rc2-mm1: oops when accessing reiser4 fs's (maybe fix provided)


I tried 2.6.10-rc2-mm1 and the last reiser4 updates gave some (many many)
oopses flooding my screen :).
I tried reverting reiser4-fix-deadlock.patch and oopses are gone.

I tried this one because thru the quick traces on my screen, I saw a reference
to get_current_context.
The speed of the traces and the unasibility of the box prevented me from
making differences between "real" oopses and BUG_ON(), sorry for that...

If you want some traces I can provide them ASAP (e.g. tomorrow)

Best,

--
"I am getting pretty good at running diff and patch now."

- Jeff Merkey


2004-11-17 07:10:14

by Vladimir V. Saveliev

[permalink] [raw]
Subject: Re: 2.6.10-rc2-mm1: oops when accessing reiser4 fs's (maybe fix provided)

Hello

On Tue, 2004-11-16 at 21:53, Mathieu Segaud wrote:
> I tried 2.6.10-rc2-mm1 and the last reiser4 updates gave some (many many)
> oopses flooding my screen :).
> I tried reverting reiser4-fix-deadlock.patch and oopses are gone.
>
Would you please instead try the attached patch?

> I tried this one because thru the quick traces on my screen, I saw a reference
> to get_current_context.
> The speed of the traces and the unasibility of the box prevented me from
> making differences between "real" oopses and BUG_ON(), sorry for that...
>
> If you want some traces I can provide them ASAP (e.g. tomorrow)




Attachments:
1.1755 (994.00 B)

2004-11-17 16:59:52

by Mathieu

[permalink] [raw]
Subject: Re: 2.6.10-rc2-mm1: oops when accessing reiser4 fs's (maybe fix provided)

Vladimir Saveliev <[email protected]> disait derni?rement que :

> Hello
>
> On Tue, 2004-11-16 at 21:53, Mathieu Segaud wrote:
>> I tried 2.6.10-rc2-mm1 and the last reiser4 updates gave some (many many)
>> oopses flooding my screen :).
>> I tried reverting reiser4-fix-deadlock.patch and oopses are gone.
>>
> Would you please instead try the attached patch?

yep.
indeed it worked
anyway, for the quick answer

>
>> I tried this one because thru the quick traces on my screen, I saw a reference
>> to get_current_context.
>> The speed of the traces and the unasibility of the box prevented me from
>> making differences between "real" oopses and BUG_ON(), sorry for that...
>>
>> If you want some traces I can provide them ASAP (e.g. tomorrow)
>
>
>
>

--
Carrots work on rabbits, they don't work on hungry weasels.

- Alan Cox on linux-kernel