linux-kernel - Re: [PATCH v2] PCI: Add information about describing PCI in ACPI

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: <CAADWXX_ipJ+pVmV5s2oLCKBrC5qUDASOZf=tpBfJWELExam+hQ@mail.gmail.com>
Date:   Tue, 29 Nov 2016 15:39:11 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Bjorn Helgaas <bhelgaas@...gle.com>
Cc:     Linux PCI <linux-pci@...r.kernel.org>,
        Ard Biesheuvel <ard.biesheuvel@...aro.org>,
        Gabriele Paoloni <gabriele.paoloni@...wei.com>,
        "Rafael J. Wysocki" <rafael@...nel.org>, Duc Dang <dhdang@....com>,
        linaro-acpi@...ts.linaro.org, lkml <linux-kernel@...r.kernel.org>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Lv Zheng <lv.zheng@...el.com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2] PCI: Add information about describing PCI in ACPI

Bjorn, this email was marked as spam, because:

  It has a from address in google.com but has failed google.com's
required tests for authentication

in particular, it looks like you used a non-google smtp server
(kernel.org) to send the email, so there is no DKIM hash (or perhaps
google just uses some other non-standard marker for "this actually
came from google"). So gmail marks it as spam because dmarc fails:

       dmarc=fail (p=REJECT dis=NONE) header.from=google.com

Just to let you know. If you use your google.com email, you do need to
go through the google smtp server.

This may or may not be new - I didn't go and look at old messages of
yours, but it is possible that google.com enabled dmarc/dkim recently.

             Linus

On Tue, Nov 29, 2016 at 1:39 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
> Here's another stab at this writeup.  I'd appreciate any comments!