linux-kernel - Re: [PATCH] vfs: return EOPNOTSUPP when ioctl

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20161219102402.GA24893@infradead.org>
Date:   Mon, 19 Dec 2016 02:24:02 -0800
From:   Christoph Hellwig <hch@...radead.org>
To:     Sami Kerola <kerolasa@....fi>
Cc:     Al Viro <viro@...iv.linux.org.uk>, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] vfs: return EOPNOTSUPP when ioctl_fsthaw() is not
 supported

On Sun, Dec 18, 2016 at 06:57:27PM +0000, Sami Kerola wrote:
> An attempt to freeze a filesystem that does not support such operation is
> reported as EOPNOTSUPP to user.  Running unfreeze to the same filesystem
> returns EINVAL.  Later is a little misleading, users can mix that message
> with return value from unfreezing when filesystem is not frozen.

This is going to break gfs2 with it's odd ->that_super method.