xfs
[Top] [All Lists]

Re: XFS memory allocation deadlock in 2.6.38

To: Sean Noonan <Sean.Noonan@xxxxxxxxxxxx>
Subject: Re: XFS memory allocation deadlock in 2.6.38
From: Michel Lespinasse <walken@xxxxxxxxxx>
Date: Mon, 28 Mar 2011 14:06:25 -0700
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Martin Bligh <Martin.Bligh@xxxxxxxxxxxx>, Trammell Hudson <Trammell.Hudson@xxxxxxxxxxxx>, Christos Zoulas <Christos.Zoulas@xxxxxxxxxxxx>, "linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx>, Stephen Degler <Stephen.Degler@xxxxxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1301346390; bh=ZwcolnCg0Iq2X/oJkskHmdfT01E=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=uL7G/6LpbzKModKMmNKgS6slaklev+jxt4fMr3KKIG0nIabwrzO+ekjS60DgtthOD d35MVHGfisbBehdfEyOOQ==
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=0/Q7wDcoRHgbZEQB481EhlvI9PFGkic+nMI4+lm1Xl4=; b=JdJ0FnESh+xa9cKjXIHjUhCzvMZ1RQETvIX3d5VkP2E7R3IEumsiNAwgWlYth9bfpS TxSbvGm4PJHOMt76QFDg==
Domainkey-signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=g3LOY+fBNG6gKjdXp/pQ+rJtQswJ2rrHRIRi0MzGXKAa3cRN16DZrqJuR/XpviFQOD kjMZ+aEToCofmab2Iy6Q==
In-reply-to: <081DDE43F61F3D43929A181B477DCA95639B5349@xxxxxxxxxxxxxxxxxxxx>
References: <081DDE43F61F3D43929A181B477DCA95639B52FD@xxxxxxxxxxxxxxxxxxxx> <081DDE43F61F3D43929A181B477DCA95639B5327@xxxxxxxxxxxxxxxxxxxx> <20110324174311.GA31576@xxxxxxxxxxxxx> <AANLkTikwwRm6FHFtEdUg54NvmKdswQw-NPH5dtq1mXBK@xxxxxxxxxxxxxx> <081DDE43F61F3D43929A181B477DCA95639B5349@xxxxxxxxxxxxxxxxxxxx>
On Mon, Mar 28, 2011 at 7:58 AM, Sean Noonan <Sean.Noonan@xxxxxxxxxxxx> wrote:
>> Regarding the deadlock: I am curious to see if it could be made to
>> happen before 5ecfda041e4b4bd858d25bbf5a16c2a6c06d7272. Could you test
>> what happens if you remove the MAP_POPULATE flag from your mmap call,
>> and instead read all pages from userspace right after the mmap ? I
>> expect you would then be able to trigger the deadlock before
>> 5ecfda041e4b4bd858d25bbf5a16c2a6c06d7272.
>
> I still see the deadlock without MAP_POPULATE

Could you test if you see the deadlock before
5ecfda041e4b4bd858d25bbf5a16c2a6c06d7272 without MAP_POPULATE ?

-- 
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.

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