David Howells wrote:
> > So my question is, what do we do here?
>
> Hmmm... As the code stands, MS_RDONLY, MS_SYNCHRONOUS, MS_MANDLOCK,
> MS_I_VERSION and MS_LAZYTIME should all be masked off before the new flags are
> set if called from mount(2) rather than fsconfig(2).
>
> do_remount()
Josef Bacik wrote:
> So my question is, what do we do here?
Hmmm... As the code stands, MS_RDONLY, MS_SYNCHRONOUS, MS_MANDLOCK,
MS_I_VERSION and MS_LAZYTIME should all be masked off before the new flags are
set if called from mount(2) rather than fsconfig(2).
do_remount() gives MS_RMT_MASK to
On 7/29/20 2:41 PM, Eric Sandeen wrote:
On 7/29/20 11:32 AM, Josef Bacik wrote:
Hello,
Eric reported a problem to me where we were clearing SB_I_VERSION on remount of a btrfs
file system. After digging through I discovered it's because we expect the proper flags
that we want to be passed in
On 7/29/20 11:32 AM, Josef Bacik wrote:
> Hello,
>
> Eric reported a problem to me where we were clearing SB_I_VERSION on remount
> of a btrfs file system. After digging through I discovered it's because we
> expect the proper flags that we want to be passed in via the mount() syscall,
> and
Hello,
Eric reported a problem to me where we were clearing SB_I_VERSION on remount of
a btrfs file system. After digging through I discovered it's because we expect
the proper flags that we want to be passed in via the mount() syscall, and
because we didn't have "iversion" in our
5 matches
Mail list logo
