On Fri, Feb 23, 2024 at 04:06:29PM +0100, Christian Brauner wrote: > On Thu, Feb 22, 2024 at 09:22:52AM -0600, Eric Sandeen wrote: > > As filesystems are converted to the new mount API, informational messages, > > errors, and warnings are being routed through infof, errorf, and warnf > > type functions provided by the mount API, which places these messages in > > the log buffer associated with the filesystem context rather than > > in the kernel log / dmesg. > > > > However, userspace is not yet extracting these messages, so they are > > essentially getting lost. mount(8) still refers the user to dmesg(1) > > on failure. > > I mean sure we can do this. But we should try without a Kconfig option > for this. > > But mount(8) and util-linux have been switched to the new mount api in > v2.39 and libmount already has the code to read and print the error > messages: Why was there not an API flag to indicate when userspace is listening for these?
