linux-kernel - Re: [RFC GIT PULL, v2] RCU changes for v4.12

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+55aFzHz3qGqKmdqih0AwGx0ggxe4gr2VbHbSfC-9W2yFn1cQ@mail.gmail.com>
Date:   Wed, 10 May 2017 13:17:54 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Paul McKenney <paulmck@...ux.vnet.ibm.com>
Cc:     Ingo Molnar <mingo@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC GIT PULL, v2] RCU changes for v4.12

On Wed, May 10, 2017 at 12:54 PM, Paul E. McKenney
<paulmck@...ux.vnet.ibm.com> wrote:
>
> I am testing a merge with current linus/master, and I looked through
> the commits in -next selected by:
>
>         gitk v4.11.. --no-merges --all-match --grep=drm --grep=selftest
>
> I didn't find anything obvious.  If the tests complete successfully,
> I will try running the DRM selftest.

The drivers/gpu/drm/i915/selftests/mock_gem_device.c had a new use of
SLAB_DESTROY_BY_RCU, which obviously conflicted with the rename to
SLAB_TYPESAFE_BY_RCU.

It doesn't show up as a merge-time code conflict, only as a build-time
failure. It's why I do allmodconfig builds after every pull. That
doesn't catch everything (I only do it for x86-64, for example), but
it catches a lot.

And no, it's not a problem. These things happen, and it's literally my
job to make sure my merges work out.

I don't actually expect submaintainers to figure things like that out,
although this *did* show up in linux-next, and it's a bit
disappointing how that information got lost somewhere on the way.

It kind of implies that the prep work that linux-next does doesn't get
fully used.

Normally I wouldn't even have mentioned it, if it wasn't for the fact
that I got a 300kB data dump in my mailbox, and that huge amount of
data wasn't actually even very relevant.

                Linus