[GIT PULL] Please pull RDMA subsystem changes

2018-11-29 Thread Jason Gunthorpe
Hi Linus, First rc pull request This is a bit later than usual for our first -rc but I'm not seeing anything worry-some in the RDMA tree right now. Quiet so far this -rc cycle, only a few internal driver related bugs and a small series fixing ODP bugs found by more advanced testing. The

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-10-26 Thread Linus Torvalds
On Thu, Oct 25, 2018 at 2:21 PM Jason Gunthorpe wrote: > > This pull request is following your recommendation from 4.19, the > for-linus tag has no merge, a for-linus-merged tag has my merge > resolution for your reference, and the diffstat below has been > replaced with the diffstat from the

[GIT PULL] Please pull RDMA subsystem changes

2018-10-25 Thread Jason Gunthorpe
Hi Linus, Here are the RDMA patches for 4.20. This time there is one simple git contextual conflict and a conflict that causes a compile failure. The latter is fixed with this patch: diff --git a/drivers/infiniband/hw/mlx5/flow.c b/drivers/infiniband/hw/mlx5/flow.c index

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-09-27 Thread Greg Kroah-Hartman
On Thu, Sep 27, 2018 at 12:24:32PM -0600, Jason Gunthorpe wrote: > Hi Greg, > > Second rc pull request > > This has a few fixes for smaller regressions introduced this cycle and > the usual various driver oops fixes. > > There is one long standing race bug in the comp_channel that Steve was >

[GIT PULL] Please pull RDMA subsystem changes

2018-09-27 Thread Jason Gunthorpe
Hi Greg, Second rc pull request This has a few fixes for smaller regressions introduced this cycle and the usual various driver oops fixes. There is one long standing race bug in the comp_channel that Steve was able to reproduce, track down and fix. I believe the HFI1 driver regression

[GIT PULL] Please pull RDMA subsystem changes

2018-09-10 Thread Jason Gunthorpe
Hi Linus, This fixes one major regression with NFS and mlx4 due to the max_sg rework in this merge window, tidies a few minor error_path regressions, and various small fixes. The HFI1 driver is broken this cycle due to a regression caused by a PCI change, it is looking like Bjorn will merge a

[GIT PULL] Please pull RDMA subsystem changes

2018-08-22 Thread Jason Gunthorpe
Hi Linus, Second merge window pull request This is the SMC cleanup promised, a randconfig regression fix, and kernel oops fix. I've learned we have at least one regression this merge window in IPoIB, which people are working on. The following changes since commit

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-08-17 Thread Linus Torvalds
On Fri, Aug 17, 2018 at 2:17 PM Jason Gunthorpe wrote: > > Would you like a patch to remove that CONFIG option? I've definitely considered it and would almost certainly just apply a patch that removed it. We haven't had this issue for a while (because people stopped using the deprecated thing),

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-08-17 Thread Jason Gunthorpe
On Fri, Aug 17, 2018 at 01:27:02PM -0700, Linus Torvalds wrote: > On Fri, Aug 17, 2018 at 1:15 PM Jason Gunthorpe wrote: > > > > We often have merge conflicts with RDMA, how do you prefer to get the > > PR? I'm actually not very clear on this part of the process. > > I generally prefer the

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-08-17 Thread Jason Gunthorpe
On Fri, Aug 17, 2018 at 01:50:05PM -0700, Linus Torvalds wrote: > On Fri, Aug 17, 2018 at 12:44 PM Linus Torvalds > wrote: > > > > Ok, everything but the max_sge thing was trivial. I just took yours. > > Oh, and doing the full test compile, I notice there are new warnings. > > That is *NOT* ok.

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-08-17 Thread Linus Torvalds
On Fri, Aug 17, 2018 at 12:44 PM Linus Torvalds wrote: > > Ok, everything but the max_sge thing was trivial. I just took yours. Oh, and doing the full test compile, I notice there are new warnings. That is *NOT* ok. The whole "x is deprecated" is not a useful warning. If you can't remove

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-08-17 Thread Linus Torvalds
On Fri, Aug 17, 2018 at 1:15 PM Jason Gunthorpe wrote: > > We often have merge conflicts with RDMA, how do you prefer to get the > PR? I'm actually not very clear on this part of the process. I generally prefer the non-merged version, but with comments about the conflicts. In fact, the really

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-08-17 Thread Jason Gunthorpe
On Fri, Aug 17, 2018 at 12:31:00PM -0700, Linus Torvalds wrote: > On Thu, Aug 16, 2018 at 2:57 PM Jason Gunthorpe wrote: > > > > This time there are many merge conflicts, all due to various tree-wide or > > RDMA > > subystem wide changes done by various people. The resolution is tricky, as > >

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-08-17 Thread Linus Torvalds
On Fri, Aug 17, 2018 at 12:31 PM Linus Torvalds wrote: > > Oh well. I'll look at what the conflicts were, but may end up just > taking your resolution. Ok, everything but the max_sge thing was trivial. I just took yours. Linus

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-08-17 Thread Linus Torvalds
On Thu, Aug 16, 2018 at 2:57 PM Jason Gunthorpe wrote: > > This time there are many merge conflicts, all due to various tree-wide or RDMA > subystem wide changes done by various people. The resolution is tricky, as git > does not highlight two areas that need revision. I was confused by this,

