From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org, allison.henderson@oracle.com
Subject: Re: [PATCH 3/5] xfs: warn about LARP once per day
Date: Sun, 22 May 2022 18:16:57 -0700 [thread overview]
Message-ID: <YorgidgW7bXAdcZt@magnolia> (raw)
In-Reply-To: <20220522225404.GN1098723@dread.disaster.area>
On Mon, May 23, 2022 at 08:54:04AM +1000, Dave Chinner wrote:
> On Sun, May 22, 2022 at 08:28:30AM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > Since LARP is an experimental debug-only feature, we should try to warn
> > about it being in use once per day, not once per reboot.
> >
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> > fs/xfs/xfs_log.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> >
> > diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> > index 9dc748abdf33..edd077e055d5 100644
> > --- a/fs/xfs/xfs_log.c
> > +++ b/fs/xfs/xfs_log.c
> > @@ -3910,8 +3910,8 @@ xfs_attr_use_log_assist(
> > if (error)
> > goto drop_incompat;
> >
> > - xfs_warn_once(mp,
> > -"EXPERIMENTAL logged extended attributes feature added. Use at your own risk!");
> > + xfs_warn_daily(mp,
> > + "EXPERIMENTAL logged extended attributes feature added. Use at your own risk!");
>
> I think even this is wrong. We need this to warn once per *mount*
> like we do with all other experimental features, not once or once
> per day. i.e. we could have 10 filesystems mounted and only one of
> them will warn that EXPERIMENTAL features are in use.
>
> We really need all filesystems that use an experimental feature to
> warn about the use of said feature, not just a single filesystem.
> That will make this consistent with the way we warn once (and once
> only) at mount time about EXPERIMENTAL features that are enabled at
> mount time...
Ok. I was thinking we could have an unsigned long m_warned then all
we'd need to do is convert the existing three callers (scrub, shrink,
larp) to something like:
if (!test_and_set_bit(XFS_WARNED_FUBAR, &mp->m_warned))
xfs_warn(mp,
"EXPERIMENTAL fubar feature is enabled, use at your own risk!");
Also, any thoughts on the last two patches?
--D
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
next prev parent reply other threads:[~2022-05-23 1:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 15:28 [PATCHSET 0/5] xfs: last pile of LARP cleanups for 5.19 Darrick J. Wong
2022-05-22 15:28 ` [PATCH 1/5] xfs: don't log every time we clear the log incompat flags Darrick J. Wong
2022-05-22 15:28 ` [PATCH 2/5] xfs: refactor the code to warn about something once per day Darrick J. Wong
2022-05-22 15:28 ` [PATCH 3/5] xfs: warn about LARP " Darrick J. Wong
2022-05-22 22:54 ` Dave Chinner
2022-05-23 1:16 ` Darrick J. Wong [this message]
2022-05-23 2:51 ` Dave Chinner
2022-05-23 2:53 ` Darrick J. Wong
2022-05-22 15:28 ` [PATCH 4/5] xfs: tell xfs_attr_set if the log is actually letting us use LARP mode Darrick J. Wong
2022-05-22 15:28 ` [PATCH 5/5] xfs: move xfs_attr_use_log_assist out of libxfs Darrick J. Wong
2022-05-23 3:34 ` Dave Chinner
2022-05-23 19:12 ` Darrick J. Wong
2022-05-23 22:56 ` Dave Chinner
2022-05-24 0:35 ` Darrick J. Wong
2022-05-24 1:02 ` Dave Chinner
2022-05-24 1:20 ` Darrick J. Wong
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=YorgidgW7bXAdcZt@magnolia \
--to=djwong@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=david@fromorbit.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox