mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: marcelo.tosatti@cyclades.com, davem@redhat.com,
	linux-kernel@vger.kernel.org, sim@netnation.com,
	viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: Linux 2.4.25-pre5
Date: Fri, 16 Jan 2004 08:58:11 +0000	[thread overview]
Message-ID: <1074243491.31120.49.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <20040116004516.5fea2995.akpm@osdl.org>

On Fri, 2004-01-16 at 00:45 -0800, Andrew Morton wrote:
> Really, the init_waitqueue_head() should be done prior to putting the inode
> back into slab.

I had that version first but preferred doing it with all the other inode
initialisation in alloc_inode() rather than in destroy_inode(). If you
do it this way, you reinit even when you're about to discard the slab
pages. I don't care much though. 

===== inode.c 1.48 vs edited =====
--- 1.48/fs/inode.c	Wed Jan 14 20:51:18 2004
+++ edited/inode.c	Fri Jan 16 08:56:14 2004
@@ -127,6 +127,10 @@
 {
 	if (inode_has_buffers(inode))
 		BUG();
+	/* Reinitialise the waitqueue head because __wait_on_freeing_inode()
+	   may have left stale entries on it which it can't remove (since
+	   it knows we're freeing the inode right now */
+	init_waitqueue_head(&inode->i_wait);
 	if (inode->i_sb->s_op->destroy_inode)
 		inode->i_sb->s_op->destroy_inode(inode);
 	else

-- 
dwmw2



  reply	other threads:[~2004-01-16  8:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 20:19 Marcelo Tosatti
2004-01-15 22:55 ` David S. Miller
2004-01-15 23:12   ` Arnaldo Carvalho de Melo
2004-01-15 23:01     ` David S. Miller
2004-01-15 23:23       ` Arnaldo Carvalho de Melo
2004-01-15 23:23   ` Marcelo Tosatti
2004-01-16  7:44     ` David Woodhouse
2004-01-16  8:45       ` Andrew Morton
2004-01-16  8:58         ` David Woodhouse [this message]
2004-01-19 15:15 ` Geert Uytterhoeven
2004-02-02 15:39   ` [PATCH] fs/inode.c warning if !HIGHMEM (was: Re: Linux 2.4.25-pre5) Geert Uytterhoeven

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=1074243491.31120.49.camel@imladris.demon.co.uk \
    --to=dwmw2@infradead.org \
    --cc=akpm@osdl.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=sim@netnation.com \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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

all inboxes | Powered by JetHome®