From: Al Viro <viro@zeniv.linux.org.uk>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>,
linux-fsdevel@vger.kernel.org, brauner@kernel.org
Subject: Re: [PATCH] ufs: convert ufs to the new mount API
Date: Fri, 17 Jan 2025 08:11:36 +0000 [thread overview]
Message-ID: <20250117081136.GP1977892@ZenIV> (raw)
In-Reply-To: <9f1435d3-5a40-405e-8e14-8cbdb49294f5@sandeen.net>
On Thu, Jan 16, 2025 at 04:07:44PM -0600, Eric Sandeen wrote:
> On 1/16/25 1:08 PM, Al Viro wrote:
> > On Thu, Jan 16, 2025 at 12:49:32PM -0600, Eric Sandeen wrote:
> >
> >> + switch (opt) {
> >> + case Opt_type:
> >> + if (reconfigure &&
> >> + (ctx->mount_options & UFS_MOUNT_UFSTYPE) != result.uint_32) {
> >> + pr_err("ufstype can't be changed during remount\n");
> >> + return -EINVAL;
> >> }
> >> + ufs_clear_opt(ctx->mount_options, UFS_MOUNT_UFSTYPE);
> >> + ufs_set_opt(ctx->mount_options, result.uint_32);
> >> + break;
> >
> > Do we really want to support ufstype=foo,ufstype=bar?
>
> well, we already do that today. Old code was:
>
> switch (token) {
> case Opt_type_old:
> ufs_clear_opt (*mount_options, UFSTYPE);
> ufs_set_opt (*mount_options, UFSTYPE_OLD);
> break;
> case Opt_type_sunx86:
> ufs_clear_opt (*mount_options, UFSTYPE);
> ufs_set_opt (*mount_options, UFSTYPE_SUNx86);
> break;
> ...
>
> so I was going for a straight conversion for now so that the behavior
> was exactly the same (i.e. keep the last-specified type. I know, it's
> weird, who would do that? Still. Don't break userspace? And we've been
> burned before.)
FWIW, see viro/vfs.git #work.ufs - separating ufs flavour and on-error
flags, dealing with -o ufstype conflicts, then your patch ported on
top of that.
next prev parent reply other threads:[~2025-01-17 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 18:49 [PATCH] ufs: convert ufs to the new mount API Eric Sandeen
2025-01-16 19:08 ` Al Viro
2025-01-16 22:07 ` Eric Sandeen
2025-01-17 8:11 ` Al Viro [this message]
2025-01-17 14:58 ` Eric Sandeen
2025-01-17 16:39 ` Al Viro
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=20250117081136.GP1977892@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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.