From: Amir Goldstein <amir73il@gmail.com>
To: Chenglong Tang <chenglongtang@google.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org,
Fei Lv <feilv@asrmicro.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] ovl: make fsync after metadata copy-up opt-in mount option
Date: Tue, 24 Mar 2026 20:09:33 +0100 [thread overview]
Message-ID: <CAOQ4uxhdpJ5+awnceRzRxmP-ot25_w0LogLYpncLJZXxQOj33Q@mail.gmail.com> (raw)
In-Reply-To: <CAOdxtTY0jsqrJVXH=eQzYcowEpkDxwrk1DMgg8QD4ojygWJQ_Q@mail.gmail.com>
On Tue, Mar 24, 2026 at 7:04 PM Chenglong Tang <chenglongtang@google.com> wrote:
>
> Hi,
>
> Regarding the patch: because we are currently locked to the 6.12 LTS
> kernel, this patch doesn't apply cleanly to our tree (due to missing
> mainline dependencies like the str_on_off helper).
Hence:
Depends: 50e638beb67e0 ("ovl: Use str_on_off() helper in ovl_show_options()")
I added it for bots and humans that do backporting to 6.12.
It is not a "real" dependency. It is a weak dependency for clean apply
which works well for 6.12.y.
>
> Since we are actively tracking this for a Google COS customer
> escalation, do you have a rough timeline for when you expect this to
> be merged into mainline and subsequently picked up by the 6.12 stable
> queue?
>
It's queued on the ovl-fixes branch to be merged into linux-next
tonight.
If there are no rejects from bots or humans, I plan to send it to Linus
before the weekend.
> We will officially pull it into the COS tree as soon as it lands in
> linux-stable.
>
> Thanks again for the excellent support,
Your report was very informative and well prepared.
This helps :)
Thanks,
Amir.
next prev parent reply other threads:[~2026-03-24 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 14:57 [PATCH] ovl: make fsync after metadata copy-up opt-in mount option Amir Goldstein
2026-03-24 18:04 ` Chenglong Tang
2026-03-24 19:09 ` Amir Goldstein [this message]
2026-03-25 5:55 ` Christoph Hellwig
2026-03-25 12:03 ` Amir Goldstein
2026-03-25 13:11 ` Amir Goldstein
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=CAOQ4uxhdpJ5+awnceRzRxmP-ot25_w0LogLYpncLJZXxQOj33Q@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=chenglongtang@google.com \
--cc=feilv@asrmicro.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stable@vger.kernel.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