Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Bob Pearson <rpearsonhpe@gmail.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: leon@kernel.org, zyjzyj2000@gmail.com,
	linux-rdma@vger.kernel.org, Bob Pearson <rpearson@hpe.com>
Subject: Re: [PATCH for-next] rdma_rxe: address an issue with hardened user copy
Date: Thu, 27 Aug 2020 11:43:41 -0500	[thread overview]
Message-ID: <8f23b006-f117-0780-81d7-fb272ae5b69a@gmail.com> (raw)
In-Reply-To: <20200827135841.GA4033418@nvidia.com>

On 8/27/20 8:58 AM, Jason Gunthorpe wrote:
> On Tue, Aug 25, 2020 at 11:58:37AM -0500, Bob Pearson wrote:
>> Change rxe pools to use kzalloc instead of kmem_cache to allocate
>> memory for rxe objects.
>>
>> Signed-off-by: Bob Pearson <rpearson@hpe.com>
>>  drivers/infiniband/sw/rxe/rxe.c      |  8 ----
>>  drivers/infiniband/sw/rxe/rxe_pool.c | 60 +---------------------------
>>  drivers/infiniband/sw/rxe/rxe_pool.h |  7 ----
>>  3 files changed, 2 insertions(+), 73 deletions(-)
> 
> It doesn't apply:
> 
> Applying: rdma_rxe: address an issue with hardened user copy
> error: sha1 information is lacking or useless (drivers/infiniband/sw/rxe/rxe.c).
> error: could not build fake ancestor
> Patch failed at 0001 rdma_rxe: address an issue with hardened user copy
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
> 
> Pleae generate patches against a v5.x tag or rdma for-next
> 
> Jason
> 
I fixed it and sent it again.

Applies to today's for-next branch. It is independent from the SPDX patch but the line numbers will move a bunch. Hope that doesn't break it.

      reply	other threads:[~2020-08-27 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 16:58 [PATCH for-next] rdma_rxe: address an issue with hardened user copy Bob Pearson
2020-08-27  1:21 ` Zhu Yanjun
2020-08-27  1:30   ` Bob Pearson
2020-08-27  7:02 ` Leon Romanovsky
2020-08-27 13:58 ` Jason Gunthorpe
2020-08-27 16:43   ` Bob Pearson [this message]

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=8f23b006-f117-0780-81d7-fb272ae5b69a@gmail.com \
    --to=rpearsonhpe@gmail.com \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearson@hpe.com \
    --cc=zyjzyj2000@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox