[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegs1AVJuh1U97cpTx14KcnQeO2XmtvrOwbyoZ8wvqfgqPA@mail.gmail.com>
Date: Tue, 20 May 2025 18:40:35 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Kent Overstreet <kent.overstreet@...ux.dev>
Cc: Amir Goldstein <amir73il@...il.com>, linux-fsdevel@...r.kernel.org,
linux-bcachefs@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-unionfs@...r.kernel.org, Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>
Subject: Re: [PATCH 0/6] overlayfs + casefolding
On Tue, 20 May 2025 at 17:21, Kent Overstreet <kent.overstreet@...ux.dev> wrote:
> Docker mounts the image, but then everything explodes when you try to
> use it with what look to the user like impenetrable IO errors.
>
> That's a bad day for someone, or more likely a lot of someones.
Wouldn't it be docker's responsibility to know that that won't work
with overlayfs?
Any error, whether at startup or during operation is not something the
user will like.
What am I missing?
Thanks,
Miklos
Powered by blists - more mailing lists