Re: [Qemu-devel] [PATCH V2] docs: add PCIe devices placement guidelines

[Marcel Apfelbaum]

On 10/13/2016 04:12 PM, Eric Blake wrote:

On 10/13/2016 05:53 AM, Marcel Apfelbaum wrote:

On 10/13/2016 12:38 PM, Paolo Bonzini wrote:



On 13/10/2016 11:11, Marcel Apfelbaum wrote:

Agreed, I sent the patch with both Red Hat and Google SMTP and each time
was rejected by the server for the recipient domain nongnu.org by
eggs.gnu.org. [2001:4830:134:3::10].

The error that the other server returned was: 550 Invalid address in
message header


You have an "alex.williamson@redhat.comberrange"@redhat.com address that
looks seriously invalid. :)



Yes, I saw that - we have 2 lucky people not spammed (yet),
but sadly is uncorrelated with the issue in hand.


How so? It could very well be that the list engine is refusing to
deliver the mail because the mail has an invalid To: header (you left
out a comma, creating a single invalid address instead of two desired
addresses).  Your outgoing SMTP is delivering to as many valid addresses
as possible, but the list engine is unable to rewrite the message for
distribution to the list as soon as it encounters something invalid.



Hi Eric,

Indeed, I sent the patch again, this time to QEMU list only and it was sent OK.

I didn't think this was the problem because:
  (a) some addresses did receive the message
  (b) I thought I didn't mess up the mails on my first mail, but I was wrong.

Anyway, thank you for the explanation, you and Paolo are right.
Marcel

Re: [Qemu-devel] [PATCH V2] docs: add PCIe devices placement guidelines

[Eric Blake]

On 10/13/2016 05:53 AM, Marcel Apfelbaum wrote:
> On 10/13/2016 12:38 PM, Paolo Bonzini wrote:
>>
>>
>> On 13/10/2016 11:11, Marcel Apfelbaum wrote:
>>> Agreed, I sent the patch with both Red Hat and Google SMTP and each time
>>> was rejected by the server for the recipient domain nongnu.org by
>>> eggs.gnu.org. [2001:4830:134:3::10].
>>>
>>> The error that the other server returned was: 550 Invalid address in
>>> message header
>>
>> You have an "alex.williamson@redhat.comberrange"@redhat.com address that
>> looks seriously invalid. :)
>>
> 
> Yes, I saw that - we have 2 lucky people not spammed (yet),
> but sadly is uncorrelated with the issue in hand.

How so? It could very well be that the list engine is refusing to
deliver the mail because the mail has an invalid To: header (you left
out a comma, creating a single invalid address instead of two desired
addresses).  Your outgoing SMTP is delivering to as many valid addresses
as possible, but the list engine is unable to rewrite the message for
distribution to the list as soon as it encounters something invalid.

-- 
Eric Blake   eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org



signature.asc
Description: OpenPGP digital signature

Re: [Qemu-devel] [PATCH V2] docs: add PCIe devices placement guidelines

[Marcel Apfelbaum]

On 10/13/2016 12:38 PM, Paolo Bonzini wrote:



On 13/10/2016 11:11, Marcel Apfelbaum wrote:

Agreed, I sent the patch with both Red Hat and Google SMTP and each time
was rejected by the server for the recipient domain nongnu.org by
eggs.gnu.org. [2001:4830:134:3::10].

The error that the other server returned was: 550 Invalid address in
message header


You have an "alex.williamson@redhat.comberrange"@redhat.com address that
looks seriously invalid. :)



Yes, I saw that - we have 2 lucky people not spammed (yet),
but sadly is uncorrelated with the issue in hand.

Thanks,
Marcel


Paolo

Re: [Qemu-devel] [PATCH V2] docs: add PCIe devices placement guidelines

[Paolo Bonzini]

