From: Jan Kara <jack@suse.cz>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>, Jan Kara <jack@suse.cz>,
Dave Chinner <dchinner@redhat.com>
Subject: Re: [PATCH] vfs: Fix missed wakeup in I_NEW handling
Date: Wed, 29 Feb 2012 12:08:36 +0100 [thread overview]
Message-ID: <20120229110836.GD18846@quack.suse.cz> (raw)
In-Reply-To: <1329759440-27490-1-git-send-email-jack@suse.cz>
On Mon 20-02-12 18:37:20, Jan Kara wrote:
> Commit 250df6ed removed wake_up_inode() (in particular a memory barrier before
> wake_up_bit()) on the basis that i_state transitions are protected by i_lock.
> That would be fine if all the readers of i_state were using i_lock as well. But
> wait_on_inode() doesn't use i_lock and thus the following can happen due to
> reordering:
>
> CPU 1 CPU 2
> unlock_new_inode()
> spin_lock(&inode->i_lock);
> wake_up_bit(&inode->i_state, __I_NEW);
> wait_on_inode()
> wait_on_bit(&inode->i_state, __I_NEW);
> inode->i_state &= ~I_NEW;
> ^^^ this store was reordered
> spin_unlock(&inode->i_lock);
>
> And waiter on CPU2 sleeps forever (or for a really long time).
>
> We fix the issue by using i_lock in wait_on_inode() in the spirit of commit
> 250df6ed.
Al, could you please pick up this fix? Thanks!
Honza
> CC: Dave Chinner <dchinner@redhat.com>
> Reported-by: Eric Buddington <ebuddington@wesleyan.edu>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/inode.c | 22 ++++++++++++++++++++++
> include/linux/writeback.h | 5 -----
> 2 files changed, 22 insertions(+), 5 deletions(-)
>
> diff --git a/fs/inode.c b/fs/inode.c
> index fb10d86..e768f9e 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -954,6 +954,28 @@ EXPORT_SYMBOL(lockdep_annotate_inode_mutex_key);
> #endif
>
> /**
> + * wait_on_inode - wait while inode is in I_NEW state
> + * @inode: inode to wait for
> + *
> + * This function waits until inode is fully initialized and exits new state
> + */
> +static void wait_on_inode(struct inode *inode)
> +{
> + DEFINE_WAIT_BIT(wq, &inode->i_state, __I_NEW);
> + wait_queue_head_t *wqh;
> +
> + might_sleep();
> + wqh = bit_waitqueue(&inode->i_state, __I_NEW);
> + spin_lock(&inode->i_lock);
> + while (inode->i_state & I_NEW) {
> + spin_unlock(&inode->i_lock);
> + __wait_on_bit(wqh, &wq, inode_wait, TASK_UNINTERRUPTIBLE);
> + spin_lock(&inode->i_lock);
> + }
> + spin_unlock(&inode->i_lock);
> +}
> +
> +/**
> * unlock_new_inode - clear the I_NEW state and wake up any waiters
> * @inode: new inode to unlock
> *
> diff --git a/include/linux/writeback.h b/include/linux/writeback.h
> index 995b8bf..e2dbc70 100644
> --- a/include/linux/writeback.h
> +++ b/include/linux/writeback.h
> @@ -96,11 +96,6 @@ long wb_do_writeback(struct bdi_writeback *wb, int force_wait);
> void wakeup_flusher_threads(long nr_pages, enum wb_reason reason);
>
> /* writeback.h requires fs.h; it, too, is not included from here. */
> -static inline void wait_on_inode(struct inode *inode)
> -{
> - might_sleep();
> - wait_on_bit(&inode->i_state, __I_NEW, inode_wait, TASK_UNINTERRUPTIBLE);
> -}
> static inline void inode_sync_wait(struct inode *inode)
> {
> might_sleep();
> --
> 1.7.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2012-02-29 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 17:37 Jan Kara
2012-02-29 11:08 ` Jan Kara [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=20120229110836.GD18846@quack.suse.cz \
--to=jack@suse.cz \
--cc=dchinner@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.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®