linux-kernel - Re: [GIT PULL] UBI/UBIFS updates for 4.9-rc1

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] [day] [month] [year] [list]

Message-ID: <CA+55aFx72t6kqrZ0m-tbXzR4UHaq2zti3ZcTeo9PJQzRGa8Syg@mail.gmail.com>
Date:   Tue, 11 Oct 2016 10:57:34 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Richard Weinberger <richard@....at>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>
Subject: Re: [GIT PULL] UBI/UBIFS updates for 4.9-rc1

On Tue, Oct 11, 2016 at 8:33 AM, Richard Weinberger <richard@....at> wrote:
>
> This pull request contains:
> * Fixes for both UBI and UBIFS
> * overlayfs support (O_TMPFILE, RENAME_WHITEOUT/EXCHANGE)
> * Code refactoring for the upcoming MLC support

In the meantime, on a VFS level, we got rid of the "rename2" naming,
and now the plain regular rename is the extended version.

There's a few other filesystems using "rename2" as a name for the now
no longer true historical reasons, but I noticed it particularly in
this pull request because I fixed up a trivial conflict around that
area.

You might consider renaming it, or just put the "rename2" logic into
the regular rename function, but whatever. It doesn't really _matter_,
it's just an odd naming artifact.

(I've not pushed out my merge yet, it's still going through the build
tests etc, but I thought I'd mention this detail).

               Linus