On 13/10/2016 11:11, Marcel Apfelbaum wrote:
> Agreed, I sent the patch with both Red Hat and Google SMTP and each time
> was rejected by the server for the recipient domain nongnu.org by
> eggs.gnu.org. [2001:4830:134:3::10].
> 
> The error that the other server returned was: 550 Invalid address in
> message header

You have an "alex.williamson@redhat.comberrange"@redhat.com address that
looks seriously invalid. :)

Paolo

Re: [Qemu-devel] [PATCH V2] docs: add PCIe devices placement guidelines

[Marcel Apfelbaum]

On 10/13/2016 11:53 AM, Laszlo Ersek wrote:

On 10/13/16 09:25, Marcel Apfelbaum wrote:

On 10/12/2016 06:28 PM, Laszlo Ersek wrote:

Marcel,

On 10/11/16 15:45, Marcel Apfelbaum wrote:

Proposes best practices on how to use PCI Express/PCI device
in PCI Express based machines and explain the reasoning behind them.

Signed-off-by: Marcel Apfelbaum 
---

Hi,

RFC->v2:
 - Addressed a lot of comments from the reviewers (many thanks to
all, especially to Laszlo)

Since the RFC mail-thread was relatively long and already
has passed a lot of time from the RFC, I post this version
even if is very possible that I left some of the comments out,
my apologies if so.

I will go over the comments again, in the meantime please
feel free to comment on this version, even if on something
you've already pointed out.

It may take a day or two until I'll be able to respond, but I
will do my best to address all comments.

Thanks,
Marcel


 docs/pcie.txt | 273
++
 1 file changed, 273 insertions(+)
 create mode 100644 docs/pcie.txt