[GIT PULL] Please pull RDMA subsystem changes

2018-08-16 Thread Jason Gunthorpe
Hi Linus, Here are the RDMA patches for 4.19. This time there are many merge conflicts, all due to various tree-wide or RDMA subystem wide changes done by various people. The resolution is tricky, as git does not highlight two areas that need revision. An overview of the conflicts: - Mark

[GIT PULL] Please pull RDMA subsystem changes

2018-08-03 Thread Jason Gunthorpe
Hi Linus, Third pull request for -rc Things are still slow on the RC side, this one patch has been sitting in the git tree for a few weeks waiting for some friends. I expect this is the last RC pull for this cycle. The following changes since commit d63c46734c545ad0488761059004a65c46efdde3:

[GIT PULL] Please pull RDMA subsystem changes

2018-07-13 Thread Jason Gunthorpe
Hi Linus, Second pull request for -rc Things have been quite slow, only 6 RC patches have been sent to the list. Lots of stuff in for-next already though. The following changes since commit 6f0d349d922ba44e4348a17a78ea51b7135965b1: Merge

[GIT PULL] Please pull RDMA subsystem changes

2018-06-20 Thread Jason Gunthorpe
Hi Linus, First pull request for -rc Here are eight fairly small fixes collected over the last two weeks. Thanks, Jason The following changes since commit c1191a19fecad92b73c25770a7f47174280ca564: RDMA/mlx5: Update SPDX tags to show proper license (2018-06-05 14:04:20 -0600) are available

[GIT PULL] Please pull RDMA subsystem changes

2018-06-06 Thread Jason Gunthorpe
Hi Linus, Here are the RDMA patches for 4.18. No merge conflicts this time, and as of this writing netdev's pull request has not been merged so the merge diffstat shows a number of ethernet related files from the various shared pull requests in the two trees. There are a few more merge commits

[GIT PULL] Please pull RDMA subsystem changes

2018-06-01 Thread Jason Gunthorpe
Hi Linus, Third pull request for -rc Just 3 small last minute regressions that were found in the last week. The Broadcom fix is a bit big for rc7, but since it is fixing driver crash regressions that were merged via netdev into rc1, I am sending it. The following changes since commit

[GIT PULL] Please pull RDMA subsystem changes

2018-05-24 Thread Jason Gunthorpe
Hi Linus, Second pull request for -rc We haven't had quite the same rate of -rc patches this cycle, not much Syzkaller related stuff right now as the remaining bugs it has found require some kind of significant redesign to solve. The -next branch is also somewhat quieter than normal. This is

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-05-16 Thread Eugene Syromiatnikov
On Wed, May 16, 2018 at 11:49:33AM -0600, Jason Gunthorpe wrote: > On Wed, May 16, 2018 at 07:39:08PM +0200, Eugene Syromiatnikov wrote: > > On Fri, Apr 06, 2018 at 10:05:41AM -0600, Jason Gunthorpe wrote: > > > RDMA: Change all uapi headers to use __aligned_u64 instead of __u64 > > Looks

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-05-16 Thread Jason Gunthorpe
On Wed, May 16, 2018 at 07:39:08PM +0200, Eugene Syromiatnikov wrote: > On Fri, Apr 06, 2018 at 10:05:41AM -0600, Jason Gunthorpe wrote: > > RDMA: Change all uapi headers to use __aligned_u64 instead of __u64 > Looks like this change changed the size of struct hfi1_ctxt_info and the > value

Re: [GIT PULL] Please pull RDMA subsystem changes

2018-05-16 Thread Eugene Syromiatnikov
On Fri, Apr 06, 2018 at 10:05:41AM -0600, Jason Gunthorpe wrote: > RDMA: Change all uapi headers to use __aligned_u64 instead of __u64 Looks like this change changed the size of struct hfi1_ctxt_info and the value of HFI1_IOCTL_CTXT_INFO ioctl number as a result. > IB/uverbs: Extend

[GIT PULL] Please pull RDMA subsystem changes

2018-04-06 Thread Jason Gunthorpe
Hi Linus, Here are the RDMA patches for for 4.17. This cycle we have some interesting conflicts, a syzkaller related bug fix in rc clashed very badly with the Mellanox shared pull request. Doug made the resolution in the RDMA tree for-next tree and DaveM refered to it when he pulled in the same

[GIT PULL] Please pull RDMA subsystem changes

2018-03-29 Thread Jason Gunthorpe
Hi Linus, Fifth pull request for -rc. It has been fairly silent lately on our -rc front. Big queue of patches on the mailing list going to for-next though. The following changes since commit e8980d67d6017c8eee8f9c35f782c4bd68e004c9: RDMA/ucma: Ensure that CM_ID exists prior to access it

[GIT PULL] Please pull RDMA subsystem changes

2018-03-20 Thread Jason Gunthorpe
Hi Linus, Fourth pull request for -rc. Not much exciting here, almost entirely syzkaller fixes. This is going to be on ongoing theme for some time, I think. Both Google and Mellanox are now running syzkaller on different parts of the user API. The following changes since commit