All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: hch@lst.de, Bart.VanAssche@sandisk.com,
	torvalds@linux-foundation.org, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, stable@vger.kernel.org,
	ubraun@linux.vnet.ibm.com
Subject: Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
Date: Tue, 16 May 2017 13:12:37 -0400	[thread overview]
Message-ID: <1494954757.3259.123.camel@redhat.com> (raw)
In-Reply-To: <20170516.124129.292555623308256441.davem@davemloft.net>

On Tue, 2017-05-16 at 12:41 -0400, David Miller wrote:
> From: Doug Ledford <dledford@redhat.com>
> Date: Tue, 16 May 2017 12:36:01 -0400
> 
> > On Tue, 2017-05-16 at 18:30 +0200, Christoph Hellwig wrote:
> >> On Tue, May 16, 2017 at 12:29:23PM -0400, David Miller wrote:
> >> > 
> >> > I can't push back on people with silly coding style and small
> >> > semantic
> >> > issues forever.  And I think I made a serious effort to keep the
> >> > patches getting posted over and over again to make sure they got
> >> > more
> >> > exposure.
> >> 
> >> You can tell them to go to linux-rdma.  I'm sending people to the
> >> right
> >> mailing list all the time.
> > 
> > Indeed.  Every single time a patch comes into linux-rdma that
> touches
> > things in net/ or include/net, unless it is exceedingly minor, I
> check
> > the To:/Cc: lines on the email and if netdev@ isn't included, or in
> the
> > case of complex/tricky items, you aren't directly Cc:ed, then I
> > specifically tell them to include netdev@ and/or you.  I've even
> had
> > things like a 12 patch series that buried three netdev@ appropriate
> > patches at different points in the series and told the submitter to
> > move all of the netdev@ related patches to the front and submit
> them to
> > netdev@ so they can be reviewed as a group before I would move on
> to
> > the others.  It's just what you do.  I've always considered that
> part
> > of my job.
> 
> To be quite honest it wasn't exceedingly clear, even to me, that this
> had such implications or was directly a RDMA thing.  From my
> perspective while reviewing I saw a patch series adding it's own
> protocol stack living inside of it's own directory under net/

OK.  Fair enough.  That implies to me that you probably dove right into
the patches and skimmed the cover letter (http://marc.info/?l=linux-s39
0&m=148397751211964&w=2), because when I read the cover letter, it
seems pretty clear to me that this is very much RDMA related.  In any
case, there are already two other code bases that live under net/ but
also involve RDMA heavily: nfs and rds.  This is a third now.  So, for
future reference, just like the RDMA related nfs/rds patches already
get Cc:ed to linux-rdma@, these probably should be too.

> And, if even one RDMA/infiniband person said to me "you really
> shouldn't apply this" then I would have dropped it on the spot.

I'm glad to hear that.  I wish we had managed to get together on this
sooner.

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
   
Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

  reply	other threads:[~2017-05-16 17:12 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10  7:26 [PATCH] net/smc: mark as BROKEN due to remote memory exposure Christoph Hellwig
2017-05-11 14:57 ` Bart Van Assche
     [not found]   ` <1494514662.2489.1.camel-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-05-14  5:58     ` Christoph Hellwig
2017-05-14  5:58       ` Christoph Hellwig
2017-05-14  5:58       ` Christoph Hellwig
2017-05-14 15:51       ` David Miller
2017-05-14 19:08         ` Bart Van Assche
2017-05-15  0:44           ` David Miller
     [not found]             ` <20170514.204404.1844909849561204299.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-05-15  1:58               ` Parav Pandit
2017-05-15  1:58                 ` Parav Pandit
2017-05-16 15:57               ` Doug Ledford
2017-05-16 15:57                 ` Doug Ledford
2017-05-16 16:29                 ` David Miller
2017-05-16 16:29                   ` David Miller
     [not found]                   ` <20170516.122923.869994491617365845.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-05-16 16:30                     ` Christoph Hellwig
2017-05-16 16:30                       ` Christoph Hellwig
     [not found]                       ` <20170516163041.GA5132-jcswGhMUV9g@public.gmane.org>
2017-05-16 16:33                         ` David Miller
2017-05-16 16:33                           ` David Miller
2017-05-16 16:35                           ` Christoph Hellwig
2017-05-16 16:36                         ` Doug Ledford
2017-05-16 16:36                           ` Doug Ledford
2017-05-16 16:41                           ` David Miller
2017-05-16 16:41                             ` David Miller
2017-05-16 17:12                             ` Doug Ledford [this message]
2017-05-16 16:42                   ` Doug Ledford
2017-05-16 16:49                     ` David Miller
2017-05-16 16:49                       ` David Miller
     [not found]                       ` <20170516.124945.386235742645153398.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-05-16 17:20                         ` Doug Ledford
2017-05-16 17:20                           ` Doug Ledford
     [not found]                           ` <1494955244.3259.130.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-05-16 17:36                             ` David Miller
2017-05-16 17:36                               ` David Miller
     [not found]                               ` <20170516.133644.850927380166261577.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-05-16 18:03                                 ` Doug Ledford
2017-05-16 18:03                                   ` Doug Ledford
2017-05-16 18:52                                   ` David Miller
2017-05-16 18:52                                     ` David Miller
     [not found]                                     ` <20170516.145249.871010194359061722.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-05-16 19:28                                       ` Doug Ledford
2017-05-16 19:28                                         ` Doug Ledford
2017-05-17 20:37                                         ` Doug Ledford
2017-05-17 22:37                                           ` Parav Pandit
     [not found]                                             ` <VI1PR0502MB3008604A216B388A440A8B53D1E70-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-05-18  0:07                                               ` Doug Ledford
2017-05-18  0:07                                                 ` Doug Ledford
2017-05-18  4:22                                                 ` Leon Romanovsky
     [not found]         ` <20170514.115116.499149210596634881.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-05-15  6:41           ` Sagi Grimberg
2017-05-15  6:41             ` Sagi Grimberg
2017-05-15  7:18           ` Leon Romanovsky
2017-05-15  7:18             ` Leon Romanovsky

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=1494954757.3259.123.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=Bart.VanAssche@sandisk.com \
    --cc=davem@davemloft.net \
    --cc=hch@lst.de \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=ubraun@linux.vnet.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.