From: Eric Sandeen <sandeen@sandeen.net>
To: Bhagi rathi <jahnu77@gmail.com>
Cc: Lachlan McIlroy <lachlan@sgi.com>,
sgi.bugs.xfs@engr.sgi.com, xfs@oss.sgi.com
Subject: Re: TAKE 981498 - Use KM_NOFS for debug trace buffers
Date: Wed, 06 Aug 2008 14:56:17 -0500 [thread overview]
Message-ID: <489A01E1.1040309@sandeen.net> (raw)
In-Reply-To: <cc7060690808061012x43511581m15c794e72129becc@mail.gmail.com>
Bhagi rathi wrote:
> I couldn't get a chance to read the diff's completely. If I click on
> Lachlan's url for diff's, I couldn't access them.
Try again, it takes a while for cvs to catch up.
-Eric
> It looks to me that
> the issue is not just with trace buffers. It can extend to xfs_iformat
> as well. The same dead-lock can spring via
>
> xfs_iread -> xfs_iformat -> xfs_iformat_extents -> xfs_iext_add ->
> xfs_iext_inline_to_direct -> which can do kmem_alloc with
> KM_SLEEP flag.
>
>
> The source of the problem is that holding a lock and entering into
> file-system once again. This can lead to dead-lock on the same
> clustered buffer during cleaning of log space.
>
> Cheers,
> Bhagi.
next prev parent reply other threads:[~2008-08-06 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 6:15 TAKE 981498 - Use KM_NOFS for debug trace buffers Lachlan McIlroy
2008-08-06 17:12 ` Bhagi rathi
2008-08-06 19:56 ` Eric Sandeen [this message]
2008-08-06 20:19 ` Dave Chinner
2008-08-06 20:27 ` Dave Chinner
2008-08-06 21:03 ` Dave Chinner
2008-08-07 2:19 ` Russell Cattelan
2008-08-07 17:45 ` Bhagi rathi
2008-08-07 17:43 ` Bhagi rathi
2008-08-08 5:16 ` Bhagi rathi
2008-08-07 22:04 ` Christoph Hellwig
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=489A01E1.1040309@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jahnu77@gmail.com \
--cc=lachlan@sgi.com \
--cc=sgi.bugs.xfs@engr.sgi.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.