public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Christoph Lameter <cl@linux.com>
Cc: <linux-rdma@vger.kernel.org>, Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH] Fix: Remove racy Subnet Manager sendonly join checks
Date: Wed, 10 Feb 2021 09:03:11 -0400	[thread overview]
Message-ID: <20210210130311.GU4247@nvidia.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2102100925200.172831@www.lameter.com>

On Wed, Feb 10, 2021 at 09:31:32AM +0000, Christoph Lameter wrote:
> On Tue, 9 Feb 2021, Jason Gunthorpe wrote:
> 
> > This one got spam filtered and didn't make it to the list:
> >
> > Received-SPF: SoftFail (hqemgatev14.nvidia.com: domain of
> >         cl@linux.com is inclined to not designate 3.19.106.255 as
> >         permitted sender) identity=mailfrom; client-ip=3.19.106.255;
> >         receiver=hqemgatev14.nvidia.com;
> >         envelope-from="cl@linux.com"; x-sender="cl@linux.com";
> >         x-conformance=spf_only; x-record-type="v=spf1"
> >
> > Also the extra From/Date/Subject ended up in the commit message
> 
> Yes the Linux Foundation guys are not willing to address this issue in any
> way. I may have to give up my linux.com email address.

It looks like you have to linux.com emails through their SMTP relay,
just like kernel.org ?

I have an exim config that auto-routes to an authenticated smarthost
based on the From email address if that would help you

> There is also another potentially racy check in there for OPA in regards
> to the support of path records?

Looks like

Jason

  reply	other threads:[~2021-02-10 13:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.22.394.2101281845160.13303@www.lameter.com>
2021-02-09 19:15 ` [PATCH] Fix: Remove racy Subnet Manager sendonly join checks Jason Gunthorpe
2021-02-10  9:31   ` Christoph Lameter
2021-02-10 13:03     ` Jason Gunthorpe [this message]
2021-02-10 18:51       ` Christoph Lameter
2021-02-12 22:16     ` Dennis Dalessandro
2021-02-12 22:13   ` Dennis Dalessandro
2021-01-25 11:28 Christoph Lameter
2021-01-25 11:44 ` Leon Romanovsky
2021-01-28 14:03 ` Jason Gunthorpe
2021-01-28 14:21   ` Leon Romanovsky
2021-01-28 14:34   ` Christoph Lameter
2021-01-28 14:44     ` Jason Gunthorpe
2021-01-28 14:58       ` Christoph Lameter
2021-01-28 18:11         ` Jason Gunthorpe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210210130311.GU4247@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=cl@linux.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox