public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Kyoji Ogasawara <sawara04.o@gmail.com>
Cc: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com,
	johannes.thumshirn@wdc.com, brauner@kernel.org,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: restore mount option info messages during mount
Date: Tue, 12 Aug 2025 13:31:49 +0200	[thread overview]
Message-ID: <20250812113149.GC5507@suse.cz> (raw)
In-Reply-To: <CAKNDObASx8Nqd85AfzbEyMAC8XubHjcgZMzDbJyC_snYV-TJpQ@mail.gmail.com>

On Mon, Aug 11, 2025 at 05:08:39PM +0900, Kyoji Ogasawara wrote:
> > > @@ -1428,7 +1430,6 @@ static void btrfs_emit_options(struct btrfs_fs_info *info,
> > >  {
> > >       btrfs_info_if_set(info, old, NODATASUM, "setting nodatasum");
> > >       btrfs_info_if_set(info, old, DEGRADED, "allowing degraded mounts");
> > > -     btrfs_info_if_set(info, old, NODATASUM, "setting nodatasum");
> >
> > Shouldn't this rather be NODATACOW? The logic around the option is the
> > same as for NODATASUM, but for some reason NODATACOW is under
> > btrfs_info_if_unset() call.
> >
> > >       btrfs_info_if_set(info, old, SSD, "enabling ssd optimizations");
> > >       btrfs_info_if_set(info, old, SSD_SPREAD, "using spread ssd allocation scheme");
> > >       btrfs_info_if_set(info, old, NOBARRIER, "turning off barriers");
> > > --
> > > 2.50.1
> > >
> 
> Thank you for your suggestion.
> I'll update the code to handle NODATASUM similarly to NODATACOW.
> 
> =====
> btrfs_info_if_set(info, old, NODATASUM, "setting nodatasum");
> btrfs_info_if_set(info, old, DEGRADED, "allowing degraded mounts");
> btrfs_info_if_set(info, old, NODATACOW, "setting nodatacow");
> ...
> btrfs_info_if_unset(info, old, NODATASUM, "setting datasum");
> btrfs_info_if_unset(info, old, NODATACOW, "setting datacow");
> =====
> 
> Let me know if there's anything else I should consider.

I haven't seen other problems in the mount options. Please send the
fixes as separate patches. Thanks.

      reply	other threads:[~2025-08-12 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28  2:07 [PATCH] btrfs: restore mount option info messages during mount sawara04.o
2025-08-07 18:23 ` David Sterba
2025-08-07 19:04   ` Kyoji Ogasawara
2025-08-08 14:56 ` David Sterba
2025-08-11  8:08   ` Kyoji Ogasawara
2025-08-12 11:31     ` David Sterba [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=20250812113149.GC5507@suse.cz \
    --to=dsterba@suse.cz \
    --cc=brauner@kernel.org \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=johannes.thumshirn@wdc.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sawara04.o@gmail.com \
    /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