From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:46214 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726378AbeG3W7y (ORCPT ); Mon, 30 Jul 2018 18:59:54 -0400 Date: Mon, 30 Jul 2018 23:23:00 +0200 From: Pavel Machek To: "Theodore Y. Ts'o" , Matthew Wilcox , Linus Torvalds , David Howells , Al Viro , linux-fsdevel , Linux Kernel Mailing List Subject: Re: [PATCH 36/38] vfs: Add a sample program for the new mount API [ver #10] Message-ID: <20180730212300.GA17452@amd> References: <153271267980.9458.7640156373438016898.stgit@warthog.procyon.org.uk> <153271292330.9458.14583488053811372222.stgit@warthog.procyon.org.uk> <25489.1532953411@warthog.procyon.org.uk> <20180730143104.GB24051@amd> <20180730180842.GA5544@bombadil.infradead.org> <20180730183847.GB5544@bombadil.infradead.org> <20180730194938.GA12962@bombadil.infradead.org> <20180730210209.GY21725@thunk.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <20180730210209.GY21725@thunk.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon 2018-07-30 17:02:09, Theodore Y. Ts'o wrote: > On Mon, Jul 30, 2018 at 12:49:38PM -0700, Matthew Wilcox wrote: > > > That said, people have wanted these kinds of extended error > > > descriptors forever, and the reason we haven't added them is that it > > > generally is more pain than it is necessarily worth. I'm not actually > > > at all convinced that has magically changed with the mount > > > configuration thing. > >=20 > > I'm not convinced we want to do this either, but if there's anywhere we > > do want to do it then mount seems like one of the few places it might be > > worth doing. The reasons that a mount failed are many, and it doesn't > > seem like a good idea to introduce a new errno every time a network > > filesystem finds a new failure mode. >=20 > We've lived without VMS-style error reporting for a long time, and it > *that* much of a real problem. Even with network file systems, I ? > So it might be that we're seriously over-thinking things. Most of the > really complicated error messages are at connection setup time, and > that can be done in userspace, and then userspace can handle all of > that awful gettext, or VMS-style error messages, or whatever other > horrors the I18N community want to inflict on us. :-) Well, this is designing brand-new error reporting channel to the userspace. I see that changing dmesg to provide something usable for gettext would be hard, but it is quite trivial to do it right this time. I agree we survived without that for a long time, but we have chance to do it right for a minimum price (because the interface is new we don't need compatibility). Thanks, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAltfgbQACgkQMOfwapXb+vIZnwCbBsE2Vih3Of6Jg+1lOejACDdA ytQAnAm4RkdrUXN5HMaOR9L1WW58IJyS =9eL7 -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l--