On Wed, 2018-01-10 at 16:54 -0500, Doug Ledford wrote: > On Tue, 2018-01-09 at 10:17 -0700, Jason Gunthorpe wrote: > > On Tue, Jan 09, 2018 at 07:04:16PM +0200, Max Gurtovoy wrote: > > > hi Guys, > > > did we forget taking this fix to mainline/stable or we found another > > > solution ? > > > > I thought it was going to NAB's tree.. My mistake, I put it back into > > patchworks and it will get into for-next > > In fairness, the email thread said exactly that. But, it never got > picked up by NAB. And being that it's in our tree and calling an rdma- > core function, it can easily enough go through our tree, so I applied it > to for-rc. Thanks Sagi + Ram, and Doug for picking this up. Per the earlier discussion, it looks like this needs a stable CC, right..? As Sagi mentioned, it's not clear if this is a regression vs. generic RDMA READ/WRITE API logic, or a day one issue. So how about adding a 4.7+ stable tag, to match commit a060b5629..? -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
