From: NeilBrown <neilb@suse.de>
To: Jeff Layton <jlayton@kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
Sargun Dhillon <sargun@sargun.me>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Vivek Goyal <vgoyal@redhat.com>,
overlayfs <linux-unionfs@vger.kernel.org>,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>, NeilBrown <neilb@suse.com>,
Jan Kara <jack@suse.cz>
Subject: Re: [RFC PATCH 1/2] errseq: split the SEEN flag into two new flags
Date: Mon, 14 Dec 2020 10:35:56 +1100 [thread overview]
Message-ID: <87ft49jn37.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20201213132713.66864-2-jlayton@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 6688 bytes --]
On Sun, Dec 13 2020, Jeff Layton wrote:
> Overlayfs's volatile mounts want to be able to sample an error for
> their own purposes, without preventing a later opener from potentially
> seeing the error.
>
> The original reason for the SEEN flag was to make it so that we didn't
> need to increment the counter if nothing had observed the latest value
> and the error was the same. Eventually, a regression was reported in
> the errseq_t conversion, and we fixed that by using the SEEN flag to
> also mean that the error had been reported to userland at least once
> somewhere.
>
> Those are two different states, however. If we instead take a second
> flag bit from the counter, we can track these two things separately,
> and accomodate the overlayfs volatile mount use-case.
>
> Add a new MUSTINC flag that indicates that the counter must be
> incremented the next time an error is set, and rework the errseq
> functions to set and clear that flag whenever the SEEN bit is set or
> cleared.
>
> Test only for the MUSTINC bit when deciding whether to increment the
> counter and only for the SEEN bit when deciding what to return in
> errseq_sample.
>
> Add a new errseq_peek function to allow for the overlayfs use-case.
> This just grabs the latest counter and sets the MUSTINC bit, leaving
> the SEEN bit untouched.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> include/linux/errseq.h | 2 ++
> lib/errseq.c | 64 ++++++++++++++++++++++++++++++++++--------
> 2 files changed, 55 insertions(+), 11 deletions(-)
>
> diff --git a/include/linux/errseq.h b/include/linux/errseq.h
> index fc2777770768..6d4b9bc629ac 100644
> --- a/include/linux/errseq.h
> +++ b/include/linux/errseq.h
> @@ -9,6 +9,8 @@ typedef u32 errseq_t;
>
> errseq_t errseq_set(errseq_t *eseq, int err);
> errseq_t errseq_sample(errseq_t *eseq);
> +errseq_t errseq_peek(errseq_t *eseq);
> +errseq_t errseq_sample_advance(errseq_t *eseq);
> int errseq_check(errseq_t *eseq, errseq_t since);
> int errseq_check_and_advance(errseq_t *eseq, errseq_t *since);
> #endif
> diff --git a/lib/errseq.c b/lib/errseq.c
> index 81f9e33aa7e7..5cc830f0361b 100644
> --- a/lib/errseq.c
> +++ b/lib/errseq.c
> @@ -38,8 +38,11 @@
> /* This bit is used as a flag to indicate whether the value has been seen */
> #define ERRSEQ_SEEN (1 << ERRSEQ_SHIFT)
Would this look nicer using the BIT() macro?
#define ERRSEQ_SEEN BIT(ERRSEQ_SHIFT)
>
> +/* This bit indicates that value must be incremented even when error is same */
> +#define ERRSEQ_MUSTINC (1 << (ERRSEQ_SHIFT + 1))
#define ERRSEQ_MUSTINC BIT(ERRSEQ_SHIFT+1)
or if you don't like the BIT macro (not everyone does), then maybe
#define ERR_SEQ_MUSTINC (ERRSEQ_SEEN << 1 )
??
> +
> /* The lowest bit of the counter */
> -#define ERRSEQ_CTR_INC (1 << (ERRSEQ_SHIFT + 1))
> +#define ERRSEQ_CTR_INC (1 << (ERRSEQ_SHIFT + 2))
Ditto.
>
> /**
> * errseq_set - set a errseq_t for later reporting
> @@ -77,11 +80,11 @@ errseq_t errseq_set(errseq_t *eseq, int err)
> for (;;) {
> errseq_t new;
>
> - /* Clear out error bits and set new error */
> - new = (old & ~(MAX_ERRNO|ERRSEQ_SEEN)) | -err;
> + /* Clear out flag bits and set new error */
> + new = (old & ~(MAX_ERRNO|ERRSEQ_SEEN|ERRSEQ_MUSTINC)) | -err;
This is starting to look clumsy (or maybe, this already looked clumsy,
but now that is hard to ignore).
new = (old & (ERRSEQ_CTR_INC - 1)) | -err
Also this assumes MAX_ERRNO is a mask, which it is .. today.
BUILD_BUG_ON(MAX_ERRNO & (MAX_ERRNO + 1));
??
>
> - /* Only increment if someone has looked at it */
> - if (old & ERRSEQ_SEEN)
> + /* Only increment if we have to */
> + if (old & ERRSEQ_MUSTINC)
> new += ERRSEQ_CTR_INC;
>
> /* If there would be no change, then call it done */
> @@ -122,14 +125,50 @@ EXPORT_SYMBOL(errseq_set);
> errseq_t errseq_sample(errseq_t *eseq)
> {
> errseq_t old = READ_ONCE(*eseq);
> + errseq_t new = old;
>
> - /* If nobody has seen this error yet, then we can be the first. */
> - if (!(old & ERRSEQ_SEEN))
> - old = 0;
> - return old;
> + /*
> + * For the common case of no errors ever having been set, we can skip
> + * marking the SEEN|MUSTINC bits. Once an error has been set, the value
> + * will never go back to zero.
> + */
> + if (old != 0) {
> + new |= ERRSEQ_SEEN|ERRSEQ_MUSTINC;
You lose me here. Why is ERRSEQ_SEEN being set, where it wasn't before?
The ERRSEQ_SEEN flag not means precisely "The error has been reported to
userspace".
This operations isn't used to report errors - that is errseq_check().
I'm not saying the code it wrong - I really cannot tell.
I'm just saying that I cannot see why it might be right.
Thanks,
NeilBrown
> + if (old != new)
> + cmpxchg(eseq, old, new);
> + if (!(old & ERRSEQ_SEEN))
> + return 0;
> + }
> + return new;
> }
> EXPORT_SYMBOL(errseq_sample);
>
> +/**
> + * errseq_peek - Grab current errseq_t value, but don't mark it SEEN
> + * @eseq: Pointer to errseq_t to be sampled.
> + *
> + * In some cases, we need to be able to sample the errseq_t, but we're not
> + * in a situation where we can report the value to userland. Use this
> + * function to do that. This ensures that later errors will be recorded,
> + * and that any current errors are reported at least once.
> + *
> + * Context: Any context.
> + * Return: The current errseq value.
> + */
> +errseq_t errseq_peek(errseq_t *eseq)
> +{
> + errseq_t old = READ_ONCE(*eseq);
> + errseq_t new = old;
> +
> + if (old != 0) {
> + new |= ERRSEQ_MUSTINC;
> + if (old != new)
> + cmpxchg(eseq, old, new);
> + }
> + return new;
> +}
> +EXPORT_SYMBOL(errseq_peek);
> +
> /**
> * errseq_check() - Has an error occurred since a particular sample point?
> * @eseq: Pointer to errseq_t value to be checked.
> @@ -143,7 +182,10 @@ EXPORT_SYMBOL(errseq_sample);
> */
> int errseq_check(errseq_t *eseq, errseq_t since)
> {
> - errseq_t cur = READ_ONCE(*eseq);
> + errseq_t cur = READ_ONCE(*eseq) & ~(ERRSEQ_MUSTINC|ERRSEQ_SEEN);
> +
> + /* Clear the flag bits for comparison */
> + since &= ~(ERRSEQ_MUSTINC|ERRSEQ_SEEN);
>
> if (likely(cur == since))
> return 0;
> @@ -195,7 +237,7 @@ int errseq_check_and_advance(errseq_t *eseq, errseq_t *since)
> * can advance "since" and return an error based on what we
> * have.
> */
> - new = old | ERRSEQ_SEEN;
> + new = old | ERRSEQ_SEEN | ERRSEQ_MUSTINC;
> if (new != old)
> cmpxchg(eseq, old, new);
> *since = new;
> --
> 2.29.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next prev parent reply other threads:[~2020-12-13 23:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 13:27 [RFC PATCH 0/2] errseq+overlayfs: accomodate the volatile upper layer use-case Jeff Layton
2020-12-13 13:27 ` [RFC PATCH 1/2] errseq: split the SEEN flag into two new flags Jeff Layton
2020-12-13 23:35 ` NeilBrown [this message]
2020-12-14 13:37 ` Jeffrey Layton
2020-12-14 22:00 ` NeilBrown
2020-12-14 23:32 ` Jeff Layton
2020-12-13 13:27 ` [RFC PATCH 2/2] overlayfs: propagate errors from upper to overlay sb in sync_fs Jeff Layton
2020-12-14 21:38 ` Vivek Goyal
2020-12-14 22:04 ` Sargun Dhillon
2020-12-14 23:01 ` Vivek Goyal
2020-12-14 23:53 ` Jeff Layton
2020-12-15 13:16 ` Jeff Layton
2020-12-15 14:59 ` Vivek Goyal
2020-12-15 15:23 ` Jeff Layton
2020-12-15 15:39 ` Vivek Goyal
2020-12-15 15:06 ` Vivek Goyal
2020-12-17 19:28 ` Sargun Dhillon
2020-12-13 20:31 ` [RFC PATCH 0/2] errseq+overlayfs: accomodate the volatile upper layer use-case Sargun Dhillon
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=87ft49jn37.fsf@notabene.neil.brown.name \
--to=neilb@suse.de \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=neilb@suse.com \
--cc=sargun@sargun.me \
--cc=vgoyal@redhat.com \
--cc=willy@infradead.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 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).