From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3 3/4] super: wait for nascent superblocks
Date: Mon, 21 Aug 2023 17:56:07 +0200 [thread overview]
Message-ID: <20230821-dingo-befund-4eb177ad9df8@brauner> (raw)
In-Reply-To: <20230821155237.d4luoqrzhnlffbti@quack3>
> I think we misunderstood here. I believe we need:
>
> /*
> * Pairs with smp_load_acquire() in super_lock() to make sure
> * all initializations in the superblock are seen by the user
> * seeing SB_BORN sent.
> */
> smp_store_release(&sb->s_flags, sb->s_flags | flag);
> /*
> * Pairs with the barrier in prepare_to_wait_event() to make sure
> * ___wait_var_event() either sees SB_BORN set or
> * waitqueue_active() check in wake_up_var() sees the waiter
> */
> smp_rmb();
> wake_up_var(&sb->s_flags);
Oh right, sorry I missed this.
> Maybe we can have in these places rather:
>
> if (!super_lock_excl(sb))
> WARN(1, "Dying superblock while freezing!");
>
> So that we reduce the amount of __super_lock_excl() calls which are kind of
> special. In these places we hold active reference so practically this is
> equivalent. Just a though, pick whatever you find better, I don't have a
> strong opinion but wanted to share this idea.
Ok, will pick yours.
Do you want me to resend?
next prev parent reply other threads:[~2023-08-21 15:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 14:00 [PATCH v3 0/4] super: allow waiting without s_umount held Christian Brauner
2023-08-18 14:00 ` [PATCH v3 1/4] super: use locking helpers Christian Brauner
2023-08-18 14:00 ` [PATCH v3 2/4] super: make locking naming consistent Christian Brauner
2023-08-18 14:00 ` [PATCH v3 3/4] super: wait for nascent superblocks Christian Brauner
2023-08-18 14:57 ` Matthew Wilcox
2023-08-18 15:21 ` Christian Brauner
2023-08-21 15:52 ` Jan Kara
2023-08-21 15:56 ` Christian Brauner [this message]
2023-08-21 16:04 ` Jan Kara
2023-08-21 16:02 ` Jan Kara
2023-08-21 16:08 ` Christian Brauner
2023-08-18 14:00 ` [PATCH v3 4/4] super: wait until we passed kill super Christian Brauner
2023-08-21 15:57 ` Jan Kara
2023-08-22 12:36 ` [PATCH v3 0/4] super: allow waiting without s_umount held Christian Brauner
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=20230821-dingo-befund-4eb177ad9df8@brauner \
--to=brauner@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).