On Wed, 28 May 2025 at 12:55, Karel Zak <kzak@xxxxxxxxxx> wrote: > Why is it fine for mount(2) but wrong for fsconfig()? This is the > question. There is an incompatibility between the APIs. Where is it documented that the fsconfig(2) shall have the same replace semantics as mount(2)? When I reviewed the new API, I certainly didn't think that it should have these semantics, and I'm not even sure it did have it back then. But of course I may have missed it. I think this is just a bad accident, and I'm wondering if this could still be fixed in a way that doesn't introduce more hackery. One idea is to introduce a flag (e.g. FSPICK_REPLACE_ONLY) that makes the filesystem initialize the fs_context with the current options. That would work, no? Thanks, Miklos
