|
|
Log in / Subscribe / Register

missing y2038 support

missing y2038 support

Posted Mar 10, 2022 17:42 UTC (Thu) by jccleaver (guest, #127418)
In reply to: missing y2038 support by arnd
Parent article: When and why to deprecate filesystems

> We originally had a patch to refuse writable mounts on file systems that have known y2038 bugs, making those images read-only, but that got Nack'ed and we ended up with just a warning printed to the console.

This really seems like something to bubble back up, at least in preparation for the actual post-2038 strategy. I can't think of a better solution for how to properly handle something that is perfectly readable fine but which has no way to encode properly-readable vital (i.e. security) metadata about an operation.

Just leave this feature flag disabled for now, and builders can enable it as desired; with a full flip in the years to come.


to post comments


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds