Date: Mon, 6 Dec 2021 22:01:09 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: freebsd-hackers@freebsd.org Subject: Re: nmount(2) returns undocumented EDEADLK Message-ID: <c08d9960-a5d3-7003-6be9-ab24cd3c1e11@grosbein.net> In-Reply-To: <CALH631kC2ZP_AXL9QyKD%2BgYaDOfqMRdH-3NBuVMyvcQctfkzeQ@mail.gmail.com> References: <CALH631mzdOFtOqwnBgQgGfOiX-CNfME%2Boa=-XT_JK0ws8A1t3Q@mail.gmail.com> <Ya3dsAJWKKctVXZs@kib.kiev.ua> <CALH631kC2ZP_AXL9QyKD%2BgYaDOfqMRdH-3NBuVMyvcQctfkzeQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
06.12.2021 21:38, Gleb Popov wrote: > > Indeed, I made a mistake in the code so the flags parameter was always 0. > After fixing it I'm now getting EOPNOTSUPP. > If remounting as ro is not supported, what are my options? Improve nullfs to implement such remounting :-) > Is there any > semantic difference between remounting with ro and unmounting/mounting > again? You will not be able to perform not-forced unmount in case of open files and maybe even current directory of a process pointing there.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c08d9960-a5d3-7003-6be9-ab24cd3c1e11>