Hi SGI guys,
From: ASANO Masahiro <masano@xxxxxxxxxxxxxx>
To: nathans@xxxxxxx
Date: Wed, 25 Aug 2004 18:21:31 +0900 (JST)
>> > The following is a kernel backtrace. Its kernel version was 2.4.25,
>> > but I guess that the recent kernel also has the same problem. What do
>> > you think of it?
>>
>> I would expect this deadlock still exists, I don't remember fixing
>> it or seeing anyone else fix it - do you have a reproducible test
>> case?
>
>I'll do it later.
This deadlock problem were reproduced in the environment of
2.4.25+maxagi.patch and 2.4.27+maxagi.patch.
I made the test tool which can reproduce the problem.
growfs.sh
subgrowfs.sh
Please, try them.
I made patch for 2.4.25+maxagi.patch.
growfs.patch
This patch changed the allocation method of m_perag and deleted
the lock of m_peraglock.
When applying this patch, the deadlock problem seems to be fixed.
But, when the error has occurred, the memory leak problem happens.
What do you think of this patch?
-----
tatsu
growfs.sh
Description: Binary data
subgrowfs.sh
Description: Binary data
growfs.patch
Description: Binary data
|