From: William Lee Irwin III <wli@holomorphy.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@osdl.org, dwmw2@infradead.org, dedekind@infradead.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] __wait_on_freeing_inode fix
Date: Wed, 11 May 2005 07:19:10 -0700 [thread overview]
Message-ID: <20050511141910.GE9304@holomorphy.com> (raw)
In-Reply-To: <E1DU1Hy-00060Q-00@dorka.pomaz.szeredi.hu>
On Fri, May 06, 2005 at 01:46:38PM +0200, Miklos Szeredi wrote:
> If I_LOCK was not set it called yield(), effectively busy waiting for
> the removal of the inode from the hash. This change was introduced
> within "[PATCH] eliminate inode waitqueue hashtable" Changeset
> 1.1938.166.16 last october by wli.
> The solution is to restore the old behavior, of unconditionally
> waiting on the waitqueue. It doesn't matter if I_LOCK is not set
> initally, the task will go to sleep, and wake up when wake_up_inode()
> is called from generic_delete_inode() after removing the inode from
> the hash chain.
I was trying to preserve some (possibly misinterpreted) behavior but I
can't remember what anymore. Anyway, since it's misbehaving, nuke it.
-- wli
prev parent reply other threads:[~2005-05-11 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 11:46 [PATCH] __wait_on_freeing_inode fix Miklos Szeredi
2005-05-06 12:14 ` Artem B. Bityuckiy
2005-05-06 12:19 ` Miklos Szeredi
2005-05-06 13:33 ` David Woodhouse
2005-05-06 13:38 ` Miklos Szeredi
2005-05-06 13:44 ` Artem B. Bityuckiy
2005-05-06 13:49 ` Miklos Szeredi
2005-05-06 13:52 ` David Woodhouse
2005-05-06 13:52 ` Artem B. Bityuckiy
2005-05-11 14:19 ` William Lee Irwin III [this message]
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=20050511141910.GE9304@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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