linux-kernel - Re: Crypto Fixes for 5.0

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: <CAHk-=whHKxA4kA8eHd+h6Zmq269usaxCoGiC+b-_bcfYCQOTbg@mail.gmail.com>
Date:   Thu, 31 Jan 2019 23:37:58 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Herbert Xu <herbert@...dor.apana.org.au>,
        Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Subject: Re: Crypto Fixes for 5.0

On Thu, Jan 31, 2019 at 9:42 PM Herbert Xu <herbert@...dor.apana.org.au> wrote:
>
> This push fixes a bug in cavium/nitrox where the callback is invoked
> prior to the DMA unmap.

This is not so much a comment about the pull itself (which I did half
an hour ago), as about the fact that it looks like the pr-tracker
robot doesn't seem to trigger for your pull requests, even if they are
cc'd to lkml.

Maybe you don't care, but while I stopped doing the manual "ack"
emails for pulls, I've continued to try to notice when some pull of
mine doesn't get the attention of the pr-tracker. I've probably missed
several cases of them...

The reason seems to be that the pr-tracker bot only tracks pull
requests from emails with one of

  - ^[GIT
  - ^[PULL
  - ^[PLEASE PULL

in the subject line (case insensitive, afaik), and so your plain
"Crypto Fixes for 5.0" doesn't trigger it.

(My list of what triggers the pr-tracker bot may be old, I suspect
Konstantin has ended up tweaking the bot more since the early
descriptions he gave, so take the above more as a rough guide than any
set-in-stone rules)

Anyway, if you do care, maybe whatever script or workflow you use for
pull requests could just add that "[GIT PULL]" to the subject line,
and you'd get that automatic ack email when I've pulled and pushed
out?

               Linus