Your patch doesn't seem to have reached qemu-devel. I got one copy from
you directly, and no copy reflected by the qemu-devel list server. I
also checked the mailing list archive:
- searched for the subject with google -- only the RFC version was found,
- checked mail-archive.com by message-id
- checked the primary archive for October
(http://lists.nongnu.org/archive/html/qemu-devel/2016-10/threads.html)
-- I found only messages in the RFC thread.

So, before I start reading this version and commenting on it, can you
please repost version 2, and verify that the list reflects it?



Hi,

That is very strange, I tried sending it again but I received the same
error:

Undelivered Mail Returned to Sender
...
: host eggs.gnu.org[208.118.235.92] said: 550
Invalid
address in message header (in reply to end of DATA command)

Reporting-MTA: dns; <>.redhat.com
X-Postfix-Queue-ID: <>
X-Postfix-Sender: rfc822; mar...@redhat.com
Arrival-Date: Thu, 13 Oct 2016 07:20:49 + (UTC)

Final-Recipient: rfc822; qemu-devel@nongnu.org
Original-Recipient: rfc822;qemu-devel@nongnu.org
Action: failed
Status: 5.0.0
Remote-MTA: dns; eggs.gnu.org
Diagnostic-Code: smtp; 550 Invalid address in message header


I'll try sending the mail with another mail server.




Hi Laszlo, thanks for the help


Something remains broken; and quite strangely at that. Now I've got two copies 
of the following message in my inbox:

[Qemu-devel] [PATCH V2 RESEND] docs: add PCIe devices placement guidelines

with the following message-id's:

  <1476343236-13192-1-git-send-email-mar...@redhat.com>
  <1476345339-5355-1-git-send-email-mar...@redhat.com>

and I have zero copies of this message in my qemu-devel folder.

Interestingly, the subject *does* have the [qemu-devel] prefix, in both copies.


This is because I have a script adding the [qemu-devel] prefix, maybe I should 
drop it.


So I thought, maybe these were reflected by the list server after all, and only their headers changed unexpectedly / inexpicably, so that my filter rules wouldn't apply any longer (and the messages 
wouldn't be moved to my qemu-devel folder).


However, the mailing list archive at 
 still 
does not list your message.

Here's the full list of headers from the first RESEND message:


Return-Path: mar...@redhat.com
Received: from zmta01.collab.prod.int.phx2.redhat.com (LHLO 
zmta01.collab.prod.int.phx2.redhat.com) (10.5.81.8) by 
zmail17.collab.prod.int.phx2.redhat.com with LMTP; Thu, 13 Oct 2016 03:20:49 
-0400 (EDT)
Received: from int-mx13.intmail.prod.int.phx2.redhat.com 
(int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by 
zmta01.collab.prod.int.phx2.redhat.com (Postfix) with ESMTP id 399BF186479; 
Thu, 13 Oct 2016 03:20:49 -0400 (EDT)
Received: from work.redhat.com (vpn-200-250.tlv.redhat.com [10.35.200.250]) by 
int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id 
u9D7KbZ4017253; Thu, 13 Oct 2016 03:20:40 -0400
From: Marcel Apfelbaum 
To: qemu-devel@nongnu.org
Cc: ler...@redhat.com, kra...@redhat.com, la...@redhat.com, peter.mayd...@linaro.org, 
drjo...@redhat.com, abolo...@redhat.com, 
"alex.williamson@redhat.comberrange"@redhat.com, m...@redhat.com, 
mar...@redhat.com
Subject: [Qemu-devel] [PATCH V2 RESEND] docs: add PCIe devices placement 
guidelines
Date: Thu, 13 Oct 2016 10:20:36 +0300
Message-Id: <1476343236-13192-1-git-send-email-mar...@redhat.com>
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26


Same from the second RESEND message:


Return-Path: marcel.apfelb...@gmail.com
Received: from zmta05.collab.prod.int.phx2.redhat.com (LHLO 
zmta05.collab.prod.int.phx2.redhat.com) (10.5.81.12) by 
zmail17.collab.prod.int.phx2.redhat.com with LMTP; Thu, 13 Oct 2016 03:55:48 
-0400 (EDT)
Received: from int-mx09.intmail.prod.int.phx2.redhat.com 
(int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by 
zmta05.col

Re: [Qemu-devel] [PATCH V2] docs: add PCIe devices placement guidelines

[Laszlo Ersek]

On 10/13/16 09:25, Marcel Apfelbaum wrote:
> On 10/12/2016 06:28 PM, Laszlo Ersek wrote:
>> Marcel,
>>
>> On 10/11/16 15:45, Marcel Apfelbaum wrote:
>>> Proposes best practices on how to use PCI Express/PCI device
>>> in PCI Express based machines and explain the reasoning behind them.
>>>
>>> Signed-off-by: Marcel Apfelbaum 
>>> ---
>>>
>>> Hi,
>>>
>>> RFC->v2:
>>>  - Addressed a lot of comments from the reviewers (many thanks to
>>> all, especially to Laszlo)
>>>
>>> Since the RFC mail-thread was relatively long and already
>>> has passed a lot of time from the RFC, I post this version
>>> even if is very possible that I left some of the comments out,
>>> my apologies if so.
>>>
>>> I will go over the comments again, in the meantime please
>>> feel free to comment on this version, even if on something
>>> you've already pointed out.
>>>
>>> It may take a day or two until I'll be able to respond, but I
>>> will do my best to address all comments.
>>>
>>> Thanks,
>>> Marcel
>>>
>>>
>>>  docs/pcie.txt | 273
>>> ++
>>>  1 file changed, 273 insertions(+)
>>>  create mode 100644 docs/pcie.txt
>>
>> Your patch doesn't seem to have reached qemu-devel. I got one copy from
>> you directly, and no copy reflected by the qemu-devel list server. I
>> also checked the mailing list archive:
>> - searched for the subject with google -- only the RFC version was found,
>> - checked mail-archive.com by message-id
>> - checked the primary archive for October
>> (http://lists.nongnu.org/archive/html/qemu-devel/2016-10/threads.html)
>> -- I found only messages in the RFC thread.
>>
>> So, before I start reading this version and commenting on it, can you
>> please repost version 2, and verify that the list reflects it?
>>
> 
> Hi,
> 
> That is very strange, I tried sending it again but I received the same
> error:
> 
> Undelivered Mail Returned to Sender
> ...
> : host eggs.gnu.org[208.118.235.92] said: 550
> Invalid
> address in message header (in reply to end of DATA command)
> 
> Reporting-MTA: dns; <>.redhat.com
> X-Postfix-Queue-ID: <>
> X-Postfix-Sender: rfc822; mar...@redhat.com
> Arrival-Date: Thu, 13 Oct 2016 07:20:49 + (UTC)
> 
> Final-Recipient: rfc822; qemu-devel@nongnu.org
> Original-Recipient: rfc822;qemu-devel@nongnu.org
> Action: failed
> Status: 5.0.0
> Remote-MTA: dns; eggs.gnu.org
> Diagnostic-Code: smtp; 550 Invalid address in message header
> 
> 
> I'll try sending the mail with another mail server.

Something remains broken; and quite strangely at that. Now I've got two copies 
of the following message in my inbox:

[Qemu-devel] [PATCH V2 RESEND] docs: add PCIe devices placement guidelines

with the following message-id's:

  <1476343236-13192-1-git-send-email-mar...@redhat.com>
  <1476345339-5355-1-git-send-email-mar...@redhat.com>

and I have zero copies of this message in my qemu-devel folder.

Interestingly, the subject *does* have the [qemu-devel] prefix, in both copies. 
So I thought, maybe these were reflected by the list server after all, and only 
their headers changed unexpectedly / inexpicably, so that my filter rules 
wouldn't apply any longer (and the messages wouldn't be moved to my qemu-devel 
folder).

However, the mailing list archive at 
 still 
does not list your message.

Here's the full list of headers from the first RESEND message:

> Return-Path: mar...@redhat.com
> Received: from zmta01.collab.prod.int.phx2.redhat.com (LHLO 
> zmta01.collab.prod.int.phx2.redhat.com) (10.5.81.8) by 
> zmail17.collab.prod.int.phx2.redhat.com with LMTP; Thu, 13 Oct 2016 03:20:49 
> -0400 (EDT)
> Received: from int-mx13.intmail.prod.int.phx2.redhat.com 
> (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by 
> zmta01.collab.prod.int.phx2.redhat.com (Postfix) with ESMTP id 399BF186479; 
> Thu, 13 Oct 2016 03:20:49 -0400 (EDT)
> Received: from work.redhat.com (vpn-200-250.tlv.redhat.com [10.35.200.250]) 
> by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id 
> u9D7KbZ4017253; Thu, 13 Oct 2016 03:20:40 -0400
> From: Marcel Apfelbaum 
> To: qemu-devel@nongnu.org
> Cc: ler...@redhat.com, kra...@redhat.com, la...@redhat.com, 
> peter.mayd...@linaro.org, drjo...@redhat.com, abolo...@redhat.com, 
> "alex.williamson@redhat.comberrange"@redhat.com, m...@redhat.com, 
> mar...@redhat.com
> Subject: [Qemu-devel] [PATCH V2 RESEND] docs: add PCIe devices placement 
> guidelines
> Date: Thu, 13 Oct 2016 10:20:36 +0300
> Message-Id: <1476343236-13192-1-git-send-email-mar...@redhat.com>
> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26

Same from the second RESEND message:

> Return-Path: marcel.apfelb...@gmail.com
> Received: from zmta05.collab.prod.int.phx2.redhat.com (LHLO 
> zmta05.collab.prod.int.phx2.redhat.com) (10.5.81.12) by 
> zmail17.collab.prod.int.phx2.redhat.com with LMTP; Thu, 13 Oct 2016 03:55:48 
> -0400 (EDT)
> Received: from int-mx09.intmail.pro

Re: [Qemu-devel] [PATCH V2] docs: add PCIe devices placement guidelines

[Marcel Apfelbaum]

On 10/12/2016 06:28 PM, Laszlo Ersek wrote:

Marcel,

On 10/11/16 15:45, Marcel Apfelbaum wrote:

Proposes best practices on how to use PCI Express/PCI device
in PCI Express based machines and explain the reasoning behind them.

Signed-off-by: Marcel Apfelbaum 
---

Hi,

RFC->v2:
 - Addressed a lot of comments from the reviewers (many thanks to all, 
especially to Laszlo)

Since the RFC mail-thread was relatively long and already
has passed a lot of time from the RFC, I post this version
even if is very possible that I left some of the comments out,
my apologies if so.

I will go over the comments again, in the meantime please
feel free to comment on this version, even if on something
you've already pointed out.

It may take a day or two until I'll be able to respond, but I
will do my best to address all comments.

Thanks,
Marcel


 docs/pcie.txt | 273 ++
 1 file changed, 273 insertions(+)
 create mode 100644 docs/pcie.txt


Your patch doesn't seem to have reached qemu-devel. I got one copy from
you directly, and no copy reflected by the qemu-devel list server. I
also checked the mailing list archive:
- searched for the subject with google -- only the RFC version was found,
- checked mail-archive.com by message-id
- checked the primary archive for October
(http://lists.nongnu.org/archive/html/qemu-devel/2016-10/threads.html)
-- I found only messages in the RFC thread.

So, before I start reading this version and commenting on it, can you
please repost version 2, and verify that the list reflects it?



Hi,

That is very strange, I tried sending it again but I received the same error:

Undelivered Mail Returned to Sender
...
: host eggs.gnu.org[208.118.235.92] said: 550 Invalid
address in message header (in reply to end of DATA command)

Reporting-MTA: dns; <>.redhat.com
X-Postfix-Queue-ID: <>
X-Postfix-Sender: rfc822; mar...@redhat.com
Arrival-Date: Thu, 13 Oct 2016 07:20:49 + (UTC)

Final-Recipient: rfc822; qemu-devel@nongnu.org
Original-Recipient: rfc822;qemu-devel@nongnu.org
Action: failed
Status: 5.0.0
Remote-MTA: dns; eggs.gnu.org
Diagnostic-Code: smtp; 550 Invalid address in message header


I'll try sending the mail with another mail server.

Thanks,
Marcel



Thanks!
Laszlo

Re: [Qemu-devel] [PATCH V2] docs: add PCIe devices placement guidelines

[Laszlo Ersek]

Marcel,

On 10/11/16 15:45, Marcel Apfelbaum wrote:
> Proposes best practices on how to use PCI Express/PCI device
> in PCI Express based machines and explain the reasoning behind them.
> 
> Signed-off-by: Marcel Apfelbaum 
> ---
> 
> Hi,
> 
> RFC->v2:
>  - Addressed a lot of comments from the reviewers (many thanks to all, 
> especially to Laszlo)
> 
> Since the RFC mail-thread was relatively long and already
> has passed a lot of time from the RFC, I post this version
> even if is very possible that I left some of the comments out,
> my apologies if so.
> 
> I will go over the comments again, in the meantime please
> feel free to comment on this version, even if on something
> you've already pointed out.
> 
> It may take a day or two until I'll be able to respond, but I
> will do my best to address all comments.
> 
> Thanks,
> Marcel
> 
> 
>  docs/pcie.txt | 273 
> ++
>  1 file changed, 273 insertions(+)
>  create mode 100644 docs/pcie.txt

Your patch doesn't seem to have reached qemu-devel. I got one copy from
you directly, and no copy reflected by the qemu-devel list server. I
also checked the mailing list archive:
- searched for the subject with google -- only the RFC version was found,
- checked mail-archive.com by message-id
- checked the primary archive for October
(http://lists.nongnu.org/archive/html/qemu-devel/2016-10/threads.html)
-- I found only messages in the RFC thread.

So, before I start reading this version and commenting on it, can you
please repost version 2, and verify that the list reflects it?

Thanks!
Laszlo