linux-kernel - Re: [PATCH] VMCI: Release resource if the work is already queued

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: <00CA348F-5ACC-4A17-A5F6-9B36C92A95E7@vmware.com>
Date:   Sun, 8 Sep 2019 04:04:39 +0000
From:   Nadav Amit <namit@...are.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     Arnd Bergmann <arnd@...db.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Francois Rigault <rigault.francois@...il.com>,
        Jorgen Hansen <jhansen@...are.com>,
        Adit Ranadive <aditr@...are.com>,
        Alexios Zavras <alexios.zavras@...el.com>,
        Vishnu Dasa <vdasa@...are.com>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH] VMCI: Release resource if the work is already queued

> On Sep 7, 2019, at 9:47 PM, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> 
> On Tue, Aug 20, 2019 at 01:26:38PM -0700, Nadav Amit wrote:
>> Francois reported that VMware balloon gets stuck after a balloon reset,
>> when the VMCI doorbell is removed. A similar error can occur when the
>> balloon driver is removed with the following splat:
> 
> <snip>
> 
> Note, google thinks your email is spam as you are not sending this from
> a valid vmware.com email server.  Please fix this up if you want to make
> sure your patches actually make it through...

I used gmail servers since I get complaints (mainly from Linus) that our
email servers use DMARC, and this causes mailing list postings to be
rejected.

I will check again if our open source people got to a solution, or I
would just send it using my gmail identity, while keeping the vmware
authorship.