All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH] patches: add patch for compat/lib-rhashtable.c
Date: Wed, 24 May 2017 08:46:15 +0200	[thread overview]
Message-ID: <1495608375.2665.1.camel@sipsolutions.net> (raw)
In-Reply-To: <1495226777-11429-1-git-send-email-arend.vanspriel@broadcom.com> (sfid-20170519_224637_347450_368DFBBA)

On Fri, 2017-05-19 at 21:46 +0100, Arend van Spriel wrote:
> The file compat/lib-rhashtable.c is a copy from the backported kernel
> source lib/rhashtable.c. This patch reverts a recent change to that
> file, ie. commit 43ca5bc4f72e ("lib/rhashtable.c: simplify a strange
> allocation pattern"). It introduced the function
> gfpflags_allow_blocking()
> introduced in 4.4 kernel and kvmalloc() introduced in 4.12-rc1.
> Looking
> at those functions backporting them is complicated so instead add
> this
> patch that reverts the change for kernel prior to 4.12.

Thanks Arend!

Why do you think backporting it is complicated though?

kvmalloc() is just kvmalloc_node(), and if we disregard the
__vmalloc_node_flags_caller() but - since kvmalloc() doesn't care about
node anyway - just use __vmalloc() there, it should be easy? The
pgprot_t argument is just PAGE_KERNEL, and the other stuff doesn't
really matter.

gfpflags_allow_blocking() is a pretty simple inline, and even if we'd
implement it to always return false we'd get the old rhashtable
behaviour.

johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

  reply	other threads:[~2017-05-24  6:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 20:46 [PATCH] patches: add patch for compat/lib-rhashtable.c Arend van Spriel
2017-05-24  6:46 ` Johannes Berg [this message]
2017-05-24 19:36   ` Arend van Spriel
2017-05-30  7:19     ` Johannes Berg

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=1495608375.2665.1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend.vanspriel@broadcom.com \
    --cc=backports@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 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.