All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] Revert "f2fs: remove unreachable lazytime mount option parsing"
Date: Thu, 21 Nov 2024 18:37:49 +0000	[thread overview]
Message-ID: <Zz99_caU7lW0m9Il@google.com> (raw)
In-Reply-To: <8b2212c6-2c11-4b9b-b8be-61c6ffb6d94b@redhat.com>

On 11/21, Eric Sandeen wrote:
> On 11/20/24 2:38 PM, Jaegeuk Kim wrote:
> > On 11/20, Eric Sandeen wrote:
> 
> ...
> 
> >> (Note that f2fs is the only filesystem that attempts to handle lazytime within
> >> the filesystem itself):
> >>
> >> [linux]# grep -r \"lazytime\" fs/*/
> >> fs/f2fs/super.c:	{Opt_lazytime, "lazytime"},
> >> [linux]#
> >>
> >> I'm not entirely sure how to untangle all this, but regressions are not acceptable,
> >> so please revert my commit for now.
> > 
> > Thanks for the explanation. At a glance, I thought it's caused that f2fs doesn't
> > implement fs_context_operations. We'll take a look at how to support it.
> 
> (cc: list trimmed)
> 
> I had thought the conversion would resolve this too, but had not considered direct
> mount(2) calls passing the string in, which is something that probably needs to be
> supported even after the conversion, sadly.
> 
> As a reminder, this might be a start / sketch of how to convert to the new mount API:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/sandeen/linux.git/log/?h=f2fs-mount-api
> 
> It's not entirely correct, but at least the first several patches are probably the right
> idea - getting sb / sbi out of the parsing path, and deferring option-vs-disk-feature
> checks until after the superblock is read, etc.
> 
> The final patch is probably not the way to go - it allocates an entire f2fs_sb_info
> in f2fs_init_fs_context - it probably makes more sense to create a new context
> structure which holds only mount options, which is then transferred into the
> sbi after option parsing during mount or remount.

Cool. Let us take a look at them soon. Thank you!

> 
> I was doing these conversions as a side project, and given the f2fs conversion
> complexity, I have yet to get to a series that I'm happy with. Perhaps expert
> eyes can help!
> 
> Thanks,
> -Eric


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2024-11-21 18:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12  1:08 [f2fs-dev] [PATCH] Revert "f2fs: remove unreachable lazytime mount option parsing" Jaegeuk Kim via Linux-f2fs-devel
2024-11-12  1:08 ` Jaegeuk Kim
2024-11-12 21:39 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2024-11-12 21:39   ` Jaegeuk Kim
2024-11-19  2:18   ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2024-11-19  2:18     ` Chao Yu
2024-11-19 20:48     ` Jaegeuk Kim via Linux-f2fs-devel
2024-11-19 20:48       ` Jaegeuk Kim
2024-11-20  2:57       ` Chao Yu via Linux-f2fs-devel
2024-11-20  2:57         ` Chao Yu
2024-11-20 20:35         ` Jaegeuk Kim via Linux-f2fs-devel
2024-11-20 20:35           ` Jaegeuk Kim
2024-11-20 14:27   ` Eric Sandeen
2024-11-20 14:27     ` Eric Sandeen
2024-11-20 14:52     ` [f2fs-dev] " Eric Sandeen
2024-11-20 14:52       ` Eric Sandeen
2024-11-20 20:38       ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2024-11-20 20:38         ` Jaegeuk Kim
2024-11-21 15:11         ` [f2fs-dev] " Eric Sandeen
2024-11-21 18:37           ` Jaegeuk Kim via Linux-f2fs-devel [this message]
2024-11-18 17:00 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-18 17:00   ` patchwork-bot+f2fs
2024-11-21  1:15 ` Chao Yu via Linux-f2fs-devel
2024-11-21  1:15   ` Chao Yu

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=Zz99_caU7lW0m9Il@google.com \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=jaegeuk@kernel.org \
    --cc=sandeen@redhat.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 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.