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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFzzKg17=RYTUomF9Fsy0mM5Acqkak0EZJPivZ5+oZErwA@mail.gmail.com>
Date:   Thu, 14 Sep 2017 13:00:24 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Miklos Szeredi <miklos@...redi.hu>
Cc:     Al Viro <viro@...iv.linux.org.uk>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        "linux-unionfs@...r.kernel.org" <linux-unionfs@...r.kernel.org>
Subject: Re: [GIT PULL] overlayfs update for 4.14

On Wed, Sep 13, 2017 at 11:46 PM, Miklos Szeredi <miklos@...redi.hu> wrote:
>
> d_real() is currently is *the* overlayfs-op:

I know. And it's ugly as #%^! hell.

We don't want to  make it uglier.

And honestly, if you think that "it's only for overlayfs, so I can do
anything I damn well want to this p[iece of shit" is valid, then I
want to re-educate you. That is *not* how the VFS layer works.

If you can't bother to try to make it act as a proper VFS thing, then
I don't want to see patches from you to the VFS code.

I'm perfectly happy just reverting those changes again. Because I'm
not making the VFS layer bend over backwards due to some overlayfs
braindamage.

                 Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