All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH V2] fs: don't scan the inode cache before SB_BORN is set
Date: Tue, 27 Mar 2018 08:24:45 +0100	[thread overview]
Message-ID: <20180327072445.GS30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180327065756.GO18129@dastard>

On Tue, Mar 27, 2018 at 05:57:56PM +1100, Dave Chinner wrote:
>  	 */
> +	smp_rmb();
> +	if (!(sb->s_flags & SB_BORN))
> +		return 0;
> +
>  	if (sb->s_op && sb->s_op->nr_cached_objects)
>  		total_objects = sb->s_op->nr_cached_objects(sb, sc);
>  
> @@ -1227,7 +1237,13 @@ mount_fs(struct file_system_type *type, int flags, const char *name, void *data)
>  	sb = root->d_sb;
>  	BUG_ON(!sb);
>  	WARN_ON(!sb->s_bdi);
> +
> +	/*
> +	 * Write barrier is for super_cache_count() to ensure it does not run
> +	 * until after the superblock is fully set up.
> +	 */
>  	sb->s_flags |= SB_BORN;
> +	smp_wmb();


Umm...  OK, I'm nearly asleep right now, but... shouldn't that be

	if (check ->s_flags)
		bugger off
	smp_rmb();
	loads
vs.
	stores
	smp_wmb();
	store ->s_flags?

IOW, your barriers seem to be in the wrong places...

      reply	other threads:[~2018-03-27  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26  4:35 [PATCH] fs: don't scan the inode cache before SB_ACTIVE is set Dave Chinner
2018-03-26  5:31 ` Al Viro
2018-03-26  5:51   ` Al Viro
2018-03-26  6:33     ` Dave Chinner
2018-03-26  6:55       ` Al Viro
2018-03-26  7:21         ` Dave Chinner
2018-03-27  6:57 ` [PATCH V2] fs: don't scan the inode cache before SB_BORN " Dave Chinner
2018-03-27  7:24   ` Al Viro [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=20180327072445.GS30522@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@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 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.