public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Jan Kara <jack@ucw.cz>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	Eugene Crosser <crosser@average.org>
Subject: Re: Deadlock problems
Date: Mon, 03 May 2004 09:11:21 -0400	[thread overview]
Message-ID: <1083589880.1607.9.camel@watt.suse.com> (raw)
In-Reply-To: <20040503115837.GC360@atrey.karlin.mff.cuni.cz>

On Mon, 2004-05-03 at 07:58, Jan Kara wrote:
>   Hi Andrew!
> 
>   I've found hard to fix problem causing deadlock - call path is
> generally following:
>   some operation -> quota code -> read/write quota -> vfs -> needs a page ->
> shrink caches -> free inodes -> free quota -> Ouch... (we need to acquire
> some lock which is already held by the quota code)
> 
Ugh, for some reason I thought we were avoiding this one in 2.6.  This
is why I made kinoded for the quota patches in 2.4.x

-chris



  reply	other threads:[~2004-05-03 13:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 11:58 Deadlock problems Jan Kara
2004-05-03 13:11 ` Chris Mason [this message]
2004-05-03 18:14 ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1083589880.1607.9.camel@watt.suse.com \
    --to=mason@suse.com \
    --cc=akpm@osdl.org \
    --cc=crosser@average.org \
    --cc=jack@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox