Re: kern/52056: mount -u / causes a kernel assertion

[Rhialto <rhialto%falu.nl@localhost>]

The following reply was made to PR kern/52056; it has been noted by GNATS.

From: Rhialto <rhialto%falu.nl@localhost>
To: Robert Elz <kre%munnari.OZ.AU@localhost>
Cc: Matt Sporleder <msporleder%gmail.com@localhost>,
        =?iso-8859-1?Q?Jarom=EDr?= Dole?ek <jaromir.dolecek%gmail.com@localhost>,
        gnats-bugs%netbsd.org@localhost, kern-bug-people%netbsd.org@localhost,
        current-users%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
        Martin Husemann <martin%netbsd.org@localhost>
Subject: Re: kern/52056: mount -u / causes a kernel assertion
Date: Mon, 10 Apr 2017 22:21:12 +0200

 --0vzXIDBeUiKkjNJl
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Sat 11 Mar 2017 at 08:00:54 +0700, Robert Elz wrote:
 > Given all that, the best might be to basically copy the FreeBSD setup,
 > though I think I would prefer if
 >=20
 > 	mount -u <filesys>
 >=20
 > with no command line options at all (which currently means mount rw,
 > and disable any other mount options previously set, on NetBSD and FreeBSD,
 > and would be a "convert to rw, leaving all other options on OpenBSD)
 > was instead treated as if (in FreeBSD syntax)
 > 	mount -u -o fstab <filesys>
 > was given, so this (just mount -u) becomes an easy way to simply set the
 > filesys mount to the way fstab says it should be.
 
 Hm, personally I would expect that an "update" option would only update
 the options  specify, and leave ALL others unchanged. So the "-o
 current" syntax would be the default.
 
 MAYBE a special case could be made in case only -u is given and no other
 options, that then the fstab options are used, but the "-o fstab" syntax
 to make that explicit seems better to me.
 
 -Olaf.
 --=20
 ___ Olaf 'Rhialto' Seibert  -- Wayland: Those who don't understand X
 \X/ rhialto/at/xs4all.nl    -- are condemned to reinvent it. Poorly.
 
 --0vzXIDBeUiKkjNJl
 Content-Type: application/pgp-signature; name="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 
 iQEcBAEBAgAGBQJY6+k4AAoJEJmJxkVhw/vTJRgIAMVb9EQQ8JGeJJ99hHVI1XHS
 muzwT8MhW7XZDxNFdDD7ePpgjVmzlBVJ5tvGcdCXSt0bQ44Qz0Q1/cLgBqbyQiKR
 Ej5m/MUsjyovPqInLaE+r6jjPwkNC+YE8tnmgr0lhoOUMQhpssF6DlKqmwbKsowQ
 A+4Ylh4xaXAHIumockJkz7AhrB1WIzHAZJUjTyJ5cZMq9Rd3PAUyw3ODdWOGWZTp
 3jSDQhjQzcTr4tT9+XIMeOR9ZXnz8MRRyoNBDUm3IhF40hWYAzC85xERxWZsvWG6
 jJ2uR0owXySiOCU9Z+cWwt7G63CfoZ42OjaOOKpC0rRlx9azG7uOK+6rk0343Gs=
 =PNmh
 -----END PGP SIGNATURE-----
 
 --0vzXIDBeUiKkjNJl--