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...
thanks,
greg k-h
> On Sep 7, 2019, at 9:47 PM, Greg Kroah-Hartman <[email protected]> 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.
On Sun, Sep 08, 2019 at 04:04:39AM +0000, Nadav Amit wrote:
> > On Sep 7, 2019, at 9:47 PM, Greg Kroah-Hartman <[email protected]> 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.
Well the email servers might not reject it now, but gmail itself sure
does as you are lying about what your domain is :(
> 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.
Please do, this is not a viable workflow.
thanks,
greg k-h