xfs
[Top] [All Lists]

Re: a deadlock at xfs_growfs

To: ASANO Masahiro <masano@xxxxxxxxxxxxxx>, "Tatsuko Yasugahira(Ohata)" <tatsu@xxxxxxxxxxxxxx>
Subject: Re: a deadlock at xfs_growfs
From: Nathan Scott <nathans@xxxxxxx>
Date: Tue, 5 Oct 2004 16:56:07 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <82C4A9B682002Ftatsu@tnes.nec.co.jp>
References: <20040825.182131.466644752.masano@tnes.nec.co.jp> <82C4A9B682002Ftatsu@tnes.nec.co.jp>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.3i
On Mon, Oct 04, 2004 at 11:04:40AM +0900, Tatsuko Yasugahira(Ohata) wrote:
> 
> Hi SGI guys,

Hi there NEC guys!

> >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.

Thanks!  Will do.

>  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?

I haven't had a chance to look in detail yet - I'm a bit
snowed under; I should be able to come up for air toward the
end of this week - I'll get back to you then if noone else
has by that time.

Thanks for looking into this.

cheers.

-- 
Nathan


<Prev in Thread] Current Thread [Next in Thread>