From: Michael Conrad <mconrad-HsDW+lVSy7tZ66HEZ9PjWw@public.gmane.org>
To: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: Vyacheslav Dubeyko
<slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Bug? Kernel doesn't prevent multiple rw nilfs mounts
Date: Fri, 25 Oct 2013 12:26:10 -0400 [thread overview]
Message-ID: <526A9BA2.7010202@intellitree.com> (raw)
In-Reply-To: <20131025.103819.27810920.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
On 10/24/2013 9:38 PM, Ryusuke Konishi wrote:
>> The double-mount should be prevented at the kernel level, right? I
>> could try a linux version direct from kernel.org, next.
>>
>> If the double-mount should be prevented in user-space, then I could
>> check things like the libc, compiler, strace, etc.
> The double-mount check is done in user-space to avoid that two garbage
> collectors run on the same device. Actually, nilfs kernel module
> itself can have two writable mounts.
>
> Nilfs-utils has two separate mount programs. One is the version
> using libmount library (nilfs-utils/sbin/mount/mount_libmount.c)
> and another is prior mount program (nilfs-utils/sbin/mount/mount.c).
>
> Recent distros use the former program because the prior mount program
> does not work when /etc/mtab is a symbolic link to /proc/mounts.
Ah-ha! Both systems use a symlink. On System 1, I compiled nilfs-tools
in a chroot so I could link them statically with recent library
versions, then installed the static binaries. Your configure script
would not have been able to see the /etc/mtab symlink.
However, System 2 had recent libraries and I was able to "emerge
nilfs-tools" normally. However, that Gentoo ebuild was marked
experimental, so maybe they know of the problem. I'll investigate which
source file was used for mount.nilfs2
Thanks for the information!
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-10-25 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 17:21 Bug? Kernel doesn't prevent multiple rw nilfs mounts Michael Conrad
[not found] ` <52695704.3010507-HsDW+lVSy7tZ66HEZ9PjWw@public.gmane.org>
2013-10-24 18:07 ` Vyacheslav Dubeyko
[not found] ` <76524A8B-8063-4335-9B26-615417123CDE-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-10-24 19:05 ` Michael Conrad
[not found] ` <52696F86.70203-HsDW+lVSy7tZ66HEZ9PjWw@public.gmane.org>
2013-10-24 19:57 ` Vyacheslav Dubeyko
[not found] ` <B40AD6B8-5EB1-4F64-9224-2F684AE3DF8A-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-10-24 20:01 ` Michael Conrad
[not found] ` <52697C8B.3090407-HsDW+lVSy7tZ66HEZ9PjWw@public.gmane.org>
2013-10-25 1:38 ` Ryusuke Konishi
[not found] ` <20131025.103819.27810920.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2013-10-25 1:54 ` Ryusuke Konishi
2013-10-25 16:26 ` Michael Conrad [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=526A9BA2.7010202@intellitree.com \
--to=mconrad-hsdw+lvsy7tz66hez9pjww@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org \
/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