From: Jelle Licht <jlicht@fsfe.org>
To: andy <chengong456@qq.com>, 63554 <63554@debbugs.gnu.org>
Subject: bug#63554: 63554
Date: Wed, 04 Sep 2024 11:17:20 +0200 [thread overview]
Message-ID: <87ikvb6an3.fsf@fsfe.org> (raw)
In-Reply-To: <tencent_9913866CE6B0DF2C1E8AC40C1C9C2509C207@qq.com>
(I decoded html entities ):
"andy" via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> Also had this exact same problem. Looking at patch #56880, it tried
> to add the shared option, but found that the `mount(2)` syscall had
> to be called twice, once to mount it, then once to make the already
> existing mount shared, so just adding the bit-flag `MS_SHARED` to
> that syscall didn't work. The patch seems to not include that bitflag
> until someone needed it enough to implement calling `mount(2)`
> twice. Pretty sure the option doesn't do anything because it doesn't
> change the bit-flag in the `mount-flags->bit-mask` procedure at
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/build/file-systems.scm#n1155
> So the bug seems to be intentional, and a fix would have to have guix
> first mount the filesystem normally, then change it to a shared
> mount.
Is this something that just needs to be picked up by someone, or would
it be more complicated than that?
- Jelle
prev parent reply other threads:[~2024-09-04 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 9:39 bug#63554: 'shared mount flag ignored on file-system configuration Wilke Schwiedop via Bug reports for GNU Guix
2024-08-20 2:34 ` bug#63554: 63554 andy via Bug reports for GNU Guix
2024-09-04 9:17 ` Jelle Licht [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ikvb6an3.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--cc=63554@debbugs.gnu.org \
--cc=chengong456@qq.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).