lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 21 Jan 2019 19:38:23 -0500
From:   "Theodore Y. Ts'o" <>
To:     "Darrick J. Wong" <>
CC:     Jann Horn <>, Richard Henderson <>,
        Ivan Kokshaysky <>,
        Matt Turner <>,
        Alexander Viro <>,
        <>, Arnd Bergmann <>,
        "Eric W. Biederman" <>,
        Andreas Dilger <>,
        <>, <>,
        Dave Chinner <>,
        Pavel Machek <>, <>,
Subject: Re: [PATCH v4 1/3] fs: hoist EFSCORRUPTED definition into uapi header

On Mon, Jan 21, 2019 at 03:51:58PM -0800, Darrick J. Wong wrote:
> I disagree with upending 13 years of established precedent for user
> visible behavior.  We possibly could've pulled this off ten years ago,
> but it's waaaay too late now.  Too much work, too little gain.

I remember the discussion; but now that we're adding it to uapi header
files, it's really going to be impossible.  And I have had some
regrets about that decision ten years ago.  I agree it would cause
confusion if we do it now, but it's basically the our last
How about this then?  We could ask glibc to change the string returned
by strerror for EUCLEAN/EFSCORRUPTED to be something like "File system
or block device corrupted".  This is how the errno is used in the
kernel; and if we don't want to change the error code, changing the
string returned by glibc should be less problematic.

					- Ted

Powered by blists - more mailing lists