linux-kernel - Re: [PATCH v3 00/23] Use asm-generic for mmu

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]

Date:   Sat, 10 Oct 2020 10:25:11 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Nicholas Piggin <npiggin@...il.com>,
        linux-arch <linux-arch@...r.kernel.org>,
        Linux-MM <linux-mm@...ck.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 00/23] Use asm-generic for mmu_context no-op functions

On Sat, Oct 10, 2020 at 4:02 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> On Fri, 9 Oct 2020 16:01:22 +0200 Arnd Bergmann <arnd@...db.de> wrote:
>
> > Are there other changes that depend on this? If not, I would
> > just wait until -rc1 and then either push the branch correctly or
> > rebase the patches on that first, to avoid pushing something that
> > did not see the necessary testing.
>
> If it is useful enough (or important enough), then put in in your
> linux-next included branch, but don't ask Linus to merge it until the
> second week of the merge window ... no worse than some other stuff I
> see :-(

By itself, it's a nice cleanup, but it doesn't provide any immediate
benefit over the previous state, while potentially introducing a
regression in one of the less tested architectures.

The question to me is really whether Nick has any pending work
that he would like to submit after this branch is merged into
mainline.

    Arnd