Re: [REGRESSION] Return change in 6.12.80+ with volatile mounting

On Sat, Apr 18, 2026 at 1:33 AM Chenglong Tang <[email protected]> wrote:
>
> CC Amir,
>
> For example, containerd 2.2.0 uses `volatile` instead of `fsync=volatile`:
> https://github.com/containerd/containerd/blob/main/core/mount/temp.go#L91C1-L92C1
>
> On Fri, Apr 17, 2026 at 3:41 PM Derek Taylor <[email protected]> wrote:
> >
> > This change seems to have so far affected at least containerd in an
> > issue reported here
> > https://github.com/containerd/containerd/issues/13250.
> >
> > In stable versions 6.12.80+, commit
> > 6c0cfbe020c0fcd2a544fcd2931fbc366ee3cd12 with the specific change
> > being:
> > [*] The mount option "volatile" is an alias to "fsync=volatile".
> > In this scenario, code relying on checking "volatile" will now fail
> > due to the return being "fsync=volatile".
> >
> > #regzbot introduced:v6.12.80

Hi Chenglong,

Thanks for the report.

Is this problem in production containerd or in a test suite?
I did not understand the purpose of WithTempMount().

Is it possible to fix this function to use string.Contains() instead of
exact match to the "volatile" mount option?

If needed I can fix the kernel to show the legacy "volatile" option,
but I would like to first understand how bad the impact of this regression
is on real production workloads.

Thanks,
Amir.